Jump to content


Photo

Walmart WPDN R7T40WWHF1 firmware


  • Please log in to reply
235 replies to this topic

#101 dragon7532

dragon7532

    Member

  • Jr. Member
  • PipPip
  • 23 posts

Posted 06 January 2013 - 08:25 PM

dragon7532, once you do a just "adb shell" command, you don't need to add it to the other commands, because you're still in the shell.

So you can do either something like:
C:\adb>adb shell
~ # flash_image recovery /data/misc/recovery

OR you can do
C:\adb>adb shell flash_image recovery /data/misc/recovery

but don't mix the two forms together.



ok i did that and now i get this


C:\adb>adb remount
remount failed: Success

C:\adb>adb push recovery.img /data/misc
2903 KB/s (1932751 bytes in 0.650s)

C:\adb>adb push kernel /data/misc
2920 KB/s (2210376 bytes in 0.739s)

C:\adb>adb shell flash_image recovery /data/misc/recovery
error opening /data/misc/recoveryfailed with error: -1

#102 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 06 January 2013 - 09:53 PM

this is as far as i can get and then i get this error any help would be greatly appreciatd
C:\adb>adb devices
List of devices attached
PD_Novel recovery


C:\adb>adb push recovery.img /data/misc
1795 KB/s (1932751 bytes in 1.051s)

C:\adb>adb push kernel /data/misc
1719 KB/s (2210376 bytes in 1.255s)

C:\adb>adb shell
~ # adb sehll flash_image recovery /data/misc/reco
adb sehll flash_image recovery /data/misc/recovery
/sbin/sh: adb: not found
~ #


After the "adb shell", just do the "flash_image recovery /data/misc/recovery.img". No "adb shell" before it.
But include the .img extension.

Robert

Edited by RRA, 06 January 2013 - 10:50 PM.


#103 mrsburnout

mrsburnout

    "Linkmeister"

  • Administrators
  • 7,254 posts
  • LocationUSA

Posted 06 January 2013 - 11:18 PM


this is as far as i can get and then i get this error any help would be greatly appreciatd
C:\adb>adb devices
List of devices attached
PD_Novel recovery


C:\adb>adb push recovery.img /data/misc
1795 KB/s (1932751 bytes in 1.051s)

C:\adb>adb push kernel /data/misc
1719 KB/s (2210376 bytes in 1.255s)

C:\adb>adb shell
~ # adb sehll flash_image recovery /data/misc/reco
adb sehll flash_image recovery /data/misc/recovery
/sbin/sh: adb: not found
~ #

After the "adb shell", just do the "flash_image recovery /data/misc/recovery.img". No "adb shell" before it.
But include the .img extension.

Robert


Dragon7532, noted some typos as well ...Spell check your commands.
YMMV = Your Mileage May Vary - Not even OEM FW is guaranteed "safe" to flash.

Hey! Newbies (n00bs) - Click the blue links ;) - Forum Rules

"Dream as if you'll live forever. Live as if you'll die today." ~James Dean
"Slatedroid: Where all the advice is free, even advice you don't want." ~Mark Adams #113449
"Women are Angels. When someone breaks our wings - we simply continue to fly - on a broomstick. We are flexible like that."

Posted Image ~cheers

#104 dragon7532

dragon7532

    Member

  • Jr. Member
  • PipPip
  • 23 posts

Posted 07 January 2013 - 06:51 AM

Dragon7532, noted some typos as well ...Spell check your commands.





C:\adb>adb devices
List of devices attached
PD_Novel recovery


C:\adb>adb remount
remount failed: Success

C:\adb>adb push recovery.img /data/misc
2833 KB/s (1932751 bytes in 0.666s)

C:\adb>adb push kernel /data/misc~ # flash_image recovery/data/misc/recovery/img
flash_image recovery/data/misc/recovery/img
usage: flash_image partition file.img
~ # exit
exit

