Kindle PW after I. Initialize Partition Table (fdisk) and format FAT

artec · 09-17-2017, 05:17 PM

Hi, I got a defective Kindle PW and want to try to fix it. Following the board's advice, I bought the TTL-232RG-VREG1V8-WE. Now I can connect through serial port to Kindle. Using Putty, I managed to run both BIST and Recovery Menu on this device. Unfortunately the problem is that after connecting Kindle to USB, the device is only available for a while in the Device Manager (Win10 Pro). I think the next step should be flash diag and main partition, but I do not know how to do it without access to the usb storage.
Please give me any tips.

Code:

U-Boot 2009.08-lab126 (Jan 08 2013 - 21:47:48)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 66666666Hz
ipg per clock : 66666666Hz
uart clock    : 24000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Celeste WFO (256 MB)
Boot Reason: [POR]
Boot Device: MMC
Board Id: 00A1607130341TZB
S/N: B02416XXXXXXXX
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffc000
POST done in 17 ms
Hit any key to stop autoboot:  0
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4748160 Bytes =  4.5 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
MX50 LPDDR2 MfgID: 0x3 [Elpida]
2.6.31-rt11-lab126 #1 Tue Jun 23 04:29:16 PDT 2015 armv7l
Press [ENTER] for recovery menu...       0 //dev/mmcblk0p4:
CHS=4/16/43712 size=1432354816 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    2797552
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
BOOTING DEFAULT.
  argc == 12
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p1"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  argv[10]: "user_debug=0x1"
  argv[11]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)
kinit: root_dev = dev(179,1)
kinit: failed to identify filesystem /dev/root, trying all
kinit: trying to mount /dev/root on /root with type ext3
kinit: trying to mount /dev/root on /root with type ext2
kinit: trying to mount /dev/root on /root with type cramfs
kinit: trying to mount /dev/root on /root with type squashfs
kinit: trying to mount /dev/root on /root with type vfat
kinit: trying to mount /dev/root on /root with type msdos
kinit: Unable to mount root fs on device dev(179,1)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

knc1 · 09-17-2017, 07:25 PM

The words: "Broke" and/or "Defective" do not give us enough information to give you a reasonable answer.

The answer might be simple, single step - it might be far more complex.

Please describe what it is about the Kindle and its behavior that you mean by the word: "Defective" .
(Although what you have posted makes me think we will have to explain to you how to undo the damage you have caused, it would still be helpful to know the original problem you where trying to solve.)

artec · 09-18-2017, 11:51 AM

I bought a Kindle on a web auction as a damaged one. The device is frozen, and the image of the Tree is displayed on the screen. The progress bar does not appear. After a hard reset the screen is extinguished and again the screen with the tree is displayed and nothing is going on. I tried to charge it over 20h but that did not help. After connecting to the computer through the serial port, I got to the recovery menu and accidentally launched the "I. Initialize Partition Table (fdisk) and FAT format" after this operation the screen state behaves the same way as the previous, tree is displayed.

knc1 · 09-18-2017, 02:45 PM

Try this:

boot to diags (directions included in the serial port jb thread)
use the diags menu to export the USB storage
USB cable, Kindle to PC
put a file in the topmost level of visible USB storage, named:
DO_FACTORY_RESTORE
All caps, no extension, no content
safely eject Kindle
remove USB cord
re-boot Kindle.

That should fix it (and would have fixed it for the person who sold it to you

).

artec · 09-18-2017, 03:47 PM

I can not get to DIAGS Menu. The rest of the procedure works, using the Recovery Menu can connect the usb storage, after placing the file "DO_FACTORY_RESTORE" in the USB storage and safe restart does not change anything.
The key is to get to the DIAGS Menu

but how. It looks like there was nothing on the partitions.

I paste the code from the operation:

Code:

