Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Flashing v2.2 to Flame doesn't work: Pushing Gecko to device failed.

  • 2 wótegronje
  • 2 matej toś ten problem
  • 10 naglědow
  • Slědne wótegrono wót feklee

more options

My Flame does not want to take production build 2.2: https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g37_v2_2-flame-kk/

Before attempting to flash, I installed base image v188. I repeated the entire process several times, with the Recovery Cable, and with a normal USB cable.

Am I doing something wrong, i.e. should it work? Or is production build 2.2 flawed? Sth. else?

Details:

   $ sudo ./shallow_flash.sh --gaia=gaia.zip --gecko=b2g-37.0a2.en-US.android-arm.tar.gz
   Are you sure you want to flash
   Gaia: gaia.zip
   Gecko: b2g-37.0a2.en-US.android-arm.tar.gz
   to your Device? [y/N]y
   ### Waiting for device... please ensure it is connected, switched on and remote debugging is enabled in Gaia
   ### Restarting adb with root permissions...
   adbd is already running as root
   ### Remounting the /system partition...
   remount succeeded
   
   ### Stopping b2g process...
   ### Processing Gecko: b2g-37.0a2.en-US.android-arm.tar.gz
   ### Untar b2g-37.0a2.en-US.android-arm.tar.gz to /tmp/shallowflashgecko.00iXx8EkcRhd ...
   ### Pushing Gecko to device...
   ### Cleaning Extra System Files ...
   ### Cleaning Done.
   ### Cleaning Extra Gecko Files ...
   ##### Removing /system/b2g/distribution ...
   ### Cleaning Done.
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/dictionaries/en-US.dic -> /system/b2g/dictionaries/en-US.dic
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/dictionaries/en-US.aff -> /system/b2g/dictionaries/en-US.aff
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/components/components.manifest -> /system/b2g/components/components.manifest
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/ua-update.json -> /system/b2g/ua-update.json
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/platform.ini -> /system/b2g/platform.ini
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/crashreporter.ini -> /system/b2g/crashreporter.ini
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/libmozsandbox.so -> /system/b2g/libmozsandbox.so
   push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/omni.ja -> /system/b2g/omni.ja
   ### Failed: Pushing Gecko to device failed.
My Flame does not want to take production build 2.2: https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g37_v2_2-flame-kk/ Before attempting to flash, I installed base image v188. I repeated the entire process several times, with the Recovery Cable, and with a normal USB cable. <em>Am I doing something wrong, i.e. should it work? Or is production build 2.2 flawed? Sth. else?</em> Details: $ sudo ./shallow_flash.sh --gaia=gaia.zip --gecko=b2g-37.0a2.en-US.android-arm.tar.gz Are you sure you want to flash Gaia: gaia.zip Gecko: b2g-37.0a2.en-US.android-arm.tar.gz to your Device? [y/N]y ### Waiting for device... please ensure it is connected, switched on and remote debugging is enabled in Gaia ### Restarting adb with root permissions... adbd is already running as root ### Remounting the /system partition... remount succeeded ### Stopping b2g process... ### Processing Gecko: b2g-37.0a2.en-US.android-arm.tar.gz ### Untar b2g-37.0a2.en-US.android-arm.tar.gz to /tmp/shallowflashgecko.00iXx8EkcRhd ... ### Pushing Gecko to device... ### Cleaning Extra System Files ... ### Cleaning Done. ### Cleaning Extra Gecko Files ... ##### Removing /system/b2g/distribution ... ### Cleaning Done. push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/dictionaries/en-US.dic -> /system/b2g/dictionaries/en-US.dic push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/dictionaries/en-US.aff -> /system/b2g/dictionaries/en-US.aff push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/components/components.manifest -> /system/b2g/components/components.manifest push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/ua-update.json -> /system/b2g/ua-update.json push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/platform.ini -> /system/b2g/platform.ini push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/crashreporter.ini -> /system/b2g/crashreporter.ini push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/libmozsandbox.so -> /system/b2g/libmozsandbox.so push: /tmp/shallowflashgecko.00iXx8EkcRhd/b2g/omni.ja -> /system/b2g/omni.ja ### Failed: Pushing Gecko to device failed.

Wót feklee změnjony

Wubrane rozwězanje

Seems that Virtual Box was to blame: I run the upgrade scripts from an Xubuntu virtual machine. After migrating to VMware player, things ran through. As reported by others as well, Virtual Box has stability issues with USB communication.

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (2)

more options

Hi feklee,

I see that you also posted this question on the dev-b2g mailing list:

That is the best place for this question, since the list is seen by hundreds of developers that are familiar with the b2g project.

In the meantime, the new base image v18D is currently being tested and should be made available in a not-so-distant future.

- Ralph

more options

Wubrane rozwězanje

Seems that Virtual Box was to blame: I run the upgrade scripts from an Xubuntu virtual machine. After migrating to VMware player, things ran through. As reported by others as well, Virtual Box has stability issues with USB communication.