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

[Cinisajoy]

Originally Posted by knc1

The only thing your missing is the correct instructions for your model:
https://www.mobileread.com/forums/sho...d.php?t=186645

See post 415. .
Thanks for the confirmation.

[knc1]

Originally Posted by Cinisajoy

See post 415. .
Thanks for the confirmation.

I saw it, but I thought the person posing the question had missed it.
So I made another try, just to be sure.

[Cinisajoy]

Originally Posted by knc1

I saw it, but I thought the person posing the question had missed it.
So I made another try, just to be sure.

Great thinking.

[knc1]

Another early 'start of day: # ...' report update made.
First 1,000 downgrade day noted.

The link in my signature is now working and the file is being distributed on cdn77.
Alice is also still on cdn77.

The traffic pattern of those small files leads to at least one question for cdn77 marketing:
"Hey, if we are paying to have France served out of Paris, why is all of France being served from Germany?"

And a question for our members and viewers:
"Don't any of you live in Phoenix?"
The data center in Phoenix is reported as "in service" but it isn't being hit anymore that the Paris data center is."

So keep on clicking Alice and my signature, whoever you are, wherever you are.

[bArDBQ]

Originally Posted by bArDBQ

Hey there,

I have the exact same problem.

I have a PW3 (G090G10......)
It was initialy running 5.7.4.1


I followed every steps. I used update_PW3_5.6.1.1_initial.bin for the downgrade. Got stuck in boot loop that ends with "REPAIR NEEDED"

Repair Code: 2
Version: 2634130033

I added the "DO_FACTORY_RESTORE" file in the root folder (that's the only file/folder there).

It's all CAPS and there is no file extension.

When I reboot it simply keeps doing the exact same thing and comes back to the REPAIR NEEDED screen....

Not sure what went wrong... Thanks for your time and devotion guys! I'll keep my fingers crossed!

G.

Hey guys,

So, I tried to restore my Kindle PW3 multiple times today. Still stuck with the same problem Nothing seems to be working. Anybody has another idea to unbrick my PW3?

I have no clue why the "DO_FACTORY_RESTORE" method seems to be working for everyone except me... I'm kinda lost... Be assure I double checked everything in order to make sure I didn't do any stupid error...

Thanks for your help!

G.

[knc1]

I added the "DO_FACTORY_RESTORE" file in the root folder (that's the only file/folder there).

At the specific time you do this, how much free space is shown on USB storage?

And exact, specific, details of PC in use, its operating system, file transfer commands used -
Any and everything related to this one step.

[bArDBQ]

Originally Posted by knc1

At the specific time you do this, how much free space is shown on USB storage?

And exact, specific, details of PC in use, its operating system, file transfer commands used -
Any and everything related to this one step.

Space used: 131 072 bytes - 128kb
Free space: 3 269 066 752 bytes - 3,04gb

Using Windows 10 Family 64bits
Intel Core i5-2410M 2.30Ghz
6gb RAM

For file transfer I simply created a new text file from the right click contextual menu on the desktop that I called DO_FACTORY_RESTORE. I removed the .txt extension and just did a copy paste from desktop to the kindle file storage during the few seconds it is available. The DO_FACTORY_RESTORE file is completely empty (8 bytes).





Thanks for your help

[knc1]

I had to ask because the kindle has a mode where the storage available shows up as zero and at the same time does not show any files.
(You mentioned the one but not the other.)

My next guess is that it has something to do with the 'Readyboost' feature.
See if you can disable that or work around it somehow (like, copy the file using the command line).

Or even better yet, change computers.
Something older or something Linux or MacOSx

[geekmaster]

I have caught ReadyBoost writing (and immediately deleting) a temp file on most USB devices when they are detected, including Kindles. That is definitely a concern, especially with a short time window.

[bArDBQ]

I checked the Kindle's storage properties in Windows and Readyboost is not enabled for this device. I tried to copy the file using command line but I get the same result. Will try to create a Linux bootable flash drive tomorrow and I'll retry the process using Linux.

Crossing my fingers!

Thanks

[knc1]

@both:
Due to the very short time window -
I have considered writing a custom u-dev rule (which gets run the moment the kernel detects a hardware change) to poke the file name onto the Kindle.

**considered** but never done.

With the number of 'bootloop hung' PW-3s out there now, perhaps it is time for someone to re-visit that idea.
(It should not be too hard - but time is not something I have - this will have to be delegated to a volunteer.)

[geekmaster]

Originally Posted by bArDBQ

I checked the Kindle's storage properties in Windows and Readyboost is not enabled for this device. I tried to copy the file using command line but I get the same result. Will try to create a Linux bootable flash drive tomorrow and I'll retry the process using Linux.

Crossing my fingers!

Thanks

Even with ReadyBoost disabled, it STILL writes the file (a speed test) to decide whether to ask you if you want to use it for ReadyBoost. It happens so quickly it is hard to see it. That is why I said no consistent way to eliminate that unwanted feature. Even if you can disable the test, switching USB ports re-enables the test again.

Linux has no such problems (yet).

From linux, no need to copy a file. Just touch one repeatedly in a loop (perhaps with a short delay) to make sure one slips in durng that short time window.

[eschwartz]

knc1,

Why a udev rule? What is wrong with `while true; do touch /media/Kindle/DO_FACTORY_RESTORE; done`?
Anyway, what does the udev rule do if the filesystem isn't mounted yet (which isn't instantaneous, and therefore will probably be a genuine problem)?

[knc1]

Originally Posted by eschwartz

knc1,

Why a udev rule? What is wrong with `while true; do touch /media/Kindle/DO_FACTORY_RESTORE; done`?
Anyway, what does the udev rule do if the filesystem isn't mounted yet (which isn't instantaneous, and therefore will probably be a genuine problem)?

The loop is very often fast enough.

The udev rule is faster, more certain and those also 'fire' when a file system is mounted (detected) not just when the hardware bus changes.
But there could be distribution differences that would prevent a 'universal' solution.

Maybe someone could post a version of that loop for Chinese-Windows.
That is where many people have boot-loop'd PW3W devices.

[knc1]

The new index page for the new distribution system is sleeping:
http://idx.gunshi.org

Will see just how many 'bots pick up the "site missing" message from this post.