5.6.5 Jailbreak (closed-kindle) -- released! - Page 56

pdurrant · 03-02-2016, 10:55 AM

Quote:

Originally Posted by catharsys

Sorry, what I meant is that if I have a jb 5.6.5 device and it auto-updates to 5.7.2.1 will the jabilbreak survive?

Yes. You'll need to reinstall some of the hacks, but the jb itself survives so that they can be reinstalled.

knc1 · 03-02-2016, 10:56 AM

Quote:

Originally Posted by catharsys

Sorry, what I meant is that if I have a jb 5.6.5 device and it auto-updates to 5.7.2.1 will the jabilbreak survive?

Yes . .
See:: https://www.mobileread.com/forums/sho...&postcount=824

HarryT · 03-02-2016, 10:58 AM

Quote:

Originally Posted by catharsys

Sorry, what I meant is that if I have a jb 5.6.5 device and it auto-updates to 5.7.2.1 will the jabilbreak survive?

In the post that you quoted, knc1 clearly stated this to be the case:

Quote:

You can let it auto-update - - the jailbreak will survive the experience.

Firmware updates do not affect jailbreaks.

catharsys · 03-02-2016, 10:59 AM

Thank you all for the help and information

knc1 · 03-02-2016, 11:01 AM

Cinisajoy · 03-02-2016, 11:20 AM

Quote:

Originally Posted by knc1

Putting a pillow on that wall so you don't hurt your head.

booklover6 · 03-02-2016, 03:23 PM

As long as you DON'T Factory Reset.

HarryT · 03-02-2016, 03:27 PM

Quote:

Originally Posted by booklover6

As long as you DON'T Factory Reset.

I'm pretty sure that a factory reset has no effect on a jailbreak. I'm sure someone will correct me if I'm wrong

.

NiLuJe · 03-02-2016, 03:39 PM

It has a directly devastating effect, which can be mitigated with some manual intervention and craftily applied backups (with the current jailbreak generation).

So, good as a last resort only.

HarryT · 03-02-2016, 03:52 PM

Thank you for the correction

. I'm a little puzzled by why it should affect it, though. I didn't think a Factory Reset did anything to the system partition.

NiLuJe · 03-02-2016, 04:00 PM

It doesn't, but it wipes the userstore and varlocal, and we need both to various degrees

.

HarryT · 03-02-2016, 04:15 PM

Ah, thank you. Yes, that would indeed explain it

.

eschwartz · 03-02-2016, 04:22 PM

Quote:

Originally Posted by HarryT

Thank you for the correction

. I'm a little puzzled by why it should affect it, though. I didn't think a Factory Reset did anything to the system partition.

That is probably because you don't know how the jailbreak works internally. (And why would you have cause to learn?)

It has become complex in order to deal with changing situations and for robustness.

...

It includes the MKK (kindlet dev keys, needed for e.g. KUAL)
"gandalf", your friendly neighborhood passwordless su binary.
The original jailbreak certificate.
The scripts which try to restore all the pieces as and when needed.

This is mostly kept in /var/local/ which handles registration -- and gets wiped during a Reset.
The semi-automated backup emergency fix relies on the userstore, which also gets wiped on a reset.
The MKK is purged whenever you cycle your registration (because only the Kindlet developer should have his private dev keys installed, right?

)

The upstart job which can fix a heavily borked jailbreak, gets wiped by a firmware update.

Factory Reset + firmware update == kiss of death.
Factory Reset alone ==

urgent manual intervention is needed to restore a working operation.

dodger666 · 03-04-2016, 07:52 PM

KT2 just OTA updated to 5.7.2.1, reinstalled the screensaver update and all is right with the world again...

jsheahawk · 03-07-2016, 07:27 PM

Quote:

Originally Posted by knc1

Keep in mind this is FAT32 (case preserved, case insensitive) -

Study of the file system contents after the initial factory update completes shows the filename in-use was:
UPDATE~1.BIN
(the 8.3 format name of a long file name and no long file name found).

And that FAT-32 is not an inode based system, mounted into a file system tree that expects an inode based system -

Translation: The driver munges up the missing information during read/write of a file or directory name.
What you see is not always what is recorded on the media.

How that munging is done and what gets munged depends on what options where passed to the VFAT driver when the FAT file system was mounted.

In the case of USB storage viewed from the outside (USB cable) it gets a little bit more obscure, you are looking at the media through two drivers (plus whatever is on the PC end of the cable):
/mnt/us -> fuse driver -> /mnt/base-us -> VFAT driver -> media

**BUT** an uppercase, 8.3 format name using the characters from 7-bit ASCII **should** pass through that mess un-touched *in name* (the drivers will still fake up the ownership, permissions, and times).

Making directory names is cheap - -
Add "UPDATE~1.BIN" to the list of directory names your going to make in the root of USB storage.

- - - -

Which may just force the OTA updater to use: UPDATE~2.BIN (or UPDATE~?.BIN in its look-up. I haven't done any testing on if it can handle that situation).

I have successfully jailbroken (THANKS!), and I've been playing with blocking auto-updating. I added several (because why not) folders to the root directory, and I noticed that /update.bin/ gets deleted when you turn off airplane mode. I added the file /update.bin/update.bin to the directory, and that seems to stop it when I turn off airplane mode. I have no idea what this means/does...if anything.

And I do realize that the JB will survive the update, but I'm just posting this for conversation's sake.

Thanks for the JB!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
KINDLE DEAL: Released: A Story of God’s Power Released in Pro Baseball ($	gospelebooks	Deals and Resources (No Self-Promotion or Affiliate Links)	0	07-14-2011 09:12 PM
iPad iPad jailbreak released	scottjl	Apple Devices	25	05-08-2010 02:20 PM

03-02-2016, 10:59 AM	#829
catharsys Junior Member Posts: 9 Karma: 10 Join Date: Feb 2016 Device: Kindle Paperwhite 3 wifi	Thank you all for the help and information

03-02-2016, 11:01 AM	#830
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA

03-02-2016, 03:23 PM	#832
booklover6 Grand Sorcerer Posts: 6,545 Karma: 14008730 Join Date: May 2008 Location: PA (USA) Device: Kobo Clara, 2E, Libre 1, PW4, PW5, 2022 Kindle, Kobo Libre Colour	As long as you DON'T Factory Reset.

03-02-2016, 03:39 PM	#834
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	It has a directly devastating effect, which can be mitigated with some manual intervention and craftily applied backups (with the current jailbreak generation). So, good as a last resort only.

03-02-2016, 03:52 PM	#835
HarryT eBook Enthusiast Posts: 85,556 Karma: 93383099 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Thank you for the correction . I'm a little puzzled by why it should affect it, though. I didn't think a Factory Reset did anything to the system partition.

03-02-2016, 04:00 PM	#836
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	It doesn't, but it wipes the userstore and varlocal, and we need both to various degrees .

03-02-2016, 04:15 PM	#837
HarryT eBook Enthusiast Posts: 85,556 Karma: 93383099 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Ah, thank you. Yes, that would indeed explain it .

03-04-2016, 07:52 PM	#839
dodger666 Banned Posts: 6 Karma: 10 Join Date: Feb 2016 Device: KT2	KT2 just OTA updated to 5.7.2.1, reinstalled the screensaver update and all is right with the world again...

Advert

Advert