View Single Post
Old 03-05-2012, 10:03 AM   #52
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: *.*
Quote:
Originally Posted by john_pb View Post
Thanks once again for the responses. I do appreciate the work you guys are doing.

Just as a further feedback:

The Kindle will not reboot successfully. It either gets stuck on ""...wait till your Kindle restarts" or at a blank screen.

I rebooted it using the "magic" restart while connected to the Windows guest, with Mfg Tool running.

Once detected and the "main" profile loaded, it restarts normally and now shows that the firmware has been upgraded to 5.0.4. It then runs fine, with all functions including 3G operating without noticeable problems; unless shut down, from which it again goes to a blank white screen and cannot be re-booted without Mfg Tool.

"Hard" reset - holding down the power button - makes no difference.

Geekmaster, would you know of any reason why this might be the case?
Try changing the idme bootmode variable to "main".

You should be able to boot to diags, and then use the "disable diagnostics" menu.

Or in diags SSH (or in a RUNME.sh) do "idme -d --bootmode main". You can do "idme ?" to see that they current bootmode var contains.

Or in fastboot mode (using MfgTool to get there), do "sudo ./fastboot setvar bootmode main".

Do you have a hack installed that is depending on a file that got replaced with an original amazon file during the update? If so, you need to either fix that, or flash a good main system partition image from diags, using "dd if=/mnt/us/mmcblk0p1 of=/dev/mmcblk0p1 bs=4K" from diags SSH or RUNME.sh (with ENABLE_DIAGS).

Flashing a partition that you booted from can cause problems, so you need to be in diags mode. The main system partition is too big to flash with fastboot, so you need the above "dd" command for that.

See the "simple debricking" thread.
geekmaster is offline   Reply With Quote