U-Boot 2009.08-lab126 (Jan 08 2013 - 21:47:48)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 66666666Hz
ipg per clock : 66666666Hz
uart clock    : 24000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Celeste WFO (256 MB)
Boot Reason: [POR]
Boot Device: MMC
Board Id: 00A1607130341TZB
S/N: B02416XXXXXXXX
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffc000
POST done in 18 ms
Hit any key to stop autoboot:  0
uboot > bootm 0xE41000
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608576 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
2.6.31-rt11-lab126 #1 Tue Sep 25 22:13:12 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36956 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (51152 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!
INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2797568 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/43712 size=1432354816 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    2797552
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
  argc == 11
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p2"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  argv[10]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p2) = dev(179,2)
kinit: root_dev = dev(179,2)
kinit: failed to identify filesystem /dev/root, trying all
kinit: trying to mount /dev/root on /root with type ext3
kinit: trying to mount /dev/root on /root with type ext2
kinit: trying to mount /dev/root on /root with type cramfs
kinit: trying to mount /dev/root on /root with type squashfs
kinit: trying to mount /dev/root on /root with type vfat
kinit: trying to mount /dev/root on /root with type msdos
kinit: Unable to mount root fs on device dev(179,2)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

coplate · 09-18-2017, 05:20 PM

Quote:

Originally Posted by artec

I can not get to DIAGS Menu. The rest of the procedure works, using the Recovery Menu can connect the usb storage, after placing the file "DO_FACTORY_RESTORE" in the USB storage and safe restart does not change anything.
The key is to get to the DIAGS Menu

but how. It looks like there was nothing on the partitions.

I paste the code from the operation:

Code:

U-Boot 2009.08-lab126 (Jan 08 2013 - 21:47:48)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 66666666Hz
ipg per clock : 66666666Hz
uart clock    : 24000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Celeste WFO (256 MB)
Boot Reason: [POR]
Boot Device: MMC
Board Id: 00A1607130341TZB
S/N: B02416XXXXXXXX
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffc000
POST done in 18 ms
Hit any key to stop autoboot:  0
uboot > bootm 0xE41000
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608576 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
2.6.31-rt11-lab126 #1 Tue Sep 25 22:13:12 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36956 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (51152 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!
INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2797568 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/43712 size=1432354816 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    2797552
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
  argc == 11
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p2"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  argv[10]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p2) = dev(179,2)
kinit: root_dev = dev(179,2)
kinit: failed to identify filesystem /dev/root, trying all
kinit: trying to mount /dev/root on /root with type ext3
kinit: trying to mount /dev/root on /root with type ext2
kinit: trying to mount /dev/root on /root with type cramfs
kinit: trying to mount /dev/root on /root with type squashfs
kinit: trying to mount /dev/root on /root with type vfat
kinit: trying to mount /dev/root on /root with type msdos
kinit: Unable to mount root fs on device dev(179,2)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

I don't recommending trying this yet, but it sounds to me that when you initialized FAT that it erased some of the required files?

