Tools Software Jailbreak for PW2, PW3, PW3W, KT2, KV, KOA and KT3 - Page 34

eschwartz · 07-14-2016, 07:17 PM

knc1,

Not only that, you asked me via PM and I told you (1801)... three hours ago.

NiLuJe · 07-14-2016, 07:30 PM

@eschwartz: I can build a zip version, if you prefer

.

So we don't lose @BD's README

.

teboso · 07-14-2016, 07:34 PM

Hi all,

It looks like my brand new PW3 has been thoroughly borked during the downgrade step. Boot-looping with corrupted graphics, not visible over USB at any point during the process. Here's exactly what I did:

1. Unbox and charge PW3.
2. Downloaded update_PW3_5.6.1.1_initial.bin and associated md5; md5 checksum OK.
3. Log into PW3 in order to access menu.
4. Factory reset.
5. Moved update_PW3_5.6.1.1_initial.bin to root Kindle directory BEFORE logging back in.
6. Logged in, triggered upgrade.

At this point the upgrade seemed to go well, got a success message after the loading bar. However, once it tried to boot the graphics were all messed up and flickering. Boot looped repeatedly, however, I was able to briefly see it over USB. Seeing the earlier similar case, I:

7. Made empty DO_FACTORY_RESET file and transferred it over.
8. Reset 10+ times with same results.

Pic of current state here: http://imgur.com/malyrmu. Note that upon reset, the L-shaped outer bit does not change at all. Only the upper right block updates in any way.

I'm running debian, and have done some mild recovery stuff with android in the past. Please let me know if you have any ideas, or if there's anything else I can do to help.

Thanks,
-teboso

Edit: dmesg:

Code:

[31125.712526] sd 43:0:0:0: Attached scsi generic sg7 type 0
[31125.720863] sd 43:0:0:0: [sdg] Attached SCSI removable disk
[31159.742484] usb 2-3: USB disconnect, device number 39
[31172.529549] usb 2-3: new high-speed USB device number 40 using ehci-pci
[31172.667798] usb 2-3: New USB device found, idVendor=1949, idProduct=0004
[31172.667803] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[31172.667806] usb 2-3: Product: Amazon Kindle
[31172.667808] usb 2-3: Manufacturer: Amazon
[31172.670848] usb-storage 2-3:1.0: USB Mass Storage device detected
[31172.671331] scsi44 : usb-storage 2-3:1.0
[31173.671741] scsi 44:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
[31173.672215] sd 44:0:0:0: Attached scsi generic sg7 type 0
[31173.680738] sd 44:0:0:0: [sdg] Attached SCSI removable disk
[31212.124582] usb 2-3: USB disconnect, device number 40
[31537.121653] usb 7-1: new low-speed USB device number 5 using uhci_hcd
[31537.289670] usb 7-1: New USB device found, idVendor=1949, idProduct=dead
[31537.289675] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[31537.289678] usb 7-1: Product: USB Charger 
[31537.305853] input: USB Charger  as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/0003:1949:DEAD.0008/input/input11
[31537.305973] hid-generic 0003:1949:DEAD.0008: input,hidraw4: USB HID v1.11 Device [USB Charger ] on usb-0000:00:1d.1-1/input0
[31537.950543] usb 7-1: USB disconnect, device number 5

knc1 · 07-14-2016, 07:35 PM

Quote:

Originally Posted by eschwartz

knc1,

Not only that, you asked me via PM and I told you (1801)... three hours ago.

I understood from the timing of the change and the posting of the most recent on the subject, that it had been changed again, within the past three hours.

NiLuJe · 07-14-2016, 07:36 PM

@ktwombley: That's the black one, right?

eschwartz · 07-14-2016, 07:47 PM

Quote:

Originally Posted by NiLuJe

@eschwartz: I can build a zip version, if you prefer

.

So we don't lose @BD's README

.

I wasn't motivated to preserve the license

but the actual instructions in the README are now inside the post itself.

Given how many people don't seem to get unzipping the Kindle Touch jailbreak attachment, I'd rather not risk it again if possible. It is one file plus instructions, and the file can be attached directly, so...

Quote:

Originally Posted by knc1

