5.6.5 Jailbreak (closed-kindle) -- released!

[baalajimaestro]

Thank you so much for those information sir!

B.Baalaji

[LordDunlow]

Originally Posted by eschwartz

The K2, DX, DXG are all still showing fw2.5.8
The K3 still shows 3.4.2 (I think they already fixed that one. )

The K1 seems to have gotten an emergency update from 1.2 to 1.2.1 and I unpacked it with kindletool -- it updates /opt/usr/java/lib/security/cacerts
That is all.

I just pulled my Kindle 2 out to use and discovered it wouldn't connect because of this update. I'm running 2.5.8 jailbroken. Any chance I can just add this file somehow or do I have to uninstall everything, then do the official update?

Thanks!

[knc1]

Originally Posted by LordDunlow

I just pulled my Kindle 2 out to use and discovered it wouldn't connect because of this update. I'm running 2.5.8 jailbroken. Any chance I can just add this file somehow or do I have to uninstall everything, then do the official update?

Thanks!

Uninstall everything and then install the 2.5.8 that Amazon now has posted for your K2.
It includes changes to support TLS in addition to the changes reported above for the K1 (more than just the certificates file).
Amazon did not update the version number when they rolled last year's update into the 2.5.8 firmware package.
So don't be fooled by the fact that the one they have posted and the one you are running are the same version number, they are different contents.

[NiMa]

Sorry to bring this thread up being so late...
But thanks to everyone who made that possible! I received a bargain PW2 today and it was absolutely effortless to jailbreak the device. I studied a bit about the code and it's very interesting.

Also, a remark; thinking I screwed up my KUAL install because it wasn't showing up (in fact I only had to put it in the Documents folder!), I factory-reset the device a few times after the jailbreak and tried to re-run it. Interestingly enough, it said that it failed but I found out how to install KUAL properly and it worked fine. Also installed kterm and KOReader, both work fine, no problems.
Did I mis-read something, but don't Kindles undo the jailbreak when a "factory" reset is done? Because mine appparently did not...

EDIT: after investigating, it turns out that the Kindle would be one of the first-gen PW3s if I look up the serial number... It seems that it has been marketed as the PW2 with a 300 ppi screen version. Is it still a PW2?

[NiLuJe]

Depends on the sequence of events. A single factory reset can be recovered (with a couple of reboots, topped by a hotfix refresh just to be safe). A factory reset back to back to an official update will kill it.

Also, check the S/N to stop guessing the exact model. There never was a 300dpi PW2 .

[NiMa]

Originally Posted by NiLuJe

Depends on the sequence of events. A single factory reset can be recovered (with a couple of reboots, topped by a hotfix refresh just to be safe). A factory reset back to back to an official update will kill it.

Also, check the S/N to stop guessing the exact model. There never was a 300dpi PW2 .

OK, so this confirms my suspicions, thanks! I read a couple of news articles about that and they all said that Amazon was selling the PW2 with 300 dpi. So they probably mixed up models...
EDIT: but the model number on the device is DP75SDI ... are you sure there never was such a version?

And for the jailbreak, I must have done 3 factory resets after that and it was still jailbroken (and it is still now). Also, I rebooted two or three times after each factory reset to see if nothing was missing or was broken. But KUAL, kterm, USBNetwork and KOReader installed just fine and I have root access to the Kindle. So maybe it is specific to the jailbreak involved?
Also, what does a "reset" does? Does it just remove the files in /var/local + /mnt/us and it ends there?
EDIT: is there a way to prevent the Kindle from updating away from 5.6.5 other than airplane mode? I don't need the lab126 services to be running, I'd just want to get an Alpine chroot running on this thing...
anyways thanks for the reply, and I hope that soon I'll have a better understanding of how the device works now that I've got one, as I do with the Kobos

[NiLuJe]

Originally Posted by NiMa

EDIT: but the model number on the device is DP75SDI ... are you sure there never was such a version?

Model numbers are much murkier than the device code encoded in the S/N, but, as I happen to have a PW2, I can definitely assure you that that's a PW2 .

Originally Posted by NiMa

Also, I rebooted two or three times after each factory reset to see if nothing was missing or was broken.

And that's precisely how you make sure a factory reset doesn't permanently hobble the JB, so, no mystery there.

Originally Posted by NiMa

Does it just remove the files in /var/local + /mnt/us and it ends there?

Yep, much like the "new" factory reset on Kobo.

Originally Posted by NiMa

EDIT: is there a way to prevent the Kindle from updating away from 5.6.5 other than airplane mode?

There's an OTA block button in the KUAL helper extension, it's mentioned in the instructions.

[NiMa]

Originally Posted by NiLuJe

Model numbers are much murkier than the device code encoded in the S/N, but, as I happen to have a PW2, I can definitely assure you that that's a PW2 .



And that's precisely how you make sure a factory reset doesn't permanently hobble the JB, so, no mystery there.



Yep, much like the "new" factory reset on Kobo.



There's an OTA block button in the KUAL helper extension, it's mentioned in the instructions.

thanks for the KUAL extension, I didn't see that while searching through the forums. I'll go check that out ASAP.
edit: I've looked at the script that does that and it does the usual update.bin.tmp.partial trick. I read that it didn't work with some firmwares. Will it work with 5.6.5?

But I've checked the RAM with free -m and it seems to have 512mb inside...
The display is astoundingly beautiful, maybe better than some of my Kobos (although my Glo HD's defunct screen would have been pretty similar) and it is indeed 300ppi, as it states in the welcome screen with the "Get started" button and as I can state with my own eyes.
I might get some serial equipment to see if I can (try) to have some fun downgrading the firmware or upgrading it the way I want.

thanks again!

[melksnor]

Originally Posted by NiMa

here's a link to the news article I found: https://goodereader.com/

There's your problem. That site is known for making up stuff. You can't trust anything on there.

[NiMa]

Originally Posted by melksnor

There's your problem. That site is known for making up stuff. You can't trust anything on there.

yeah maybe... but some are true.
removed it from my post.

[NiLuJe]

Originally Posted by NiMa

But I've checked the RAM with free -m and it seems to have 512mb inside...

That would confirm my "model numbers are meaningless" comment above. Check the S/N.

The PW2 only had 256MB of RAM (and a 758x1024 212dpi screen), and its screen should *technically* have been on par with a Kobo Mk. 6 (e.g., typically, a Glo HD). In practice, it'd have been better than the Kobo, because Amazon was very much trouncing everybody at driving those screens. Kobo managed to catch up w/ the Mk. 7 series, though.

[NiMa]

Originally Posted by NiLuJe

That would confirm my "model numbers are meaningless" comment above. Check the S/N.

The PW2 only had 256MB of RAM (and a 758x1024 212dpi screen), and its screen should *technically* have been on par with a Kobo Mk. 6 (e.g., typically, a Glo HD). In practice, it'd have been better than the Kobo, because Amazon was very much trouncing everybody at driving those screens. Kobo managed to catch up w/ the Mk. 7 series, though.

ok, it is definitely a PW3 then.
thanks!

[NiLuJe]

Originally Posted by NiLuJe

Check the S/N.

I mean, I don't know how many times I'm going to have to repeat that?
It's the very first thing the sticky asks you to do, there's a reason for that.

[NiMa]

Originally Posted by NiLuJe

I mean, I don't know how many times I'm going to have to repeat that?
It's the very first thing the sticky asks you to do, there's a reason for that.

Yes, I checked it beforehand but I was not sure about the model number. It clearly showed that it was a PW3 but I didn't know what to think...