Send me across the link of the ".bat" files you have used. Will see if they are any problems with the script. Thanks,U.M.K. Dikshit
From: [email protected] Date: Sat, 9 Jan 2016 18:05:49 +0100 Subject: Re: Configure Ubuntu to flash Flame roms To: [email protected] CC: [email protected]; [email protected] I was not able to to execute the script. It just frozen at the start in a waiting phase. I am using Windows 10 btw! I can use adb and fastboot on it as I tried them before and they work ok. On Sat, Jan 9, 2016 at 4:05 PM, U.M.K. Dikshit <[email protected]> wrote: The best way to shallow flash in Windows Environment is to have adb installed and also the USB Drivers installed for flame.You don't need Cygwin / Linux VM for flashing the Flame.Just follow the MDN Links and downlaod the ".bat" file for flashing the flame. Steps:1. Flash with the Base Image Latest [Base Image 18D V4] 2. Then you can download the latest Gaia and Gecko Images from the download repository or3. You can get it by changing the channel in your flame from"nightly" to "nightly-latest". You will receive 2 updates per day. Happy Flashing !! Thanks,U.M.K. Dikshit > Subject: Re: Configure Ubuntu to flash Flame roms > To: [email protected] > From: [email protected] > Date: Sat, 9 Jan 2016 14:47:50 +0100 > > 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 _______________________________________________ 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
