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

[eschwartz]

Apparently, 5.6.1 is even meaner than we thought... talented!

[NiLuJe]

Oops. Did I forget to mention that I *thought* 5.6.1 worked around the 'partial' trick? My bad :/.

[Ruskie_it]

Originally Posted by NiLuJe

Oops. Did I forget to mention that I *thought* 5.6.1 worked around the 'partial' trick? My bad :/.

Well if you did, I didn't notice! But there is such a whole lot of 5.6.1 threads these days... more than I have time to read.
Well, if you only "thought" it, now you "know". It definitely does.
I don't know about the other method (that I can't even recall right now), 'cause I read it but I wasn't willing to go through it. :P

[NiLuJe]

@Ruskie_it: I vaguely remember seeing something wonky, and not having had time to check it out. Guess I don't need to anymore...

Note that I also have no idea if BDL is safe/effective on 5.6.x either...

[eschwartz]

Is it a different dl name, or a pre-dl cleanup?

[NiLuJe]

@eschwartz: No idea. I'm guessing cleanup, though.

[NiLuJe]

Okay, as promised earlier, here's an early winter break present .

PSA: All downloads have been moved to the Snapshots thread! (Under the "K5 JailBreak HotFix" listing).

If you've just successfully ran any iteration of a Factory JailBreak, this is your next step .
Alternatively, if you happened to be running a live, but outdated version of this JailBreak when you got a >= 5.6.x update, this package should get you back on track.

Download the latest package from the Snapshots thread, under the "K5 JailBreak HotFix" listing, and unpack it.
Copy the Update_jailbreak_hotfix_1.16.N_install.bin file to the root directory of your Kindle.

Now, eject & unplug your Kindle, and go to [HOME] -> [MENU] > Settings -> [MENU] > Update Your Kindle. If the update is successful, you're golden. If it fails, it probably means you weren't properly jailbroken before the update, in which case, you're still screwed.

----

If you're coming straight from the 5.6.5 JB or the Factory Downgrade threads and you completely skipped the first post of *this* thread, be aware that on FW >= 5.5.x (i.e., you), using MRPI is REQUIRED to install every other custom packages!

[gianpaoloc]

Dear NiLuJe,
as I said in a previous message, I had a jailbroken PW2 with 5.4.5.1 version, with jailbreak 1.10.N and the corresponding bridge (and usbnetwork "0.16.N-r10711") installed. A few days ago my PW2 updated to 5.6.1 so I lost my JB.

Now I tested your new hotfix above and it was recognized. I could go with the usual "[HOME] -> [MENU] > Settings -> [MENU] > Update Your Kindle" sequence and my PW2 rebooted. Now, how may I test if I recovered my JB? I tried to install latest usbnetwork hack "kindle-usbnet-0.18.N-r11218.tar.xz" but in this case, when I do "[HOME] -> [MENU] > Settings -> [MENU]", the "Update Your Kindle" option is grayed out. Does this mean I was not able to recover my JB?

Anything may I test?

Thanks in advance

[GoSharks]

@gianpaoloc-
I'd bet the jailbreak worked...try installing other things via the KUAL MRInstaller extension...should work.

@NiLuJe- 'You can't stop the signal, Mal' !!...

[Ruskie_it]

Originally Posted by gianpaoloc

Dear NiLuJe,
as I said in a previous message, I had a jailbroken PW2 with 5.4.5.1 version, with jailbreak 1.10.N and the corresponding bridge (and usbnetwork "0.16.N-r10711") installed. A few days ago my PW2 updated to 5.6.1 so I lost my JB.

I am curious... if 5.6.1 deletes "old" .bin files on eject (so that hacks can't be installed without using mrinstaller), how is this new jb recognized?

[NiLuJe]

@gianpaoloc: As @GoSharks mentioned, if the update was successful (that the Kindle restarted is only an indication the update *attempted* to run, what we care about is the final result of the update process, before the reboot), use MRPI to install your packages (cf. the full 5.6.x notice if the first post).

@Ruskie_it: By being packaged differently, in a way that makes FW 5.6.1.x mostly happy.

[mfirewire]

Originally Posted by NiLuJe

Okay, as promised earlier, here's an early winter break present .

If you happened to be running a live, but outdated version of the JailBreak when you got the 5.6.x update, this package should get you back on track.

Download the attached zip file, and unpack it.
Copy the Update_jailbreak_1.14.N_install.bin file to the root directory of your Kindle.

Now, eject & unplug your Kindle, and go to [HOME] -> [MENU] > Settings -> [MENU] > Update Your Kindle. If the update is successful, you're golden. If it fails, it probably means you weren't properly jailbroken before the update, in which case, you're still screwed.

@NiLuJe Great! this hotfix works for me. I've jailbroken KPW2 on 5.4.3.2 with 1.10.N. And it silently OTA to 5.6.1. Now I am jailbroken AGAIN!

Thanks!

[eschwartz]

Originally Posted by NiLuJe

Okay, as promised earlier, here's an early winter break present .

If you happened to be running a live, but outdated version of the JailBreak when you got the 5.6.x update, this package should get you back on track.

Download the attached zip file, and unpack it.
Copy the Update_jailbreak_1.14.N_install.bin file to the root directory of your Kindle.

Now, eject & unplug your Kindle, and go to [HOME] -> [MENU] > Settings -> [MENU] > Update Your Kindle. If the update is successful, you're golden. If it fails, it probably means you weren't properly jailbroken before the update, in which case, you're still screwed.

Thanks for all your hard work!

[pghaworth]

NiLuJe - Thanks for making Christmas just a bit more merry for a lot of folks!

[satchmo]

Originally Posted by NiLuJe

Okay, as promised earlier, here's an early winter break present .

If you happened to be running a live, but outdated version of the JailBreak when you got the 5.6.x update, this package should get you back on track.

Download the attached zip file, and unpack it.
Copy the Update_jailbreak_1.14.N_install.bin file to the root directory of your Kindle.

Now, eject & unplug your Kindle, and go to [HOME] -> [MENU] > Settings -> [MENU] > Update Your Kindle. If the update is successful, you're golden. If it fails, it probably means you weren't properly jailbroken before the update, in which case, you're still screwed.

Zat you, Santa Claus?
Big thank!