MobileRead Forums - View Single Post - K5 Can a Kindle Touch battery die without triggering the "Critical Battery" error?

WaseemAlkurdi · 08-18-2019, 01:26 PM

****** UPDATE 2 ******

I flashed the diags partition via USB. I first checked that fastboot actually works by issuing a fastboot download diagsys.bin. It flashed without an error, and did so in six seconds, so I tried again and unplugged the USB cable to make sure that it isn't just saying "Success" without really downloading anything. It did fail when I did that, and after that I flashed diags, then booted there. It worked. Previously, it didn't.

Upon exporting my USB storage, it was completely empty (save for an apparently recently generated file) ... I figured out that the filesystem might have sustained some real damage ... but on second thoughts, it might just be a result of having tried fastboot setvar bootmode factory and fastboot setvar bootmode reset.

Anyhow, I immediately SSH'ed into the Kindle ... I tried to transfer mmcblk0p1 from my backup, but I apparently screwed something up, reversing the direction of the nc pipe, I got garbled output onto my local terminal. Anyhow, I figured out that I should copy over the mmcblk0p* files to the exported USB storage instead of transferring via nc, as I was too anxious about getting it over with.

I tried disabling SSH from the menu (which did not work, obviously). I had to reboot again to diags. Since diags is fixed, that would be easy, right? I didn't want to be bitten twice by the same snake, so I selected the "Gas Gauge" option on the main diags screen to see how much battery I have. 36% and 500 mAh of capacity ... hmmm, not bad. Exit. Exit? Tap tap tap ... it had frozen again. Houston, we're in trouble.

Gave the button the good hard hold until the light goes off, then pressed Home, like I've done a million times now, then imx_usb'd the diags bundle ... to no avail. The thing is refusing to leave USB downloader mode. Just like with the dead battery.

A few minutes of self-loathing later, I tried again, it would boot to diags, but would freeze very soon after that. It even managed to successfully export the USB storage once, but didn't hold on to it for much longer as to copy mmcblk0p1.bin, much less flashing it.

And now, the battery (or something) is so dead that holding the power button for [13 | 40] seconds for a [reboot | full reboot] won't work at all, and USB download mode won't flash anything.

So, what do you think? Before flashing diags via fastboot, diags used to wait for something then reboot into main. After flashing, it booted diags. Therefore, diags was broken. Is that the case with main as well?
And is the battery going to charge up when broken like this?
And ... could it be an issue of broken solder on the CPU or other chip like in this link?

08-18-2019, 01:26 PM	#30
WaseemAlkurdi Zealot Posts: 147 Karma: 20 Join Date: Jul 2019 Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen	**** UPDATE 2 ** I flashed the diags partition via USB. I first checked that fastboot actually works by issuing a fastboot download diagsys.bin. It flashed without an error, and did so in six seconds, so I tried again and unplugged the USB cable to make sure that it isn't just saying "Success" without really downloading anything. It did fail when I did that, and after that I flashed diags, then booted there. It worked.** Previously, it didn't. Upon exporting my USB storage, it was completely empty (save for an apparently recently generated file) ... I figured out that the filesystem might have sustained some real damage ... but on second thoughts, it might just be a result of having tried fastboot setvar bootmode factory and fastboot setvar bootmode reset. Anyhow, I immediately SSH'ed into the Kindle ... I tried to transfer mmcblk0p1 from my backup, but I apparently screwed something up, reversing the direction of the nc pipe, I got garbled output onto my local terminal. Anyhow, I figured out that I should copy over the mmcblk0p* files to the exported USB storage instead of transferring via nc, as I was too anxious about getting it over with. I tried disabling SSH from the menu (which did not work, obviously). I had to reboot again to diags. Since diags is fixed, that would be easy, right? I didn't want to be bitten twice by the same snake, so I selected the "Gas Gauge" option on the main diags screen to see how much battery I have. 36% and 500 mAh of capacity ... hmmm, not bad. Exit. Exit? Tap tap tap ... it had frozen again. Houston, we're in trouble. Gave the button the good hard hold until the light goes off, then pressed Home, like I've done a million times now, then imx_usb'd the diags bundle ... to no avail. The thing is refusing to leave USB downloader mode. Just like with the dead battery. A few minutes of self-loathing later, I tried again, it would boot to diags, but would freeze very soon after that. It even managed to successfully export the USB storage once, but didn't hold on to it for much longer as to copy mmcblk0p1.bin, much less flashing it. And now, the battery (or something) is so dead that holding the power button for [13 \| 40] seconds for a [reboot \| full reboot] won't work at all, and USB download mode won't flash anything. So, what do you think? Before flashing diags via fastboot, diags used to wait for something then reboot into main. After flashing, it booted diags. Therefore, diags was broken. Is that the case with main as well? And is the battery going to charge up when broken like this? And ... could it be an issue of broken solder on the CPU or other chip like in this link?