Unbricking some kindles, advice welcome...

techanic · 01-20-2018, 11:19 AM

Hi

Bought a box of "defective" Kindles out of a whim... now I have 5 PW3s. I opened 4 of them, so I have the possibility to connect the serial console. (Working on a Debian system, with working fastboot connection, got that hurdle...)

No1 had a dead battery... replacing it brought it back to life but I suspect the charging circuit might be broken, have to test that.

No2 is starting up but then just showing the screensaver (no touch or anything). On the serial console I see U-boot starting up

Code:

...
Welcome to Kindle
...
info asr_setup:Not in asr mode::reason=flag file not present. shutting down asr_setup::
info hardware:no_wan::WiFi only device. No WAN found
info board_data_file :/opt/ar6k/target/AR6003/hw2.1.1/bin/AR6003_wfo_calfile.bin::
[   29.377434] ath6kl: ath6kl_fetch_board_file: Board calibration file fetched: /opt/ar6k/target/AR6003/hw2.1.1/bin/AR6003_wfo_calfile.bin
[   29.449979] ath6kl: MAC from kernel xx:xx:xx:xx:xx:C2
[   29.859981] ath6kl: host only supports scatter of :1 entries, need: 16
[  400.888536] pmic_soda_connects_notify_otg_out:423

and that's it... if I connect it to a Win PC I see a drive detected, but I cannot access it.

Any Ideas on what might be wrong and how to fix it? I've read about DO_FACTORY_RESET file but I cannot access the drive...

No3 shows the same behavior as No2.

No4 displays a page of a book but does nothing more, no reaction to reset via power button (>20sec).

No5 has a whole in the screen and a bent motherboard... so no help there, but the batter was still alive.

Then I've a WP63GW with a strange looking image on the screen, serial console shows

Code:

[    1.741247] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    1.748534] Regulator Fault Occurred! Retrying powerup...

Guess this on is fatal as well...

And I've a SY69JL with a kindle Power On picture and a D01100 with a drained battery on the screen, which I did not yet open up.

Would be thankful for some tips/hints, I'm fairly new to this kindle stuff

coplate · 01-20-2018, 12:02 PM

On number 2 and 3, the "..." you have listed could have useful information it it.

but if it says "Welcome to Kindle", then the whole bootup process has occured. On your serial console, press enter and it should ask you for a login name, just for you to check what mode you are in.

Login is disabled on the regular partition, so check the resot fo your logs for "press <something> to enter diags", and consider doing that, knc1 has the most recent post on what options to select here: "https://www.mobileread.com/forums/showthread.php?t=289497

I know there are certain triggers on when the paperwhite will 'export USB' and you can do it manually in diags mode form the command line, but I dont know why it wouldnt be showing up as a drive if you got to the "welcome to kindle" log.

Are you doing this on Linux? I know that some versions of linux without certain updates will not automatically mount the new Oasis, I wonder if that culd be possible for the PW# you have there as well. Can you list the USB VendorID and ProductID? If you are on windows those are usefult too - kindle changes product ID to DEAD sometimes. You can view that with a tool called 'USBDeview'

But you should also read through the main serial jailbreaking for dummies to learn about diags mode if you haven't already.

As for #5, I have a need for the power button off of the screen ( see attachment if what I need isn't clear ); the clicky part fell off after manhandling it in an out of the case too many times.

I wonder if you would be willing to part with it for cheap :-)

Click image for larger version

Name: power.jpg
Views: 330
Size: 107.4 KB
ID: 161703

techanic · 01-20-2018, 12:35 PM

thanks coplate, I'll go through those threads!

Here is the complete log of the boot up:
serial_boot_dump.txt

I'm on a Debian 9 Linux Box since I did not get fastboot working on Win10.

Regarding USB IDs:

Code:

[253120.153619] usb 1-1.6: new high-speed USB device number 49 using ehci-pci
[253120.267657] usb 1-1.6: New USB device found, idVendor=1949, idProduct=0004
[253120.267660] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[253120.267662] usb 1-1.6: Product: Amazon Kindle
[253120.267663] usb 1-1.6: Manufacturer: Amazon
[253120.267679] usb 1-1.6: SerialNumber: G090G1**********
[253120.270740] usb-storage 1-1.6:1.0: USB Mass Storage device detected
[253120.270953] scsi host9: usb-storage 1-1.6:1.0
[253121.294844] scsi 9:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
[253121.296953] sd 9:0:0:0: Attached scsi generic sg3 type 0
[253121.303795] sd 9:0:0:0: [sdd] Attached SCSI removable disk

