Good Evening All,
Been spending the last 24 hours working on this, but I'm not getting a result, so I thought I'd ask for assistance here. I have looked and searched and scoured these forums, but no luck. Wanted to try fixing it myself if I could before I bothered you all.
I don't want to open the device to wire in a serial cable. I'd rather keep a device that still works as an eReader in case I want to pass it on to someone else.
So, essentially, if the answer to the below is - 'no, you're stuck now until things can be fixed in the future', then I am happy with that. It's just a case of knowing. :)
So my Kindle Oasis (G0B0GC Kindle Oasis WiFi KOA) has been jailbroken for a while, using KUAL and the screensaver hack, worked a treat for many a year.
Looking at my linkss directory - I'm at version 0.24.N.
The "You are now jailbroken.txt" file has a timestamp of 15/7/16 (I cannot remember when I performed this, but it was a long time ago using the instructions here: https://lifehacker.com/how-to-jailbr...dle-1783864074)
Unfortunately, like a dummy, I accidentally left my WiFi on and the device plugged in and it's updated itself to 5.12.3, which of course, killed the screensaver hack and KUAL. Reading the threads, yes this is my own fault. I understand that one.
It's been a case of in the past, reinstalling KUAL and the Screensaver hack.
In this case, I had no luck with ;log mrpi (I found out later this function was removed, but more on this later)
I followed this link: https://www.mobileread.com/forums/sh...postcount=1597 and used the update your kindle option to update. It went through fine and I thought everything was dandy, but no luck with KUAL installing (;log mrpi not available). I'd had the jailbreak on before, so I believed all I had to do was update it.
Which led me to: https://www.mobileread.com/forums/sh...d.php?t=325477, which succesfully got ;log mrpi back up and running. Based on that thread, the jail break would appear to be there and working, from my understanding of it.
I deleted the old extensions and mrpackages from the root of the Kindle and put the newest ones on.
Then, tried to install KUAL (tried both the coplate and the non coplate version), but after ;log mrpi completes and the interface reloads, opening KUAL gives a pop up that the application cannot be opened
The log for mrpi reports (replace 'package_name' with the name of the package, for example KUAL:
[2020-03-05 @ 22:27:30 -0001] :: [MRPI r16257] - Beginning the processing of package 'package_name.bin' (package_name) . . .
Failed to parse package 'Upackage_name.bin' (package_name) [return code: 126], skipping . . . :(
It looks as though it's using an old version of MRPI, even though I copied the latest MRPI extensions and mrpackages directories into the root of the kindle. (r16858.tar.xz) Did I do it wrong?
So I am confused and not sure where to go from here, if there is anywhere to go from here. It's a shame really since it was working just fine and from the threads, I've seen people have success in getting KUAL back up and running on the 5.12 firmware. I feel like I am very close, but just missing that last step.
As I say, I am happy to know if I am stuck in a situation where I am stuck, as long as I know. I'm looking at other eReader devices which may be a bit more flexible and customisable that Amazons devices. There is just something about personalising the device with your own image screensaver that makes the device yours.
I thank you for your time reading this thread and apologies for its length.
Been spending the last 24 hours working on this, but I'm not getting a result, so I thought I'd ask for assistance here. I have looked and searched and scoured these forums, but no luck. Wanted to try fixing it myself if I could before I bothered you all.
I don't want to open the device to wire in a serial cable. I'd rather keep a device that still works as an eReader in case I want to pass it on to someone else.
So, essentially, if the answer to the below is - 'no, you're stuck now until things can be fixed in the future', then I am happy with that. It's just a case of knowing. :)
So my Kindle Oasis (G0B0GC Kindle Oasis WiFi KOA) has been jailbroken for a while, using KUAL and the screensaver hack, worked a treat for many a year.
Looking at my linkss directory - I'm at version 0.24.N.
The "You are now jailbroken.txt" file has a timestamp of 15/7/16 (I cannot remember when I performed this, but it was a long time ago using the instructions here: https://lifehacker.com/how-to-jailbr...dle-1783864074)
Unfortunately, like a dummy, I accidentally left my WiFi on and the device plugged in and it's updated itself to 5.12.3, which of course, killed the screensaver hack and KUAL. Reading the threads, yes this is my own fault. I understand that one.
It's been a case of in the past, reinstalling KUAL and the Screensaver hack.
In this case, I had no luck with ;log mrpi (I found out later this function was removed, but more on this later)
I followed this link: https://www.mobileread.com/forums/sh...postcount=1597 and used the update your kindle option to update. It went through fine and I thought everything was dandy, but no luck with KUAL installing (;log mrpi not available). I'd had the jailbreak on before, so I believed all I had to do was update it.
Which led me to: https://www.mobileread.com/forums/sh...d.php?t=325477, which succesfully got ;log mrpi back up and running. Based on that thread, the jail break would appear to be there and working, from my understanding of it.
I deleted the old extensions and mrpackages from the root of the Kindle and put the newest ones on.
Then, tried to install KUAL (tried both the coplate and the non coplate version), but after ;log mrpi completes and the interface reloads, opening KUAL gives a pop up that the application cannot be opened
The log for mrpi reports (replace 'package_name' with the name of the package, for example KUAL:
[2020-03-05 @ 22:27:30 -0001] :: [MRPI r16257] - Beginning the processing of package 'package_name.bin' (package_name) . . .
Failed to parse package 'Upackage_name.bin' (package_name) [return code: 126], skipping . . . :(
It looks as though it's using an old version of MRPI, even though I copied the latest MRPI extensions and mrpackages directories into the root of the kindle. (r16858.tar.xz) Did I do it wrong?
So I am confused and not sure where to go from here, if there is anywhere to go from here. It's a shame really since it was working just fine and from the threads, I've seen people have success in getting KUAL back up and running on the 5.12 firmware. I feel like I am very close, but just missing that last step.
As I say, I am happy to know if I am stuck in a situation where I am stuck, as long as I know. I'm looking at other eReader devices which may be a bit more flexible and customisable that Amazons devices. There is just something about personalising the device with your own image screensaver that makes the device yours.
I thank you for your time reading this thread and apologies for its length.