Tools Snapshots of NiLuJe's hacks

[Siaubas]

Originally Posted by zivilyn

I didn’t make it clear.

"kual-mrinstaller-1.7.N-r16535" didn't work for me and I returned to "kual-mrinstaller-1.7.N-r15470" downloaded in July.

Could you sent it, I can't find.

I wanted check you way (maybe it helps), because I don't know if it the MRPI problem, or I lost jailbreak after firmware update

[hius07]

Originally Posted by Siaubas

Could you sent it, I can't find.

I wanted check you way (maybe it helps), because I don't know if it the MRPI problem, or I lost jailbreak after firmware update

You wrote that you had installed the hotfix after update. It would be impossible without jaibreak.

[radamo]

Sorry for the nube question but after manually updating FW on the KOA2 ";log mrpi" no longer works. I reinstalled MR Package installer but still no go.

[Siaubas]

Originally Posted by radamo

Sorry for the nube question but after manually updating FW on the KOA2 ";log mrpi" no longer works. I reinstalled MR Package installer but still no go.

Have you found any solution?
I want read with the Koreader, not with the standart Kindle program, which doesn't understand different file format and not enough setting according my needs

[NiLuJe]

@zivilyn: That doesn't make any sense (i.e., logs or it didn't happen ).

@Siaubas:

Originally Posted by NiLuJe

WARNING: FW >= 5.12.2 is definitely much more aggressive, and it will *probably* destroy your JailBreak. Having an up-to-date (>= 1.16.N) bridge *before* the update *might* help, or not.
TL;DR: Stay away from FW >= 5.12.x.

@radamo: Updating from what to what? And that wouldn't be MRPI you'd need to reinstall, but the hotfix.

Originally Posted by NiLuJe

As mentioned earlier, an official FW update will basically throw you back to the post-hotfix step: you'll basically have to reinstall anything that came bundled in a .bin, except for the hotfix/bridge itself.

Speaking of the bridge/hotfix, you shouldn't ever need to reinstall it, unless you want to make extra sure it's got its hooks set in right before and/or after doing a severely destructive manipulation, like a factory reset. But, technically, if nothing untoward ever happened to your device, this shouldn't be needed, it's just a precaution.

[radamo]

I did have the latest hotfix installed but must have misunderstood some of the posts on here and thought it was safe to install 5.12.2. Apparently NOT. I guess I have hosed my JB. It was fun while it lasted.

[hius07]

As I understand, both @radamo and @Siaubas have jailbreak survived (as they can install the hotfix after update), but they cannot start mrpi installation of KUAL via ;log mrpi.

[radamo]

Originally Posted by hius07

As I understand, both @radamo and @Siaubas have jailbreak survived (as they can install the hotfix after update), but they cannot start mrpi installation of KUAL via ;log mrpi.

I installed the HOTFIX prior to the update to 5.12.2. When trying to put the hotfix on post update I now get an ERROR message from the Kindle saying it is an invalid update file. So apparently 5.12.2 is EVIL...

[hius07]

Originally Posted by radamo

I installed the HOTFIX prior to the update to 5.12.2. When trying to put the hotfix on post update I now get an ERROR message from the Kindle saying it is an invalid update file. So apparently 5.12.2 is EVIL...

Oh, sorry, you definitely have lost jb.

[Siaubas]

Originally Posted by hius07

As I understand, both @radamo and @Siaubas have jailbreak survived (as they can install the hotfix after update), but they cannot start mrpi installation of KUAL via ;log mrpi.

yes, you are right.
Could I try to do some steps, or it is better to wait for some future solution?

[hius07]

I believe only NiLuJe can guess why ;log mrpi doesn't work while jb persists.
5.12.2 is a strange and dangerous thing.

[NiLuJe]

Reboot, reinstall the *latest* hotfix, reboot.

If the install succeeded, and ;log doesn't work after that, either you're doing something wrong, or there's black magic at work.

[radamo]

Originally Posted by NiLuJe

Reboot, reinstall the *latest* hotfix, reboot.

If the install succeeded, and ;log doesn't work after that, either you're doing something wrong, or there's black magic at work.

Attempted install of hotfix gives message:
Update Error
An invalid update file has been loaded on you device......

So looks like I am SOL.

[NiLuJe]

On the upside, that, at least, is a chain of events that makes sense .

[hius07]

Downgrading from 5.12.2 confirmed!
https://www.mobileread.com/forums/sh...d.php?t=323882