I understood from the timing of the change and the posting of the most recent on the subject, that it had been changed again, within the past three hours.

Ah, nope. Just alerting NiLuJe to the fact that everyone's factory-jailbreak should be on the same page now.

knc1 · 07-14-2016, 07:48 PM

Quote:

Originally Posted by teboso

Hi all,

It looks like my brand new PW3 has been thoroughly borked during the downgrade step. Boot-looping with corrupted graphics, not visible over USB at any point during the process. Here's exactly what I did:

1. Unbox and charge PW3.
2. Downloaded update_PW3_5.6.1.1_initial.bin and associated md5; md5 checksum OK.
3. Log into PW3 in order to access menu.
4. Factory reset.
5. Moved update_PW3_5.6.1.1_initial.bin to root Kindle directory BEFORE logging back in.
6. Logged in, triggered upgrade.

At this point the upgrade seemed to go well, got a success message after the loading bar. However, once it tried to boot the graphics were all messed up and flickering. Boot looped repeatedly, however, I was able to briefly see it over USB. Seeing the earlier similar case, I:

7. Made empty DO_FACTORY_RESET file and transferred it over.
8. Reset 10+ times with same results.

Pic of current state here: http://imgur.com/malyrmu. Note that upon reset, the L-shaped outer bit does not change at all. Only the upper right block updates in any way.

I'm running debian, and have done some mild recovery stuff with android in the past. Please let me know if you have any ideas, or if there's anything else I can do to help.

Thanks,
-teboso

Edit: dmesg:

Code:

[31125.712526] sd 43:0:0:0: Attached scsi generic sg7 type 0
[31125.720863] sd 43:0:0:0: [sdg] Attached SCSI removable disk
[31159.742484] usb 2-3: USB disconnect, device number 39
[31172.529549] usb 2-3: new high-speed USB device number 40 using ehci-pci
[31172.667798] usb 2-3: New USB device found, idVendor=1949, idProduct=0004
[31172.667803] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[31172.667806] usb 2-3: Product: Amazon Kindle
[31172.667808] usb 2-3: Manufacturer: Amazon
[31172.667811] usb 2-3: SerialNumber: G090G105621305MC
[31172.670848] usb-storage 2-3:1.0: USB Mass Storage device detected
[31172.671331] scsi44 : usb-storage 2-3:1.0
[31173.671741] scsi 44:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
[31173.672215] sd 44:0:0:0: Attached scsi generic sg7 type 0
[31173.680738] sd 44:0:0:0: [sdg] Attached SCSI removable disk
[31212.124582] usb 2-3: USB disconnect, device number 40
[31537.121653] usb 7-1: new low-speed USB device number 5 using uhci_hcd
[31537.289670] usb 7-1: New USB device found, idVendor=1949, idProduct=dead
[31537.289675] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[31537.289678] usb 7-1: Product: USB Charger 
[31537.305853] input: USB Charger  as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/0003:1949:DEAD.0008/input/input11
[31537.305973] hid-generic 0003:1949:DEAD.0008: input,hidraw4: USB HID v1.11 Device [USB Charger ] on usb-0000:00:1d.1-1/input0
[31537.950543] usb 7-1: USB disconnect, device number 5

That does not sound like you where following the directions in the top post of this thread at all.

What directions where you following?
Link please.

teboso · 07-14-2016, 07:56 PM

Hi knc1,

I was following the directions here; I just listed a more detailed version of the steps I took to help with troubleshooting and in the hopes of identifying a cause.

I was going through the "Step-by-Step" section, and followed 1, 2, 3, 4, and the subset of 4 for hanging and loops.

knc1 · 07-14-2016, 08:07 PM

(1) You wrote "logged in" so you missed the part about clearing passcodes and special offers.
(2) You missed the part to use the 5.7.4 firmware version, because 5.6.1.1 bootloops all too often.

Now you have a bootloop because of (2) and it will not export USB storage until you log in because of (1), which is a bit hard to do while it is bootlooping.

Welcome to the world of serial port debricking.

teboso · 07-14-2016, 08:15 PM

...So I did!

That's what I get for not reading the Notices. I've heard Amazon will take returns on these; should I try for an exchange? Or is serial port debricking reliable enough that I ought to be able to recover?

