Jailbreak lost after 5.7.3 reset

[irreld]

I updated my PW2 to 5.7.3 with jailbreak adn re-installed everything. Then I found cvm was draining my battery, so I did a factory reset as usual.

However the 'mkk banner' did NOT appear in my next reboot, which was supposed to be Then I tried to install the 'bridge' and forced a reboot, nothing happened.

Does that mean I've lost my jailbreak and I have to get a serial port connection to jailbreak or to downgrade?

Spoiler:

Amazon is always making things harsher than ever. But I have to stick within its loop because I heavily rely on 3rd party stuff. sad.

[Cinisajoy]

If you factory reset after the jailbreak, you literally put the device back to its defaults.

If you got lucky and it reset to 5.6.5 you can redo the jailbreak. If it is on 5.7 + then no jailbreak is possible at the moment.

[eschwartz]

Assuming you were running the latest (1.14.N) jailbreak, you just need to copy some backups ( rp/ && mkk/ ) to the userstore and reboot a few times.

The problem with a Factory Reset is that it wipes the partition which stores the jailbreak, MKK, and "gandalf" addon.
Yes, recent versions are resilient with an upstart script which can restore the jailbreak -- but that requires manual intervention, cf. the very great importance of MKK and gandalf.

A combination of Factory Reset followed by firmware update is an unilateral destruction of the jailbreak, with NO hope of recovery (unless your firmware can be jailbroken from scratch).
Avoid this at all costs.


tl;dr
Factory reset is BAD. If at all possible (unless of course something is seriously wrong with the Kindle, but you'd know if that were the case ), you should look for other solutions like manually deleting your documents and Search Index folders.

[NiLuJe]

Simply reinstalling the hotfix should also do the trick.

[knc1]

Originally Posted by irreld

I updated my PW2 to 5.7.3 with jailbreak adn re-installed everything. Then I found cvm was draining my battery, so I did a factory reset as usual.
- - - -

Now would be a good time to change your usual habits, at least that one.
Perhaps give up 'factory reset' for Lent?

How did you determine that it was cvm that was draining your battery?
That is a question being looked into at the moment.
So any information on your methods and findings might help.

[irreld]

Originally Posted by knc1

How did you determine that it was cvm that was draining your battery?
That is a question being looked into at the moment.
So any information on your methods and findings might help.

Yeah, That's REALLY a bad habit. Now I realized kindle is NOT as easy-going as any of my Android device.

After OTAed to 5.7.3 from 5.7.2.1 my battery only lasted two days with almost no use. So ps -e to find cvm using more cpu time than usual. vmstat said only 89% time cpu is idle. That's weird, and no index was seeming to be rebuilt. It seemed something prevented kindle to sleep. When I deleted my 120+ books, I even found several files won't delete from Windows.

That's all my experience, and finally, a factory reset ruined everything. Ah.

BTW backdoorlockhack somehow failed to keep me in 5.7.2

[NiLuJe]

FTR, a factory reset is in fact liable to cause *more* battery drain than simply doing nothing, so better let the device churn for a while, sucking energy plugged to a wall charger...

[knc1]

Originally Posted by irreld

Yeah, That's REALLY a bad habit. Now I realized kindle is NOT as easy-going as any of my Android device.

After OTAed to 5.7.3 from 5.7.2.1 my battery only lasted two days with almost no use. So ps -e to find cvm using more cpu time than usual. vmstat said only 89% time cpu is idle. That's weird, and no index was seeming to be rebuilt. It seemed something prevented kindle to sleep. When I deleted my 120+ books, I even found several files won't delete from Windows.

That is (was) a PW-2 on 5.7.3 - similar to other reports here.

Also observed on my PW-3 on 5.6.1.1 - as high as 98% cpu time used while showing a screen saver.
After indexing 4 books (not 120).

See:
https://www.mobileread.com/forums/sho...0&postcount=33

Use the top command embedded in that post to see the framework threads (including the cvm threads).

1) The indexer was re-designed (well, at least re-implemented) with the 5.6.x series firmware and may still not be a 'stable' implementation (translation: lab126 may still be playing with it).

2) The old "search for garbage" test to see if the indexer is done no longer works (since the new indexer never really stops - it is just throttled now).

Originally Posted by irreld

That's all my experience, and finally, a factory reset ruined everything. Ah.

BTW backdoorlockhack somehow failed to keep me in 5.7.2

