Tools Snapshots of NiLuJe's hacks

[NiLuJe]

Okay, updated the snapshots (and the sticky) to mention the KUAL/;log shenanigans on >= 5.12.2.

Updated a bunch of stuff:

* Python & SQLite shells now behave properly (i.e., they have working readline support, which makes them actually usable).
* dropbear has been updated (and is once more built against its own libtom* copies, because there were growing API mismatches w/ upstream). Might be faster, will probably be less glitchy.
* FBGrab has been updated (mainly to handle amdgpu fbs properly, which I broke when I tweaked nvidia EFI fbs handling. Which, granted, doesn't have anything to do with Kindles ).

And, most importantly, Python 2's EoL is approaching, so I've started pinning some 3rd-party modules to their final versions in the Python 2 build (Python 3 will happily keep chugging along on bleeding edge code).

(i.e., Pillow is stuck @ 6.2.x on Python 2).

So, if you start noticing stuff that relies on third-party modules breaking with Python 2, do ping me. (Because, for instance, Pillow master currently happily still builds against Python 2, but will implode in fun and interesting ways at runtime ^^).

[kostya]

Guys, I have pw3 and with 1.15 hotfix. After getting 5.12.2 nothing works (neither ;log mrpi nor update with 1.16 hotfix). Does it mean I lost jailbreak or there is a way to downgrade somehow?

Thank you!

[hius07]

Is ;log runme dead too in 5.12.2?

[richelmy]

Originally Posted by kostya

Guys, I have pw3 and with 1.15 hotfix. After getting 5.12.2 nothing works (neither ;log mrpi nor update with 1.16 hotfix). Does it mean I lost jailbreak or there is a way to downgrade somehow?

Thank you!

same here

[NiLuJe]

@hius07: Yep, the ;log command is plain gone .

[NiLuJe]

@kostya/@richelmy: 1.15.N was likely too old. If hotfixing fails, JB is gone. If it's gone, there's no downgrading on the horizon.

[Schattenjager]

@NiLuJe: please add a hotfix version to the regular KUAL (not only for coplate variant) for those who still use it on older devices like PW3. Thanks in advance)

[NiLuJe]

@Schattenjager: Gah. -_-".

Done. Won't install on Zelda/Rex because there's no point even trying there. Might install on some Warios were it won't actually work, I honestly don't remember where it stopped working.

[Schattenjager]

@NiLuJe: just tried on PW3 with 5.12.2 - it works!
Thanks again)

[NiLuJe]

@Schattenjager: Good to know, thanks. I'd kind of forgotten about that quirk (despite having a PW2 on 5.9.x running the stock Booklet ;p).

[Schattenjager]

@NiLuJe: I prefer the regular version. I think it loads a little faster and without a blank white screen.

[indiecognition]

NiLuJe and knc1,
My Voyage has the squaretrade warranty (and the 5.5.12 update also screwed up page-turns), so I gave it a shot to see what they'd send. Unfortunately the replacement has 5.10.3...just barely not jailbreakable.

Before sending back my original device, I had a few thoughts. While ;log doesn't work, some of the hotfix updates (installed via UYK) aren't rejected entirely. What I mean is that some of them are detected as invalid as soon as they're transferred to the Kindle, but others at least get the device to restart and try to install before triggering Error 007.

Just wondering if there was some way to sneak in KUAL in that process. Or if there are specific builds you recommend that I try before sending back the Voyage that had jailbreak and lost it at 5.12.2.

As far as the reason that I had the 1.14_nomax, there was a point where the most recent hotfix didn't work, but that one did. So I just kept going with it, and all was good as long as I manually updated and stayed on wifi with the folder to prevent auto-updates. So obviously I'm a little bummed with the 5.12.2 update being so stealthy.

Anyway, this is all dumb because the only part of Jailbreak I really used actively was the screensavers hack, which Amazon could just provide if people paid the $20 to remove special offers...so it would be a win win. But they won't so now I'm torn between trying to keep a shred of hope with my old device before sending it back, just using the warranty replacement knowing that at least books will work, or trying the open-and-solder method despite not being very good at soldering.

Sorry for the long post, but really appreciate all your dedication to the Kindle hacking community, and even if there's no hope for me short of surgery on the new Voyage, at least venting here might help me skip a step or two on the stages of grief over the lost jailbreak.

[NiLuJe]

@indiecognition: In short: no.

(An update package passing the sanity checks has zero relation to your JB status).

[galneon]

I updated my jailbroken Voyage to 5.12.0 (or something late in the 5.11.x series) before it was known, or widely known, that the usual method of blocking updates had been deprecated. Several weeks later, I was automatically updated to 5.12.1 to my surprise. The hotfix worked and I'm still jailbroken, but my Voyage never leaves airplane mode now and I miss Wikipedia lookups a bit. :/

I apologize if I've overlooked something here, but is there a new method for blocking updates yet? I've read of the speculative less than 200 MB free fix, but this is less than appealing for a few reasons. I'm used to blocking updates in hosts at the router level for gaming consoles and other things I don't want updating themselves, but I'm concerned the Kindle might not bother with hostname resolution and connects directly to a specific IP. That's not a very practical method for most auto-updaters, but a corporation the size of Amazon can hold a static as long as it wants... I'm not willing to risk my jailbreak as the screen savers plugin is a must for me--the Amazon screensavers are revolting. None of those images translate well to eink. For me, it's cover mode or another brand of reader.

[knc1]

Originally Posted by galneon

I updated my jailbroken Voyage to 5.12.0 (or something late in the 5.11.x series) before it was known, or widely known, that the usual method of blocking updates had been deprecated. Several weeks later, I was automatically updated to 5.12.1 to my surprise. The hotfix worked and I'm still jailbroken, but my Voyage never leaves airplane mode now and I miss Wikipedia lookups a bit. :/

I apologize if I've overlooked something here, but is there a new method for blocking updates yet? I've read of the speculative less than 200 MB free fix, but this is less than appealing for a few reasons. I'm used to blocking updates in hosts at the router level for gaming consoles and other things I don't want updating themselves, but I'm concerned the Kindle might not bother with hostname resolution and connects directly to a specific IP. That's not a very practical method for most auto-updaters, but a corporation the size of Amazon can hold a static as long as it wants... I'm not willing to risk my jailbreak as the screen savers plugin is a must for me--the Amazon screensavers are revolting. None of those images translate well to eink. For me, it's cover mode or another brand of reader.

I wrote a KUAL add-in called BBB (Block Big Brother).
It drops any IPv4 address assigned to Amazon.
It has not been updated since I posted it, but this is only IPv4, whose allocations where assigned years ago, there are no "new" IPv4 addresses to be had.
Well, there is still some traffic (no pun intended) in IPv4 blocks, like when some company goes bust and another company wants these blocks for their own use.
Translation:
Although written a number of years ago, the block assignments will rarely change.
And of course, the Linux network scripts are all in "user space" (like a KUAL add-in config - which they are).
And, there is documentation plus the existing script entries as examples if someone needs to remove an address range or add another address range. (perhaps for your use).

I do not have the slightest idea of the link to where I posted it.
I only write this stuff, not keep track of it.