View Single Post
Old 09-09-2013, 01:42 PM   #8
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ixtab View Post
Well... I never claimed that Kubrick could make all malfunctioning devices work again.

In this particular case, it seems like the device *can* boot an externally supplied loader (like fastboot, diags/main via imx_usb or mfgtool), but fails to boot on its own. In other words: It looks like the on-device boot loader is screwed up. This can only be fixed manually, and probably only through serial debricking. Don't ask me how though, I've never done anything like that.
The on-device boot loader is in hardware, write-protected, flash.

Very hard for the end-user to screw up, although they can if they try hard enough.
I would suspect a more general hardware failure than a corrupted u-boot image. (Unless the O.P. did something they are not admitting to now.)

I have never replaced the on-device u-boot image, only read about doing it (in Amazon's u-boot source code).

So, sorry, I can't be of any help with this one.
knc1 is offline   Reply With Quote