C:\adb>adb reboot recovery
error: protocol fault (no status)
2817 KB/s (2210376 bytes in 0.766s

#105 mrsburnout

mrsburnout

    "Linkmeister"

  • Administrators
  • 7,254 posts
  • LocationUSA

Posted 07 January 2013 - 10:05 AM

C:\adb>adb devices
List of devices attached
PD_Novel recovery


C:\adb>adb remount
remount failed: Success

C:\adb>adb push recovery.img /data/misc
2833 KB/s (1932751 bytes in 0.666s)

C:\adb>adb push kernel /data/misc~ # flash_image recovery/data/misc/recovery/img
flash_image recovery/data/misc/recovery/img
usage: flash_image partition file.img
~ # exit
exit

C:\adb>adb reboot recovery
error: protocol fault (no status)
2817 KB/s (2210376 bytes in 0.766s


dragon7532 -- you are like talking to a brick wall, I swear. I am going try to explain in a way you understand here.

People, please do not alter your devices before learning about them.

I inserted a code box in your quote above --- LOOK at what edca2002 and RRA told you again ---

Are you understanding that you are entering two different forms of command languages? Do you know you are confusing your system this way?

Spelling is important... typos are not acceptable

Now Look at the code box above again... See what is wrong... You did not enter the shell command after pushing the kernel and need to eliminate part of your syntax. so enter ONLY this (in the code box below) after pushing the kernel:

adb shell flash_image recovery /data/misc/recovery.img

Good luck.
YMMV = Your Mileage May Vary - Not even OEM FW is guaranteed "safe" to flash.

Hey! Newbies (n00bs) - Click the blue links ;) - Forum Rules

"Dream as if you'll live forever. Live as if you'll die today." ~James Dean
"Slatedroid: Where all the advice is free, even advice you don't want." ~Mark Adams #113449
"Women are Angels. When someone breaks our wings - we simply continue to fly - on a broomstick. We are flexible like that."

Posted Image ~cheers

#106 dragon7532

dragon7532

    Member

  • Jr. Member
  • PipPip
  • 23 posts

Posted 08 January 2013 - 05:48 PM

How do you install cwm on a brick novel?

#107 dragon7532

dragon7532

    Member

  • Jr. Member
  • PipPip
  • 23 posts

Posted 08 January 2013 - 07:06 PM

+1 and then some. This unbricked my unit. The first trick was getting adb to work properly. It took trying it on 3 different computers (both Windows and Linux) to get it to work. There's a good section on getting adb to work, including the necessary driver at:
ADB Setup
I had a black screen, the LED came on when I applied power, but went off when I tried to power up. I installed the CWM program, and voila, I had a display to work with. Booting just kept me stuck at the blue flash screen, but the above instructions were gold and now I'm running fine.

Thanks, Giant Wookie!



2.911923] onenand_probe: Use four bases (128K, 16M, 16M, 256K)
2.918365] OneNAND Manufacturer: Samsung (0xec)
2.918390] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
2.922643] OneNAND version = 0x0121
2.926177] Chip support all block unlock
2.995794] Scanning device for bad blocks
3.335905] Bad eraseblock 722 at 0x05a40000
3.959438] Creating 8 MTD partitions on "onenand":
3.959485] 0x000000000000-0x000000200000 : "bootloader"
3.967495] 0x000000200000-0x000000a00000 : "kernel"
3.971937] 0x000000a00000-0x000000b00000 : "id"
3.976473] 0x000000b00000-0x000001500000 : "recovery"
3.981593] 0x000001500000-0x000001800000 : "ramdisk"
3.986661] 0x000001800000-0x00000e000000 : "system"
3.992383] 0x00000e000000-0x000014400000 : "cache"
3.993450] mtd: partition "cache" extends beyond the end of devi
size truncated to 0x2000000
4.006565] 0x000010000000-0x000010000000 : "userdata"

ok i have done everything in this post just not sure how to get cwm on

#108 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 09 January 2013 - 12:38 AM

2.911923] onenand_probe: Use four bases (128K, 16M, 16M, 256K)
2.918365] OneNAND Manufacturer: Samsung (0xec)
2.918390] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
2.922643] OneNAND version = 0x0121
2.926177] Chip support all block unlock
2.995794] Scanning device for bad blocks
3.335905] Bad eraseblock 722 at 0x05a40000
3.959438] Creating 8 MTD partitions on "onenand":
3.959485] 0x000000000000-0x000000200000 : "bootloader"
3.967495] 0x000000200000-0x000000a00000 : "kernel"
3.971937] 0x000000a00000-0x000000b00000 : "id"
3.976473] 0x000000b00000-0x000001500000 : "recovery"
3.981593] 0x000001500000-0x000001800000 : "ramdisk"
3.986661] 0x000001800000-0x00000e000000 : "system"
3.992383] 0x00000e000000-0x000014400000 : "cache"
3.993450] mtd: partition "cache" extends beyond the end of devi
size truncated to 0x2000000
4.006565] 0x000010000000-0x000010000000 : "userdata"

ok i have done everything in this post just not sure how to get cwm on


