Quote:
Originally Posted by SymmetryrtemmyS
The 5.6.5 Kindle jailbreak is out!
Quite easy to use, and unlike what the post states, you do not need to host a file on a webserver.
- Download the file attachments at these two links:
The Jail break archive (jb.zip) and
the Hotfix package .
Extract them on your PC.
- Inside the 'jb' folder created by extracting jb.zip, there is a file called jb.
Connect your Kindle to your PC with the USB cable.
Place the jb file in the top level of the mounted directory of your Kindle. right alongside the '/documents' directory.
Now 'safely remove' or 'eject' the Kindle and remove the USB cable.
The next steps require you to work quickly.
If you're going to set down your Kindle for a minute, place it in airplane mode first.
- Turn off airplane mode and connect to http://45.78.56.44/jb/ (Canada) in the Experimental Browser.
If that's down, use http://kindlefere.com/jb/ (China).
Make sure that you include the full URL, including the http:// and the trailing /
- Go to "Stage 1" and let it fail to load. Return to the URL you entered.
- Go to "Stage 2" and watch the instructions on your titlebar.
It will tell you to run the ;fc-cache command in the search bar when it's ready to proceed.
- Set airplane mode back on when finished.
- Place the .bin file from the 'Hotfix' zip archive in the mounted directory of your Kindle.
- Home -> Menu ->Settings -> Menu -> Update Device
If you are going to install any of the other add-in packages,
you must install: KUAL
and the KUAL extension: MrPI
The MrPI installer (a KUAL extension) **MUST** be used to install packages on the new firmware (both 5.6.5 and 5.7.2).
Now you are ready to add any other extensions that you find useful.
There are a few threads with compilations of links located here.
This jailbreak does survive an update to 5.7.2, but I chose to remain on the 5.6.5 firmware version.
NOTE: You can not block automatic updates using BackDoorLock.
That is known to not protect devices running 5.6.x firmware.
Choose instead one of the other alternatives.
In-line edits by knc1 |
One of the alternatives is here:
https://www.mobileread.com/forums/sho...&postcount=184
That one has a mixed history, some firmware versions can over-ride it, others can not.
Since it depends on the currently executing firmware version, not the version being upgraded to, we don't know if it will protect 5.7.2 from the next update.
I don't recall that its protection of 5.6.5 was ever tested/reported.
This one works on 5.6.5, see:
https://www.mobileread.com/forums/sho...&postcount=269
and the previous post test report.
The other two -
They are both the same sad song, only the names have been changed
In the top level of user storage, as seen over the USB cable when connected to a computer (no jb required):
- UPDATE~.BIN
This file name is one used by the OTA update process, the update_*whatever*.bin is renamed to this name to be processed.
Create a folder by this name - all uppercase, with the ~ and the uppercase extension.
Enter the folder and create a file by the name:
.keepme
Yes, the first character is a period.
Uncertain if any versions of the firmware can detect and circumvent this one.
This one does not work for 5.6.5:
https://www.mobileread.com/forums/sho...5&postcount=41
- testWrite.txt
Capitalization exactly as shown.
Create a folder by this name.
Enter the folder and create a file by the name:
.keepme
Yes, the first character is a period.
What effect this has on the update process, if any, is unknown.
But it certainly makes the indexer get its panties in a bunch.
(Your books may not get indexed - but the 5.6.x indexer does not get caught in a loop as in earlier firmware versions.)
Going by the ;dm log files, there are a lot of things that use this hard-coded file-name to discover if user storage is writable.
I actually expected this one to crash my PW-3 - - but it hasn't yet. 
YMMV on any/all of the above.
But my PW-3 is still running 5.6.1.1 after 7 months of Wifi usage.