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

[knc1]

A UUID or a hash-sum of some kind?

Sounds like they are getting ready to filter Amazon vs. Mobileread update packages with an on-device of "acceptable" update_hashsum.bin list.

Well, as long as they don't break our 5.4.+ downgrader ...

- - - -

Sure would be interesting to know how much money Amazon has spent fighting device ownership by the device owners.

[eschwartz]

Originally Posted by NiLuJe

@eschwartz: It does, but that's mostly harmless in those cases (besides the 'update' vs. 'Update' thing I mentioned). .

Oh -- so it's "fixed" just by renaming the Updates?

Originally Posted by williamrochira

@NiLuJe

Thanks fr the KUAL thread recommendation, downloading to my heart's content ;-)

Do you know anything about the backdoorlock? (https://www.mobileread.com/forums/sho...d.php?t=205666) Is it safe?

Will

BackDoorLock is safe.

Kindle Touch Hacking#Blocking_Official_Updates explains it (and the easy way) quite nicely.

[NiLuJe]

@eschwartz: No, what I meant was that FW 5.4.5 renames everything to update_*, even if it started out as Update_*. Which reintroduces the possibility of rebooting with custom update packages and hitting the factory updater, instead of the OTA one.

[knc1]

A totally false alarm, my bad.

[afterbox]

Anyone know how to make kterm run a shell script on start?

I tried adding "-e sh start.sh" as a parameter in kterm.sh, but nope, didn't work.

Will.

EDIT: Never mind. I had PARAM='-e "sh start.sh"' but bash was parsing the speech marks, so I fixed it with PARAM="-e \"sh start.sh\""

[readandread]

So if I'm already jailbroken on Kindle PW2 and upgrade to the newest firmware I don't have to reinstall the kindlet or anything else - just update the FW and keep and reading on my rooted Kindle, right?

[NiLuJe]

@readandread: Not exactly. It's still a full update, the usual caveats apply, check the FAQ.

[afterbox]

Hi again guys. Does anyone know how to set kernel variables for the PW?

Will.

EDIT: Can I just execute the command "sysctl -w parameter=1" ? Or is this too dangerous...

[eschwartz]

Originally Posted by williamrochira

Anyone know how to make kterm run a shell script on start?

I tried adding "-e sh start.sh" as a parameter in kterm.sh, but nope, didn't work.

Will.

EDIT: Never mind, it was my idiocy once again. I had PARAM='-e "sh start.sh"' but bash was parsing the speech marks, so I fixed it with PARAM="-e \"sh start.sh\""

Why not just run start.sh before you run kterm? It will inherit the environment of kterm.sh.

Using params never worked for me.

[afterbox]

@eschwartz

Tried it, didn't work. This works, 'sall good ;-)

[Doitsu]

Originally Posted by readandread

So if I'm already jailbroken on Kindle PW2 and upgrade to the newest firmware I don't have to reinstall the kindlet or anything else - just update the FW and keep and reading on my rooted Kindle, right?

Didn't work on my machine. You can still read your books, but KUAL no longer displays kindlets and a MKK re-install failed.

Originally Posted by NiLuJe

ANT notice to FW >= 5.4.5 users:

This will NOT work on FW >= 5.4.5!
Currently, it does survive an update to 5.4.5 though, so, if you intend to update to 5.4.5, JailBreak your device first .
If your device shipped on 5.4.5 or newer, for now, you're, err, screwed, sorry.

Are you 100% sure that jailbroken devices survive the 5.4.5 firmware update?
I've just updated my PW2 to 5.4.5 and got a "Mobileread Kindlet Kit is not installed" error message after running KUAL.
I've tried to re-install MKK but got a 007 update error, which, AFAIK, is usually displayed on non-jailbroken devices.

Is the fact that I can at least execute KUAL an indicator that my PW2 is still jailbroken or am I out of luck?

Originally Posted by NiLuJe

@readandread: Not exactly. It's still a full update, the usual caveats apply, check the FAQ.

I did read the FAQ, but I'm still confused as to what to do now. Do I simply need to re-install the full jail-break or will I need to wait for a possible MKK update for PW2s with 5.4.5 firmware.

[rupor]

Doitsu, I installed 5.4.5 on top of jailbroken 5.4.3.2 - jailbreak survived. Re-installed of MKK, USBNet and KUAL. Now everything is exactly as it was before the upgrade. I did not test every feature of course, but whatever I use - works.

[NiLuJe]

@Doitsu: I'm sure -- provided you've never done a factory reset after installing the jailbreak. Will add that to the first post, my bad :/.

And nope, being able to *try* to launch KUAL (or any Kindlet) isn't related to the JB.

I'll look into downgrade possibilities later, but that doesn't look terribly promising.

As for the usual 'What To Do After An OTA Update' question, the answer is basically to just reinstall your stuff, except for the JB (unless an updated JB is necessary, which happened when 5.4 hit the PW1, for example).

[Doitsu]

Originally Posted by NiLuJe

@Doitsu: I'm sure -- provided you've never done a factory reset after installing the jailbreak. Will add that to the first post, my bad :/.

I'm pretty sure that I've never done a factory reset and all KUAL kindlets were working prior to the firmware update.

Originally Posted by NiLuJe

And nope, being able to *try* to launch KUAL (or any Kindlet) isn't related to the JB.

Is there any other simple test to find out if the Kindle is still jail-broken? (I haven't installed USBNet and other developers' tools, except for Python and MKK, which were required for the KUAL font override.)

[NiLuJe]

@Doitsu: No, installing a custom package is really the best way to check. And a U007 error indeed is the kiss of death in this instance :/.

On the off-chance something wonky happened, try restarting your device, but I'm not hopeful, since that already happened after both the official update and any other failed update attempts.