Cygwin has a different issue. I can't recall what it was. The gecko/gaia shallow flash script by default will reset the webapps.json file to the default one which clears apps I believe. If you check to see your webapps in the /data/b2g/webapps folder you might still see them there. You can probably comment out the script to not swap that file.
On Mon, Jan 11, 2016 at 9:52 AM, Mihai Barbat <[email protected]> wrote: > Hi > > It's possible! But then why am I able to partially run the shallow flash > on Windows 10 using Cygwin? There the script works, but gets stuck at a > point...the phone never restarts...yet the update is done, I see the new > version of the build, but my apps then gone (not my ringtone, wallpaper and > pinned sites/pages) > > Looking forward for the FOTA script > > Mihai > > On Mon, Jan 11, 2016 at 6:45 PM, Naoki Hirata <[email protected]> wrote: > >> I think you may be hitting the same issue in regards to why we can't OTA >> the phone any more. >> I haven't tried shallow flashing since we switched over to the partial >> FOTA. (gecko / gaia fota only ). >> It gives me reason to think that maybe we should have a script to use >> partial FOTA as well... >> >> On Sun, Jan 10, 2016 at 12:46 PM, Mihai Barbat <[email protected]> wrote: >> >>> ah, and my base image is the V4! >>> >>> On Sun, Jan 10, 2016 at 9:44 PM, Mihai Barbat <[email protected]> wrote: >>> >>>> the first one was from my windows box >>>> >>>> and from my VM >>>> >>>> shell@flame:/ $ df >>>> Filesystem Size Used Free Blksize >>>> /dev 451.7M 132.0K 451.6M 4096 >>>> /sys/fs/cgroup 451.7M 0.0K 451.7M 4096 >>>> /sys/fs/cgroup/memory: Permission denied >>>> /mnt/asec 451.7M 0.0K 451.7M 4096 >>>> /mnt/obb 451.7M 0.0K 451.7M 4096 >>>> /system 412.0M 280.0M 132.1M 4096 >>>> /data 2.0G 387.9M 1.6G 4096 >>>> /cache 70.8M 61.0M 9.8M 4096 >>>> /persist 4.9M 4.0M 852.0K 4096 >>>> /firmware 64.0M 31.7M 32.2M 16384 >>>> /mnt/media_rw/sdcard: Permission denied >>>> /storage/sdcard 3.8G 3.1G 721.7M 4096 >>>> >>>> >>>> On Sun, Jan 10, 2016 at 9:40 PM, Mihai Barbat <[email protected]> >>>> wrote: >>>> >>>>> adb shell df >>>>> >>>>> Filesystem Size Used Free Blksize >>>>> /dev 451.7M 132.0K 451.6M 4096 >>>>> /sys/fs/cgroup 451.7M 0.0K 451.7M 4096 >>>>> /sys/fs/cgroup/memory: Permission denied >>>>> /mnt/asec 451.7M 0.0K 451.7M 4096 >>>>> /mnt/obb 451.7M 0.0K 451.7M 4096 >>>>> /system 412.0M 280.0M 132.1M 4096 >>>>> /data 2.0G 387.9M 1.6G 4096 >>>>> /cache 70.8M 61.0M 9.8M 4096 >>>>> /persist 4.9M 4.0M 852.0K 4096 >>>>> /firmware 64.0M 31.7M 32.2M 16384 >>>>> >>>>> On Sun, Jan 10, 2016 at 9:32 PM, Fabrice Desré <[email protected]> >>>>> wrote: >>>>> >>>>>> It look like you're hitting a "partition full" condition. What's your >>>>>> base image? >>>>>> >>>>>> Also, can you check what |adb shell df| returns? >>>>>> >>>>>> Fabrice >>>>>> >>>>>> On 01/10/2016 12:05 PM, Mihai Barbat wrote: >>>>>> > Hi Naoki >>>>>> > >>>>>> > I have put the android rules from you on /etc/udev/rules.d and then >>>>>> did >>>>>> > a sudo udevadm control --reload-rules >>>>>> > >>>>>> > then I tried to flash a build with this command: sudo >>>>>> ./shallow_flash.sh >>>>>> > --gaia=gaia.zip --gecko=b2g-46.0a1.en-US.android-arm.tar.gz >>>>>> > >>>>>> > and I got an error. I uploaded the log to pastebin: >>>>>> > http://pastebin.com/et5gKGBg >>>>>> > >>>>>> > I have to say that following the mozilla instructions I also did >>>>>> this >>>>>> > before running the shallow flash: >>>>>> > >>>>>> > 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="" >>>>>> > >>>>>> > >>>>>> > Do you have any idea what is going wrong on my system? >>>>>> > >>>>>> > I wonder if maybe it would be better if Mozilla would offer a Linux >>>>>> > Ubuntu ISO that is configured correctly to flash images. >>>>>> > >>>>>> > >>>>>> > On Sun, Jan 10, 2016 at 6:59 PM, Naoki Hirata <[email protected] >>>>>> > <mailto:[email protected]>> wrote: >>>>>> > >>>>>> > Mihai, fyi, the fastboot is on a different udev rule than the >>>>>> adb >>>>>> > mode for some devices. So you may have to end up adding two >>>>>> > different udev rules. >>>>>> > >>>>>> > I mess around with lots of devices, so I just decided to add >>>>>> all the >>>>>> > udev rules on my machine. You can get the rule set I used here >>>>>> : >>>>>> > https://github.com/nhirata/android_rules ; It saves me time >>>>>> when I >>>>>> > help other people with their linux machines. >>>>>> > >>>>>> > Also to note : For the flame specifically, the device will have >>>>>> in >>>>>> > purple letters "Fastboot" when in fastboot mode. >>>>>> > >>>>>> > Interesting. I didn' t realize there was a windows batch file >>>>>> for >>>>>> > shallow flashing. What it looks like it does is it uses cygwin >>>>>> in >>>>>> > order to flash. If I recall correctly we've had issues shallow >>>>>> > flashing on cygwin in the past so we decided to strictly go with >>>>>> > using linux or a vm in our QA department. >>>>>> > >>>>>> > Also, I think we ran into some issues with the shallow flash >>>>>> script >>>>>> > to batch file conversion; I can't recall. I might pick up that >>>>>> > project again to refresh my mind in what issue I ran into >>>>>> before. >>>>>> > >>>>>> > On Sun, Jan 10, 2016 at 7:42 AM, U.M.K. Dikshit >>>>>> > <[email protected] <mailto: >>>>>> [email protected]>> >>>>>> > wrote: >>>>>> > >>>>>> > 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] <mailto:[email protected]> >>>>>> > Date: Sat, 9 Jan 2016 18:05:49 +0100 >>>>>> > Subject: Re: Configure Ubuntu to flash Flame roms >>>>>> > To: [email protected] <mailto: >>>>>> [email protected]> >>>>>> > CC: [email protected] <mailto:[email protected]>; >>>>>> > [email protected] <mailto: >>>>>> [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] >>>>>> > <mailto:[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 or >>>>>> > 3. 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] >>>>>> > <mailto:[email protected]> >>>>>> > > From: [email protected] <mailto:[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] >>>>>> > <mailto:[email protected]> >>>>>> > > > https://lists.mozilla.org/listinfo/dev-fxos >>>>>> > > > >>>>>> > > >>>>>> > > _______________________________________________ >>>>>> > > dev-fxos mailing list >>>>>> > > [email protected] <mailto: >>>>>> [email protected]> >>>>>> > > https://lists.mozilla.org/listinfo/dev-fxos >>>>>> > >>>>>> > _______________________________________________ >>>>>> > dev-fxos mailing list >>>>>> > [email protected] <mailto: >>>>>> [email protected]> >>>>>> > https://lists.mozilla.org/listinfo/dev-fxos >>>>>> > >>>>>> > >>>>>> > >>>>>> > _______________________________________________ dev-fxos >>>>>> mailing >>>>>> > list [email protected] >>>>>> > <mailto:[email protected]> >>>>>> > https://lists.mozilla.org/listinfo/dev-fxos >>>>>> > >>>>>> > _______________________________________________ >>>>>> > dev-fxos mailing list >>>>>> > [email protected] <mailto: >>>>>> [email protected]> >>>>>> > https://lists.mozilla.org/listinfo/dev-fxos >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > _______________________________________________ >>>>>> > dev-fxos mailing list >>>>>> > [email protected] >>>>>> > https://lists.mozilla.org/listinfo/dev-fxos >>>>>> > >>>>>> >>>>>> >>>>>> -- >>>>>> Fabrice Desré >>>>>> b2g team >>>>>> Mozilla Corporation >>>>>> _______________________________________________ >>>>>> 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
