Can uefi+gpt use the iso file?

[skythatun...@gmail.com]

I am installing x86 on my surface pro 3 through img files. However I found most of the builds are iso files. So I'm asking if uefi+gpt support iso files installation, thanks!

[Chiem Ma]

Hi.  I spent a fair amount of time learning how to get Android working on the SP3.

You need the .img version because the SP3 is a UEFI only system.  It has no BIOS emulation mode.

Unfortunately, you also need the x32 version, because the x64 version lacks working root functionality.

In order to get things working, you have to build the project yourself to create an x32 EFI .img version of Android.

You'll need close to 100GB of space to compile, and 4 GB RAM.

I used Ubuntu to create my .img.  I think this is a complete list of commands required.  Check out the instructions for building Android on your own.  Warning: it took HOURS to build this.

sudo apt-get update

sudo apt-get install python.mako openjdk-7-jdk git-core repo gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip

mkdir android-x86

cd android-x86

EDIT THIS LINE: git config --global user.email "<your email>"

EDIT THIS LINE: git config --global user.name "<your username>"

repo init -u git://gitscm.sf.net/gitroot/android-x86/manifest -b lollipop-x86

repo sync

(you must rerun both build/envsetup.sh and lunch if you reboot)

. build/envsetup.sh

lunch

SELECT 10 - Engineering build of Android x86

make efi_img -j4

[Darren Clark]

Also, I created docker images to build android-x86. Might be a bit easier than hoping you have get all the dependencies first try.

To use:

1. Install Docker (https://docs.docker.com/engine/installation/)

2. Create directory and CD into it.

3. Pull android-x86 source: repo init -u git://gitscm.sf.net/gitroot/android-x86/manifest -b lollipop-x86 && repo sync

4. docker run --rm -ti -e ANDROID_BUILD_PRODUCT=android_x86-eng -e ANDROID_BUILD_TARGET=efi_img -e ANDROID_BUILD_UID=$(id -u) -e ANDROID_BUILD_GID=$(id -g) darrenclark/android-build-lollipop-x86 -e ANDROID_BUILD_JOBS=<job count> -v $(pwd):/source darrenclark/android-build-lollipop-x86

Replacing <job count> with how many concurrent compile tasks you want. See https://hub.docker.com/r/darrenclark/android-build-lollipop-x86/ for more docs on the image.

Also an image for kitkat-x86, just change the name.

-Darren

[Darren Clark]

Whoops. Messed up the last command line. Should be:

 docker run --rm -ti -e ANDROID_BUILD_PRODUCT=android_x86-eng -e ANDROID_BUILD_TARGET=efi_img -e ANDROID_BUILD_UID=$(id -u) -e ANDROID_BUILD_GID=$(id -g) -e ANDROID_BUILD_JOBS=<job count> -v $(pwd):/source darrenclark/android-build-lollipop-x86

[rbg]

so job count is like -jx in a regular build??? if so how many processors do you have available....

8 / 12 / 16 / 20 / etc. ???

thanks 

[おとめ座ひなたぼっこ]

How to install img file, also if grub2 is install on uefi partition , how to remove it later. I ask for my Yoga

[Darren Clark]

Yeah, it just uses environment variables given to the container to build the command line. If you look at the build script in the image or at http://github.com/darren-clark/android-build you can see the command line that it ends up with.

-Darren