KOA Kindle Oasis Question

[CjFox]

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.

[NiLuJe]

That's the current MRPI version (the tarball is versioned after the last commit in the full MRPI directory tree, the script after its own).

That return code is funky as hell, though.

Try again after rebooting your device, just in case?

And before you do so, replace extensions/MRInstaller/bin/mrinstaller.sh with this one.

This *should* output some more details about the failure in MRPI's log (or not ).

[NiLuJe]

That said, since the JB Hotfix apparently went through fine, you can also simply install the hotfix variants of KUAL via UYK (they're in the KUAL tarballs, I can't recall whether the Oasis falls on the '"classic" KUAL might work' boat, so I'd stick with coplate's).

[NiLuJe]

Sidebar: I *abhor* edited/truncated logs. I make logs extremely verbose for specific reasons. Trying to be smart with it only makes it harder for both of us .

[CjFox]

Afternoon,

Firstly, my sincerest appreciation for your responses to me, very thankful you're willing to help me out

I replaced the extensions/MRInstaller/bin/mrinstaller.sh file with the one you provided and restarted the device.
I then added the Coplate version of KUAL (Update_KUALBooklet_f54e864_install.bin) through MRPI, placing the file in the mrextensions with the command ;log mrpi after ejecting and unplugging the device.

After a couple minutes, the display resets and reloads with the loading bar. Upon returning to the main screen, I use the search bar for KUAL.
There are no items returned.

The results of the log file are in untruncated form!

**** **** **** ****

[2020-03-06 @ 17:09:29 -0001] :: [MRPI r$Revision$] - Beginning the processing of package 'Update_KUALBooklet_f54e864_install.bin' (KUALBooklet f54e864 I) . . .


Failed to parse package 'Update_KUALBooklet_f54e864_install.bin' (KUALBooklet f54e864 I) [return code: 126], skipping . . .


KindleTool output:
env: can't execute '/mnt/us/extensions/MRInstaller/bin/PW2/kindletool': Permission denied

I decided to give the UYK route a try.

This returns immediately, Update Error: 007, then changes to Please wait whilst your Kindle starts up
The Kindle appears to restart itself, returning to the loading bar.

The device returns to the main screen, KUAL unfortunately doesn't install.

I hope this helps one way or another

[NiLuJe]

Okay, that confirms what I was suspecting: are you *absolutely* sure the original JB hotfix install after the update actually went through successfully?

Because I highly doubt it . Otherwise, everything would be working, and you could reinstall any hotfix without throwing a U007.

That's the typical failure seen with a (really) old bridge after the >= 5.10 update.

[NiLuJe]

What you might try is to reinstall the *bridge* package (not the hotfix) from the JailBreak tarball with the attached version of mrinstaller.sh

It might work. It might also not and leave you with no UI (in which case, just hard reboot) ^^.

If it does work, restart your device, and everything should be back in order (i.e., you should be able to install KUAL).

[CjFox]

Hello!

First, my sincerest thanks for your continued efforts to assist me, I do appreciate it,

I wasn't aware or saw any errors when I did the first JB update from: https://www.mobileread.com/forums/sh...postcount=1597.
There were no errors displayed and it restarted successfully. There is always the chance I missed something though.



I overwrote the mrinstaller.sh with your attached file and then reinstalled the bridge.
The Kindle restarted following and returned the UI.

However, using ;log mrpi still did not manage to install KUAL.

The logs say:
**** **** **** ****

[2020-03-07 @ 00:48:59 -0001] :: [MRPI r16914] - Beginning the processing of package 'Update_jailbreak_bridge_1.16.N_install.bin' (jailbreak bridge 1.16.N I) . . .


Failed to parse package 'Update_jailbreak_bridge_1.16.N_install.bin' (jailbreak bridge 1.16.N I) [return code: 127], skipping . . .


KindleTool output:
/mnt/us/extensions/MRInstaller/bin/PW2/kindletool: error while loading shared libraries: /mnt/us/extensions/MRInstaller/bin/PW2/kindletool: failed to map segment from shared object



**** **** **** ****

[2020-03-07 @ 00:57:37 -0001] :: [MRPI r16914] - Beginning the processing of package 'Update_KUALBooklet_f54e864_install.bin' (KUALBooklet f54e864 I) . . .


Failed to parse package 'Update_KUALBooklet_f54e864_install.bin' (KUALBooklet f54e864 I) [return code: 127], skipping . . .


KindleTool output:
/mnt/us/extensions/MRInstaller/bin/PW2/kindletool: error while loading shared libraries: /mnt/us/extensions/MRInstaller/bin/PW2/kindletool: failed to map segment from shared object

I tried the UYK method and recieved the Error 007 again.

Apologies,

[NiLuJe]

Eh, that was a long shot anyway .

[CjFox]

Morning,

That's okay. Thank you for your efforts.

If you have any other thoughts I can try let me know.

With Kindest Regards,

[CjFox]

If there is nothing that can be done then that's okay as well. I understand this one's my fault.
(I'm also looking at either the Kobo Forma or the Kobo Libra H20 as a new device. I think they are a bit more flexible too)

[NiLuJe]

I'll probably have a last ditch attempt for you later tonight .

(But, yes, I would heartily recommend looking at a Kobo if you're not tied to the Amazon ecosystem).

[NiLuJe]

Okay, try unpacking this at the USB root, then restart.

Then restart again.

Then try installing the JB hotfix. Then if that works, the KUAL hotfix.

[CjFox]

Evening,
Thanks for everything,

I copied the file to the root and rebooted a couple times,
I then put the JB hotfix in the root and used UYK and that rebooted ok.
I then tried the coplate hotfix for KUAL and got error code 007. I tried the standar KUAL to the same result.

Doesn't look good huh?

[NiLuJe]

That... doesn't make sense.

I assume you used the latest JB hotfix from the snapshots thread, and not a random old package you had laying around? ^^.

Could I take a look at the system log that a ;dm in the searchbar will dump to the root of the USB?