But I can not mount it (or better don't know how to)...

Got to go now.
PM me regarding the button!

knc1 · 01-20-2018, 01:03 PM

Code:

[253121.296953] sd 9:0:0:0: Attached scsi generic sg3 type 0
[253121.303795] sd 9:0:0:0: [sdd] Attached SCSI removable disk

The messages should not stop at that point.
So unless you simply failed to quote the following messages, then ->
That is the end of "Device discovery".
It should be immediately followed by "Partition and File discovery" as in:

Code:

[274497.795501] usb-storage 2-5.5:1.0: USB Mass Storage device detected
[274497.795629] scsi host8: usb-storage 2-5.5:1.0
[274498.809816] scsi 8:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
[274498.810082] sd 8:0:0:0: Attached scsi generic sg5 type 0
[274498.815811] sd 8:0:0:0: [sdf] 6385664 512-byte logical blocks: (3.27 GB/3.04 GiB)
[274498.920054] sd 8:0:0:0: [sdf] Write Protect is off
[274498.920057] sd 8:0:0:0: [sdf] Mode Sense: 0f 00 00 00
[274499.030044] sd 8:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[274499.250917]  sdf: sdf1 <<--
[274499.489912] sd 8:0:0:0: [sdf] Attached SCSI removable disk

And sometimes dmesg includes a hint about what is wrong:

Code:

[274256.057721] sd 8:0:0:0: [sdf] Attached SCSI removable disk
[274256.494704] FAT-fs (sdf1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

coplate · 01-21-2018, 03:05 AM

Quote:

Originally Posted by techanic

thanks coplate, I'll go through those threads!

Here is the complete log of the boot up:
Attachment 161704

I'm on a Debian 9 Linux Box since I did not get fastboot working on Win10.

Regarding USB IDs:

Code:

[253120.153619] usb 1-1.6: new high-speed USB device number 49 using ehci-pci
[253120.267657] usb 1-1.6: New USB device found, idVendor=1949, idProduct=0004
[253120.267660] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[253120.267662] usb 1-1.6: Product: Amazon Kindle
[253120.267663] usb 1-1.6: Manufacturer: Amazon
[253120.267679] usb 1-1.6: SerialNumber: G090G1**********
[253120.270740] usb-storage 1-1.6:1.0: USB Mass Storage device detected
[253120.270953] scsi host9: usb-storage 1-1.6:1.0
[253121.294844] scsi 9:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
[253121.296953] sd 9:0:0:0: Attached scsi generic sg3 type 0
[253121.303795] sd 9:0:0:0: [sdd] Attached SCSI removable disk

But I can not mount it (or better don't know how to)...

Got to go now.
PM me regarding the button!

In the log you attached it says this:

Code:


Press [ENTER] for recovery menu...       0 /Charge: 100% [##########################################################]



Menu
====
3. Load MMC over USB storage
4. Erase MMC
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:  10 /

Menu timeout
BOOTING DEFAULT.

I don't know if that's because you pressed a key, or the device is booting into diags on its own at startup, but that 'E. Export FAT partition' option is the one I was thinking of to get to the usb drive.

It looks like this device is booted up in diags mode, so I think you have to do the login on that.

There's a post here somewhere saying how to get the password for the account - it is different for each serial #

After the console shows 'Welcome to Kindle', you can press enter to put in username and password. The serial number is in that log file to use to create the password for that device.

knc1 · 01-21-2018, 08:38 AM

That menu has a (short) time out on it.
You can't sit around and think of what to do next, you must start typing.
Use "Export FAT Partition", have USB cord (one end already connected) ready to plug in, amazon update image ready to transfer.
You have 3 to 5 seconds to complete each of those steps, get after it, no sleeping on the keyboard allowed.

IIRC, you can install ANY firmware version (for your device) from that menu (no protection from a "downgrade attack") and you have probably already read here that you can get any firmware version from Amazon. They are all still on the server, you just have to edit the URL.
I would strongly suggest that you install a version that can be jailbroken.

and stay away from choices I, O, #3 and #4 - your asking for a lot of hurt if you select any of them

techanic · 01-21-2018, 10:07 AM

Quote:

Originally Posted by knc1

The messages should not stop at that point.
So unless you simply failed to quote the following messages, then ->
That is the end of "Device discovery".
It should be immediately followed by "Partition and File discovery"

No, unfortunately that was it no more from dmesg!

Quote:

Originally Posted by coplate

I don't know if that's because you pressed a key, or the device is booting into diags on its own at startup, but that 'E. Export FAT partition' option is the one I was thinking of to get to the usb drive.

It looks like this device is booted up in diags mode, so I think you have to do the login on that.

Yes, I pressa a key during boot up, to see if I get the menu.
Did not try any of the options yet, but I will as knc1 suggested.

I noticed that after the last line of the boot log I can press enter to get the kindle login. Unfortunately the generated password from sn# does not work (none of the two) I tried with root as username, but I might be wrong on that one?

I downloaded an older update file (v5.8.7.0.1) and will try my luck with the USB export now.

Thanks for your help so far!

******** Update ********
Here we go: the usb export worked, I was able to upload the update.bin to the kindle and reboot, BUT... There is now the message: "The update was not successful." on the screen (Update Error: 12)

Here the console log: export_usb_dump.txt

I guess the relevant part is here:

Code:

[    6.661368] ERROR:bundle/unbundle_common.c:350:valid_version_to_update():OTA version is less then current device version
[    6.661420] ERROR:bundle/unbundle_wario.c:1563:do_unbundle():do_unbundle: validate_version failed.
[    6.661976] INFO:bundle/unbundle_wario.c:2076:unbundle():No uboot image found! skipping uboot installation.
[    6.662028] ERROR:update.c:262:update_os():Could not unbundle /mnt-us/update_kindle_all_new_paperwhite_5.8.7.0.1.bin,error_code=12
[   17.830643] /mnt-us/update_kindle_all_new_paperwhite_5.8.7.0.1.bin MD5SUM: 05f4018f1841730d7ddb08c5e6673ab1
[   17.830811] INFO:update.c:43:remove_file_ll():removing /mnt-us/update_kindle_all_new_paperwhite_5.8.7.0.1.bin
[   18.138505] ERROR:recovery-util.c:1698:autopilot_update():*** There was a problem in the updates!

@knc1, maybe I can not chose any version I want for the update?

Now, how should I proceed? Update with the latest version?

knc1 · 01-21-2018, 10:56 AM

Quote:

Originally Posted by techanic

@knc1, maybe I can not chose any version I want for the update?

Now, how should I proceed? Update with the latest version?

error code 12 == "Downgrade attack detected"

Since you probably don't know what fw version is running...
Try this first:
https://www.adrive.com/public/bvT3kT..._5.8.9.0.1.bin
i'll PM you the password.

That **should** install if the current firmware is 5.8.9 or older.
If it does install, then you can follow the directions to jb that version (except the part about installing the factory image, which you just did.)

If that does not work, install something newer -
Avoid either of the 5.9.x.y.z firmwares, use either 5.8.10 or 5.8.11

NO - you have not been able to log into the 'main' system as root or anyone else since very early in the days of the KT (prior to 5.3.x).

Although there is a 'runme.sh' script example in the runme.sh thread that will change that to "no password requested or required".

techanic · 01-21-2018, 03:23 PM

I was able to copy the 5.8.9.0.1.bin over and start the update via menu successfully.
Everything was extracted (update screen with progressbar visible) and the pw3 rebooted but after reboot it still hangs on screensaver.
I can not wake it via power button... but I have still the login prompt on the console (which is useless if I understood you correctly?).

So I will read up on the JB stuff and do this tomorrow (if I get time)... although I do not quite see how this will help with the screensaver!?

knc1 · 01-21-2018, 03:46 PM

Did you create a capture file of those message on the serial console?
compress the file and attach it to your next post

why?
I can not see over your shoulder and just saying "its broke" does not give me much to go on.

techanic · 01-21-2018, 03:55 PM

my bad... here is the log: update_5.8.7.0.1.txt

knc1 · 01-21-2018, 04:39 PM

It looks like it is running to me - what was the problem again?

Is this the one where you had only a partial transfer by fastboot?
partial because fastboot silently fails is the image is too big.
I.E: you may have part of the new image and part of the old image on the device. not good(tm)

Let see if I can give you some hints, with:

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit

Select E - connect USB cable to PC
transfer the amazon update file to top level of visible USB storage
remove cable
(the system will automatically un-export USB storage)
Select M
wait - it should reboot by itself when done.

NOTE:
Do not try to transfer the main rootfs.img file using fastboot - the Kindle fastboot can not handle a file that large (it is larger than available ram as it un-compressed).

You can transfer the kernels and the diags system image - fastboot can handle those file sizes.
(except maybe not on the KOA2 - diags no longer has a partition to itself)

coplate · 01-21-2018, 11:18 PM

Quote:

Originally Posted by techanic

I was able to copy the 5.8.9.0.1.bin over and start the update via menu successfully.
Everything was extracted (update screen with progressbar visible) and the pw3 rebooted but after reboot it still hangs on screensaver.
I can not wake it via power button... but I have still the login prompt on the console (which is useless if I understood you correctly?).

So I will read up on the JB stuff and do this tomorrow (if I get time)... although I do not quite see how this will help with the screensaver!?

If you hold down the power button for 20 seconds, does the light flash and the device reboot? It could be the power button is broken on that.

Another way to test, if you have a magnet, you can try to wake the kindle up from the screensaver with the magnet. In the bottom right hand corner of the screen is the sleep/wake magnet sensor.

You can put a magnet on that corner, and then take it away. If everything is working right except the power buttons, that might wake it up.

techanic · 01-22-2018, 03:27 PM

Quote:

Originally Posted by knc1

It looks like it is running to me - what was the problem again?

Is this the one where you had only a partial transfer by fastboot?
partial because fastboot silently fails is the image is too big.
I.E: you may have part of the new image and part of the old image on the device. not good(tm)

Let see if I can give you some hints, with:

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit

Select E - connect USB cable to PC
transfer the amazon update file to top level of visible USB storage
remove cable
(the system will automatically un-export USB storage)
Select M
wait - it should reboot by itself when done.

NOTE:
Do not try to transfer the main rootfs.img file using fastboot - the Kindle fastboot can not handle a file that large (it is larger than available ram as it un-compressed).

You can transfer the kernels and the diags system image - fastboot can handle those file sizes.
(except maybe not on the KOA2 - diags no longer has a partition to itself)

On this device I initially flashed the PW2 images (diags and system) with fastboot only...

But I learned, thanks to you guys!

Since uboot still worked I was able do this:
Export USB:

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:    8 \E

USB CONNECTED!!
Charge: 100% [##########################################################]

[FAT32]
1. done
R. reboot
Choose: -still alive...
Charge: 100% [##########################################################]

copy over update_pw3_factory_5.8.9.0.1.bin

Code:

[FAT32]
1. done
R. reboot
Choose: -still alive...
Charge: 100% [##########################################################]

[FAT32]
1. done
R. reboot
Choose: |-1

done

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:   8 \M

tried 'M' but nothing happened...
tried 'U' and the following happened:

Code:

/dev/mmcblk0p4:
CHS=4/16/99776 size=3269459968 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6385648
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:

update-J8901-wario_muscat-011.dat:128 f11735a40ba95f8da92d92e6c2ae59a4 imx60_wario/u-boot.bin 2 bootloader_bin
1 d0a877de573980c8fb86b768748d5e46 imx60_wario/uImage 22 main_kernel
128 fe65243f1db67cf165b1d3f3e022d748 rootfs.img.gz 1713 update_image_rootfs
128 3c2d494573d8ec8dbe1546b9797742a1 data.stgz demo_data.stgz voice_data.stgz 4195 update_data_data

update-J8901-wario_muscat-011.dat:EOF

imx60_wario/u-boot.bin 293828     [######################################]
imx60_wario/uImage 2918312    [######################################]
rootfs.img.gz 224645144  [######################################]
data.stgz 549899020  [######################################]
imx60_wario/u-boot.bin 293828     [######################################]
imx60_wario/uImage 2918312    [######################################]
rootfs.img.gz 224645144  [######################################]
data.stgz 549899020  [######################################]
2918312    [######################################]
293828     [######################################]
Charge: 100% [##########################################################]

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:   3   2   1 /
Menu timeout
BOOTING DEFAULT.

Rest of the log: booting_default.txt

to me this looks not really suspicious... except for the lipc-send-event lines, but I have no idea what they mean.
After booting up the device displays again the screensaver, and nothing more (no touch, no magnet wake up not power button reaction, nothing... just kindle login prompt on serial console.

Problem is since I flashed the wrong diags kernel and image (PW2) I'm not able to JB for further testing... as I've understood so far diags is required for serial JB (since my screen does not work).

I'll try to export the diags kernel and image from another device and re-flash the 'correct' ones, unless you suggest anything else?

knc1 · 01-22-2018, 05:10 PM

Quote:

Originally Posted by techanic

- - - -
I'll try to export the diags kernel and image from another device and re-flash the 'correct' ones, unless you suggest anything else?

That should fix the "booting default" -> "what default?" problem.
See if you can find my script - it gets you everything you need.
And fastboot can handle the size of the 'diags' image and kernel.

01-20-2018, 11:19 AM	#1
techanic Junior Member Posts: 6 Karma: 10 Join Date: Jan 2018 Device: PW3	Unbricking some kindles, advice welcome... Hi Bought a box of "defective" Kindles out of a whim... now I have 5 PW3s. I opened 4 of them, so I have the possibility to connect the serial console. (Working on a Debian system, with working fastboot connection, got that hurdle...) No1 had a dead battery... replacing it brought it back to life but I suspect the charging circuit might be broken, have to test that. No2 is starting up but then just showing the screensaver (no touch or anything). On the serial console I see U-boot starting up Code: ... Welcome to Kindle ... info asr_setup:Not in asr mode::reason=flag file not present. shutting down asr_setup:: info hardware:no_wan::WiFi only device. No WAN found info board_data_file :/opt/ar6k/target/AR6003/hw2.1.1/bin/AR6003_wfo_calfile.bin:: [ 29.377434] ath6kl: ath6kl_fetch_board_file: Board calibration file fetched: /opt/ar6k/target/AR6003/hw2.1.1/bin/AR6003_wfo_calfile.bin [ 29.449979] ath6kl: MAC from kernel xx:xx:xx:xx:xx:C2 [ 29.859981] ath6kl: host only supports scatter of :1 entries, need: 16 [ 400.888536] pmic_soda_connects_notify_otg_out:423 and that's it... if I connect it to a Win PC I see a drive detected, but I cannot access it. Any Ideas on what might be wrong and how to fix it? I've read about DO_FACTORY_RESET file but I cannot access the drive... No3 shows the same behavior as No2. No4 displays a page of a book but does nothing more, no reaction to reset via power button (>20sec). No5 has a whole in the screen and a bent motherboard... so no help there, but the batter was still alive. Then I've a WP63GW with a strange looking image on the screen, serial console shows Code: [ 1.741247] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12] [ 1.748534] Regulator Fault Occurred! Retrying powerup... Guess this on is fatal as well... And I've a SY69JL with a kindle Power On picture and a D01100 with a drained battery on the screen, which I did not yet open up. Would be thankful for some tips/hints, I'm fairly new to this kindle stuff

01-20-2018, 12:02 PM	#2
coplate Guru Posts: 645 Karma: 1888888 Join Date: Jun 2009 Device: prs-505, Kindle Keyboard 3g, PW3	On number 2 and 3, the "..." you have listed could have useful information it it. but if it says "Welcome to Kindle", then the whole bootup process has occured. On your serial console, press enter and it should ask you for a login name, just for you to check what mode you are in. Login is disabled on the regular partition, so check the resot fo your logs for "press <something> to enter diags", and consider doing that, knc1 has the most recent post on what options to select here: "https://www.mobileread.com/forums/showthread.php?t=289497 I know there are certain triggers on when the paperwhite will 'export USB' and you can do it manually in diags mode form the command line, but I dont know why it wouldnt be showing up as a drive if you got to the "welcome to kindle" log. Are you doing this on Linux? I know that some versions of linux without certain updates will not automatically mount the new Oasis, I wonder if that culd be possible for the PW# you have there as well. Can you list the USB VendorID and ProductID? If you are on windows those are usefult too - kindle changes product ID to DEAD sometimes. You can view that with a tool called 'USBDeview' But you should also read through the main serial jailbreaking for dummies to learn about diags mode if you haven't already. As for #5, I have a need for the power button off of the screen ( see attachment if what I need isn't clear ); the clicky part fell off after manhandling it in an out of the case too many times. I wonder if you would be willing to part with it for cheap :-) Last edited by coplate; 01-20-2018 at 12:07 PM.

01-21-2018, 08:38 AM	#6
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	That menu has a (short) time out on it. You can't sit around and think of what to do next, you must start typing. Use "Export FAT Partition", have USB cord (one end already connected) ready to plug in, amazon update image ready to transfer. You have 3 to 5 seconds to complete each of those steps, get after it, no sleeping on the keyboard allowed. IIRC, you can install ANY firmware version (for your device) from that menu (no protection from a "downgrade attack") and you have probably already read here that you can get any firmware version from Amazon. They are all still on the server, you just have to edit the URL. I would strongly suggest that you install a version that can be jailbroken. and stay away from choices I, O, #3 and #4 - your asking for a lot of hurt if you select any of them Last edited by knc1; 01-21-2018 at 08:44 AM.

01-21-2018, 04:39 PM	#12
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	It looks like it is running to me - what was the problem again? Is this the one where you had only a partial transfer by fastboot? partial because fastboot silently fails is the image is too big. I.E: you may have part of the new image and part of the old image on the device. not good(tm) Let see if I can give you some hints, with: Code: Menu ==== 3. Load MMC0 over USB storage 4. Erase MMC0 I. Initialize Partition Table (fdisk) and format FAT O. Format and overwrite FAT partition E. Export FAT partition U. Update using update.bin file on FAT partition M. Update using update.bin file on FAT partition of second MMC port D. dmesg / kernel printk ring buffer. Q. quit Select E - connect USB cable to PC transfer the amazon update file to top level of visible USB storage remove cable (the system will automatically un-export USB storage) Select M wait - it should reboot by itself when done. NOTE: Do not try to transfer the main rootfs.img file using fastboot - the Kindle fastboot can not handle a file that large (it is larger than available ram as it un-compressed). You can transfer the kernels and the diags system image - fastboot can handle those file sizes. (except maybe not on the KOA2 - diags no longer has a partition to itself) Last edited by knc1; 01-21-2018 at 04:46 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Aura Help unbricking Aura	mikeash	Kobo Developer's Corner	21	09-25-2015 09:45 PM
Need help for unbricking PW 5.3.1	szfisher	Kindle Developer's Corner	22	07-12-2013 08:38 AM
HELP PLEASE!!! Unbricking EE	Yellowman1	enTourage eDGe	8	07-21-2011 08:54 AM
Help Unbricking PE	vicinc	enTourage eDGe	113	07-16-2011 12:40 AM
Hacks Any advice on unbricking the Kindle 2?	synapse	Amazon Kindle	5	01-20-2010 08:45 PM

01-21-2018, 03:23 PM	#9
techanic Junior Member Posts: 6 Karma: 10 Join Date: Jan 2018 Device: PW3	I was able to copy the 5.8.9.0.1.bin over and start the update via menu successfully. Everything was extracted (update screen with progressbar visible) and the pw3 rebooted but after reboot it still hangs on screensaver. I can not wake it via power button... but I have still the login prompt on the console (which is useless if I understood you correctly?). So I will read up on the JB stuff and do this tomorrow (if I get time)... although I do not quite see how this will help with the screensaver!?

01-21-2018, 03:46 PM	#10
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Did you create a capture file of those message on the serial console? compress the file and attach it to your next post why? I can not see over your shoulder and just saying "its broke" does not give me much to go on.

01-21-2018, 03:55 PM	#11
techanic Junior Member Posts: 6 Karma: 10 Join Date: Jan 2018 Device: PW3	my bad... here is the log: update_5.8.7.0.1.txt