Tools Snapshots of NiLuJe's hacks

[radamo]

Originally Posted by NiLuJe

@radamo: What 'data', exactly, and what does your RUNME look like?


(Also, double-check you haven't bungled the MRPI install, on the off-chance it's something trivial ).

Isn't the MRPI install just extracting the directories (and files) onto the kindle root directory? I deleted and redid just to be sure. I do not have any version of Kual installed... am I supposed to?

The "data" flies by too quickly... screen goes blank and then a few lines of text start from the top and go about 2 inches down on the kindle then goes back to the regular home screen.

[7hir7een]

Originally Posted by NiLuJe

@7hir7een: Fantastic, thanks for your feedback .

Which KUAL build is that? Because it's missing actual Oasis2 detection (c.f., the K?? in the bottom), which explains why you're not seeing some menu entries.

Wow, sorry. Post-shift brain got me there. I did indeed update everything except KUAL.

And turns out I'm actually having issues doing so. The snapshot install bin resulted in the blank-page KUAL problem, even after uninstalling and reinstalling. The only version I have been able to get to show up is from coplate's thread here: https://www.mobileread.com/forums/sh...d.php?t=294765

From looking at the runme code they posted and poking around in ssh in Transit after installing your bin, it appear the issue could be that it is not placing KUALBooklet.jar in /opt/amazon/ebook/booklet (the file is absent)

I'm not actually familiar with how to unpack the bin files, or I would move the file there myself.

Originally Posted by NiLuJe

And a bonus question: If you're familiar with my stuff, do the monospace status messages that usually show up on the bottom of the screen actually show up on your KOA2, and are they actually printed at the bottom of the screen, or more somewhere around the middle?

The monospace messages like S checking screensavers. . . and the mrpi installer feedback and kual status printouts do show up and show up at the bottom of the screen. It's been quite some time since I've set up a hacked kindle from scratch, so I can't recall if there are others I should be seeing? But it seems like they're showing up correctly.



EDIT: sorry, I started drafting this before I saw your response!

[NiLuJe]

@radamo: Huh. I'm guessing that at least *some* part of it runs, then.

Would you be able to record that w/ something (even a cellphone camera would do the job)? That'd allow us to frame-step through it and hopefully figure out where it's falling on its ass .

(Barring that, you can also try to trudge through a ;dumpMessages system log, there's should be some "mr_installer" bits to search for).

[NiLuJe]

For people coming here from the KUAL thread: the package you want is the one listed under "KUAL (coplate)" in the Snapshots thread. In it, you'll find an update package you'll be able to install via MRPI, and that's it . For all intents & purposes, you can go back to the rest of KUAL's documentation as if you had installed the original Booklet variant of KUAL.


What follows is simply my original answer in the initial flow of the thread .

----

@7hir7een: Totally not your fault, AFAIK, my package is *expected* to fail on some devices/FW combos.

I had forgotten to check if coplate's build included the latest few commits from November, my bad.

So I just backported those in coplate's tree, can you try the KUAL package attached to this post?

Hopefully, it'll work, but that entirely depends on whether coplate's GitHub tree matches his latest binaries from that thread .

Thanks for the confirmation about the messages, that was indeed those I was talking about .

EDIT: And in case there's some mysterious Java shenanigans going on, and that package *also* gets you a disappearing jar (I seriously don't get that bit, )., here's the jar itself to install as described in @coplate's thread (either via RUNME or via @knc1's SSH instructions).

EDIT²: Good news! The manual .jar method install should not be needed!
I'm leaving it up in case wackyness ensues and it one day becomes of use...

[7hir7een]

That worked like a charm! Testing custom fonts now and will report back shortly

ETA: works great

[NiLuJe]

@7hir7een: Just to be perfectly clear: did the update package work, or did you need to install the jar manually?

[7hir7een]

Originally Posted by NiLuJe

@7hir7een: Just to be perfectly clear: did the update package work, or did you need to install the jar manually?

Installing Update_KUALBooklet_f17051f_install.bin via mrpi worked without any additional steps. I nabbed the bin file before I saw your edit with the jar

[radamo]

Originally Posted by NiLuJe

@radamo: Huh. I'm guessing that at least *some* part of it runs, then.

Would you be able to record that w/ something (even a cellphone camera would do the job)? That'd allow us to frame-step through it and hopefully figure out where it's falling on its ass .

(Barring that, you can also try to trudge through a ;dumpMessages system log, there's should be some "mr_installer" bits to search for).

Here is the video of ;log runme output...

[NiLuJe]

@7hir7een: Great, thanks! I'll update KUAL's first post to make it slightly less useless then .

@radamo: Okay, then, back to: what RUNME script is this? ^^.

[radamo]

Originally Posted by NiLuJe

@7hir7een: Great, thanks! I'll update KUAL's first post to make it slightly less useless then .

@radamo: Okay, then, back to: what RUNME script is this? ^^.

Oh, my bad I never replied to that... I believe it was part of the jailbreak and bridge code. Should I be running something different to load the SS hack from the MRPackages directory? It seemed to load Python?

[NiLuJe]

@radamo: I'm not exceedingly familiar with the KOA2 JailBreak (ping @knc1), but my old dispatch script used to have a mrpi special-case....

Does ;log mrpi do anything useful?

EDIT: I'm not seeing anything in @knc1's RUNME (at least the version I have) that would *ever* run MRPI, so I'm a bit confused . The good news is that mrpi special-case should still apply.

[radamo]

Originally Posted by NiLuJe

@radamo: I'm not exceedingly familiar with the KOA2 JailBreak (ping @knc1), but my old dispatch script used to have a mrpi special-case....

Does ;log mrpi do anything useful?

EDIT: I'm not seeing anything in @knc1's RUNME (at least the version I have) that would *ever* run MRPI, so I'm a bit confused . The good news is that mrpi special-case should still apply.

Well... it ran an installer which looked like Python? But the SS hack still not active unless there is something else I do to activate it. With Kual this was more straight forward. Sorry for the clueless questions. The SS hack is really my only reason to do the Jailbreak and I have not had much luck researching how to run these tools on the Koa2.

[NiLuJe]

@radamo: Well, at least if the installer ran, you now have a log for me to look at .

[radamo]

Originally Posted by NiLuJe

@radamo: Well, at least if the installer ran, you now have a log for me to look at .

First... thank you for taking so much time to help me.
Second... now rerunning with the SS hack .bin.

SS Hack is INSTALLED!!!! I now see your "splash screen" telling me it is installed. Is there a doc somewhere so I can stop taking up your time? All I am trying to do is display my current book's cover as the screensaver.

[NiLuJe]

@radamo: The dedicated thread (which is also linked to in the first post of this thread for everything listed there) should cover (ha!) the basics. Reply in there if you're encountering an issue that doesn't appear to be specific to the snapshots package (i.e., anything, really, now that you've got it installed ^^).