When the device goes into fastboot mode, the vendor id changes to 18d1. When the phone is in fastboot mode, you should see an entry like this when you run lsusb: Bus 003 Device 097: ID 18d1:d00d Google Inc.
The line for the USB id 05c6 covers everything except fastboot mode. You need the line 18d1 for fastboot mode. Did you reload the rules and replug the USB cable AFTER reloading? Plugging in the usb cable is what udev uses as a trigger. While the phone is in fastboot mode, running lsusb should show a line like the following: Bus 003 Device 097: ID 18d1:d00d Google Inc. The 097 portion is dynamic and will change every time the device is plugged in. What does: find /dev -name 097 -ls show? (change the 097 to match the number from your lsusb output). The permissions on that file is what fastboot needs and what the udev file should be modifying. Dave Hylands ----- Original Message ----- > From: "Dee" <[email protected]> > To: "Dave Hylands" <[email protected]> > Cc: [email protected] > Sent: Tuesday, November 11, 2014 8:15:03 AM > Subject: Re: [b2g] Trouble updating Firefox OS on Mozilla Flame > Hello Dave, > I have copied this rule before from the website. Mine > /etc/udev/rules.d/android.rules looks like this: > SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev" > But even after reloading the rules with your line below, fastboot does > not work without sudo. > $ fastboot devices > no permissions fastboot > Best regards > Dominik > Am 11.11.2014 um 08:26 schrieb Dave Hylands: > > To add a udev rule for fastboot, create a file (mine is called > > android.rules) in the /etc/udev/rules. directory with this in it: > > > > SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666" # Google (also > > fastboot) > > SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666" # Flame (adb) > > > > You then need to run: > > > > sudo udevadm control --reload-rules > > > > and unplug and replug the usb cable. > > > > Dave Hylands > > > > ----- Original Message ----- > > > >> From: "Dee" <[email protected]> > >> To: [email protected] > >> Sent: Sunday, November 9, 2014 8:56:34 AM > >> Subject: Re: [b2g] Trouble updating Firefox OS on Mozilla Flame > > > >> Hello again, > > > >> I have solved the problem myself. I executed every line in the flash.sh > >> and saw: > > > >> $ fastboot devices > >> no permissions fastboot > > > >> So the permissions are not correct. The upgrade page says that you > >> should not execute the script with sudo, unfortunately it does not say > >> what I should do so that I can execute it without. (A general hint to > >> udev is not enough.) > > > >> So I executed every fastboot-line in the script with sudo and that works > >> until: > > > >> $ sudo fastboot flash custpack custpack.img > >> target reported max download size of 301989888 bytes > >> error: cannot load 'custpack.img': No such file or directory > > > >> There is no custpack.img in the v188.zip. So I have checked the v180.zip > >> in comparison and there are some strange things: > > > >> 1. The v180.zip does not have any custpack.img either. But the flash.sh > >> script does not have any custpack.img line. So I ignored it for v188.zip. > > > >> 2. The v180-script has a line > > > >> fastboot flash partition gpt_both0.bin > > > >> That line is missing in the v188.zip flash.bat/sh. Is it necessary? > > > >> At the end my update worked. Unfortunately my phone is in English now. > >> :( Some bugs were fixed and some new bugs were added. :( > > > >> Who's responsible for the page > >> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software > >> and especially for the images on this page. The script should be > >> corrected as soon as possible. The problem with "sudo fastboot" should > >> be mentioned more clearly how to fix. > > > >> Best regards > >> Dominik > > > >> Am 09.11.2014 um 15:05 schrieb Dee: > >>> Hello, > >>> > >>> I own a Flame since four months. Because of some bugs and crashes I > >>> wanted to update the software. So I went to > >>> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software. > >>> I thought that I needed to update the base image first. So I've download > >>> the Base Image v188.zip and followed the instructions: > >>> > >>> $ adb devices -l > >>> List of devices attached > >>> f30ecc6b device usb:2-2 product:msm8610 model:Flame > >>> device:flame > >>> > >>> $ unzip v188.zip > >>> $ cd 188 > >>> $ mv flash.bat flash.sh > >>> $ chmod +x flash.sh > >>> > >>> $ ./flash.sh > >>> * daemon not running. starting it now on port 5037 * > >>> * daemon started successfully * > >>> List of devices attached > >>> f30ecc6b device > >>> > >>> Flash nCPU... > >>> < waiting for device > > >>> > >>> The Flame vibrated shortly and now I see the ThunderSoft logo in the > >>> display. Nothing happens at all since 30 minutes. I don't think anything > >>> else will happen. > >>> > >>> I'm not sure if it's safe to remove the phone from the USB connection or > >>> to stop the flash script. > >>> > >>> Any hints how to "rescue" my phone and proceed with the update? > >>> > >>> Best regards > >>> Dominik > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> dev-b2g mailing list > >>> [email protected] > >>> https://lists.mozilla.org/listinfo/dev-b2g > >>> > > > >> _______________________________________________ > >> dev-b2g mailing list > >> [email protected] > >> https://lists.mozilla.org/listinfo/dev-b2g > > > > > > > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
