View Single Post
Old 08-22-2012, 05:35 PM   #16
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 Zephyrus View Post
Thank you. Tried but failed.

Actually I suspected another thing.

After I set the bootmode to diags by using "fastboot setvar bootmode diags", I try to check the var I set by "fastboot getvar bootmode" and it remains as main.... but when I try to reboot by "fastboot reboot", the machine response and restarted (the tree screen flashed). Don't know if this is related or is just the same as other machines here.

Thanks.
That is NOT normal behavior. It could happen if the fastboot portion of your u-boot bist partition on mmc is damaged, or if your fastboot utility is damaged. Perhaps fastboot does not return an error status when if fails while writing to the bootmode var (similar to the false success report when flashing mmcblk0p1 with fastboot).

I do not know what else might cause that abnormal fastboot behavior.

Last edited by geekmaster; 08-22-2012 at 05:46 PM.
geekmaster is offline   Reply With Quote