MobileRead Forums - View Single Post

drianos · 07-15-2018, 03:13 PM

Hello guys, PW3 here. I jailbreaked my device several months ago with jailbreak JailBreak-1.14.N-FW-5.x-hotfix.zip but it was not until last week that I installed Collection Manager and cover screensaver with the help of KUAL with mrpi installation.

I may or may not have updated the kindle before applying the hacks, at least the multiple font feature was installed. I made all the hacks work, even the remove special offer chatting with amazon, and was happy reorganizing my library in Calibre and updating the collections in the kindle with Collection Manager.

But yesterday I removed airplane mode without noticing and I received this update. Today Kual and Collection manager give me application Error and I'm getting the default kindle screensaver when device sleeps instead of the cool looking book cover that was working yesterday.

Any ideas of what happened? suggestion? someone else affected.

P.D. As my first post, thanks to all people that have fill this forums with such useful information and obviously the incredible work of the developers.

07-15-2018, 03:13 PM	#26
drianos Junior Member Posts: 1 Karma: 10 Join Date: Jul 2018 Device: kindle pw3	Hello guys, PW3 here. I jailbreaked my device several months ago with jailbreak JailBreak-1.14.N-FW-5.x-hotfix.zip but it was not until last week that I installed Collection Manager and cover screensaver with the help of KUAL with mrpi installation. I may or may not have updated the kindle before applying the hacks, at least the multiple font feature was installed. I made all the hacks work, even the remove special offer chatting with amazon, and was happy reorganizing my library in Calibre and updating the collections in the kindle with Collection Manager. But yesterday I removed airplane mode without noticing and I received this update. Today Kual and Collection manager give me application Error and I'm getting the default kindle screensaver when device sleeps instead of the cool looking book cover that was working yesterday. Any ideas of what happened? suggestion? someone else affected. P.D. As my first post, thanks to all people that have fill this forums with such useful information and obviously the incredible work of the developers.