Out of curiosity, has anyone who's run into this tried raising an issue with VMware about it?
--Jed On Thu, Jul 04, 2013 at 11:50:37AM +0100, Zac Campbell wrote: > I see you've got a solution already but I get this problem often > with my VMware setup too and it's so frustrating that I've gone to > the effort to set up a 2nd machine just for flashing (and occasional > test running)! > > However I did persist with this for quite a while and have some tips; > When you get that Turkcell logo and < waiting for device > that's > the device having rebooted into fastboot mode. The flash script > needs the device to be in fastboot mode. > VMWare doesn't automatically re-connect it up after the script > reboots into fastboot (for whatever reason) unfortunately and you > may need to unplug and replug the usb cable a few times before > VMWare will make the connection. You may see a VMWare error message > pop up saying the driver connection has failed while doing this. > The best way around this is to put it into fastboot mode manually by > holding volume up and turning the device on.. then connect it to > your computer, run "adb devices" to make sure VMWare has picked it > up and then run ./flash.sh. This way it won't need to reboot itself > into fastboot and you won't be exposed to VMWare 'losing' the link > from the host. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
