View Single Post
Old 03-24-2012, 10:02 PM   #4
geekmaster
Carpe diem, c'est la vie.
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: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
If you can boot to main by TEMPORARILY setting bootmode to main, then your bootmode idme var is set to something else (probably fastboot mode).

You can accidentally set it to fastboot mode in diagnostics by selecting the fastboot package in the exit menu.

Previously, the only way out of fastboot was using the fastboot tool to change the idme bootmode var, but now you can do it from diagnostics, either in an SSH shell, or from a RUNME.sh that is launched from diags.

In diags, you can change your bootmode var permanently (until you change it to something else) with:

idme -d --bootmode main


you also need to remove your ENABLE_DIAGS file if you have one, and reboot. You can do these commands:

rm -f /mnt/us/ENABLE_DIAGS
reboot

After you set bootmode to main, it should boot to main without needing to use MfgTool to do a tethered boot.
geekmaster is offline   Reply With Quote