View Single Post
Old 03-05-2012, 12:11 PM   #3
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
When I debricked my touch using the serial port, it would halt at the repair needed screen within 10 to 30 seconds after I logged in, which terminated my serial port session. I successfully "uploaded" and ran a few scripts to debug and repair it by copying the script contents to the clipboard and pasting it to my serial terminal immediately after logging in. And yes, you need to ignore a LOT of status messages interleaved with your desired output.

It took a few passes, after I pasted some "scripts" to snoop around and display output (which I later analyzed in my terminal scrollback buffer). Then finally, I pasted script contents into my serial login session that fixed the problem (a broken startup script).

Even if you have access for only 10 seconds per reboot, you CAN investigate and repair your kindle like I did.

Last edited by geekmaster; 03-05-2012 at 12:17 PM.
geekmaster is offline   Reply With Quote