Quote:
Originally Posted by mastermmon88
Good evening Davidfor and thanks for the image.
Suspecting a bad SD card i just flash the image you gave me and sill no go 
I have a latent image of the last book on the screen, a message " Turned Off" and the percentage the book was read to.
When a press the power on button the led will lit for some seconds and after goes off, no changes on the screen. No response to usb cable connection to the PC.
Hard reseat with the button as no effect.
Full power drain of the mother board done.
Reseat all motherboard connection done.
Any idea or can I give it as dead ?
Thanks for your much appreciated help with this issue! |
Does the screen look damaged at all? If there are any cracks or other affects, then it is probably damages. Sometimes it is easier to see the cracks from the back back of the screen.
Does the screen light ever come on? That is a sign of how far it is booting. If it does, and the screen is damaged, it might actually be booting completely. In that case, it will be prompting you to do the setup. If we knew were to tap on the screen, it might be possible to get the PC to see the device. But, the PC will not see the device until it is put into the USB connection mode.
What do you mean by "Hard reseat with the button"? If you just pressed the pinhole reset button, all that does is to forcibly restart the device. It doesn't do anything if the device is off. It doesn't trigger a factory reset. You can try the actual factory reset which is the last method on
https://wiki.mobileread.com/wiki/Kobo_Reset:_Aura_H2O.
On thing you can use the pinhole reset for is pushing it after the power LED goes off. If the LED flash again, it is restarting the device. If it doesn't, it means the device turned off.
One thing I am not sure of is if you used a new SD card. Your statement about this isn't clear. If you aren't using a new card, you should try one. You can use a larger card and resize the book partition later to use it all all. If it was a failing SD card that caused the original problem, it could still be causing this.
Lastly, but probably should have been earlier, have you tried doing this with the device plugged in? Your symptoms do match a battery that no longer holds charge. If it starts when plugged, then it is probably the battery. And you should never assume the battery is charged when the device isn't responding. It could be that whatever the problem was ran the battery out.