Hmm...
First things first -
Terminal voltage of a Li-Ion battery does not indicate
**storage capacity**.
The battery in the Kindles has a terminal voltage of 4.2 volts when fully charged (and new).
Not being able to get it above 3.9 volts (assuming no measurement errors) is not a good sign.
That the terminal voltage dropped to 3.7 volts with only 2 hours of flash erase and re-programming is not a good sign.
The auto-shutoff point is somewhere around 3.6 volts.
Try another 1-day charge on an external charger, then try to re-boot it again (the hold more than 30 seconds thing).
That battery **might** have enough capacity to re-boot it.
But keep in mind - Kubrick does not touch the part of storage that is visible as FAT-32, USB storage (unless you told it to rebuild it).
So if there is anything found wrong with that file system that causes the K3 to start a filesystem check - that can be a very long process - perhaps longer than the battery will run the Kindle.
Also see:
https://www.mobileread.com/forums/sho...49&postcount=3
Quote:
|
Do you still think that the battery is the problem? If so, I will buy one and give it a try.
|
Yes.
Quote:
|
If not, are there any hopes that by using a serial to USB cable and following the steps I have seen in another thread I could solve the problem?
|
No.
Kubrick already did what can be done.
**UNLESS**:
Your K3 is 'stuck' in diagnostics mode.
Some of the very early K3 diagnostics mode firmware has problems -
problems where you can only 'get out' using the serial port (I have one of those).
But you should be seeing the diagnostics mode menu on the screen even in the above case.
- - - -
Is there any chance that there are two failures here?
Both a screen problem and a battery problem?
I.E: Have you ever seen the screen change since you started trying to un-brick it?