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

Cinisajoy · 07-13-2016, 02:33 PM

Quote:

Originally Posted by iscrewedup

Yup, read it. I was tired and somehow misclicked. I think I made it very clear, I simply screwed up. Big time.
So there isn't virtually any way of debricking it?
Thank you.

I know a serial port jailbreak will work.
Not sure about anything else.
Oh and be glad it was a gift and not an Oasis.
Good luck.

Oh and little secret: you can convert epub to a kindle friendly format with Calibre.

knc1 · 07-13-2016, 02:39 PM

Quote:

Originally Posted by iscrewedup

Yup, read it. I was tired and somehow misclicked. I think I made it very clear, I simply screwed up. Big time.
So there isn't virtually any way of debricking it?
Thank you.

Push the filename:
DO_FACTORY_RESTORE
(all capitals, no extension, no contents) onto the visible root of USB storage (again).

You may need a scripted loop on a Linux box to get it done in small time it is visible.
See posts earlier today by eschwartz.

(On Linux and MacOSx, use the 'touch' command)
(On Windows, use Linux or MacOSx

)

iscrewedup · 07-13-2016, 03:18 PM

Quote:

Originally Posted by Cinisajoy

I know a serial port jailbreak will work.
Not sure about anything else.
Oh and be glad it was a gift and not an Oasis.
Good luck.

Oh and little secret: you can convert epub to a kindle friendly format with Calibre.

Thanks a lot.

Quote:

Originally Posted by knc1

Push the filename:
DO_FACTORY_RESTORE
(all capitals, no extension, no contents) onto the visible root of USB storage (again).

You may need a scripted loop on a Linux box to get it done in small time it is visible.
See posts earlier today by eschwartz.

(On Linux and MacOSx, use the 'touch' command)
(On Windows, use Linux or MacOSx

)

I tried the while loop to no avail.
I'm checking syslog trough a tail -f and get this output several times while connecting the Kindle in a debian-based distro. This is the whole process, from start to end (when I get the "this kindle needs repairing" message):

Code:

