Tools Snapshots of NiLuJe's hacks - Page 43

hius07 · 10-23-2019, 02:07 PM

A new report from Voyage: it was on 5.12.1, installed the latest hotfix, updated to 5.12.2, installed the hotfix, updated mrpi, failed to install KUAL (coplate) with mrpi.
The user didn't try to downgrade to the initial factory firmware.

NiLuJe · 10-23-2019, 03:03 PM

@hius07: Failed how?

hius07 · 10-23-2019, 04:02 PM

Quote:

Originally Posted by NiLuJe

@hius07: Failed how?

No info.
The user has done factory reset so mrpi log cannot be traced.
He says that he has not seen "Hush little baby", but he is not sure.

hius07 · 10-25-2019, 03:10 AM

One more try. PW3 updated to 5.12.2, installed hotfix, installed KUAL (coplate).
Trying to run KUAL caused error some of "Application cannot be started. Try again later".
Logs attached.

knc1 · 10-25-2019, 10:40 AM

Quote:

Originally Posted by hius07

One more try. PW3 updated to 5.12.2, installed hotfix, installed KUAL (coplate).
Trying to run KUAL caused error some of "Application cannot be started. Try again later".
Logs attached.

That log file has an awful lot of error and warning messages.
About the same as the last ten years.
Lab126 again ships a firmware that is f...ing lucky to even boot.

Things might improve a little bit if they got their compiler setup to match the machine's instruction set (now that is not up to "professional" standards of any kind).

-- -- -- -- --

That all reads as if it was a start or re-start of the 5.12.2 and the logs produced during the previous run (the installation of the new firmware by the previous firmware) have been "lost" in the bit bucket.
Hmm ...
Well it does report some of the kernel's print buffer from the prior execution, but not enough to be interesting.
I should have written above that the "interesting logs" have been lost in the bit bucket.

hius07 · 10-26-2019, 12:48 PM

So thanks to the latest hotfix jailbreak survives on 5.12.2 but KUAL cannot be started.

hius07 · 10-30-2019, 03:43 AM

Another report: Voyage, hotfix, update 5.12.2, hotfix, update mrpi
Tried to install KUAL - mrpi cannot be started, no "Hush little baby", no mrinstaller.log.
System log (after ;log mrpi) attached.

knc1 · 10-30-2019, 10:47 AM

I am getting very pissed off at Amazon/Lab126.
I might just have to come out of retirement and work on these problems.

Although I think it would be an entire waste of time now.
I fear we have all taught them way too much over the years.

NiLuJe · 10-30-2019, 10:58 AM

That's yet another useless log, and yet another inconsistent report, since that's the first I've heard of ;log not working. -_-".

NiLuJe · 10-30-2019, 11:03 AM

On the other hand, that one does finally make sense, as ;log is indeed gone in 5.12.2

.

NiLuJe · 10-30-2019, 11:14 AM

Okay then, let's try this: a hotfix variant of KUAL (i.e., install it via UYK).

(It's the full package, because I'm lazy. Just pick the hotfix install package).

hius07 · 10-30-2019, 02:23 PM

Quote:

Originally Posted by NiLuJe

Okay then, let's try this: a hotfix variant of KUAL (i.e., install it via UYK).

Great! Report from Voyage 5.12.2: KUAL hotfix installed, KUAL started, Koreader started.
Do you need any tests from him?

update: Python, Screen Saver Hack installed via KUAL mrpi button.

lucasrato · 10-30-2019, 06:11 PM

Quote:

Originally Posted by NiLuJe

Okay then, let's try this: a hotfix variant of KUAL (i.e., install it via UYK).

(It's the full package, because I'm lazy. Just pick the hotfix install package).

Tried it on PW4 5.12.2, error 007

darkassassinua · 10-30-2019, 07:16 PM

Quote:

Originally Posted by NiLuJe

Okay then, let's try this: a hotfix variant of KUAL (i.e., install it via UYK).

(It's the full package, because I'm lazy. Just pick the hotfix install package).

installed the latest hotfix, updated to 5.12.2, installed the hotfix, installed that KUAL`s build - its all worked, kual and koreader.Thank u!

NiLuJe · 10-30-2019, 08:06 PM

@hius07: Yay! Nah, I'll update the docs for the next snapshots build, thanks!

@lucasrato: You do need a working JB.

10-30-2019, 11:14 AM	#641
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Okay then, let's try this: a hotfix variant of KUAL (i.e., install it via UYK). (It's the full package, because I'm lazy. Just pick the hotfix install package). Last edited by NiLuJe; 11-19-2019 at 02:06 PM. Reason: Removed deprecated package. This is now shipped with the usual KUAL packages listed in the first post of this very thread.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
I removed the hacks, installed 3.1, then new hacks, and now Kindle is dead	cloudyvisions	Amazon Kindle	55	11-29-2023 08:27 PM
Tools Snapshots of Coplate's packages	coplate	Kindle Developer's Corner	104	10-24-2022 12:41 AM
NiLuJe offline?	picree	Kindle Developer's Corner	1	09-28-2016 11:29 PM
Snapshots test in Live version	Michele Clinco	OpenInkpot	7	09-08-2009 03:42 PM

10-23-2019, 02:07 PM	#631
hius07 Wizard Posts: 1,190 Karma: 3592925 Join Date: Sep 2014 Location: Ukraine Device: Kindle	A new report from Voyage: it was on 5.12.1, installed the latest hotfix, updated to 5.12.2, installed the hotfix, updated mrpi, failed to install KUAL (coplate) with mrpi. The user didn't try to downgrade to the initial factory firmware.

10-23-2019, 03:03 PM	#632
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@hius07: Failed how?

10-26-2019, 12:48 PM	#636
hius07 Wizard Posts: 1,190 Karma: 3592925 Join Date: Sep 2014 Location: Ukraine Device: Kindle	So thanks to the latest hotfix jailbreak survives on 5.12.2 but KUAL cannot be started.

10-30-2019, 10:47 AM	#638
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	I am getting very pissed off at Amazon/Lab126. I might just have to come out of retirement and work on these problems. Although I think it would be an entire waste of time now. I fear we have all taught them way too much over the years.

10-30-2019, 10:58 AM	#639
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	That's yet another useless log, and yet another inconsistent report, since that's the first I've heard of ;log not working. -_-".

10-30-2019, 11:03 AM	#640
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	On the other hand, that one does finally make sense, as ;log is indeed gone in 5.12.2 .

10-30-2019, 08:06 PM	#645
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@hius07: Yay! Nah, I'll update the docs for the next snapshots build, thanks! @lucasrato: You do need a working JB.