K5 FW 5.x ScreenSavers Hack

[knc1]

Originally Posted by polygonica

Reinstalled MrPI 1.6.N. Getting the same issue with installing MrPI packages.

I doubt my hardware is broken. Everything else is working fine. The default browser and reader work fine. KUAL and its extensions are fine (so I also assume MKK is working). Kterm is working (and basic shell commands).

Any ideas?

MrPI v-1.6.N-r13408 from:
https://www.mobileread.com/forums/sh...d.php?t=225030

Also, what 2 packages are you trying to install (name and link you got them from please).

[polygonica]

Originally Posted by knc1

MrPI v-1.6.N-r13408 from:
https://www.mobileread.com/forums/sh...d.php?t=225030

Also, what 2 packages are you trying to install (name and link you got them from please).

Yesterday, I was using MRPI r13359 and trying to install the packages linked from the first post of this thread (kindle-python 0.14.N (touch_pw) r13360, and linkss 0.24.N (touch_pw))

Today:
Upgraded MRPI from r13359 to r13408 (deleted r13359, ejected, restarted (disconnected), added r13408, ejected, restarted (disconnected)).

Then, I tried to install kindle-python-0.14.N-r13420 from NiLuJe's thread (copied the touch_pw .bin to /mrpackages , ejected, restarted (disconnected), used MRPI to install). Seem to be getting the same result -- the installation ends almost immediately and python doesn't seem to be present (not a valid command in kterm). I'd check the logs but ;dm isn't doing anything.

[knc1]

Originally Posted by polygonica

Yesterday, I was using MRPI r13359 and trying to install the packages linked from the first post of this thread (kindle-python 0.14.N (touch_pw) r13360, and linkss 0.24.N (touch_pw))

Today:
Upgraded MRPI from r13359 to r13408 (deleted r13359, ejected, restarted (disconnected), added r13408, ejected, restarted (disconnected)).

Then, I tried to install kindle-python-0.14.N-r13420 from NiLuJe's thread (copied the touch_pw .bin to /mrpackages , ejected, restarted (disconnected), used MRPI to install). Seem to be getting the same result -- the installation ends almost immediately and python doesn't seem to be present (not a valid command in kterm). I'd check the logs but ;dm isn't doing anything.

That has worked since the days of the K2.
The OS is damaged.
Re-install 5.6.1.1

Note:
You may have to follow the directions on downgrading the PW-1 first - see the link to the 'how to' that is part of the PW-1 jb instructions.
The link is a little bit hard to see, read carefully the first post, it is in the text.

[polygonica]

Originally Posted by knc1

That has worked since the days of the K2.
The OS is damaged.
Re-install 5.6.1.1

Note:
You may have to follow the directions on downgrading the PW-1 first - see the link to the 'how to' that is part of the PW-1 jb instructions.
The link is a little bit hard to see, read carefully the first post, it is in the text.

;dm worked this time. I'm 2 for 3, so I'm just going to assume I made a typo.

170113:171506 system: I mr_installer:eips_print_bottom_centered::* python 0.14.N I K5 *
170113:171506 FAT: Filesystem error (dev loop0)
170113:171506 fat_get_cluster: invalid cluster chain (i_pos 241713)
[this goes on for a while]
170113:171507 FAT: Filesystem error (dev loop0)
170113:171507 fat_get_cluster: invalid cluster chain (i_pos 241713)
170113:171507 system: I mr_installer:eips_print_bottom_centered::Failed to extract package, skipping
170113:171507 system: I mr_installer:eips_print_bottom_centered:estroyin g package . . .
170113:171507 system: I mr_installer:make_rootfs_ro::trying to remount rootfs ro
170113:171507 system: E mntusartition_unmount_failed:artition unmount failed (1)
170113:171507 volumd[1117]: I volumd:unmount_userstore:Userstore unmount failed:
170113:171508 system: W mr_installer:make_rootfs_ro::rootfs is already ro!
170113:171509 system: I mntus:fs_error_recover::File system errors recovered

WELL THEN. Might have to reinstall anyhow.

[knc1]

Originally Posted by polygonica

;dm worked this time. I'm 2 for 3, so I'm just going to assume I made a typo.



WELL THEN. Might have to reinstall anyhow.

It is the last item on my list, failing eMMC.

If you have a Linux (or MacOSx) pc, you can access the raw storage device, zero the first 16 sectors, reboot, and the system will re-build the user storage area.
There are directions here, probably indexed by the sticky 'master index' post.

But you had better be sure to have backed up everything you have on user storage first.
And if you have to do that now, expect to get files with errors.

Re-installing will probably not do much good -
The update system does not verify what it writes.

Also, we have a utility script here that DOES do write, read-back, verify -
Which you really must use now to transfer the Amazon update file to user storage -
Really bad things will happen if you try to run an update image file from failing storage.

