5.6.5 Jailbreak (closed-kindle) -- released!

[doctorfrog]

Originally Posted by knc1

Not possible.
The 2014 runs series 4.x firmware.

But if you skipped a year due to lack of interest, actually meant 2015 (its 2016 now), then you mean a KT-2
my bad, that is what the wiki table says.
and my initial thread on the KT-2 is dated Nov. 2014
(I couldn't have written about it, if I didn't have it then )

Ah, I don't have 100% faith in Wikis for a reason. Unlike forum posts, they're reasonably easy to find information. And unlike forum posts, there's no telling just how out of date the information you're going to find (even slightly). I always like to reference my reliance on them just in case. So I guess mine's a Kindle Basic c. 2015.

[doctorfrog]

Originally Posted by NiLuJe

@doctorfrog: Okay, then first and foremost, re-install the JB hotfix to make sure everything is back in order after your factory reset.

Then, yeah, double-check the date/time, because my other "fix" for those kind of weird issues was "do a factory reset", but you've already done that .

Ok, I did some searching, and since I'm new to this forum, that took some doing.

Referencing this series of posts: https://www.mobileread.com/forums/sho...postcount=1939

There's no KUAL button to do this, but I should be able to issue the command ;st from the search box as described in the linked post:

Skip that, I found it - in the home page search bar, enter:
;st YYYY-MM-DD hh:mm:ss
the ':ss' is optional, no access to setting the timezone.
the letters should be obvious, I.E:
;st 2016-04-09 07:50
would work for me, now.

update: Nah, didn't work. MOBI books still forget their places.

I ran the command with current date/time, flipped between two MOBI books, still happens. Restarted the device, same result. Removed the books, re-added them, same, restarted, same.

Just for fun I tried to change the time to something else to confirm the command was working, and it appears to be (confirmed by creating a Clippings entry).

It's not completely broken, other tested functions are fine and Calibre can convert MOBI to AZW without issues, I believe, but let me know if I can help narrow this down further.

update2: just noticed that the Kindle calls these "Docs" and highlights them as "personal." Don't recall seeing that before, could be it's treating them as non-books? Or my memory's bad. I'm done fiddling with this for tonight but I suppose for science I could wipe out my documents folder and rebuild it and see if that fixes things. Failing that another factory reset and hotfix reinstall if I just can't stand not knowing.

[knc1]

Originally Posted by doctorfrog

Ah, I don't have 100% faith in Wikis for a reason. Unlike forum posts, they're reasonably easy to find information. And unlike forum posts, there's no telling just how out of date the information you're going to find (even slightly). I always like to reference my reliance on them just in case. So I guess mine's a Kindle Basic c. 2015.

No, the Kindle currently named "Kindle Basic" by Amazon Marketing (in most countries) was introduced in November, 2014 (in the USA).

When you say "Wiki" - if you mean:
https://wiki.mobileread.com/wiki/Kindle_Serial_Numbers
That is the exception that breaks your general rule.

That page is as up-to-date as it can be, it is maintained along with KindleTool (the packager/un-packager for the model locked update_*.bin packages).

At the moment there is one model known that is not listed -
Only because the person who reported it has failed to give the details of country and options.

= = = =

How to find things on this forum is a FGA - which was near the first of things you found.
At least it was if you started at the sticky thread: "Where do I start".

[NiLuJe]

@doctorfrog: That thery're flagged PDOCs might be interesting...

How did these MOBI files find their way on your device? (Because Calibre should do the right thing to get plain mobi flagged as Books, not pdocs).
Things *might* be wonky for PDOCs without network connectivity...

