Howdy Aaron,
Thanks for the reply. Unfortunately, I already have both vendor
strings in my udev.
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
And the device gets picked up by the appropriate interface when it
reboots (either into regular mode, or bootloader mode).
$ adb devices
List of devices attached
roamer2 device
$ adb reboot bootloader
<wait a few seconds>
$ fastboot devices
ROAMER2 fastboot
The initial fastboot flash command finds the device correctly when
"erasing" data, so I don't think it's a problem with the initial udev
setup.
Daniel Roesler
On Sat, Oct 19, 2013 at 11:37 PM, Aaron Borden <[email protected]> wrote:
> On Sat, 2013-10-19 at 11:50 -0700, Daniel Roesler wrote:
>> Howdy all,
>>
>> I am trying to build and install B2G onto my ZTE Open, following the
>> instructions on
>> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Installing_on_a_mobile_device
>> using Ubuntu 12.04.
>>
>> However, I am getting a "No such device" error when flashing via
>> flash.sh or manually (see below). I noticed after the "OKAY" after
>> sending data the phone reboots. However it does not reboot into the
>> bootloader, but rather normal mode.
>>
>> After the flash fails, the phone does appear on "adb devices" but not
>> "fastboot devices". Thus when fastboot tries to write, it can't find
>> the device because the device did not reboot into bootloader mode.
>>
>> How can I fix fastboot so that it correctly reboots into bootloader
>> mode? Alternatively, is there a way to flash without the reboot? What
>> steps can I take to troubleshoot this? Thanks!
>>
>> Command outputs:
>> =========
>> $ ./flash.sh
>> < waiting for device >
>> erasing 'cache'...
>> OKAY [ 0.531s]
>> finished. total time: 0.531s
>> erasing 'userdata'...
>> OKAY [ 1.407s]
>> finished. total time: 1.407s
>> sending 'userdata' (49378 KB)...
>> OKAY [ 4.175s]
>> writing 'userdata'...
>> FAILED (status read failed (No such device))
>> finished. total time: 9.494s
>> =========
>>
>> =========
>> $ fastboot flash system system.img
>> sending 'system' (111020 KB)...
>> OKAY [ 9.394s]
>> writing 'system'...
>> FAILED (status read failed (No such device))
>> finished. total time: 14.748s
>> =========
>
> 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).
>
> --
> Aaron Borden
> Human and Hacker
>
>
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
