View Single Post
Old 12-17-2011, 12:39 PM   #4
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,066
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by JRyn View Post
Thank Geekmaster for your reply.

I can see and access the Kindle Drive for 20-30 seconds. So I guess it's enough for put that file you mentioned. I'd like to give that shot but I don't know How I can get that file.

Anyway, so this problem is just some boot file damage?. Is there any thread about this "Repair Needed" problem in Kindle Touch?. I tried search this forum but found nothing for KindleTouch.
Quote:
Originally Posted by JRyn
Thanks Geekmaster. So I just put that file in Kindle Drive? Would you give me some clue how to get that file?.
My Kindle4 came with that file already on the USB Drive, and I saw another user who had it on his. I am looking now...

It is a zero-length file called DONT_HALT_ON_REPAIR

It does not have a file extension. This can be a bit difficult to create from windows. On linux you can use a touch command. From a DOS window you could do domething like
echo X > DONT_HALT_ON_REPAIR
but that would create a one-byte file (okay because the scripts just check whether the file exists.

Beware that the file CANNOT have a .txt extension on the filename.

You can find out what the problem is from the diagnostic logs on the kindle. You need access to a command shell (SSH or telnet) on it --OR-- you need to connect to the kindle internal serial port, to see the log files.

You need to install the jailbreak to SSH into it, as described on the forum.

I am going by what the K4 and earlier kindles used for getting past that error screen. My Touch is scheduled to be delivered later today.

On my kindle3, the script:
/etc/init.d/framework
contains code to set or check the DONT_HALT_ON_REPAIR file.
If that file is missing, the kindle halts if the battery ID is not authorized by amazon, or if the framework (GUI) could not start.
If that file exists, the framework startup code drops to a command prompt (presumably on the serial port).

Unless you can SSH or telnet into your kindle to repair it, you may need to add a DONT_HALT_ON_REPAIR file, and connect using a serial port cable (documented in the Touch Jailbreak threads).
geekmaster is offline   Reply With Quote