NiLuJe
First I have not specified the necessary commands in runme.sh - only the test.
And time up to YKNR differs at each broken loading - imho, sleep strongly reduced probability of start runme.sh...

Many thanks for the fast help!
All of you the greatest experts on Kindle!!!

Good to see that you managed to solve it.

Just for reference, could you please post the exact runme.sh that you used? It's not entirely understandable from your post if your original version worked, or if you had to adapt it some more.

You are (to my knowledge) the first person who debricked a "Your Kindle Needs Repair" Paperwhite, so this is invaluable information for the many, many other people who will undoubtedly come in the future with similar problems.

@kaznelson: I added your success report to the "success reports" list. Using a custom runme.sh script is the OLD way of debricking, before we started recommending simple debricking by simply flashing uncorrupted firmware images.

It is great to have the "old debricking method" working here, but I think we still need to find out how to get USB Downloader mode working. Or at least, we need a way to make using runme.sh more noob-friendly. Thanks guys!

@kaznelson: I added your success report to the "success reports" list. Using a custom runme.sh script is the OLD way of debricking, before we started recommending simple debricking by simply flashing uncorrupted firmware images.

It is great to have the "old debricking method" working here, but I think we still need to find out how to get USB Downloader mode working. Or at least, we need a way to make using runme.sh more noob-friendly. Thanks guys!

Well... yeah, runme.sh was actually the first method discovered, but it required/requires at least a half-way working system to function.

The USB downloader method is much more powerful (and preferrable, of course), but at this time we simply don't know how to make the PW hardware enter that mode. If anybody figures out a hardware "key combination" that makes the PW show up as 15A2:0052 (or even as another unsupported device), that'll be a major breakthrough for PW debricking.

It is great to have the "old debricking method" working here, but I think we still need to find out how to get USB Downloader mode working.

I've just remembered that I've found how to enable USB downloader mode on KT while tinkering with it in hopeless tries to debrick after changing localization-related file in a way that fail some program and, therefore, some upstart job and, therefore, whole boot process. Pressing that single button in reboot moment was just an incidental idea.

But USB Downloader mode entered from a failed boot does not communicate with USB Downloader apps. You really need to use the magic key, in my experience. If you really did discover a useful way to get there without the magic key, please enlighten me.

Well... yeah, runme.sh was actually the first method discovered, but it required/requires at least a half-way working system to function.

The USB downloader method is much more powerful (and preferrable, of course), but at this time we simply don't know how to make the PW hardware enter that mode. If anybody figures out a hardware "key combination" that makes the PW show up as 15A2:0052 (or even as another unsupported device), that'll be a major breakthrough for PW debricking.

USB Downloader mode sure simplified things when the kindle was "too bricked" for runme.sh script debricking which required opening the kindle and using its internal serial port. In fact, simple debricking is so simple that it is now used to do a "full factory reset" without needing to uninstall a pile of hacks. Yes, we need that for the PW too.

I sure hope we do not need to remove the cover of a PW to activate USB Downloader mode.

Pressing that single button in reboot moment was just an incidental idea.

Quote:

Originally Posted by geekmaster

But USB Downloader mode entered from a failed boot does not communicate with USB Downloader apps. You really need to use the magic key, in my experience. If you really did discover a useful way to get there without the magic key, please enlighten me.

I was speaking about "Home" button (which is the single button that is non-pressed in reboot moment by default). And "failed boot" was just a failed init sequence represented by a stuck image of boy under tree. So I've rebooted many times after seeing that image and once decided to press Home button also just before a moment of depressing power button (i.e. "reboot moment").

I have now used 7-Zip (all ok but haven't checked yet) but after uninstalling and reinstalling ATK, still it's telling me no USB detected. During install I did nothing differently but this time it asked me to confirm I wanted half a dozen drivers installed, had to say yes to each, which gave me hope that the drivers were installing... but no.

Also during install, a DOS-look window came up (years since I've seen that) and told me I had to have administrator privileges to install these drivers, which surely is irrelevant as (a) I'm the only user and have full privileges (always sounds so posh, like the members' enclosure), and (b) ATK did install. ??

Or should the kindle be connected before running ATK? In the debrick guide, plugging it comes next, not before.

Aaagh...

ps I have got 32bit Win7. The noob debrick gives no other suggestions for getting the USB drivers to work.

The author of the guide should be subscribed to that thread.
If you don't find the answer then post your question there about how get the driver to install.

:

I was *this* close to giving up and buying a new Kindle.
But the comatose is returned!

And it's not even going slow as it was for weeks leading up to this.
I couldn't have wifi on without losing it on the first or second page turn.

THANK YOU.

ps A couple of changes to the wiki page - but I can't do it (no-brain strikes...) so if someone else has the chance:
- to swap steps 5 and 4
- to swap steps 9 and 10 (because step 10 resets first box of operation settings section to all zeroes)
- maybe mention the right-click on ATK and select 'Run as administrator'; I thought it meant being able to change user passwords etc in Windows, believed I was unlimited. Bright enough, but zero experience. (If it had been a dead language on the other hand...)