I'm not convinced you need the CWM for this to work. Did you follow Giant Wookie's instructions from his Jan 03 post? You probably only need steps 3-5. Make sure you downloaded his PandigitalOEM.tgz file and got all four of the .img files pushed and flashed as per his instructions. I assume you can unarchive a .tgz file? If not, and you're on a Windows box, download 7-Zip from www.7-zip.com and use it to unarchive the .img files. Then power the unit off then back on and it will likely work again. It did for me. If not, go back to mac1_131's post and download his file MAC1_CWM_RECOVERY_C1SL20_20120224_B_PD_INX7E_ENG_6410POP.zip
Place it on an external SD card, or the internal one if you don't have an external card. Make sure you have no other .zip or .dat files on either card. Hold down the volume+ key and press and hold the power on button. Hold both for about 15 seconds (on mine, the screen first comes on, then about 13 seconds later it blinks). After that, it should start flashing the CWM file. Wait till it's complete. The next time you do this, it should boot into the CWM screen. From there you can use the Vol key to go through the menu, and tap the screen to select an option. Again, I'm not sure you need this, as for me all it gave me is the ability to use adb when my bricked unit didn't before that.

Robert

Edited by RRA, 09 January 2013 - 12:41 AM.


#109 hbk4041

hbk4041

    Newbie

  • Jr. Member
  • Pip
  • 6 posts
  • LocationErie, PA

Posted 09 January 2013 - 01:24 PM

Ok maybe a typing problem with the commands try

^ = space

adb^remount
adb^push^recovery.img^/data/misc
adb^push^kernel^/data/misc
adb^shell

at the new prompt type

flash_image^recovery^/data/misc/recovery.img
flash_image^kernel^/data/misc/kernel
reboot

If you don't put spaces in the command line in the right places it will not work correctly that's what I think may be happening just replace the ^ with a space when you type the commands


I currently have a bricked white Pandigital Novel (WPDN) that I need some help getting it unbricked.

I want to first thank you for all of your help because before I found slatedroid.com I had a large paperweight. It started with a black screen and with this site it has been partially revived.

Background:
Bricked the WPDN trying to update with openandroid from the Pandigital website
Flashed CWM recovery
Stuck with the blue start up screen

Errors out using adb to shell flash recovery and kernel
Message "directory not found"

Tried both on /system/misc and /data/misc - Yes, checked my spelling

Please any guidance to what I am doing wrong will be helpful to get my WPDN back to usable. I want to flash KG's Gapps with SDK of 7 so that I can install Netflix and Dropbox.

#110 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 09 January 2013 - 06:48 PM

I currently have a bricked white Pandigital Novel (WPDN) that I need some help getting it unbricked.

I want to first thank you for all of your help because before I found slatedroid.com I had a large paperweight. It started with a black screen and with this site it has been partially revived.

Background:
Bricked the WPDN trying to update with openandroid from the Pandigital website
Flashed CWM recovery
Stuck with the blue start up screen

Errors out using adb to shell flash recovery and kernel
Message "directory not found"

Tried both on /system/misc and /data/misc - Yes, checked my spelling

Please any guidance to what I am doing wrong will be helpful to get my WPDN back to usable. I want to flash KG's Gapps with SDK of 7 so that I can install Netflix and Dropbox.


Did you read my previous post to dragon? What worked for me was Giant Wookie's instructions. Seems to me if you were able to push the .img files, you should be able to flash them. Use the four .img files from his post. Thus:

adb push bootloader.img /data/misc
adb push kernel.img /data/misc
adb push id.img /data/misc
adb push ramdisk.img /data/misc
adb shell
flash_image bootloader /data/misc/bootloader.img
flash_image kernel /data/misc/kernel.img
flash_image id /data/misc/id.img
flash_image ramdisk /data/misc/ramdisk.img
reboot

If you can't do the above, let me know the error messages, and also do a:
adb shell
cat /proc/mtd

and show the output.

Edited by RRA, 09 January 2013 - 07:01 PM.


#111 hbk4041

hbk4041

    Newbie

  • Jr. Member
  • Pip
  • 6 posts
  • LocationErie, PA

Posted 10 January 2013 - 09:07 PM

Did you read my previous post to dragon? What worked for me was Giant Wookie's instructions. Seems to me if you were able to push the .img files, you should be able to flash them. Use the four .img files from his post. Thus:

adb push bootloader.img /data/misc
adb push kernel.img /data/misc
adb push id.img /data/misc
adb push ramdisk.img /data/misc
adb shell
flash_image bootloader /data/misc/bootloader.img
flash_image kernel /data/misc/kernel.img
flash_image id /data/misc/id.img
flash_image ramdisk /data/misc/ramdisk.img
reboot

