07/04/2016 jailbreak failure reports.

[knc1]

That is, the jailbreak release of 07/04/2016, not the failure reports of 07/04/2016.


It may be that Amazon/Lab126 has been able to prevent our current jailbreak with the release of firmware 5.8.8 version.

The 5.8.8 version firmware is being pushed to all PW-2 and newer devices (all i.MX6 devices).

There is also one report that the current jailbreak process has new difficulties introduced with the 5.8.7.0.1 firmware release.

First 5.8.8 failure report by checkmermaid:
https://www.mobileread.com/forums/sh...postcount=1511

Please add success/failure reports to this thread.

[knc1]

This thread refers only to failures of the jailbreak that was first released on 07/04/2016.

[hius07]

one more fail report: PW2 with 5.8.8
here in Russian

[knc1]

Thanks.
That is 2 reports for the PW-2, none for other models.

Note to users of other models already running 5.8.8 and not yet jailbroken:
It is safe to try loading the initial firmware, if it doesn't work, it will just be deleted.

I would like to hear about other attempts, other models.

Note:
If already jailbroken, the jb will survive the update to 5.8.8 and the device remain jailbroken.
(Everything else needs to be re-installed, but that is normal.)

[hius07]

more details
after safe removal from usb the update factory bin file is deleted, menu "update" is grey
if the book is not removed from usb, long press of the power button begins update process which fails with message: Update error

[hius07]

more report, just for testing
cannot install update_PW3_5.6.1.1_initial.bin on PW3 5.8.8 *jailed*

[knc1]

Originally Posted by hius07

more details
after safe removal from usb the update factory bin file is deleted, menu "update" is grey
if the book is not removed from usb, long press of the power button begins update process which fails with message: Update error

Originally Posted by hius07

more report, just for testing
cannot install update_PW3_5.6.1.1_initial.bin on PW3 5.8.8 *jailed*

Sounds like their improvements broke our jailbreak.

I will assume it is the same for all models, and fix-up the first jb post.

[jscris]

Have so been hoping there would be a new, larger screen kindle available that could be jailbroken before they figured out how to ruin it again. Although I can get along without most everything else, I need KindleLazy! Sure would like an 8" screen, though. <sigh>

[checkmermaid]

Originally Posted by knc1

That is, the jailbreak release of 07/04/2016, not the failure reports of 07/04/2016.


It may be that Amazon/Lab126 has been able to prevent our current jailbreak with the release of firmware 5.8.8 version.

The 5.8.8 version firmware is being pushed to all PW-2 and newer devices (all i.MX6 devices).

There is also one report that the current jailbreak process has new difficulties introduced with the 5.8.7.0.1 firmware release.

First 5.8.8 failure report by checkmermaid:
https://www.mobileread.com/forums/sh...postcount=1511

Please add success/failure reports to this thread.

Update:

I tried to stay connected with my PC, and hold the power/unlock key in order to force the Kindle to reboot. Luckily the system was able to boot into the update mode, but soon a "failure" notification jumped out said "update error: 16". This may explain something to the developers.

[madame_newbie]

To report in, Kindle Basic 2014 (KT2).

Prior to reset, the jailbreak allowed me to upgrade to 5.8.8. Had to reset because librarysync was not working only to find that it refuses to downgrade. Copying the .bin file and it will be deleted once ejected from PC, this is even after setting the .bin to 'read only'. Tried also a 'DO_FACTORY_RESTORE' to force downgrade but didn't work either.

[knc1]

Originally Posted by madame_newbie

To report in, Kindle Basic 2014 (KT2).

Prior to reset, the jailbreak allowed me to upgrade to 5.8.8. Had to reset because librarysync was not working only to find that it refuses to downgrade. Copying the .bin file and it will be deleted once ejected from PC, this is even after setting the .bin to 'read only'. Tried also a 'DO_FACTORY_RESTORE' to force downgrade but didn't work either.

How could I have made this clearer?

This is the ONLY TIME you should ever use the Reset menu entry in the lifetime of the device because it wipes out the jail break survival code that is about to be added in step 6 below.
NEVER AGAIN USE THE "Reset" MENU ENTRY. Never, ever, unless you intended to wipe out the jailbreak survival code. Which you really, really, need.

If one of our add-ins does not work, tell us about it, doing a 'reset' will not fix anything.

[madame_newbie]

Originally Posted by knc1

How could I have made this clearer?


If one of our add-ins does not work, tell us about it, doing a 'reset' will not fix anything.

Haha, lesson learned.

[knc1]

Originally Posted by madame_newbie

Haha, lesson learned.

Do you (or did you) have our "Rescue Pack" installed?

There is a recent thread here by someone that had to recover from a (Amazon CS required) "Reset" (on 5.8.8) using the Rescue Pack.

[madame_newbie]

Originally Posted by knc1

Do you (or did you) have our "Rescue Pack" installed?

There is a recent thread here by someone that had to recover from a (Amazon CS required) "Reset" (on 5.8.8) using the Rescue Pack.

Unfortunately, no.

[dhdurgee]

Originally Posted by knc1

Do you (or did you) have our "Rescue Pack" installed?

There is a recent thread here by someone that had to recover from a (Amazon CS required) "Reset" (on 5.8.8) using the Rescue Pack.

That leads to a speculation. Can the maintenance partition be started by the user even without the Rescue Pack installed? If so, I would think an approach could take advantage of that to do the jailbreak. Probably more user interaction required than the current methods, but it sounds like a means to the end.

Dave