On Wed, 2013-10-16 at 11:37 -0700, Sven Ehret wrote:
> Hi,
>
> I have no luck flashing my ZTE Open:
>
> # ./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
>
> Can anyone help?
I ran into a similar problem. I realized that the fastboot device is
different from the adb device. If you check your dmesg you'll see two
different vendor strings. Make sure you have both vendors in your
android udev rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev" # ZTE Open
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev" # Google device
And then restart udev (or reload it's configs).
Note: I still don't have a bootable image on the ZTE Open yet. In fact,
I can't get it back to boot via ZTE's latest firmware update either.
It's like the system.img was missing from their update. This post[1]
seems to indicate we'll have to build a new boot.img to be compatible
with a custom B2G, though I'd much rather build it myself than grab some
random binary off the web ;)
-Aaron
[1]
http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html