Firmware since early in the 5.6 series (5.6.2...?) is known able to defeat the backdoor lock.

But this (revised old one) does work on 5.6.5 and is being tested on 5.7.x:
https://www.mobileread.com/forums/sho...&postcount=269

See post 4 of this thread if you haven't already seen it.

Note: Only the color Kindles run Android.
The grayscale devices run "Amazon Linux".

[irreld]

Originally Posted by eschwartz

Assuming you were running the latest (1.14.N) jailbreak, you just need to copy some backups ( rp/ && mkk/ ) to the userstore and reboot a few times.

Too bad I ve lost my backup of mkk.

A good lesson for all to remember to backup important files.

[irreld]

Originally Posted by knc1

Use the top command embedded in that post to see the framework threads (including the cvm threads).

Top command needs extra terminal definition files in /usr/share/terminfo since 5.6.x on my PW2. Maybe @NiLuJe should include then in his USBNetworking hack.

Bought usb-ttl cable, preparing my soldering iron, and swear not to be so stupid again.

[knc1]

Originally Posted by irreld

Top command needs extra terminal definition files in /usr/share/terminfo since 5.6.x on my PW2. Maybe @NiLuJe should include then in his USBNetworking hack.

Bought usb-ttl cable, preparing my soldering iron, and swear not to be so stupid again.

It should not in single pass batch mode - use the: -bn1 option shown.

Plus - it is included in USBnetworking (to support htop and nano) -

[root@kindle us]# find . -name terminfo
./usbnet/etc/terminfo

[root@kindle us]# ls -ld /usr/bin/top /usr/bin/htop /usr/share/terminfo
lrwxrwxrwx    1 root     root            23 Dec 31  2014 /usr/bin/htop -> /mnt/us/usbnet/bin/htop
-rwxr-xr-x    1 root     root         48771 Apr 15  2015 /usr/bin/top
drwxr-xr-x    6 root     root          1024 Apr 15  2015 /usr/share/terminfo

So you should be able to fix Amazon's goof-up by (**WITHOUT** having USB exported in USB storage mode):

mntroot rw
cd /usr/share
ln -s /mnt/us/usbnet/etc/terminfo .
mntroot ro

PS: There are alternatives to soldering posted.

[eschwartz]

Originally Posted by irreld

Too bad I ve lost my backup of mkk.

A good lesson for all to remember to backup important files.

Assuming the upstart script survived (which it should -- you had a fully working jailbreak on fw5.7.3 and then did a Factory Reset, right? So you just need to repair the jailbreak) you aren't lost.

You can extract MKK/gandalf from the original jailbreak installer, or as NiLuJe said, the jailbreak hotfix should restore operations.

...

The main reason for all the scary descriptions is because I am trying to instill a general fear of that Factory Reset button in people. It is a dangerous button and avoiding it can only ever be a good thing.

[knc1]

Originally Posted by irreld

Too bad I ve lost my backup of mkk.

A good lesson for all to remember to backup important files.

How can you lose something that is posted as the first entry in the KUAL section of the snapshots page?
https://www.mobileread.com/forums/sho...d.php?t=225030

And has its own thread?
https://www.mobileread.com/forums/sho...d.php?t=233932

And if you need something from inside of the package -
The KindleTool is what you need to open the package with, see:
https://www.mobileread.com/forums/sho...d.php?t=225030

(Yes, I know, that is the same as the first link given in this post.)

[irreld]

Originally Posted by knc1

How can you lose something that is posted as the first entry in the KUAL section of the snapshots page?
https://www.mobileread.com/forums/sho...d.php?t=225030

And has its own thread?
https://www.mobileread.com/forums/sho...d.php?t=233932

And if you need something from inside of the package -
The KindleTool is what you need to open the package with, see:
https://www.mobileread.com/forums/sho...d.php?t=225030

(Yes, I know, that is the same as the first link given in this post.)

Sorry for a misunderstanding. I thought it was a developer keystore signed to each device like Amazon. Now I found the hotfix useless. I must have gone somewhere dark and lost the precious upstart script.

[NiLuJe]

@irreld: As @knc1 mentioned, I instead chose to bundle htop with a hardcoded trimmed down terminfo DB . Because I like htop, and also never could figure out how the hell to use top efficiently ^^.

As for the hotfix, what kind of error did the OTA updater fail with?

Last resort is hoping the backup/restore feature is still active and restore the necessary bits to the userstore, as @eschwartz mentioned.