If you can't do the above, let me know the error messages, and also do a:
adb shell
cat /proc/mtd

and show the output.



Ok, tired the method above and kept getting the following error:

Error - Shell flash_image (all files)
error opening /data/misc/bootloader.imgfailed with error: -1
error opening /system/misc/bootloader.imgfailed with error: -1
error opening /PD_Novel/recovery.imgfailed with error: -1

Tired following Giant Wookie Instrucitons - same errors occured with the shell flash.

This is my output from "adb shell cat /proc/mtd"

dev: size erasesize name
mtd0: 00200000 00020000 "bootloader"
mtd1: 00800000 00020000 "kernel"
mtd2: 00100000 00020000 "id"
mtd3: 00a00000 00020000 "recovery"
mtd4: 00300000 00020000 "ramdisk"
mtd5: 0c800000 00020000 "system"
mtd6: 02000000 00020000 "cache"
mtd7: 00000000 00000000 "userdata"

"adb shell cat /proc/partitions"

major minor #blocks name

179 0 3872256 mmcblk0
179 1 1936128 mmcblk0p1
179 2 1936063 mmcblk0p2
179 8 992000 mmcblk1
179 9 991935 mmcblk1p1
31 0 2048 mtdblock0
31 1 8192 mtdblock1
31 2 1024 mtdblock2
31 3 10240 mtdblock3
31 4 3072 mtdblock4
31 5 204800 mtdblock5
31 6 32768 mtdblock6
mtdblock7 - None

I hope this hleps

#112 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 10 January 2013 - 09:15 PM

Ok, tired the method above and kept getting the following error:

Error - Shell flash_image (all files)
error opening /data/misc/bootloader.imgfailed with error: -1
error opening /system/misc/bootloader.imgfailed with error: -1
error opening /PD_Novel/recovery.imgfailed with error: -1

Tired following Giant Wookie Instrucitons - same errors occured with the shell flash.

This is my output from "adb shell cat /proc/mtd"

dev: size erasesize name
mtd0: 00200000 00020000 "bootloader"
mtd1: 00800000 00020000 "kernel"
mtd2: 00100000 00020000 "id"
mtd3: 00a00000 00020000 "recovery"
mtd4: 00300000 00020000 "ramdisk"
mtd5: 0c800000 00020000 "system"
mtd6: 02000000 00020000 "cache"
mtd7: 00000000 00000000 "userdata"

"adb shell cat /proc/partitions"

major minor #blocks name

179 0 3872256 mmcblk0
179 1 1936128 mmcblk0p1
179 2 1936063 mmcblk0p2
179 8 992000 mmcblk1
179 9 991935 mmcblk1p1
31 0 2048 mtdblock0
31 1 8192 mtdblock1
31 2 1024 mtdblock2
31 3 10240 mtdblock3
31 4 3072 mtdblock4
31 5 204800 mtdblock5
31 6 32768 mtdblock6
mtdblock7 - None

I hope this hleps


Strange... Looks like there's no /data partition, so try replacing each of the 8 references to "/data/misc" with simply "/system" and see if there's any more luck there.

#113 hbk4041

hbk4041

    Newbie

  • Jr. Member
  • Pip
  • 6 posts
  • LocationErie, PA

Posted 13 January 2013 - 08:09 AM

Strange... Looks like there's no /data partition, so try replacing each of the 8 references to "/data/misc" with simply "/system" and see if there's any more luck there.