Jul 13 15:10:51 debian-machine kernel: [ 4103.012164] usb 1-2: new low-speed USB device number 7 using uhci_hcd
Jul 13 15:10:51 debian-machine kernel: [ 4103.180215] usb 1-2: New USB device found, idVendor=1949, idProduct=dead
Jul 13 15:10:51 debian-machine kernel: [ 4103.180234] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Jul 13 15:10:51 debian-machine kernel: [ 4103.180247] usb 1-2: Product: USB Charger
Jul 13 15:10:51 debian-machine kernel: [ 4103.198541] input: USB Charger  as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/0003:1949:DEAD.0006/input/input19
Jul 13 15:10:52 debian-machine kernel: [ 4103.254008] hid-generic 0003:1949:DEAD.0006: input,hidraw0: USB HID v1.11 Device [USB Charger ] on usb-0000:00:1d.0-2/input0
Jul 13 15:10:52 debian-machine mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-2"
Jul 13 15:10:52 debian-machine mtp-probe: bus: 1, device: 7 was not an MTP device
Jul 13 15:10:52 debian-machine kernel: [ 4103.824436] usb 1-2: USB disconnect, device number 7
Jul 13 15:11:04 debian-machine kernel: [ 4115.888121] usb 5-2: new high-speed USB device number 24 using ehci-pci
Jul 13 15:11:04 debian-machine kernel: [ 4116.026401] usb 5-2: New USB device found, idVendor=1949, idProduct=0004
Jul 13 15:11:04 debian-machine kernel: [ 4116.026421] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 13 15:11:04 debian-machine kernel: [ 4116.026434] usb 5-2: Product: Amazon Kindle
Jul 13 15:11:04 debian-machine kernel: [ 4116.026445] usb 5-2: Manufacturer: Amazon
Jul 13 15:11:04 debian-machine kernel: [ 4116.026456] usb 5-2: SerialNumber: 90C606064467****
Jul 13 15:11:04 debian-machine kernel: [ 4116.036405] usb-storage 5-2:1.0: USB Mass Storage device detected
Jul 13 15:11:04 debian-machine kernel: [ 4116.036753] scsi host17: usb-storage 5-2:1.0
Jul 13 15:11:04 debian-machine mtp-probe: checking bus 5, device 24: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-2"
Jul 13 15:11:04 debian-machine mtp-probe: bus: 5, device: 24 was not an MTP device
Jul 13 15:11:05 debian-machine kernel: [ 4117.038650] scsi 17:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
Jul 13 15:11:05 debian-machine kernel: [ 4117.041821] sd 17:0:0:0: Attached scsi generic sg2 type 0
Jul 13 15:11:05 debian-machine kernel: [ 4117.053570] sd 17:0:0:0: [sdc] Attached SCSI removable disk
Jul 13 15:11:41 debian-machine kernel: [ 4152.389900] usb 5-2: USB disconnect, device number 24
Jul 13 15:11:53 debian-machine kernel: [ 4165.148179] usb 5-2: new high-speed USB device number 25 using ehci-pci
Jul 13 15:11:54 debian-machine kernel: [ 4165.286433] usb 5-2: New USB device found, idVendor=1949, idProduct=0004
Jul 13 15:11:54 debian-machine kernel: [ 4165.286454] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 13 15:11:54 debian-machine kernel: [ 4165.286467] usb 5-2: Product: Amazon Kindle
Jul 13 15:11:54 debian-machine kernel: [ 4165.286479] usb 5-2: Manufacturer: Amazon
Jul 13 15:11:54 debian-machine kernel: [ 4165.286490] usb 5-2: SerialNumber: 90C606064467****
Jul 13 15:11:54 debian-machine kernel: [ 4165.289583] usb-storage 5-2:1.0: USB Mass Storage device detected
Jul 13 15:11:54 debian-machine kernel: [ 4165.293869] scsi host18: usb-storage 5-2:1.0
Jul 13 15:11:54 debian-machine mtp-probe: checking bus 5, device 25: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-2"
Jul 13 15:11:54 debian-machine mtp-probe: bus: 5, device: 25 was not an MTP device
Jul 13 15:11:55 debian-machine kernel: [ 4166.294650] scsi 18:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
Jul 13 15:11:55 debian-machine kernel: [ 4166.300950] sd 18:0:0:0: Attached scsi generic sg2 type 0
Jul 13 15:11:55 debian-machine kernel: [ 4166.308163] sd 18:0:0:0: [sdc] Attached SCSI removable disk
Jul 13 15:12:32 debian-machine kernel: [ 4203.477417] usb 5-2: USB disconnect, device number 25
Jul 13 15:12:45 debian-machine kernel: [ 4216.272188] usb 5-2: new high-speed USB device number 26 using ehci-pci
Jul 13 15:12:45 debian-machine kernel: [ 4216.410425] usb 5-2: New USB device found, idVendor=1949, idProduct=0004
Jul 13 15:12:45 debian-machine kernel: [ 4216.410446] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 13 15:12:45 debian-machine kernel: [ 4216.410459] usb 5-2: Product: Amazon Kindle
Jul 13 15:12:45 debian-machine kernel: [ 4216.410470] usb 5-2: Manufacturer: Amazon
Jul 13 15:12:45 debian-machine kernel: [ 4216.410481] usb 5-2: SerialNumber: 90C606064467****
Jul 13 15:12:45 debian-machine kernel: [ 4216.413605] usb-storage 5-2:1.0: USB Mass Storage device detected
Jul 13 15:12:45 debian-machine kernel: [ 4216.416798] scsi host19: usb-storage 5-2:1.0
Jul 13 15:12:45 debian-machine mtp-probe: checking bus 5, device 26: "/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-2"
Jul 13 15:12:45 debian-machine mtp-probe: bus: 5, device: 26 was not an MTP device
Jul 13 15:12:46 debian-machine kernel: [ 4217.417854] scsi 19:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
Jul 13 15:12:46 debian-machine kernel: [ 4217.423548] sd 19:0:0:0: Attached scsi generic sg2 type 0
Jul 13 15:12:46 debian-machine kernel: [ 4217.429707] sd 19:0:0:0: [sdc] Attached SCSI removable disk
Jul 13 15:13:26 debian-machine kernel: [ 4257.403951] usb 5-2: USB disconnect, device number 26

