You're right, I was trying to connect to fastboot without having the phone in fastboot mode. Nevertheless I was not able to flash an image from linux for my Flame.
I followed the steps from my first email but the script get stuck here: push: /tmp/shallowflashgecko.DEH6vdfampDm/b2g/models/en-US/mixture_weights -> /system/b2g/models/en-US/mixture_weights on windows the shallow script works until it hits the point with 78 files pushed. 0 files skipped. 873 KB/s (69219058 bytes in 77.382s) 3 KB/s (3646 bytes in 1.000s) 506 KB/s (311697 bytes in 0.601s) ### Push Done. I added the full log here: http://pastebin.com/BQZg1gFQ when I unplug the phone, it restarts but the apps are gone, the addons are gone. The pinned sites, pinned pages, wallpaper, contacts, ringtone are still there though! Still, it took me 2 hours to restore all my settings. I wish this updating flow would be more easy. Like a one button script that sets up everything. This is beyond the reach of 99% of consumers at this point. I hope I can meet a guru at Fosdem to show me light from scratch how to setup a linux env to flash images for the Flame. Right now this is impossible for me. On Sat, Jan 9, 2016 at 2:47 PM, Alexandre Lissy <[email protected]> wrote: > Le 09/01/2016 14:29, Mihai Barbat a écrit : > > Hi guys > > > > Because the shallow flash doesn't go all the way on my Windows 10 > > machine using Cygwin I tried to flash the latest OTA using a Linux > > machine. I installed VmWare Workstation Player 12 and the latest Ubuntu > > ISO and then did the following config > > > > 1: I did an lsusb and saw that my id is 05c6 > > Bus 001 Device 003: ID 05c6:9025 Qualcomm, Inc. Qualcomm HSUSB Device > > For the third time, this is wrong. Your device is not in fastboot mode > or it's not plugged to your VM. > > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub > > Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse > > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > > > 2: I did: > > > > |wget -S -O - > > > https://raw.githubusercontent.com/cm-b2g/B2G/1230463/tools/51-android.rules > > | sudo tee >/dev/null /etc/udev/rules.d/51-android.rules; sudo udevadm > > control --reload-rules | > > > > > > 3: I modified the rules file from /etc/udev/rules.d/51-android.rules > > > > I modified SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0664", > > GROUP="plugdev" to > > SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666" > > > > 4: then I renamed the 51-android.rules to 99-android.rules > > > > 5: then I went to /lib/udev/rules.d/40-usb_modeswitch.rules > > > > after ATTR{idVendor}=="05c6", ATTR{idProduct}=="f000", > > RUN+="usb_modeswitch '%b/%k'" > > I added: > > ATTR{idVendor}=="05c6", ATTR{idProduct}=="f000", RUN="" > > > > 6: then I did: sudo udevadm control --reload-rules > > > > 7: I unplugged the phone and retried fastboot devices and didn't get > > anything > > > > I am able to get the correct reply from: adb devices but fastboot > > devices doesn't give me anything. > > > > What am I doing wrong there? > > > > > > _______________________________________________ > > dev-fxos mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-fxos > > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
