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

[geekmaster]

Originally Posted by knc1

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

I just cleaned it up. Please "peer review" it and suggest changes. My brain is stuck in low gear at the moment.

[knc1]

@geekmaster: tomorrow

@all:
A big edit tonight, but the post did get smaller from pulling all of the PW-3 special case stuff out of it (we no longer distribute the trouble making update_*.bin).

It isn't exactly ready for "Cliff's Notes" yet but it is still a work in progress.

May break 5,000 downgrades (including a guess at China) sometime tonight.

[Cinisajoy]

Originally Posted by knc1

@geekmaster: tomorrow

@all:
A big edit tonight, but the post did get smaller from pulling all of the PW-3 special case stuff out of it (we no longer distribute the trouble making update_*.bin).

It isn't exactly ready for "Cliff's Notes" yet but it is still a work in progress.

May break 5,000 downgrades (including a guess at China) sometime tonight.

It is looking good.

[knc1]

Originally Posted by Cinisajoy

It is looking good.

Thank you very much.

The hardest part of computer science is communicating with the humans involved.

[bArDBQ]

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:

[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

Pretty much the same issue as me except I don't get the display problem... Let me know if you get this resolved...

[geekmaster]

Originally Posted by bArDBQ

Pretty much the same issue as me except I don't get the display problem... Let me know if you get this resolved...

It is resolved by using the new 5.7.4 firmware image instead of the old 5.6.1.1 firmware image. Because the old one kept getting used anyway, we removed it from the pastebin this evening.

The failure rate using the old firmware was low, but better to force (rather than encourage) using the newer version, to prevent problems like this. The old firmware is still available on request if somebody wishes to study it or experiment with it.

Depending on how well instructions were followed, either you can repair it by injecting a factory restore flag file (see above), or you may need to repair it using the internal serial port (also see above).

[Kindol]

@NiLuJe

Just a quick update, kindle-jb-factory-1.2-r13366 does not work it flashes once and back to the home page.

I should add, it's a new KP3 -Black-WiFi S/N is: G090 G105 running Firmware Version 5.7.4

Thank you for your continuous support.

[knc1]

Originally Posted by Kindol

@NiLuJe

Just a quick update, kindle-jb-factory-1.2-r13366 does not work it flashes once and back to the home page.

I should add, it's a new KP3 -Black-WiFi S/N is: G090 G105 running Firmware Version 5.7.4

Thank you for your continuous support.

Probably not, we do not support a model nicknamed: KP3 here.

Once you figure out what model you have, try again with the currently posted jb file from the correct post, as linked to in step #5 of the directions.

[notsoinsane]

Originally Posted by knc1

They should.

If from NiLuJe's snapshots thread.
Forum index, prefix filter: Tools, click: "Show Threads"

Most of those things have options and controls in the form of KUAL menu entries, and KUAL will not run on the KOA.
But they also have a manual version of those options and controls in their configuration files - see directions packed with each.

You will need the most recent 'hotfix' package -
If not sure, get it and install it (again), it will not hurt anything even if already installed.

You will need the most recent build of MrPI -
Install it (it is one of the "un-zip into correct place" packages).
Directions included in package.

On the KOA you run MrPI with a main page, search bar command:
;log mrpi

Other than the above change in how to activate the package installer, all of its directions remain the same.

Report problems in the related thread (last entry of its description line in the 'snapshot' entry is a link to the related thread).

Thanks for that and sorry to double post - my flawed thinking was that the subjects were different enough to justify it. I was able to do that but even with the latest nightly build of the screensavers hack it did not work. It definitely installed with mrpi but I do not get any change in screensaver when I turn off my device. Do you have any advice as to how I can troubleshoot it?

[knc1]

We do not do nightly builds here.

The most recently built screensaver hack (a four letter word) can be found in this list:
https://www.mobileread.com/forums/sho...d.php?t=225030

The thread related to the screensaver after-market add-in is shown at the end of the descriptive line, reprinted here:
https://www.mobileread.com/forums/sho...d.php?t=195474

Do not be confused about posting in the correct thread, just because this one is on the top of the index page list.
The index is sorted by most recent post - once you post in the correct place, that thread will be at the top of the list.

[Kindol]

@knc1

am so so sorry buddy, I totally forgot to type 'W' between 'P' and '3' it was purely un-intentional. A typo that went unchecked. I know I should have double checked before I posted.

I was meant to type PW3 as in Kindle Paperwhite 3.

I'll promise to check my messages properly in the future.

As always, thank you for your help and prompt reply

[knc1]

Not only will you discover that the JB for your PW-3 was recently (hours ago) changed, you will find that the directions were recently edited on the subject of files that remain behind.

wasted a great # 11 0 55 on a rtfm post

[geekmaster]

Originally Posted by Kindol

... I totally forgot to type 'W' between 'P' and '3' it was purely un-intentional. ...

There is also NO 'K' in "PW3" (you asked for help on a KP3). K3 and PW3 are different beasts entirely, as far as firmware is concerned.

[laiba]

Originally Posted by knc1

They should.

If from NiLuJe's snapshots thread.
Forum index, prefix filter: Tools, click: "Show Threads"

Most of those things have options and controls in the form of KUAL menu entries, and KUAL will not run on the KOA.
But they also have a manual version of those options and controls in their configuration files - see directions packed with each.

You will need the most recent 'hotfix' package -
If not sure, get it and install it (again), it will not hurt anything even if already installed.

You will need the most recent build of MrPI -
Install it (it is one of the "un-zip into correct place" packages).
Directions included in package.

On the KOA you run MrPI with a main page, search bar command:
;log mrpi

Other than the above change in how to activate the package installer, all of its directions remain the same.

Report problems in the related thread (last entry of its description line in the 'snapshot' entry is a link to the related thread).

usbnet cannot be installed as the README_FIRST.txt told，but it is worked with mrpi！！！

[geekmaster]

Originally Posted by laiba

usbnet cannot be installed as the README_FIRST.txt told，but it is worked with mrpi！！！

As expected. KOA support is a very recent thing. Perhaps the README_FIRST.txt will get updated to mention mrpi at some point RSN. Glad it worked for you.