So, it seems that it's impossible to mount it correctly event on Linux.

bArDBQ · 07-13-2016, 03:54 PM

Update:

Using a portable version of Ubuntu on a flash drive I was able to mount my PW3 and saw that there was a SYSTEM VOLUME INFORMATION folder in root with the DO_FACTORY_RESTORE file (the SYSTEM VOLUME INFORMATION folder was not visible through Windows even if hidden files were visible). I deleted the file and folder in root so that it was 100% empty and was able to touch the DO_FACTORY_RESTORE file alone and then unmounted the Kindle.

Result was the same... Device needs repair Error code 2

Let me know if you have any other idea!

Thanks

geekmaster · 07-13-2016, 03:55 PM

Code:

0003:1949:DEAD.0006: input,hidraw0: USB HID v1.11 Device [USB Charger ] on usb-0000:00:1d.0-2/input0

That is the "dead battery" fake 0MB usb device, used to keep the host from powering down USB while charging the kindle identification for a totally dead battery than cannot be charged. It indicates that your kindle battery is very discharged, but may also indicate ERASED firmware. Charge it for a couple of days on a wall charger (very slow trickle charge in that mode), then try slipping that file onto it. Be sure that your kindle has a full battery charge before attempting repair. See this update below:
https://www.mobileread.com/forums/sho...26#post3352626

Is it possible your kindle battery was discharged before firmware updates compelted? Not good if so, you MIGHT need to go the serial port route in that case. But charge it first and try again.

There is a GOOD REASON why charging the battery is listed as the third step in the "step by step" in the first post in this thread.

knc1 · 07-13-2016, 04:13 PM

It is one of the steps **before** you can even start step #1.

When we get all of the special cases figured out, then I can start to simplify the directions.

geekmaster · 07-13-2016, 04:26 PM

Quote:

Originally Posted by knc1

It is one of the steps **before** you can even start step #1.

When we get all of the special cases figured out, then I can start to simplify the directions.

What instruction steps can you add for these guys:
Study says 64% of men don’t even read the manual before calling tech support

niftium · 07-13-2016, 04:37 PM

Just as a data point - I was able to downgrade my KV from 5.8.1 to the factory image, jailbreak, and install MrPI without any issues by following the well-written instructions on the first page.

To those who had package problems after a FW update to the newest version post-jb, a quick re-installation of those packages was all I needed to get things working again.

Big thanks to everybody in the first post who's credited with making this all happen!

eschwartz · 07-13-2016, 04:54 PM

Quote:

Originally Posted by knc1

The udev rule is faster, more certain and those also 'fire' when a file system is mounted (detected) not just when the hardware bus changes.

I did not know that, I thought udev was all about the hardware.

NullNix · 07-13-2016, 05:48 PM

Quote:

Originally Posted by eschwartz

I did not know that, I thought udev was all about the hardware.

It's about spotting kernel events (roughly) associated with device nodes appearing or disappearing and doing stuff. The 'stuff' might be fiddling permissions, creating symlinks, or running arbitrary programs, like a mount && touch && umount

bArDBQ · 07-13-2016, 06:05 PM

Is it safe to format the storage device (in FAT or FAT32?) in Windows?

geekmaster · 07-13-2016, 06:19 PM

Quote:

Originally Posted by bArDBQ

Is it safe to format the storage device (in FAT or FAT32?) in Windows?

Yes, but then the default files (dictionaries and such) will be missing (restored on factory reset).

bArDBQ · 07-13-2016, 06:27 PM