But one option that might work ( probably cannot make things worse if you already have serial in place, is to try to put the factory update file on the USB export.

I'm basing this on the line that seems to be looking for thse files here:

Quote:

INFO:No update*.bin found; no update needed.

knc1 · 09-18-2017, 07:01 PM

Yup, that should work (install an Amazon update package ).

= = = =

The "Initialize Partitions and Format Fat" are two operations, on two different parts of storage.
the eMMC has a partition table that divides it into four primary partitions.
the fourth partition also has a partition table at its start (yes, that is a DOS allowed but rarely used feature).

So maybe it would be better if the menu label read: "Initial Partition TABLES (2) and Format Fat (1)"

Why didn't that command say anything about formatting the other three partitions in the first partition table?
Because they get checked an formatted as required during normal start-up..

= = = =

If coplate's suggestion above does not work -
Then assume you have to do the same recovery that you would be doing if you had pressed "Erase All".

NOTE:
The Amazon update packages do not include the diags system (which you need).
I have posted a script that will do a backup of a touchscreen device, that script will extract the diags system and the matching diags kernel (among other things).

All you have to do is find someone with a jailbroken PW-1 (B024) to run the script and post the diags system file and matching diags kernel file somewhere on the 'net.

artec · 09-20-2017, 09:09 AM

Thank you, it worked.

I started the Recovery Menu.
Exported FAT
Uploaded update_xxxxxx.bin
Safely remove USB and disconnect the cable.
I restarted the device and everything was updated.
The device works.

I start to like it

knc1 · 09-20-2017, 09:56 AM

Quote:

Originally Posted by artec

Thank you, it worked.

I started the Recovery Menu.
Exported FAT
Uploaded update_xxxxxx.bin
Safely remove USB and disconnect the cable.
I restarted the device and everything was updated.
The device works.

I start to like it

See if you can boot into the diags system.
You may still need to re-install that.
Let us know, we can give you directions on how to re-install that also.

09-17-2017, 07:25 PM	#2
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	The words: "Broke" and/or "Defective" do not give us enough information to give you a reasonable answer. The answer might be simple, single step - it might be far more complex. Please describe what it is about the Kindle and its behavior that you mean by the word: "Defective" . (Although what you have posted makes me think we will have to explain to you how to undo the damage you have caused, it would still be helpful to know the original problem you where trying to solve.) Last edited by knc1; 09-17-2017 at 07:28 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
M92 Partition Table	Aradan	Onyx Boox	5	12-06-2013 07:47 AM
nook glowlight partition table	srgarfi	Barnes & Noble NOOK	0	08-03-2012 04:51 PM
kindle touch partition within a partition?	geekmaster	Kindle Developer's Corner	8	03-12-2012 08:53 AM
PRS-505 Format - FAT or FAT32?	wen	Sony Reader	6	07-08-2011 09:36 AM

09-18-2017, 11:51 AM	#3
artec Junior Member Posts: 4 Karma: 10 Join Date: Jul 2017 Device: PW2, K3	I bought a Kindle on a web auction as a damaged one. The device is frozen, and the image of the Tree is displayed on the screen. The progress bar does not appear. After a hard reset the screen is extinguished and again the screen with the tree is displayed and nothing is going on. I tried to charge it over 20h but that did not help. After connecting to the computer through the serial port, I got to the recovery menu and accidentally launched the "I. Initialize Partition Table (fdisk) and FAT format" after this operation the screen state behaves the same way as the previous, tree is displayed.

09-18-2017, 02:45 PM	#4
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Try this: boot to diags (directions included in the serial port jb thread) use the diags menu to export the USB storage USB cable, Kindle to PC put a file in the topmost level of visible USB storage, named: DO_FACTORY_RESTORE All caps, no extension, no content safely eject Kindle remove USB cord re-boot Kindle. That should fix it (and would have fixed it for the person who sold it to you ).

09-18-2017, 07:01 PM	#7
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Yup, that should work (install an Amazon update package ). = = = = The "Initialize Partitions and Format Fat" are two operations, on two different parts of storage. the eMMC has a partition table that divides it into four primary partitions. the fourth partition also has a partition table at its start (yes, that is a DOS allowed but rarely used feature). So maybe it would be better if the menu label read: "Initial Partition TABLES (2) and Format Fat (1)" Why didn't that command say anything about formatting the other three partitions in the first partition table? Because they get checked an formatted as required during normal start-up.. = = = = If coplate's suggestion above does not work - Then assume you have to do the same recovery that you would be doing if you had pressed "Erase All". NOTE: The Amazon update packages do not include the diags system (which you need). I have posted a script that will do a backup of a touchscreen device, that script will extract the diags system and the matching diags kernel (among other things). All you have to do is find someone with a jailbroken PW-1 (B024) to run the script and post the diags system file and matching diags kernel file somewhere on the 'net.

09-20-2017, 09:09 AM	#8
artec Junior Member Posts: 4 Karma: 10 Join Date: Jul 2017 Device: PW2, K3	Thank you, it worked. I started the Recovery Menu. Exported FAT Uploaded update_xxxxxx.bin Safely remove USB and disconnect the cable. I restarted the device and everything was updated. The device works. I start to like it

Advert

Advert