Solution: Installing Clockwork Recovery and bypassing the Verification. Now let's see how the OS can be updated sensibly.
Am Freitag, 18. Oktober 2013 09:51:10 UTC+2 schrieb Sven Ehret: > I have a sort-of bricked ZTE Open UK that does not recover anymore. When I > try to install the image from ZTE, it complains about failed verification. > > > > I remember installing the fastboot patch before and then trying to flash, > failing. I was able to recover that by installing the image from ZTE. I then > followed the gisthub about creating and installing boot.img. > > > > What happened then I do not remember exactly. I had FxOS running and it was > offering an update, I think 3.5 MB, which I happily tried to install. It did > and rebooted into recovery mode, which changed appearance with a reddish > background, automatically trying to update something but failing due to bad > verification. I tried to flash my self-build B2G but failed: > > > > # ./flash.sh > > < waiting for device > > > erasing 'cache'... > > OKAY [ 0.528s] > > finished. total time: 0.528s > > erasing 'userdata'... > > OKAY [ 1.397s] > > finished. total time: 1.397s > > sending 'userdata' (66670 KB)... > > OKAY [ 5.608s] > > writing 'userdata'... > > FAILED (status read failed (No such device)) > > finished. total time: 10.991s > > > > # adb devices > > List of devices attached > > roamer2 device > > > > Current situation is: The phone does not boot, shows the firefox but its tail > does is not animated. ADB commands do run. I cannot recover via ZTE image > because verification fails. I contacted ZTE but they simply stated that I > shouldn't have tried to update. > > > > Well I felt that I had to update because the version with which it shipped > did not meet my needs. > > > > Any help is greatly appreciated! > > > > Thanks for reading. Sven _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
