Update: I was advised to try removing the first lines from updater-script, like
described in
http://www.androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html.
I removed the following lines from the beginning of updater-script:
assert(getprop("ro.product.device") == "roamer2" ||
getprop("ro.build.product") == "roamer2");
assert(getprop_new("ro.build.display.id") == "OPEN_EU_DEV_FFOS");
But unfortunately it does not accept my edited version as well with the same
error message. There is a log file “recovery.log” on my sd card with litltle
more information:
[…]
-- Install /sdcard/edited ...
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1746 bytes; signature 1728 bytes from end
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
Perhaps the verification (checksum?) can be removed someplace else?
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
