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

[NiLuJe]

You don't need to flash anything, or an SSH access anywhere.

You just need to be able to boot into diags, and have access to the userstore. Drop the jailbreak (either one [tar.gz or stgz], at least on the diags version on my PW, although the number of reboots needed to trigger it might be different between one and the other, I didn't check) in the userstore, (re)boot once or twice into diags, and voilà.

If you broke your rootfs, but you still have access to the userstore, and no SSH in diags, you can try to just drop the official 5.3.0 update in the userstore and reboot, IIRC, it doesn't care (much) what state the partition is in, it will reflash it.

[awh_tokyo]

Thank you, that seems to have done it! Now, is there anything else I should do while I have access to the serial console, or can I close my Kindle back up?

[NiLuJe]

@awh_tokyo: If you have confirmed that both main & diags boot properly, and that main is on 5.3.0 & jailbroken, then, no, I don't think so, at least from a SW POV .

[prnoct90]

I just got a Kindle Paperwhite that was unfortunately already at 5.3 when it arrived. Is there no solution for the time being?

[awh_tokyo]

I think the only way for the time being involves taking the unit apart and soldering three leads to the board so you can access the serial console during boot. Whether you are comfortable with that, I'll leave as an exercise for the reader.

[ixtab]

Originally Posted by prnoct90

I just got a Kindle Paperwhite that was unfortunately already at 5.3 when it arrived. Is there no solution for the time being?

No, not for the time being. (Except for taking it apart and accessing it via serial port).

I'm still actively searching for a new exploit, and I hope that a few others here do as well. I found a few minor glitches which allow to delete some files, or to create empty files (but unfortunately, part of the filename is fixed, which renders it useless). IOW: none of that allows for a full-fledged jailbreak (yet?).

[dos1]

Originally Posted by ixtab

No, not for the time being. (Except for taking it apart and accessing it via serial port).

I'm still actively searching for a new exploit, and I hope that a few others here do as well. I found a few minor glitches which allow to delete some files, or to create empty files (but unfortunately, part of the filename is fixed, which renders it useless). IOW: none of that allows for a full-fledged jailbreak (yet?).

Could you share your findings? (maybe in some dedicated topic) Getting more eyes to look at those glitches may result in finding some different, but now successful approach

[ixtab]

Originally Posted by dos1

Could you share your findings? (maybe in some dedicated topic) Getting more eyes to look at those glitches may result in finding some different, but now successful approach

That's being discussed in a "conspirative inner circle" via PMs - it's not a good idea to discuss this in the public forums (IMO).

But yeah... I'll ask the other folks if anybody objects to you taking part in the discussion

[knc1]

Originally Posted by dos1

Could you share your findings? (maybe in some dedicated topic) Getting more eyes to look at those glitches may result in finding some different, but now successful approach

This is not the place for such findings.
We certainly do not want to teach lab126 how to do their job better.

Secure chat, or non-general public web site is the place for that stuff.

A lot of us run their own web sites, not associated with Kindles.

[dos1]

Originally Posted by ixtab

That's being discussed in a "conspirative inner circle" via PMs - it's not a good idea to discuss this in the public forums (IMO).

But yeah... I'll ask the other folks if anybody objects to you taking part in the discussion

Originally Posted by knc1

This is not the place for such findings.
We certainly do not want to teach lab126 how to do their job better.

Secure chat, or non-general public web site is the place for that stuff.

A lot of us run their own web sites, not associated with Kindles.

I see, point taken