View Single Post
Old 07-16-2012, 11:09 AM   #3
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: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
MfgTool boots using a custom u-boot bootloader, so it is possible that your u-boot image on the mmc is damaged. You may need to reflash it with fastboot. A good uboot image can probably be extracted similarly to how kernels get extracted (a new variation of the getkernels.sh script). There are currently no u-boot forensic images online that I am aware of.

Until you can reflash u-boot, you are stuck with an MfgTool "tethered boot".

BTW, did you try setting the bootmode var to main with fastboot?

Does anybody here have time to extract a K4 u-boot and provide a link?
geekmaster is offline   Reply With Quote