MobileRead Forums - View Single Post - Noob's guide to debricking through ATK :D

notimp · 09-24-2012, 02:58 AM

You are doing nothing wrong. Its just an extreme oversight on part of the people who have written the tutorials for debricking. Tutorials in which they forgot to mention where exactly you should unzip files, in which broken downloads are still linked and people encouraged to flash files with checksum errors, tutorials where it is not mentioned that you should leave out 0x when entering certain hex numbers in adress fields...

One of those "oversights" on part of the tutorial people was to mention, that ATK only comes with 32bit drivers. When you install it on a 64bit Windows system, the driver installation routine is simply skipped. If you try to install the drivers manually (by executing the bat files coming with ATK you will see that the program used to register the drivers simply refuses to work on 64bit systems, the same goes for the uninstallation of ATK, where actually for the first time ever ATK decides to push error messages to the non command line user).

People in this forum adviced on booting into Windows with "allow unsigned drivers" enabled (its a preboot F8 option), because someone using some other driver, flashing through some other program once had success doing that. You can scrap this as well, it doesn't work, since at no time ATK gets its drivers installed properly. Therefore at no time Windows does actually know that such drivers are on the system. Also pointing the drivers update to the drivers folder within the ATK installation on 64bit systems, even with "allow unsigned drivers" enabled - doesn't work.

The solution is as ludicrous as it is simple. You have to use a 32bit installation of Windows. Then ATK upon installation will pop up a command line Window and for the first time install the required drivers. Its as simple as that.

Just everyone fails to mention it. So yes for the Kindle 3/Keyboard - currently use the 3.0.2 kernel and mmcblk0p1 file (attention it comes in a split archive with two parts) (not the 3.3 files (dropbox upload is corrupt)), unzip them until you have the .img files of both. Rename them like stated in the tutorial (to .bin files), then use a 32bit Windows installation to install ATK on. And for the flashing process itself, use the same adress spaces (0x......) that are mentioned for 3.3 in the tutorial, just leave out the first two digits (0x) in the beginning, as they are already presumed by ATK. The last step may be optional, but I had a successful K3 Keyboard debrick by not entering 0x as the first two digits in the adress fields.

09-24-2012, 02:58 AM	#172
notimp Addict Posts: 248 Karma: 892441 Join Date: Jul 2010 Device: K2i	You are doing nothing wrong. Its just an extreme oversight on part of the people who have written the tutorials for debricking. Tutorials in which they forgot to mention where exactly you should unzip files, in which broken downloads are still linked and people encouraged to flash files with checksum errors, tutorials where it is not mentioned that you should leave out 0x when entering certain hex numbers in adress fields... One of those "oversights" on part of the tutorial people was to mention, that ATK only comes with 32bit drivers. When you install it on a 64bit Windows system, the driver installation routine is simply skipped. If you try to install the drivers manually (by executing the bat files coming with ATK you will see that the program used to register the drivers simply refuses to work on 64bit systems, the same goes for the uninstallation of ATK, where actually for the first time ever ATK decides to push error messages to the non command line user). People in this forum adviced on booting into Windows with "allow unsigned drivers" enabled (its a preboot F8 option), because someone using some other driver, flashing through some other program once had success doing that. You can scrap this as well, it doesn't work, since at no time ATK gets its drivers installed properly. Therefore at no time Windows does actually know that such drivers are on the system. Also pointing the drivers update to the drivers folder within the ATK installation on 64bit systems, even with "allow unsigned drivers" enabled - doesn't work. The solution is as ludicrous as it is simple. You have to use a 32bit installation of Windows. Then ATK upon installation will pop up a command line Window and for the first time install the required drivers. Its as simple as that. Just everyone fails to mention it. So yes for the Kindle 3/Keyboard - currently use the 3.0.2 kernel and mmcblk0p1 file (attention it comes in a split archive with two parts) (not the 3.3 files (dropbox upload is corrupt)), unzip them until you have the .img files of both. Rename them like stated in the tutorial (to .bin files), then use a 32bit Windows installation to install ATK on. And for the flashing process itself, use the same adress spaces (0x......) that are mentioned for 3.3 in the tutorial, just leave out the first two digits (0x) in the beginning, as they are already presumed by ATK. The last step may be optional, but I had a successful K3 Keyboard debrick by not entering 0x as the first two digits in the adress fields. Last edited by notimp; 09-24-2012 at 03:02 AM.