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.

How to restore Paperwhite? ("Repair Needed")
Damaged this file: AdManager.jar.

USB-disk is accessible less than 10 seconds, "Magic Key" for the diags menu is unknown...

Diags menu doesn't use a "magic key". On previous kindles you start the diags menu by booting with an ENABLE_DIAGS file on the USB Drive, but this method does not work for the PW.EDIT: I have explored the PW diags menu, but I cannot remember how I got there... I hope I posted it somewhere. I see that I posted information ABOUT using it but now HOW to get there:https://www.mobileread.com/forums/sho....php?p=2265817

ixtab
I experimented with AdManager.jar and was mistaken - have cleaned old, and new have put in other place.
The command is necessary:
mv -f /opt/amazon/ebook/lib/AdManager.jar.bak /opt/amazon/ebook/lib/AdManager.jar

How to create correct data.stgz?

geekmaster
I download MfgTool, but it see Kindle less than 10 seconds. Communication interrupts, activate "Repair Needed" screen.
What it is possible to make?

Does anybody know how to get into the diags menu on a Paperwhite. I have explored it TWICE, and yet, I cannot remember how to get there now. EDIT: Oh yeah, I remember now. After installing NiLuJe's simple usbNet repackaged for the PW, I did "idme -d --bootmode diags". It is nice that amazon added the "-d" parameter to idme, when booting from main (unlike the K4 and K5 where it was only available in diags). I was planning to add a main startup script that looks for /mnt/us/ENABLE_DIAGS and changes bootmode to diags before restarting.

@kaznelson: At which point in the boot process does the PW throw the 'YKNR' screen, exactly?

If it's during/after the splash screen with the spinner, you might be able to get in via SSH if you enabled ssh @ boot, and throw a quick 'stop framework' [or whatever job actually handles the YKNR fallback].

@geekmaster: I assume you used idme to set the bootmode var from SSH on main? (Because, yeah, I was starting to wonder how you managed to use imx_usb_loader, since I thought it relied on the device being in recoverymode ^^). No idea if the diags exit properly sets this back to main, though.

@geekmaster: I assume you used idme to set the bootmode var from SSH on main? (Because, yeah, I was starting to wonder how you managed to use imx_usb_loader, since I thought it relied on the device being in recoverymode ^^)

See my edit above. Yes, that whole (now removed) MfgTool and /imx_usb_loader comment was just a brain fart (I am now drinking my morning coffee). It was "idme -d". Unfortunately, that does not help us for debricking if main cannot boot.

@kaznelson: At which point in the boot process does the PW throw the 'YKNR' screen, exactly?

If it's during/after the splash screen with the spinner, you might be able to get in via SSH if you enabled ssh @ boot, and throw a quick 'stop framework' [or whatever job actually handles the YKNR fallback].

@geekmaster: I assume you used idme to set the bootmode var from SSH on main? (Because, yeah, I was starting to wonder how you managed to use imx_usb_loader, since I thought it relied on the device being in recoverymode ^^). No idea if the diags exit properly sets this back to main, though.

@NiLuJe: does the jailbreak still support RUNME.sh? That would be the easiest option, I guess

@kaznelson: remember that if the PW uses the same logic as the Touch, you will also need to remove the "marker" file which causes the YKNR screen to appear in the first place. (echo 0 > /var/local/upstart/lab126_gui.restarts)

...and, assuming that you get it to run again: Don't make the same mistake again. If you only want to mess around with java stuff, your safest bet is to "restart framework" via ssh, instead of actually rebooting.

@NiLuJe: does the jailbreak still support RUNME.sh? That would be the easiest option, I guess

Stock firmware provides some sort of poor man's RUNME.sh. Check /etc/upstart/filesystems_var_local.conf. There could be
/var/local/system/fixup and /var/local/system/onetimefixup. Of course, creating of these files isn't so easy as creating of RUNME.sh on user parition , but wuth data.stgz it's a feasible task.

(These files should have executable bit set. And include shebang line if they are shell scripts.)

At which point in the boot process does the PW throw the 'YKNR' screen, exactly?

I press power button:
1) Screen blinks, ~5 seconds the screen with a tree and bookboy.
2) Screen blinks, ~7 seconds the screen with a tree and bookboy, bottom on a circle of a stick (not progressbar).
3)Screen light, YKNR-screen activate.

That looks correct to me. You should append some line which allows you to verify that the script was actually run - like "touch /mnt/us/kaznelson.ok" or "cp /opt/amazon/ebook/lib/AdManager.jar /mnt/us/", or whatever. If it does work, then it's likely that the lab126_gui.restarts is not the correct file anymore. Try with "rm -f /var/local/upstart/*.restarts" ...

Or, in the worst case, you can go for the brutal method:

dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K

However, I cannot guarantee that this will work on the PW (it does on the Touch). In the worst case, it could make things even worse. You have been warned, so use this at your own risk (if at all).

@kaznelson: Right, there's a bunch of sleeps in the JB. That probably doesn't help.

Note that if reseting the counter only made it loop a bit more, that's because you didn't actually fix what was wrong (besides reseting the counter), and doing the same thing in a script without the sleep calls probably won't change much.

EDIT: That said, here's a nerfed JB that doesn't sleep. (There's absolutely no safety checks anymore, don't use this on anything other than a K5 [well, not that you can in this form, but, still]).