View Single Post
Old 07-03-2013, 11:10 AM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
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
@gmask: You're gonna need to remember exactly *which* jailbreak you used, because if you tried my latest uninstaller and your device is still jailbroken, then it wasn't mine .

Hint: https://www.mobileread.com/forums/sho...d.php?t=122519

And *restart* your Kindle after the uninstall.

@knc1: The FW 3.x jailbreaks are trickier than that . There's no concept of dev private key, so we're bind-mounting our custom key on top the one of Amazon's one dynamically, right before the updater launches, if we detect a custom update package .

That means some versions have a 'broken' uninstaller that doesn't restore the default keys after the uninstall process, hence the need for a full restart to kill the bind mount.
NiLuJe is offline   Reply With Quote