Tools Software Jailbreak for PW2, PW3, PW3W, KT2, KV, KOA and KT3

[helpomg]

Say I were to get another PW3, I should be fine with one of these 'update_PW3_5.7.4_initial.bin' right?

Don't want to end up with another Kindle Paperweight™ :')

[geekmaster]

Originally Posted by helpomg

Say I were to get another PW3, I should be fine with one of these 'update_PW3_5.7.4_initial.bin' right?

Don't want to end up with another Kindle Paperweight™ :')

Another? The first one is not a paperweight. People in this thread have discussed how they debricked theirs (also caused in relatively rare cases by PW3 5.6.1.1 firmware).

[knc1]

Originally Posted by helpomg

Say I were to get another PW3, I should be fine with one of these 'update_PW3_5.7.4_initial.bin' right?

Don't want to end up with another Kindle Paperweight™ :')

It is not a Paperweight.
Not unless you where inventing your own version of the instructions more than you have admitted.

IF
You did not have an ad supported (Special Offers) Kindle ;
IF
You followed the directions about clearing any and all passcode entries ;

Then during the boot-up (with USB cable connected) it will present the USB storage for a few seconds.
Push the file:
DO_FACTORY_RESTORE
(all caps, no contents, no extension)
to the highest level of USB storage.

safely remove (or eject), disconnect cable, re-boot the Kindle, start over at step #0
and follow the directions this time. If you can not or will not, then its a "You bricked it, you fix it" situation.

otherwise -
read the threads about de-bricking (and/or jailbreaking) over the serial port.

[helpomg]

Originally Posted by knc1

It is not a Paperweight.
Not unless you where inventing your own version of the instructions more than you have admitted.

IF
You did not have an ad supported (Special Offers) Kindle ;
IF
You followed the directions about clearing any and all passcode entries ;

Then during the boot-up (with USB cable connected) it will present the USB storage for a few seconds.
Push the file:
DO_FACTORY_RESTORE
(all caps, no contents, no extension)
to the highest level of USB storage.

safely remove (or eject), disconnect cable, re-boot the Kindle, start over at step #0
and follow the directions this time. If you can not or will not, then its a "You bricked it, you fix it" situation.

otherwise -
read the threads about de-bricking (and/or jailbreaking) over the serial port.

I did not have Special Offers on my Kindle. I did not have any passwords for the device.

After step 4 in the first post, using the 5.6.1.1 firmware, it got stuck updating and then the error code 2 showed up. After I pushed the file DO_FACTORY_RESTORE to the Kindle next to /documents, it rebooted and got to a page where it asked to set my language (at this point, the left and bottom edges of the screen were frozen and only the right upper part was moving).

Then it restarted and got back to the error code 2 page (still with the frozen left and bottom edge). I've tried rebooting it to no avail. It also no longer shows me the USB storage when I connect it to the computer.

I see in this thread that some had success with the DO_FACTORY_RESTORE but a few others didn't.

I wasn't trying to imply that the Kindle was a bad product or the instructions here were no good. I realize that I'm only in this situation because I didn't read the top of the pastebin and it's entirely my fault that my Kindle is bricked. Just making a pun that might not have gone over too well. If so, I'm sorry!

Yes, I'm currently taking a look over at the jailbreak-over-serial-port thread.

Thanks for all the help!

[helpomg]

Originally Posted by geekmaster

Another? The first one is not a paperweight. People in this thread have discussed how they debricked theirs (also caused in relatively rare cases by PW3 5.6.1.1 firmware).

Sorry was just making a pun!
I've tried the DO_FACTORY_RESTORE method but it's still not working.
It also no longer shows me the USB storage when I connect it to the computer.

I'm looking at the jailbreak-over-serial-port thread now.

Thanks for all the help!

[Cinisajoy]

Originally Posted by helpomg

Sorry was just making a pun!
I've tried the DO_FACTORY_RESTORE method but it's still not working.
I'm looking at the jailbreak-over-serial-port thread now.

Thanks for all the help!

Idea. Charge it for at least 24 hours, then do the factory restore.
It might work.
Use a wall charger not a computer or power bank.

[helpomg]

Originally Posted by Cinisajoy

Idea. Charge it for at least 24 hours, then do the factory restore.
It might work.
Use a wall charger not a computer or power bank.

Thanks, but I forgot to mention that I also no longer see the usb storage when I connect it to the computer.

[shalym]

Originally Posted by helpomg

Thanks, but I forgot to mention that I also no longer see the usb storage when I connect it to the computer.

Yup. Try plugging it into a wall charger for at least 24 hours. Then plug it back into your computer and see if you see the USB storage.

Shari

[mjkarma]

great work . great jailbreak . great effort . tnx a lot
i really need this jaibreak . Koredaer is amazing especially its reflow capability

[NiLuJe]

Once the counters are blown, you might have to resort to scripting pushing the FACTORY reset flag, the devices get stupidly shutdown by the upstart jobs really quick.

I don't recall if anyone actually ever did this successfully on recent devices, but I seem to recall various successful experiments of the sort around the old data.tgz jailbreak on older devices (where pushing the rescue file had to be done programmatically).

[eschwartz]

Yes, there are recent instances of recovery with a rapidly-disappearing userstore.

As a recap for all concerned, you can do it on linux by running the following in a terminal prompt:

mountpoint=/media
# Usually devices are mounted to /media but udisks2 is insane by default.
[[ -d "/run/media/$EUID/" ]] && mountpoint="/run/media/$EUID/"
# Why must Ubuntu patch the world???
[[ -d "/media/$EUID/" ]] && mountpoint="/media/$EUID/"
while true; do
    touch $mountpoint/Kindle/DO_FACTORY_RESTORE
done

And then rebooting the Kindle while it is attached to the computer.

Some similar process can probably be done in Windows' cmd.exe but I have no idea what the syntax might be. Also, Windows is annoying because mounting drives and getting access may or may not be delayed while it asks you stupid questions like "do you want to use your Kindle for ReadyBoost (whatever terribly unwise thing that may be )".

[NiLuJe]

@eschwartz: That implies automounting in /media/Kindle .

But yeah, some form of automounting, whatever the target directory, is *probably* helpful when doing these kind of things .

A (hopefully) bulletproof approach would be via udev rules, as I think was recently mentioned?

[eschwartz]

Well, my Kindle recently took to claiming to be an internal device, so it doesn't get automounted and udisks2 wanted sudo to mount it!
(But calibre still mounts it for me, so I don't care anyway.)

And despite the ridiculous move of media devices to weird obscure directories, I added the following udev rule:

[eschwartz@arch ~]$ cat /etc/udev/rules.d/99-udisks-fix-media.rules 
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"

Which I think is also automatically used on Ubuntu (intelligent policy choice). That should cover the common non-techie case. EDIT: Or they just stuck with old udisks1 for a really long time.
If not, well, I cannot make ALL the disclaimers, it would take too long.

[NiLuJe]

@eschwartz: Whaaaat, you don't like /run/media/$EUID/$FSLABEL as a mountpoint? .

[eschwartz]

One of the things I have always admired about Linux is the fact that filesystems have stable and predictable mountpoints.

Shure 'nuff, they promptly did a Windows. Although it isn't like they haven't done other Windowses before...
It's like the only thing that matters is the point-and-click file browser. Insanity.

The rationale offered was the most hysterical part.
"Multiple USB devices mounted by different user accounts will *confuse* people. And /run is cleaned on reboot."
Or, "security". x2

Also, I updated the above code to be fully idiocy-compliant.