[polygonica]

Originally Posted by knc1

It is the last item on my list, failing eMMC.

If you have a Linux (or MacOSx) pc, you can access the raw storage device, zero the first 16 sectors, reboot, and the system will re-build the user storage area.
There are directions here, probably indexed by the sticky 'master index' post.

But you had better be sure to have backed up everything you have on user storage first.
And if you have to do that now, expect to get files with errors.

Re-installing will probably not do much good -
The update system does not verify what it writes.

Also, we have a utility script here that DOES do write, read-back, verify -
Which you really must use now to transfer the Amazon update file to user storage -
Really bad things will happen if you try to run an update image file from failing storage.

Will try that next week. Thanks for the help.

Also, nothing important is on user storage. Just my one-line fix to Front Light Master which I've noted down already.

[s1s2s3s4s5]

I have a jailbroken Kindle Oasis with 5.8.7.
I've installed Python and SSH and have got a message as a cover "The ScreenSavers Hack has been successfully installed!".
And since that it is the only cover that I see although I have a lot of different books in Kindle (from Kindle store and other books with covers converted from epub and fb2 to azw2).
I've put the empty file "cover" to listss folder (see printscreen) and have set setting in KUAL / Screen Savers / Screen Savers Behavior / Cover and have restarted the device several times and re-installed both Python and SSH once. Nothing helps. What could be the problem?

[jwilker]

Curious if the KFX fix needs to be updated? I know something changed because Calibre needed an update to see the latest KFX files on a Kindle. I'm noticing that newer books fail to process the covers.

[ssholloway]

Originally Posted by jwilker

Curious if the KFX fix needs to be updated? I know something changed because Calibre needed an update to see the latest KFX files on a Kindle. I'm noticing that newer books fail to process the covers.

I also have KFX books with covers that will not display but my issue does not seem to be related to file dates since some of my older books will not process while newer ones do. I suspect the format of the cover is incompatible with the hack. Perhaps when NiLuJe returns to the forum, he can provide some insight.

[aqswde]

I joined this forum just so I could tell you all that you rock. Thank you thank you thank you.

Also:

Originally Posted by dan3008

Just so people know, there has been a OTA upgrage pushed, which seems to brake this. It somehow disabled KUAL and all the extensions... I had to backup my screensavers, uninstall and reinstall linkss, but its finally worked again... lesson learned, remember to lock the back door...

This fixed it for me, too, except I didn't bother uninstalling before reinstalling. I assume that's somewhat riskier and less advisable, but just letting anyone else know that it worked for me.

[knc1]

Originally Posted by aqswde

I joined this forum just so I could tell you all that you rock. Thank you thank you thank you.

Also:
This fixed it for me, too, except I didn't bother uninstalling before reinstalling. I assume that's somewhat riskier and less advisable, but just letting anyone else know that it worked for me.

There is no reason to un-install, the image update already over-wrote the parts you can not see.

The easiest to remember rule is:
Re-install anything that is broke after an Amazon image update.

It has been that way since Amazon started shipping complete images rather than change files (years ago).

This is also why the contents labeled #7 (installing recent firmware version) comes before the contents labeled #8 (installing add-ins) in the current jail break.

[penguintri]

Originally Posted by jwilker

Curious if the KFX fix needs to be updated? I know something changed because Calibre needed an update to see the latest KFX files on a Kindle. I'm noticing that newer books fail to process the covers.

I've noticed the same, 3 books I've purchased in the last week don't show covers.

[knc1]

Originally Posted by penguintri

I've noticed the same, 3 books I've purchased in the last week don't show covers.

Each of you with this problem ::

Which ss add-in are you using?
Full name and link please.

[jwilker]

I might be mixing my terms (apologies), I know when KFX started cropping up there was a hot fix, that's what I meant with "fix". Unfortunately I renamed the folder so don't know what it's original folder name was.

Since you asked I went looking for what release I was using, etc and decided to check against what's linked in post 1. release r13390.

So to be safe I tried that release (what I had was been using was r13265).

All that to say, r13390 still exhibits the behavior. On a newly purchased book, no cover processed.

Hopefully that helps?

[knc1]

Originally Posted by jwilker

I might be mixing my terms (apologies), I know when KFX started cropping up there was a hot fix, that's what I meant with "fix". Unfortunately I renamed the folder so don't know what it's original folder name was.

Since you asked I went looking for what release I was using, etc and decided to check against what's linked in post 1. release r13390.

So to be safe I tried that release (what I had was been using was r13265).

All that to say, r13390 still exhibits the behavior. On a newly purchased book, no cover processed.

Hopefully that helps?

Does the book actually have a cover in the document itself?
Or is this an Amazon purchase where the "cover" is a separate file?