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

[Karnivour]

Originally Posted by dhdurgee

Safe at this point, as the JB will remain, but you will need to reinstall much of the enhancements as only the JB itself is preserved over an update.

Thx Dave! Update 5.8.9.2 was succesfull and the screensaver is still working.

Now I can keep the PW3, thank you all for your help

[knc1]

I do wish Amazon would make mistakes that allow me to shorten this first post - not add in more special conditions.
But we have had enough reports now, so for as long as the 'mistakes' remain in-stock ...

It was this 'just add a line or two' that made it grow to the size it is now.
(I do, from time to time, try to hack it back in size.)

[hius07]

Confirm jailbreak survives on PW3 5.8.10.

[knc1]

Originally Posted by hius07

Confirm jailbreak survives on PW3 5.8.10.

That is nice to know.

Want to try using the PW3 'factory-initial' package on it?
See if it deletes it or if it will allow the factory firmware install (which is required to jb the PW3).

It should not matter if you already have the PW3 jail broken, the bridge code **should** jb the 'factory-initial' for you.

If it does install, you can always just manually upgrade back to where you came from (5.8.10).

= = = =

And I saw yesterday where you had added the 5.8.9..0.1 exception to your jb thread.

[coplate]

Originally Posted by knc1

That is nice to know.

Want to try using the PW3 'factory-initial' package on it?
See if it deletes it or if it will allow the factory firmware install (which is required to jb the PW3).

It should not matter if you already have the PW3 jail broken, the bridge code **should** jb the 'factory-initial' for you.

If it does install, you can always just manually upgrade back to where you came from (5.8.10).

= = = =

And I saw yesterday where you had added the 5.8.9..0.1 exception to your jb thread.

I had unpacked the 5.8.9.2 code and found something ,I haven't had a chance to look at the same thing in 5.8.10.
In the image file inside the .bin, there is a new file called roughtly /etc/bundle_type.txt, that has "FB03" in it.

There are two other files /usr/bin/otav3 and /usr/lib/libota_utils.so.1.0 that have a function called 'shouldAllowDowngrade" and "shouldAllowFB02Bundle"

I can't dissassemble those binaries very well, by they do reference the file /mnt-rootfs/PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC and /mnt-rootfs/etc/bundle_type.txt

the PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC file is used to control some things that are not supposed to make it out the door.

So my guess is very strongly that we cannot downgrade to FB02 packages, unless we create that file ( which you would need to be jailbroken for, but he is ), and that file is referenced in a lot of shell scripts, so it may not be a good thing to leave it lying around.

[hius07]

PW3 5.8.10: downgrade to factory-initial firmare is impossible.

[knc1]

Originally Posted by hius07

PW3 5.8.10: downgrade to factory-initial firmware is impossible.

Thank you for checking.

[mcdull]

Is it hopeless for G090LL (KPW3 32GB) Users? It has been out for almost 2 years and still not any hack discovered.
I would really want to change those messy wallpaper.

[knc1]

Originally Posted by mcdull

Is it hopeless for G090LL (KPW3 32GB) Users? It has been out for almost 2 years and still not any hack discovered.
I would really want to change those messy wallpaper.

As long as there is a lack of PW3-32 developers posting their contributions here, then nothing new about them will be found here.
The device is not available outside of Japan, so don't expect any after-market development to be done outside of Japan.
This type of development can not be done without the hardware and a group of owners willing to test things at the risk of their devices.

Your more likely to see progress made by a native Japanese web-site / forum.
One with the people and the devices required to do after-market development.

= = = = =

I have checked with several "International Purchasing Services" -
That service would almost double the cost of an already expensive device.
That leaves me out of this ball game.
The people other than myself, with a background in after-market development, are either dead, dying or just gone from this site.

[nightauthor]

Have a KV I just got a few days ago, want to disable the touchscreen to prevent accidental pageturns.

My KV is on 5.8.9.2 , and when I try to put the factory firmware on the device it wont take. I go to the menu and update is grayed out. I plugged the device back into my PC and the file had disappeared.

It looked like JB by serial would be an option for me, however I'm very hesitant to operate on my device that is brand new.

Is there anything else I am missing? Some other software JB method for the KV and this firmware version?

[Lowantong]

My device is KOA, SN is G0B0 GR09 6182 00E7, 3G + Wi-Fi
Follow to the instructions from https://www.mobileread.com/forums/sh...d.php?t=275877 by knc1

1/ Downgrade to v5.7.4 by “update_KOA_5.7.4_initial.bin” – ok (See attached pic_1)

2/ JB by “main-htmlviewer.tar.gz” – ok (See attached pic_2)

3/ Install “hotfix by Update_jailbreak_hotfix_1.14.N_install.bin” - remove USB cable after copied the file, the device show up Update Error (See attached pic_3)

Have any idea about this problem?

[knc1]

Originally Posted by Lowantong

My device is KOA, SN is G0B 0GR xx xxxx xxxx, 3G + Wi-Fi
Follow to the instructions from https://www.mobileread.com/forums/sh...d.php?t=275877 by knc1

1/ Downgrade to v5.7.4 by “update_KOA_5.7.4_initial.bin” – ok (See attached pic_1)

2/ JB by “main-htmlviewer.tar.gz” – ok (See attached pic_2)

3/ Install “hotfix by Update_jailbreak_hotfix_1.14.N_install.bin” - remove USB cable after copied the file, the device show up Update Error (See attached pic_3)

Have any idea about this problem?

Remove the last part of your serial number from your post. Example in the quote I made here.

Remove any update_*.bin file from the top of visible USB storage.
Either ours or any received over Wifi.

Enable 'Airplane Mode'

Now repeat Step #1.
Did you find your device's serial number in the table?

Now tell me what part of:

The factory images **are not** model locked, your care taken with this step is your Kindle's only protection! If not found in the table, STOP HERE and tell us.

did not translate for you?
Specifically the: STOP HERE part of the second sentence.

You will have to re-package the 'hotfix' update_*.bin file to recognize your model using KindleTool.
Although KindleTool does not have your model built-in, it can be used to build a package for a model passed on its command line.

Somebody here will help you with doing that if you have any problems doing it yourself.

Do not update the Kindle away from the 'factory use only' firmware until you have installed the 'hotfix' package.
Without the 'hotfix' package, any update will wipe out the jail break.

You will have to re-package the KUAL booklet the same way.
Also, any other package in an: update_*.bin format file name.

[JotaCe]

I am sorry if this has been already answered before (sure it has), but it is difficult to find something in a thread of more than 2200 posts...

I want to jailbreak a PW2 with firmware 5.8.9.2. I have seen that this method does not work for this version, but... is there any way to downgrade this firmware to any other compatible with the jailbreak?

Thanks!

[knc1]

Originally Posted by JotaCe

I am sorry if this has been already answered before (sure it has), but it is difficult to find something in a thread of more than 2200 posts...

I want to jailbreak a PW2 with firmware 5.8.9.2. I have seen that this method does not work for this version, but... is there any way to downgrade this firmware to any other compatible with the jailbreak?

Thanks!

The top post is always current.
You only need to read the first post, not the entire thread.

[JotaCe]

Originally Posted by knc1

The top post is always current.
You only need to read the first post, not the entire thread.

I did. And I saw that this method will not work form that firmware. I wondered if it would exist any workaround. I suspect that you answer means not.