Kindle Touch/PW1/PW2 5.0.x - 5.4.4.2 JailBreak. Plus FW 5.x USBNetwork.

[Glover]

On Kindle Touch 3G after update try I see always 'Error 007'. Can't update/jailbreak with this pack my Kindle.

[NiLuJe]

@Glover: Don't reboot with a custom .bin file, always use the "UYK" link in the settings.

[Glover]

Thx - it's done.

[chrispoupart]

So it would seem that I improperly disabled OTA updates. Last night, 5.6.1.0.4 was pushed to my Paperwhite 2, and the it would seem that the previously functional fix for this does not work this time around.

Does anyone have any ideas? Do you think that it would be possible/worth it to downgrade to another 5.6.x version and try again?

Thanks!

[knc1]

Originally Posted by chrispoupart

So it would seem that I improperly disabled OTA updates.

Last night, 5.6.1.0.4 was pushed to my Paperwhite 2, and the it would seem that the previously functional fix for this does not work this time around.

Does anyone have any ideas?
Do you think that it would be possible/worth it to downgrade to another 5.6.x version and try again?

Thanks!

What method of disabling OTA updates did you use?
What was the prior version of the firmware that the OTA disabling did not protect?

^^ We do need to know these things, please answer.

- - - -

Version 5.6.x is protected from "downgrade attacks" (Lab126's phrase for it - its error code 12).

So downgrading is not possible (if the prior jb wasn't bridged, can't be fixed, and the serial port can't be used).

[chrispoupart]

Originally Posted by knc1

What method of disabling OTA updates did you use?
What was the prior version of the firmware that the OTA disabling did not protect?

^^ We do need to know these things, please answer.

I honestly do not remember what method of disabling OTA updates I used.

As for the firmware, it was the previous stable version that had been pushed out OTA.

A bit of back history: I jailbroke the firmware when it was running 5.4.x. I never disabled the OTA updates, and then it updated to 5.6.x (whatever I was running before this last OTA update).

I was not happy about that, but glad to see the fix that was provided here. It restored my jailbreak. I updated my KUAL, installed a couple of other mods (fonts, screensavers, pdf reader) and thought that I had disabled OTA updates using KUAL (backdoor lock maybe?), but clearly I did not.

The jailbreak was working on a 5.6.x firmware, if that helps. Perhaps best to assume that I /didn't/ do any OTA blocking, because I can't find any trace of it on my system at the moment. I am a bit sleep deprived with a baby at home right now, so it is possible that it was still on my "todo" list.

[knc1]

Originally Posted by chrispoupart

I honestly do not remember what method of disabling OTA updates I used.

- - - - -

thought that I had disabled OTA updates using KUAL (backdoor lock maybe?), but clearly I did not.

- - - - -

That reads as if you did not re-install the backdoor lock with the most recent version after the initial update to series 5.6.x firmware.

It is only the most recent backdoor lock that is effective on any of the 5.6.x firmwares.

[chrispoupart]

Originally Posted by knc1

That reads as if you did not re-install the backdoor lock with the most recent version after the initial update to series 5.6.x firmware.

It is only the most recent backdoor lock that is effective on any of the 5.6.x firmwares.

That is very possible. Though, also not helpful to getting back to a functional jailbreak.

I think that it is safe to assume that I did not have an up-to-date block for OTA, and now it has burned me.

As far as I can tell, my previous jailbreak was properly bridged. In an ideal world, the Update_jailbreak_1.14.N_install.bin fix should have worked again, but alas, that does not seem to be the case.

[knc1]

Originally Posted by chrispoupart

That is very possible. Though, also not helpful to getting back to a functional jailbreak.

I think that it is safe to assume that I did not have an up-to-date block for OTA, and now it has burned me.

As far as I can tell, my previous jailbreak was properly bridged. In an ideal world, the Update_jailbreak_1.14.N_install.bin fix should have worked again, but alas, that does not seem to be the case.

Ah, but it does make it un-neccessary for our developers to try to fix something that isn't broke (the most recent backdoor lock version).
Although it does not get you closer to a working jailbreak now, it is important information for us to have here, on-site.

It is still possible that the jailbreak "hot fix" may need to be updated for this version of the firmware.

[chrispoupart]

Originally Posted by knc1

Ah, but it does make it un-neccessary for our developers to try to fix something that isn't broke (the most recent backdoor lock version).
Although it does not get you closer to a working jailbreak now, it is important information for us to have here, on-site.

Fair. I thought that I had made it clear that I did not do the OTA block properly, but I do understand the need to double-check from a developer standpoint.

Originally Posted by knc1

It is still possible that the jailbreak "hot fix" may need to be updated for this version of the firmware.

If it helps any, after applying the "hot fix", the "mkk" folder on my kindle is there along with the new timestamps. It has the usual files (bridge, keystore, gandalf, etc).

Just... no successful jailbreak.

[NiLuJe]

@chrispoupart: I'm gonna need way more details than "does not work" .

[Ruskie_it]

Originally Posted by NiLuJe

@chrispoupart: I'm gonna need way more details than "does not work" .

These developers are getting more and more demanding every passing day...

[Doitsu]

Is it safe to install the lastest PW2 5.6.1.0.4 update on a jail-broken PW2 with 5.6.1.0.2?

[NiLuJe]

@Doitsu: Theoretically ^^.

[chrispoupart]

Originally Posted by NiLuJe

@chrispoupart: I'm gonna need way more details than "does not work" .

I would be happy to provide you with any and all more details. Is there a FAQ on how/what I should be providing?

What I can say is that I can apply the afore mentioned "hotfix", which installs successfully. The Kindle reboots... and then nothing. By "nothing", I mean no jailbreak. The kindle boots up just fine. But none of the jailbreak hacks work (no screen savers, no fonts, kual doesn't load, etc).

This is a Paperwhite 2 going from (if I remember correctly) 5.6.1.0.2 to 5.6.1.0.4 via a forced OTA update.

What else can I provide you with? (I am a senior linux sysadmin, so feel free to get technical. I just am not all that familiar with the underbelly of the kindle operating system or jailbreak!).