Noob's guide to debricking through ATK :D

[twobob]

Originally Posted by hawhill

libusb(x) is now statically compiled into the versions I've provided in the first post. So a reasonably recent glibc is all that's needed.

BTW: I very well got the phrase "any old", but was wondering about the reference since the last reference point in that paragraph was the "flashing program", not the "linux distribution".

My Enlgish sucks.

[qlob]

Originally Posted by twobob

My Enlgish sucks.

So does my American

[geekmaster]

Originally Posted by twobob

My Enlgish sucks.

You spelling sucks too!

[twobob]

Originally Posted by geekmaster

You spelling sucks too!

I wuz beeing Ironical

[stiny861]

Well no luck with ATK or k3flasher. Im beginning to think that there is a physical hardware issue that I will not be able to fix. Well it had a good run at least.

[twobob]

Originally Posted by stiny861

Well no luck with ATK or k3flasher. Im beginning to think that there is a physical hardware issue that I will not be able to fix. Well it had a good run at least.

tough break. good attitude

[geekmaster]

Originally Posted by twobob

tough break. good attitude

Perhaps you can get a cheap "broken screen" K3 on ebay and swap screens? Sometimes you can get them for just the shipping cost. I did.

[geekmaster]

Originally Posted by twobob

tough break. good attitude

If your eink screen is still good, then perhaps you can get a cheap "broken screen" K3 on ebay and swap screens? Sometimes you can get them for just the shipping cost. I did.

[atjeff1]

Hello, I am a complete and total noob at Linux and Kindle related matters. I followed the wiki guide and flashed my K3 but have encountered several problems. While flashing rootfs.bin, my Kindle's charge light indicator thing turned However, even though the light was turned off, ATK continued to flash it. After it was done flashing, I unplugged it and tried to reboot it...No luck. As mentioned in many posts before mine, my Kindle seems to be stuck in a loop where it tries to boot and gives me the USB connect and disconnect sounds every 90 seconds. My K3 was a demo unit that I have received from a neighbor. It is current stuck on a screen from the demo. It has been stuck on said screen since I plugged it in for the flashing. Any help?

I used the 3.0.2 files. The rootfs file was in one .zip file. It is around 350mb compressed and 650mb after I extracted it. I did the flashing with ATK on a Win7 32 bit because my laptop was 64 bit. Any solutions?

[twobob]

Originally Posted by atjeff1

Hello, I am a complete and total noob at Linux and Kindle related matters. I followed the wiki guide and flashed my K3 but have encountered several problems. While flashing rootfs.bin, my Kindle's charge light indicator thing turned However, even though the light was turned off, ATK continued to flash it. After it was done flashing, I unplugged it and tried to reboot it...No luck. As mentioned in many posts before mine, my Kindle seems to be stuck in a loop where it tries to boot and gives me the USB connect and disconnect sounds every 90 seconds. My K3 was a demo unit that I have received from a neighbor. It is current stuck on a screen from the demo. It has been stuck on said screen since I plugged it in for the flashing. Any help?

I used the 3.0.2 files. The rootfs file was in one .zip file. It is around 350mb compressed and 650mb after I extracted it. I did the flashing with ATK on a Win7 32 bit because my laptop was 64 bit. Any solutions?

you dont mention flashing a matching kernel.

thats my first thought. Was that done?

[twobob]

I'm not sure how to solve that issue. assuming you flashed the rootfs completely (should have taken about 3 hours) and you flashed on a matching kernel. then you shouldnt HAVE any demo data on the device. it feels like the procedure wasnt completed somehow if you can still see demo stuff.

[atjeff1]

Originally Posted by twobob

I'm not sure how to solve that issue. assuming you flashed the rootfs completely (should have taken about 3 hours) and you flashed on a matching kernel. then you shouldnt HAVE any demo data on the device. it feels like the procedure wasnt completed somehow if you can still see demo stuff.

Yes, sorry for being so vague, by files, I meant both of them, Including the matching kernel. No, the device was a demo device. When I shut it off and held the power button for 30 seconds and the volume button for 1 second, it froze on one of the demo screen pages. After flashing the Kernel first and then the matching rootfs, I unplugged it and tried rebooting it but to no avail...The image on the K3 is still frozen on one of the demo pages. And the key thing that caught my attention was that the charge light turned off half way into flashing the rootfs but ATK continued flashing it. And yes, it took approximately 3-4 hours.

[knc1]

You might be running in a mode that does not do any display output.

[geekmaster]

I had a similar problem with a K3 demo. I think that the battery discharged before flashing was successful. I charged it on a wall charger overnight, and then debricking it again was successful.

I used k3flasher to debrick mine. You may wish to try that instead of using ATK.

[atjeff1]

Originally Posted by geekmaster

I had a similar problem with a K3 demo. I think that the battery discharged before flashing was successful. I charged it on a wall charger overnight, and then debricking it again was successful.

I used k3flasher to debrick mine. You may wish to try that instead of using ATK.

Well, when I plug it into any computer, it goes into that continuous loop of 90 seconds on and off. Does charging really work? When I charge it with a wall socket, the charge light turns off within an hour or two. What does it mean? Do I charge it for a few more days and then try reflashing it with k3flasher? And do I disconnect and reconnect the charger when the charge light turns off?