eschwartz · 07-14-2016, 08:16 PM

I don't think they will accept it if there is visible signs of you doing something wonky. Plus it is a bit dishonest.

Fortunately the serial debrick is reliable. It just requires methods many people cannot handle.

knc1 · 07-14-2016, 08:20 PM

Quote:

Originally Posted by teboso

...So I did!

That's what I get for not reading the Notices. I've heard Amazon will take returns on these; should I try for an exchange? Or is serial port debricking reliable enough that I ought to be able to recover?

Go to step-by-step - -
There is a bullet list of things to do before the actual step one.

You are in full control over the serial port, you are the god of your kindle.
The only thing to watch out for is speed-reading the directions.

Cinisajoy · 07-14-2016, 08:35 PM

Quote:

Originally Posted by teboso

...So I did!

That's what I get for not reading the Notices. I've heard Amazon will take returns on these; should I try for an exchange? Or is serial port debricking reliable enough that I ought to be able to recover?

Read twice, do once.

geekmaster · 07-14-2016, 09:06 PM

Quote:

Originally Posted by knc1

See: "Reason for edit" at bottom.

Your suggestion is the correct way to do it, but . . . . .

I think you should add after the K5 JB paragraph:

"For all previous kindles models, see the Jailbreak Index sticky thread:
https://www.mobileread.com/forums/showthread.php?t=275881"

knc1 · 07-14-2016, 09:30 PM

Quote:

Originally Posted by geekmaster

I think you should add after the K5 JB paragraph:

"For all previous kindles models, see the Jailbreak Index sticky thread:
https://www.mobileread.com/forums/showthread.php?t=275881"

That index page is still more than a bit obscure, but if you want it used as-is . . . .

07-14-2016, 08:16 PM	#506
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I don't think they will accept it if there is visible signs of you doing something wonky. Plus it is a bit dishonest. Fortunately the serial debrick is reliable. It just requires methods many people cannot handle. Last edited by eschwartz; 07-14-2016 at 08:19 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
USB OTG Mouse Support and page turn on PW3(possible KV/KOA)	lucida	Kindle Developer's Corner	105	12-07-2024 02:18 PM
PW3 PW3-4, PW3-32, fw-5.8.9.0.1 software jailbreak	knc1	Kindle Developer's Corner	203	01-27-2020 11:53 PM
Will jailbreak survive a 5.9.2.0.1 update on KOA?	tigrisg	Kindle Developer's Corner	1	12-19-2017 05:49 AM
PW3 stuck in "code 2" after software jailbreak attempt from 5.8.10	Varijus	Kindle Developer's Corner	10	12-17-2017 03:08 AM

07-14-2016, 07:17 PM	#496
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	knc1, Not only that, you asked me via PM and I told you (1801)... three hours ago.

07-14-2016, 07:30 PM	#497
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@eschwartz: I can build a zip version, if you prefer . So we don't lose @BD's README .

07-14-2016, 07:36 PM	#500
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@ktwombley: That's the black one, right?

07-14-2016, 07:56 PM	#503
teboso Junior Member Posts: 5 Karma: 54046 Join Date: Jul 2016 Device: Kindle Paperwhite 3	Hi knc1, I was following the directions here; I just listed a more detailed version of the steps I took to help with troubleshooting and in the hopes of identifying a cause. I was going through the "Step-by-Step" section, and followed 1, 2, 3, 4, and the subset of 4 for hanging and loops.

07-14-2016, 08:07 PM	#504
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	(1) You wrote "logged in" so you missed the part about clearing passcodes and special offers. (2) You missed the part to use the 5.7.4 firmware version, because 5.6.1.1 bootloops all too often. Now you have a bootloop because of (2) and it will not export USB storage until you log in because of (1), which is a bit hard to do while it is bootlooping. Welcome to the world of serial port debricking.

07-14-2016, 08:15 PM	#505
teboso Junior Member Posts: 5 Karma: 54046 Join Date: Jul 2016 Device: Kindle Paperwhite 3	...So I did! That's what I get for not reading the Notices. I've heard Amazon will take returns on these; should I try for an exchange? Or is serial port debricking reliable enough that I ought to be able to recover?

Advert

Advert