Quote:
Originally Posted by domsch1988
Ok, first post here, so.. Hi everyone 
I have some trouble with my KT2. A few weeks back i jailbroke it succesfully. After putting something on (don't ask me what it was exactly, it was weeks back. Some Book.) and rebooting the device i'm stuck in a bootloop/update loop.
Currently i get a "Your Kindle needs to be repaired" screen. After a Hard reboot it tries to update, Fails on the way and goes back to that screen. While it's booting i have access to the storage over USB on Windows. Sadly it doesn't stay so long enough to put the full 190MB Firmware on it. As soon as the "Repair needed" Screen pops up, access to storage is gone.
Since most threads i found are a bit all over the place, i'm not sure where to start. I tried running mfgtool, but i crashes under Windows 10. From what i've read, i could get to fastboot and get it to work with a special cable. But since, my reader is still reacting to input i'd rather avoid buying special stuff and get it back up and running some other way.
Any help or input on how to resolve my Problem would be greatly appreciated. If you need any further information, i'll do my very best to brovide that. |
Why do you want to put a 190Mbyte file on the device?
What do you think you will accomplish?
"Tries to update" ???
What is happening to give you that conclusion?
It could be important.
Has this device ever been allowed to run it battery down?
Down low enough that the 'charge battery' picture is displayed.
Have you tried:
DO_FACTORY_RESTORE
all caps, no extension, no contents, place at top of visible USB storage, reboot.
Although you don't mention:
If you tried to delete any *.bin file that might be at the top of visible USB storage
If you want to keep your jailbreak
What firmware version the device has installed, what version it is trying to install, if it is really trying to install an update
If you have tried to delete the entire contents of /documents to get rid of the suspected book without knowing which one
Note:
You mention two possible reasons for the boot loop:
A bad book file (if that was going to cause a boot loop, it would have done it "weeks ago" but you aren't clear if it did)
A bad update file
but you don't give enough information to help decide which it might be.
= = = =
You have a technical question to ask on a technical forum -
So yes, we need all of those gory, technical details.
