On Thursday, 17 October 2013 08:18:51 UTC+1, Aaron Borden  wrote:
> 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

I've been round the brick / reload to stock / re-root loop a few times now. 
Somewhere along the line, it has stopped being recognised as a roamer2 device 
in my VirtualBox ubuntu machine.

Using a virtual machine on my mac has been working fine, but now it just sees 
'Handset [0231]' instead of roamer2, and no google device is seen for fastboot.

Not really worried about that, but is there a way of flashing the built img's 
from a windows or mac, without using flash.sh?

How about using clockworkmod rooted shell? Or will having CWM on the phone stop 
the B2G img's from working?

I think I'm close now, compiled with no errors using the image of the stock 
phone.

Any ideas gratefully received.
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to