Thank agian for you help. The /system notation for adb worked great got my WPDN up and somewhat working. Now it keeps will not connect to a wifi signal (keeps turning on and off) and the clock settings are frozen (can't change to the time and date). I am now looking to see how to resolve this issue.

Thanks for all your help.

#114 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 13 January 2013 - 07:18 PM

Thank agian for you help. The /system notation for adb worked great got my WPDN up and somewhat working. Now it keeps will not connect to a wifi signal (keeps turning on and off) and the clock settings are frozen (can't change to the time and date). I am now looking to see how to resolve this issue.

Thanks for all your help.


Nice to hear you're alive again. A quick question - is this a model R7T40WWHF1? Check the sticker on the back of the unit and make sure. It's commonly found at Walmart. There's lots of different models of the Novel with different firmware. I have the white Walmart version; apparently there is a black version too. Don't know if there's any difference between the two on the insides. Also, it couldn't hurt to delete the files you put in /system. From adb shell, you can do "rm /system/bootloader.img", etc for each of the 4 files you put there.

Edited by RRA, 13 January 2013 - 07:24 PM.


#115 edeboss

edeboss

    Newbie

  • Jr. Member
  • Pip
  • 1 posts

Posted 13 January 2013 - 10:11 PM

I have a white pandigital that I bricked C1SL20_20120224
adb is working but I cannot get pass the readonly error below

C:\abd>adb remount
remount succeeded

C:\abd>adb push recovery.img /data/misc
failed to copy 'recovery.img' to '/data/misc': Read-only file system

C:\abd>adb push kernel /data/misc
failed to copy 'kernel' to '/data/misc': Read-only file system

#116 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 14 January 2013 - 11:01 AM

I have a white pandigital that I bricked C1SL20_20120224
adb is working but I cannot get pass the readonly error below

C:\abd>adb remount
remount succeeded

C:\abd>adb push recovery.img /data/misc
failed to copy 'recovery.img' to '/data/misc': Read-only file system

C:\abd>adb push kernel /data/misc
failed to copy 'kernel' to '/data/misc': Read-only file system


I'm assuming you have the R7T40WWHF1 version (see the sticker on the back of the reader). If so, go back to mac1_131's earlier post and download his file MAC1_CWM_RECOVERY_C1SL20_20120224_B_PD_INX7E_ENG_6410POP.zip
Place it on an external SD card, or the internal one if you don't have an external card. Make sure you have no other .zip or .dat files on either card. Hold down the volume+ key and press and hold the power on button. Hold both for about 15 seconds (on mine, the screen first comes on, then about 13 seconds later it blinks). After that, it should start flashing the CWM file. Wait till it's complete. The next time you do this, it should boot into the CWM screen. Once there, you should be able to connect with adb and have a writable filesystem. Then you can follow Giant Wookie's instructions (as I paraphrased just above) to unbrick it.

#117 Spokehedz

Spokehedz

    Newbie

  • Jr. Member
  • Pip
  • 9 posts

Posted 18 January 2013 - 01:10 PM

I'm assuming you have the R7T40WWHF1 version (see the sticker on the back of the reader). If so, go back to mac1_131's earlier post and download his file MAC1_CWM_RECOVERY_C1SL20_20120224_B_PD_INX7E_ENG_6410POP.zip
Place it on an external SD card, or the internal one if you don't have an external card. Make sure you have no other .zip or .dat files on either card. Hold down the volume+ key and press and hold the power on button. Hold both for about 15 seconds (on mine, the screen first comes on, then about 13 seconds later it blinks). After that, it should start flashing the CWM file. Wait till it's complete. The next time you do this, it should boot into the CWM screen. Once there, you should be able to connect with adb and have a writable filesystem. Then you can follow Giant Wookie's instructions (as I paraphrased just above) to unbrick it.


I can't find this file anywhere. I have several dozens of these units, and I can test all day long on these things. Why are these things so terrible...

#118 mrsburnout

mrsburnout

    "Linkmeister"

  • Administrators
  • 7,254 posts
  • LocationUSA

Posted 18 January 2013 - 01:30 PM

I can't find this file anywhere. I have several dozens of these units, and I can test all day long on these things. Why are these things so terrible...

Then you missed it... Try (re)reading the first page of this thread... reply #9

Good luck. :drinks:
YMMV = Your Mileage May Vary - Not even OEM FW is guaranteed "safe" to flash.

Hey! Newbies (n00bs) - Click the blue links ;) - Forum Rules

"Dream as if you'll live forever. Live as if you'll die today." ~James Dean
"Slatedroid: Where all the advice is free, even advice you don't want." ~Mark Adams #113449
"Women are Angels. When someone breaks our wings - we simply continue to fly - on a broomstick. We are flexible like that."

Posted Image ~cheers

#119 Spokehedz

Spokehedz

    Newbie

  • Jr. Member
  • Pip
  • 9 posts

Posted 18 January 2013 - 01:42 PM

Then you missed it... Try (re)reading the first page of this thread... reply #9

Good luck. :drinks:


great. now it says "failed to copy 'recovery.img' to '/data/misc': Read-only file system"

Awesome. Now I can't get into the shell either.

#120 RRA

RRA

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 56 posts

Posted 18 January 2013 - 04:46 PM

great. now it says "failed to copy 'recovery.img' to '/data/misc': Read-only file system"

Awesome. Now I can't get into the shell either.


Did you successfully boot the CWM? It should have a menu on it above a picture of Andy. When booted, it should give you R/W access.
Also note that depending on what you had on there earlier, the directory /data may not exist, so use /system instead.