Quote:

Originally Posted by geekmaster

Yes, but then the default files (dictionaries and such) will be missing (restored on factory reset).

Should I go with FAT or FAT32?

Thanks

knc1 · 07-13-2016, 06:34 PM

Quote:

Originally Posted by geekmaster

Yes, but then the default files (dictionaries and such) will be missing (restored on factory reset).

No, not really, Windows does not support the combination of special options the Kindle system uses.

Better to wipe the mbr and disk label in the reserved area of storage and let the Kindle re-format it on the next boot.

bArDBQ · 07-13-2016, 06:49 PM

Quote:

Originally Posted by knc1

No, not really, Windows does not support the combination of special options the Kindle system uses.

Better to wipe the mbr and disk label in the reserved area of storage and let the Kindle re-format it on the next boot.

How would I do that using Ubuntu?

07-13-2016, 03:55 PM	#455
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	Code: 0003:1949:DEAD.0006: input,hidraw0: USB HID v1.11 Device [USB Charger ] on usb-0000:00:1d.0-2/input0 That is the "dead battery" fake 0MB usb device, used to keep the host from powering down USB while charging the kindle identification for a totally dead battery than cannot be charged. It indicates that your kindle battery is very discharged, but may also indicate ERASED firmware. Charge it for a couple of days on a wall charger (very slow trickle charge in that mode), then try slipping that file onto it. Be sure that your kindle has a full battery charge before attempting repair. See this update below: https://www.mobileread.com/forums/sho...26#post3352626 Is it possible your kindle battery was discharged before firmware updates compelted? Not good if so, you MIGHT need to go the serial port route in that case. But charge it first and try again. There is a GOOD REASON why charging the battery is listed as the third step in the "step by step" in the first post in this thread. Last edited by geekmaster; 07-13-2016 at 08:20 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 03:18 PM
PW3 PW3-4, PW3-32, fw-5.8.9.0.1 software jailbreak	knc1	Kindle Developer's Corner	203	01-28-2020 12:53 AM
Will jailbreak survive a 5.9.2.0.1 update on KOA?	tigrisg	Kindle Developer's Corner	1	12-19-2017 06:49 AM
PW3 stuck in "code 2" after software jailbreak attempt from 5.8.10	Varijus	Kindle Developer's Corner	10	12-17-2017 04:08 AM

07-13-2016, 03:54 PM	#454
bArDBQ Member Posts: 11 Karma: 10 Join Date: Jun 2012 Device: Samsung Galaxy Tab 7 Plus	Update: Using a portable version of Ubuntu on a flash drive I was able to mount my PW3 and saw that there was a SYSTEM VOLUME INFORMATION folder in root with the DO_FACTORY_RESTORE file (the SYSTEM VOLUME INFORMATION folder was not visible through Windows even if hidden files were visible). I deleted the file and folder in root so that it was 100% empty and was able to touch the DO_FACTORY_RESTORE file alone and then unmounted the Kindle. Result was the same... Device needs repair Error code 2 Let me know if you have any other idea! Thanks

07-13-2016, 04:13 PM	#456
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	It is one of the steps before you can even start step #1. When we get all of the special cases figured out, then I can start to simplify the directions.

07-13-2016, 04:37 PM	#458
niftium Junior Member Posts: 7 Karma: 10 Join Date: Nov 2015 Device: Kindle Voyage	Just as a data point - I was able to downgrade my KV from 5.8.1 to the factory image, jailbreak, and install MrPI without any issues by following the well-written instructions on the first page. To those who had package problems after a FW update to the newest version post-jb, a quick re-installation of those packages was all I needed to get things working again. Big thanks to everybody in the first post who's credited with making this all happen!

07-13-2016, 06:05 PM	#461
bArDBQ Member Posts: 11 Karma: 10 Join Date: Jun 2012 Device: Samsung Galaxy Tab 7 Plus	Is it safe to format the storage device (in FAT or FAT32?) in Windows?