Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Compiling Firefox OS 1.2 for ZTE Open using Ubuntu 13.04
sudo apt-get install –no-install-recommends autoconf2.13 bison bzip2 ccache curl flex gawk gcc g++ g++-multilib gcc-4.6 g++-4.6 g++-4.6-multilib git ia32-libs lib32ncurses5-dev lib32z1-dev zlib1g:amd64 zlib1g-dev:amd64 zlib1g:i386 zlib1g-dev:i386 libgl1-mesa-dev libx11-dev make zip
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
sudo apt-get install oracle-java6-set-default
sudo apt-get install android-tools-adb
sudo echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev"' > /etc/udev/rules.d/android.rules
sudo echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/android.rules
sudo chmod a+r /etc/udev/rules.d/android.rules
sudo service udev restart
export CC=gcc-4.6
export CXX=g++-4.6
ccache –max-size 3GB
git config –global xxxx
git config –global "yyyy"
git clone git://
cd B2G
BRANCH=v1.2 VARIANT=user ./ inari
BRANCH=v1.2 VARIANT=user ./
cp [location of that binary boot.img] out/target/product/inari/boot.img
Copy link

asdf23 commented Apr 2, 2014

Hello, thanks for providing this. It cleared up some questions I had.

I've asked over at #b2g with no success. Could you explain the boot.img a little? Specifically if it is unchanged then why bother to flash it at all? Can I pull this file off of the device? Should there be a different boot.img for each version (does 1.1 have a different boot.img than of 1.4)?

Also.. the end result is a few img files that I can use fastboot to load onto the device. How different is this from the zip file? Would it be possible to create my own zip flash image -- so that I could use cwm to flash the device? And on that subject what would it take to sign the zip file so that I would not need cwm at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment