5.3 Update for Paperwhite -- will it interfere with the jailbreak?

[knc1]

Originally Posted by knc1

While your doing that, I will audit the sources of 5.2 and 5.3 for changes.

For myself, the next working Kindle I have is going to get that OTA updater name replaced with a symlink to /bin/true.

The two source code bundles have identical contents:

core2quad kpw $ diff -ru 5.2.0_1729740065  5.3.0_1774700020
core2quad kpw $

But since it is a full "recovery image" - it should be runnable under emulation.

[xbingo]

so, is it save to upgrade the firmware without uninstall the previous jailbreak?
The new features that supporting simplified chinese are so attactive to me!

[xbingo]

Originally Posted by xbingo

so, is it save to upgrade the firmware without uninstall the previous jailbreak?
The new features that supporting simplified chinese are so attractive to me!

sorry for my pool English

[CrazyCoder]

Is there a list of hosts Kindle is using to check/download updates from Amazon so that I can block it via /etc/hosts?

Edit: trying to block it via
127.0.0.1 todo-g7g.amazon.com
in /etc/hosts on Kindle per https://www.mobileread.com/forums/sho...9&postcount=14

[knc1]

@xbingo: There is no jailbreak for 5.3.0 (yet) and the update from 5.2.0 to 5.3.0 will over-write the entire image, including any hacks.

@crazycoder: That way is not certain and can be defeated in minutes by Amazon. Block the communications in iptables instead.

[eureka]

Originally Posted by NiLuJe

On a somewhat related note, one convoluted way to update to 5.3.0 for devs would be to boot to diags, flash the rootfs & kernel from the unpacked update, and manually reapply the jailbreak/usbnet on main. The entry point is plugged, but AFAICT, if we manage to put the stuff back in, most of the simple things should still work. If you mess up, you potentially only get one shot, though, ;D.

5.3.0 still runs /var/local/system/fixup and/or /var/local/system/onetimefixup (if they were found). And /var/local isn't overwrited by update.

[NiLuJe]

@eureka: Good point, and way easier, to boot ;-). (And I already have something mostly written from the PW release frenzy...).

[ixtab]

... but that still leaves the question of how to write a file to /var/local... (Essentially, that's what the data.(tar.gz|stgz) files did, but that hole is closed now.

Seems like Amazon has now officially declared war on us.

As foreseeable as that was, it's still a pity that companies keep employing the same idiotic and short-sighted strategy of trying to lock their customers in, instead of providing an open (or at least "openable") environment which allows for open development.

I'll keep my PW shutdown and in Airplane mode until we find some way to crack open the 5.3.0 firmware. (I'll still manually download it and look through it).

[knc1]

Originally Posted by ixtab

... but that still leaves the question of how to write a file to /var/local... (Essentially, that's what the data.(tar.gz|stgz) files did, but that hole is closed now.

The support for the requirement that those files be signed was in the original Kpw firmware. I just didn't think to mention it.

In answer to that question:
It would (will?) require a 5.2.0.a hack to put our code into that location in a way which makes it still usable after the update to 5.3.
Prior to doing the update to 5.3.0.
It would also be necessary to confirm that user additions to that part of the directory tree don't get scrubbed by the handling of the md5sum file manifest.

[NiLuJe]

@ixtab:

Yep, what knc1 said. Eureka & I meant that this was (possibly) usable for JailBroken 5.2.0 users to 'carry over' the jailbreak into 5.3.0 .

'Cracking' 5.3.0/getting into USB downloader mode would still be preferable, of course .

[ixtab]

Originally Posted by knc1

The support for the requirement that those files be signed was in the original Kpw firmware. I just didn't think to mention it.

In answer to that question:
It would (will?) require a 5.2.0.a hack to put our code into that location in a way which makes it still usable after the update to 5.3.
Prior to doing the update to 5.3.0.

Yes, but this will only help for people who actually still run 5.2.0, and are aware of the situation. It won't help folks who got their PW shipped with 5.3.0, or who already went through the auto-update without being aware that it's also an auto-lockdown. We need to find a proper solution for "vanilla" 5.3.0. I guess that it's time to get our hands dirty and try to find another exploit.

It would also be necessary to confirm that user additions to that part of the directory tree don't get scrubbed by the handling of the md5sum file manifest.

That's highly improbable. First, /var/local/ is a different partition, and second, it only contains user data. Wouldn't make sense to expect any particular state there.

[NiLuJe]

@ixtab: Yeah... Especially since I'm suspecting the soon-to-be-released Japanese device will ship on 5.3.0 ;'(.

[knc1]

Originally Posted by ixtab

That's highly improbable. First, /var/local/ is a different partition, and second, it only contains user data. Wouldn't make sense to expect any particular state there.

Highly improbably or not, it should still be checked.
I do not believe that if: "it makes sense" or not is in the Amazon design qualifications.

And since the system firmware does check for specific things in that part of the tree the system does expect certain specific states there.
Perhaps not exclusively, but still that is one or more particular states.

[addmyn]

Originally Posted by knc1

Not a problem, we have the original 5.2.0 images posted.
You should be able to downgrade with them until 5.3.0 is dealt with.

where's the download link?

[ixtab]

Originally Posted by addmyn

where's the download link?

In the first post of the "simple debricking" sticky.