EDIT: Your other possibility is updating to 5.7.x (only if you're sure you fixed the state of the JB). 5.6.5 is known to suffer from a number of weird quirks on some devices.

[Cinisajoy]

Originally Posted by doctorfrog

Ah, I don't have 100% faith in Wikis for a reason. Unlike forum posts, they're reasonably easy to find information. And unlike forum posts, there's no telling just how out of date the information you're going to find (even slightly). I always like to reference my reliance on them just in case. So I guess mine's a Kindle Basic c. 2015.

I understand you don't like wikis. But, here is an important detail. If the person or people trying to help you say go to our wiki and find your model it is so they know which particular model you have and what they call it. Otherwise, they cannot give you help.

Note all the helpers here get paid the very large sum of $0. So please do what they ask. It makes helping so much easier.

[NiLuJe]

A whole zero! THAT'S SO NICE!

Thanks! .

[geekmaster]

Originally Posted by Cinisajoy

I understand you don't like wikis. But, here is an important detail. If the person or people trying to help you say go to our wiki and find your model it is so they know which particular model you have and what they call it. Otherwise, they cannot give you help.

Note all the helpers here get paid the very large sum of $0. So please do what they ask. It makes helping so much easier.

I wish I made $0. It is COSTING me to work here. I keep BUYING more kindle models to support. And the utility costs to run my computer, and the internet bandwidth to connect my computer to MobileRead.com.

[Barty]

Originally Posted by geekmaster

Crap! is the F-word appropriate here? The ORIGINAL instructions say to go to a website after copying the jb files to the kindle, so I turned off airplane mode and I had just connected my PW2 to my wi-fi network, when I got a phone call. When I got off the phone call, my PW2 said "Your Kindle has been Updated!". It is no longer on FW 5.6.5. It is on FW 5.7.4.

What now? Grr... F-F-F!

The F word is apt because serial is now the only choice you have for jb, at least until BD or someone else finds another exploit.

For others thinking of using this jailbreak: when you open the browser, it will ask to turn off airplane mode, ie turn on Wi-Fi, but do not hit ok, hit cancel instead. The browser will happily open a local file eg file:///mnt/us/whatever without a Wi-Fi connection.

[geekmaster]

The local file method did not work for me, for whatever reason...

[knc1]

Originally Posted by geekmaster

The local file method did not work for me, for whatever reason...

Hmm...
I have two similar reports still open, waiting for replies.

5.6.5 on what device?
- - Not that it should make any difference, but information is needed - -

[geekmaster]

Originally Posted by knc1

Hmm...
I have two similar reports still open, waiting for replies.

5.6.5 on what device?
- - Not that it should make any difference, but information is needed - -

PW2. It is since updated itself, much to my displeasure, to whatever amazon saw fit to put on it without my explicit consent. Most annoying until I find my big box of devkits and USB serial adapters and logic analyzers and whatnot... I am seriously toying with the idea of bending a spare kindle into being my USB serial adapter.

Branch Delay suggested trying the ORIGINAL method, but that involved connecting to a remote web server, which involved turning on wifi, which involved (lacking adequate anti-amazon firewall rules) getting my firmware hijacked by amazon, as mentioned above.

My state (Minnesota) is toying with the idea (actually on paper) of making it illegal for companies to lock down devices owned by the consumer. Surely some large company will stomp on such a potential law (with a heavy bag of cash) before it sees the light of day...

Anyway, 5.6.5 on a PW2, local file jailbreak, was not working for me (and others also with PW2s), depite the fact that it was originally developed on a PW2. Something must have changed somewhere along the way -- but one thing -- I did *NOT* do a factory reset immediately before the local file jailbreak.

[knc1]

Let's collect build identifications 5.6.5 (digits) <- the digits.
Not that we can do anything about it now.

[geekmaster]

Originally Posted by knc1

Let's collect build identifications 5.6.5 (digits) <- the digits.
Not that we can do anything about it now.

I have the firmware (download links in previous post). Extracting... Unlike other firmwares I have examined, this one does not have an install script. The uImage and roots.img.gz files must get flashed automagically. The subversion must be encoded into it somewhere. /etc/prettyversion.txt just says "Kindle 5.6.5 (~~otaVersion~~)". The install scripts replace that with the real otaVersion when it is copied to /mnt/us/system/version.txt. Unfortunately, the only copies of that file I have for this device say "Kindle 5.6.2.1 (263439 002)" and "Kindle 5.7.4 (292962 018)". So we need to get the 5.6.5 ovaVersion from somebody else who is running 5.6.5 on their PW2 (and where this method of JB also fails).

[NiLuJe]

FWIW, to parse the /etc/version.txt file (mostly) correctly:

# Get the FW version
fw_build_maj="$(awk '/Version:/ { print $NF }' /etc/version.txt | awk -F- '{ print $NF }')"
fw_build_min="$(awk '/Version:/ { print $NF }' /etc/version.txt | awk -F- '{ print $1 }')"
# Legacy major versions used to have a leading zero, which is stripped from the complete build number. Except on really ancient builds, that (or an extra) 0 is always used as a separator between maj and min...
fw_build_maj_pp="${fw_build_maj#0}"
# That only leaves some weird diags build that handle this stuff in potentially even weirder ways to take care of...
if [ "${fw_build_maj}" -eq "${fw_build_min}" ] ; then
        # Weird diags builds... (5.0.0)
        fw_build="${fw_build_maj_pp}0???"
else
        # Most common instance... maj#6 + 0 + min#3 or maj#5 + 0 + min#3 (potentially with a leading 0 stripped from maj#5)
        if [ ${#fw_build_min} -eq 3 ] ; then
                fw_build="${fw_build_maj_pp}0${fw_build_min}"
        else
                # Truly ancient builds... For instance, 2.5.6, which is maj#5 + min#4 (with a leading 0 stripped from maj#5)
                fw_build="${fw_build_maj_pp}${fw_build_min}"
        fi
fi

(Snippet from the device_id script in the Helper extension).

[Cinisajoy]

Originally Posted by Cinisajoy

I understand you don't like wikis. But, here is an important detail. If the person or people trying to help you say go to our wiki and find your model it is so they know which particular model you have and what they call it. Otherwise, they cannot give you help.

Note all the helpers here get paid the very large sum of $0. So please do what they ask. It makes helping so much easier.

I thought of the perfect analogy today.
A southerner walks into a New England/British restaurant.
She orders biscuits and gravy.
The waitress asks if she is sure that is what she wants.
Southerner says yes.
The waitress brings her out exactly what she ordered.
Cookies covered in tomato sauce.
The southerner was expecting a baking powder round bread like a scone and milk gravy.

So as one can see, make sure everyone is speaking the same exact language or you might get something useless and inedible.