im trying to build android from source on ubuntu 10.04. im on a 64 bit system . but this is what im stuck on.
when i enter the repo command:
repo init -u git://android.git.kernel.org/platform/manifest.git -b eclair
it get this error back
exec: 23: python: not found
any ideas.
python: not found
yeah how do i fix it though?
thanks
install python
i have it installed already v2.6
You may have to install a version of python prior to the version you've got installed. Check which version the SDK is compatible with. =)
INSANENEIVIESIS said:
im trying to build android from source on ubuntu 10.04. im on a 64 bit system . but this is what im stuck on.
when i enter the repo command:
repo init -u git://android.git.kernel.org/platform/manifest.git -b eclair
it get this error back
exec: 23: python: not found
any ideas.
Click to expand...
Click to collapse
Unsure what you have done up to this point. It seems as though your PATH to repo is not set. I'm assuming you have already done this:
$ mkdir ~/bin
$ curl http://android.git.kernel.org/repo >~/bin/repo
$ chmod +x ~/bin/repo
$ export PATH="${PATH}:~/bin"
$ mkdir ~/xdandroid
$ cd ~/xdandroid
Have you checked your PATH settings to make sure ~/bin is in there?
Code:
echo $PATH
If you are following the wiki, the command that's on there for path doesn't work for Ubuntu (I experienced it myself and haven't looked into why...it could be because it needs to be done as sudo). Try this in terminal:
Code:
gedit ~/.bashrc
then go to the end of the file and add this to the end:
Code:
PATH=~/bin:"${PATH}"
Close any terminal windows you have open and then reopen terminal. Try the command again...
[HOW-TO] Building CM10, AOKP & TeamBaked For The JB Bootloader [Ubuntu 12.04+ 64-bit]
As many of you know, I no longer have my Transformer Prime, and hence cannot continue development for this device. So until the official CM10, AOKP and TeamBaked ROMs are updated to support the new JellyBean bootloader, as a final useful contribution to this device, I decided to provide a how-to guide to help people make their own builds.
This guide assumes that you have some experience building ROMs for Android and that you are comfortable with Linux. It is focused towards building on Ubuntu 12.04+ 64-bit.
1. Prepare the system (common for CM10, AOKP & TeamBaked)
a. Install Java JDK6
Code:
$ wget https://raw.github.com/flexiondotorg/oab-java6/master/oab-java.sh
$ chmod +x oab-java.sh
$ sudo ./oab-java.sh
$ sudo apt-get install sun-java6-jdk
b. Install required applications
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils xsltproc zlib1g-dev:i386 schedtool pngcrush
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
c. Get the repo binary
Code:
$ mkdir -p ~/bin
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
2. Building CM10
a. Get the CM10 source
Code:
$ mkdir -p ~/CM10
$ cd ~/CM10
$ repo init -u git://github.com/CyanogenMod/android.git -b jellybean
$ repo sync -j8
b. Get my JB device, kernel & vendor source trees (You could use any other, just make sure it includes the changes needed for the JB bootloader and has the 3.1 kernel)
Code:
//JB device source to device/asus/tf201
$ mkdir -p ~/CM10/device/asus
$ cd ~/CM10/device/asus
$ git clone git://github.com/craigacgomez/android_device_asus_tf201.git -b cm_jb tf201
//JB kernel source to kernel/asus/tf201
$ mkdir -p ~/CM10/kernel/asus
$ cd ~/CM10/kernel/asus
$ git clone git://github.com/craigacgomez/android_kernel_asus_tf201 -b 10.4.2.15-nvtegra tf201
//JB vendor source to vendor/asus/tf201
$ mkdir -p ~/CM10/vendor/asus
$ cd ~/CM10/vendor/asus
$ git clone git://github.com/craigacgomez/vendor_proprietary_asus_tf201 -b jellybean tf201
c. Comment out CMUpdater since this is not an official build (No harm in leaving it there as long as people are instructed not to use it)
Code:
$ cd ~/CM10/vendor/cm/config/
$ gedit common.mk [comment the line which says CMUpdater \]
d. Resync & build
Code:
$ cd ~/CM10
$ repo sync -j8
$ sh vendor/cm/get-prebuilts
$ . build/envsetup.sh && brunch tf201
3. Building TeamBaked
a. Get the TeamBaked source
Code:
$ mkdir -p ~/BAKED
$ cd ~/BAKED
$ repo init -u https://github.com/TeamBAKED/platform_manifest.git -b jb
$ repo sync -j8
b. Delete the tf201 directories
Code:
$ mkdir -p ~/BAKED/device/asus
$ rm -rf tf201
$ mkdir -p ~/BAKED/kernel/asus
$ rm -rf tf201
$ mkdir -p ~/BAKED/vendor/asus
$ rm -rf tf201
c. Get my JB device, kernel & vendor source trees (You could use any other, just make sure it includes the changes needed for the JB bootloader and has the 3.1 kernel)
Code:
//JB device source to device/asus/tf201
$ mkdir -p ~/BAKED/device/asus
$ cd ~/BAKED/device/asus
$ git clone git://github.com/craigacgomez/android_device_asus_tf201.git -b blackbean_jb tf201
//JB kernel source to kernel/asus/tf201
$ mkdir -p ~/BAKED/kernel/asus
$ cd ~/BAKED/kernel/asus
$ git clone git://github.com/craigacgomez/android_kernel_asus_tf201 -b 10.4.2.15-nvtegra tf201
//JB vendor source to vendor/asus/tf201
$ mkdir -p ~/BAKED/vendor/asus
$ cd ~/BAKED/vendor/asus
$ git clone git://github.com/craigacgomez/vendor_proprietary_asus_tf201 -b jellybean tf201
d. Resync & build
Code:
$ cd ~/BAKED
$ repo sync -j8
$ . build/envsetup.sh && brunch tf201
4. Building AOKP
a. Get the AOKP source
Code:
$ mkdir -p ~/AOKP
$ cd ~/AOKP
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb
$ repo sync -j8
b. Get my JB device, kernel & vendor source trees (You could use any other, just make sure it includes the changes needed for the JB bootloader and has the 3.1 kernel)
Code:
//JB device source to device/asus/tf201
$ mkdir -p ~/AOKP/device/asus
$ cd ~/AOKP/device/asus
$ git clone git://github.com/craigacgomez/android_device_asus_tf201.git -b aokp_jb tf201
//JB kernel source to kernel/asus/tf201
$ mkdir -p ~/AOKP/kernel/asus
$ cd ~/AOKP/kernel/asus
$ git clone git://github.com/craigacgomez/android_kernel_asus_tf201 -b 10.4.2.15-nvtegra tf201
//JB vendor source to vendor/asus/tf201
$ mkdir -p ~/AOKP/vendor/asus
$ cd ~/AOKP/vendor/asus
$ git clone git://github.com/craigacgomez/vendor_proprietary_asus_tf201 -b jellybean tf201
c. Add tf201 to the vendor & build setup
Code:
$ cd ~/AOKP/vendor/aokp
$ gedit vendorsetup.sh
Add this line vendorsetup.sh below add_lunch_combo aokp_tf101-userdebug
Code:
add_lunch_combo aokp_tf201-userdebug
Code:
$ cd ~/AOKP/vendor/aokp/products
$ gedit AndroidProducts.mk
Add this line vendorsetup.sh below $(LOCAL_DIR)/tf101.mk \
Code:
$(LOCAL_DIR)/tf201.mk \
Code:
$ cd ~/AOKP/vendor/aokp/products
$ touch tf201.mk
$ gedit tf201.mk
Add these line to tf201.mk
Code:
# Inherit device configuration for tf201.
$(call inherit-product, device/asus/tf201/full_tf201.mk)
# Inherit some common AOKP stuff.
$(call inherit-product, vendor/aokp/configs/common_tablet.mk)
$(call inherit-product, vendor/aokp/configs/gsm.mk)
PRODUCT_NAME := aokp_tf201
PRODUCT_DEVICE := tf201
PRODUCT_BRAND := asus
PRODUCT_MODEL := Transformer Prime TF201
PRODUCT_MANUFACTURER := asus
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=EeePad \
BUILD_FINGERPRINT="asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.15-20120917:user/release-keys" \
PRIVATE_BUILD_DESC="US_epad-user 4.1.1 JRO03C US_epad-10.4.2.15-20120917 release-keys" \
PRODUCT_COPY_FILES += \
vendor/aokp/prebuilt/bootanimation/bootanimation_1280_800.zip:system/media/bootanimation.zip
d. Resync & build
Code:
$ cd ~/AOKP
$ repo sync -j8
$ . build/envsetup.sh && brunch tf201
Craig, you are so awesome. Thank you so much for all you have done for the community. I hope I can end up with a nexus so I can continue to follow your development, but I'm also glad for the instruction and inspiration to start figuring out how to do more myself. Thanks again.
You're an absolute legend.
I just pressed return to start the build of my first ROM from your previous guide when I saw this..
qubz said:
Your an absolute legend.
Click to expand...
Click to collapse
I'm so sorry if I seem mean... but I just had to do this... I'm a grammar nazi!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
craigacgomez said:
I'm so sorry if I seem mean... but I just had to do this... I'm a grammar nazi!!
Click to expand...
Click to collapse
Ha ha, you got me. It's been a long day. Unfortunately the reply box had no compiler, fix uploaded.
Hey craigacgomez,
thanks for your work.
But I got a problem while trying to build CM10.
Pastebin entry:
http://pastebin.com/st0DfWv4
I'm trying to build it on a server without a gui, what should make no problems. Installed all the requirements you mentioned.
Do you know how to get rid of this error?
Greetz
Chrischdi
chrischdi said:
Hey craigacgomez,
thanks for your work.
But I got a problem while trying to build CM10.
Pastebin entry:
http://pastebin.com/st0DfWv4
I'm trying to build it on a server without a gui, what should make no problems. Installed all the requirements you mentioned.
Do you know how to get rid of this error?
Greetz
Chrischdi
Click to expand...
Click to collapse
libjli.so is a Java binary... somehow it cannot find it... could you try this...
http://serverfault.com/questions/57...ject-file-libjli-so-no-such-file-or-directory
Thanks for this.
I'm hoping to keep your work going , this is a great start
its sad that you no longer have a prime though.
sent from my Prime
Thanks for posting this! You are an absolute legend! It is a massive help as I just started setting up my build environment for compiling my own CM10 and maybe even look at Paranoid :silly:
marko! said:
Thanks for this.
I'm hoping to keep your work going , this is a great start
its sad that you no longer have a prime though.
sent from my Prime
Click to expand...
Click to collapse
gunzy83 said:
Thanks for posting this! You are an absolute legend! It is a massive help as I just started setting up my build environment for compiling my own CM10 and maybe even look at Paranoid :silly:
Click to expand...
Click to collapse
Nice to see people pick up where I left off... to be honest, all I did for this device was the first time for me... I've just been good at modding and I never dug deep into ROM & kernel work before, so I'm pretty sure you guys could do the same or even better!
Hi,
many thanks again Craig for all your work..
I tried to follow your guide for Team Baked, and ended up with::
""build/core/product_config.mk:193: *** _nic.PRODUCTS.[[vendor/baked/products/p5wifi.mk]]: "device/samsung/p5wifi/p5wifi.mk" does not exist. "Stop.
"** Don't have a product spec for: 'baked_tf201'
"** Do you have the right repo manifest?
"
Itried running breakfeast command as suggested but same error.
Anyone has a suggestion ?
Thanks
Striatum_bdr said:
Hi,
many thanks again Craig for all your work..
I tried to follow your guide for Team Baked, and ended up with::
""build/core/product_config.mk:193: *** _nic.PRODUCTS.[[vendor/baked/products/p5wifi.mk]]: "device/samsung/p5wifi/p5wifi.mk" does not exist. "Stop.
"** Don't have a product spec for: 'baked_tf201'
"** Do you have the right repo manifest?
"
Itried running breakfeast command as suggested but same error.
Anyone has a suggestion ?
Thanks
Click to expand...
Click to collapse
Don't run breakfast... just brunch... looks like it has something to do with the p5wifi... try resyncing or comment out that 'add_lunch_combo baked_p5wifi-userdebug' from vendor/baked/vendorsetup.sh
craigacgomez said:
Don't run breakfast... just brunch... looks like it has something to do with the p5wifi... try resyncing or comment out that 'add_lunch_combo baked_p5wifi-userdebug' from vendor/baked/vendorsetup.sh
Click to expand...
Click to collapse
My noob is going to start showing here, but when you say "Comment out" does that simply mean putting brackets around? Does it mean deleting that from the script? I haven't tried to build since your first little guide, but I think I put brackets around what it said to "Comment out."
lortay78 said:
My noob is going to start showing here, but when you say "Comment out" does that simply mean putting brackets around? Does it mean deleting that from the script? I haven't tried to build since your first little guide, but I think I put brackets around what it said to "Comment out."
Click to expand...
Click to collapse
That means out a # at the beginning of the line.
Hi,
Commented out all lines except tf201 in vendorsetup.sh and same error.
Striatum_bdr said:
Hi,
Commented out all lines except tf201 in vendorsetup.sh and same error.
Click to expand...
Click to collapse
Add these lines to the manifest.xml, then repo sync and brunch tf201:
<project path="device/samsung/p4-common" name="device_samsung_p4-common" remote="baked" revision="jb" />
<project path="device/samsung/p5wifi" name="device_samsung_p5wifi" remote="baked" revision="jb" /> :good:
csrabear said:
Add these lines to the manifest.xml, then repo sync and brunch tf201:
<project path="device/samsung/p4-common" name="device_samsung_p4-common" remote="baked" revision="jb" />
<project path="device/samsung/p5wifi" name="device_samsung_p5wifi" remote="baked" revision="jb" /> :good:
Click to expand...
Click to collapse
Great !
It does the trick but... lol
Then error with prebuilts arm toolchain,
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc : binary file impossible to execute
Same error endless. Files are there, permission set to executable...
Is there a way to use arm ubuntu toolchain (easily installed by Synaptic)?
Thanks again
Striatum_bdr said:
Great !
It does the trick but... lol
Then error with prebuilts arm toolchain,
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc : binary file impossible to execute
Same error endless. Files are there, permission set to executable...
Is there a way to use arm ubuntu toolchain (easily installed by Synaptic)?
Thanks again
Click to expand...
Click to collapse
Hi,
Try this thread for answer---
http://www.google.com/url?sa=t&rct=j&q=%2Fbin%2Fbash%3A%20prebuilts%2Fgcc%2Flinux-x86%2Farm%2Farm-linux-androideabi-4.6%2Fbin%2Farm-linux-androideabi-gcc%20%3A%20binary%20file%20impossible%20to%20execute&source=web&cd=1&cad=rja&ved=0CDAQFjAA&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1762641%26page%3D34&ei=T9KsUOnCMIuK8QS0wYHIAQ&usg=AFQjCNEZuCIRoHJX7_h_34dD3tvmeBbVsQ
or maybe this one will help--
http://www.google.com/url?sa=t&rct=j&q=%2Fbin%2Fbash%3A%20prebuilts%2Fgcc%2Flinux-x86%2Farm%2Farm-linux-androideabi-4.6%2Fbin%2Farm-linux-androideabi-gcc%20%3A%20binary%20file%20impossible%20to%20execute&source=web&cd=2&cad=rja&ved=0CDkQFjAB&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1807505%26page%3D2&ei=T9KsUOnCMIuK8QS0wYHIAQ&usg=AFQjCNE0FwC2wWy8UE5QHperdU0rI72MKw
csrabear said:
Hi,
Try this thread for answer---
or maybe this one will help--
http://www.google.com/url?sa=t&rct=j&q=%2Fbin%2Fbash%3A%20prebuilts%2Fgcc%2Flinux-x86%2Farm%2Farm-linux-androideabi-4.6%2Fbin%2Farm-linux-androideabi-gcc%20%3A%20binary%20file%20impossible%20to%20execute&source=web&cd=2&cad=rja&ved=0CDkQFjAB&url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1807505%26page%3D2&ei=T9KsUOnCMIuK8QS0wYHIAQ&usg=AFQjCNE0FwC2wWy8UE5QHperdU0rI72MKw
Click to expand...
Click to collapse
Thanks that's what I suspected, I build on a 32bits machine, found 32 arm binaries in the above post.
Will try later. Thanks.
You really need a 64 bit os. Compilation started fine, but a some point gcc sdk binaries are used and again the default paths lead only to 64 bits ones.
I'll install a 64 version if ubuntu.
Thanks guys for you helps
AOSPA+ Building from sources
Pre reuirments :
A 64 bit PC
Some knowlegde About Git
A brain
This is unofficial. This thread is intended for devs & advanced users only.
For the first time you try to build AOSPA
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Download & compile lz4 compression tool
Code:
sudo apt-get install subversion
cd ~/Downloads
svn checkout -r 91 http://lz4.googlecode.com/svn/trunk/ lz4
cd lz4 && make && cp lz4demo ~/bin/lz4demo
Initialize the AOSPA source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/ParanoidAndroid/manifest.git -b jb43-legacy
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Get the prebuilts
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
Setup the environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-10.2-DATE-UNOFFICIAL-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Setup the environment
Code:
. build/envsetup.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/PA-3.9-DATE-UNOFFICIAL-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Credits: Thanks to hnl_dk , mikeioannia for the initial CM9 & CM10 , 10.1 , 10.2 guides.
And you built successfully with that method? Because as far as I know it's impossible... You didn't define anything about the device in the vendor/pa folders so it can't even find your device while trying to ./rom-build.sh
Sent from my Nexus 4 running Android 4.2.2
As reported by mihahn this thread seems a blatant copy of another guide without any actual research. I've maintained AOSPA for several devices for some time and see at least 2 mistakes when quickly scanning through it.
Thread closed for now, if it's solved I'll reopen, otherwise it will be deleted.
Hi there, I'm extremely new to building a ROM or even to git and other stuff and am now trying to learn to build ROM. I have downloaded the cm12 sources for now, and trying to learn how it works, but seems to have stuck at a location.
I have been following the cm build page instructions for now from this page, and have done following stuff until now:
Make folders:
Code:
mkdir -p ~/bin
$ mkdir -p ~/android/system
Installed the repo command and entered the following to download the "repo" binary and make it executable (runnable):
Code:
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution
Initialize the CyanogenMod source repository and initialized the repository:
Code:
$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b ics
Downloaded the source code
Code:
$ repo sync -j4 -f -c
[*]Get prebuilt apps
Code:
$ cd ~/android/system/vendor/cm
Now when I get to the get prebuilt apps, and I run cd ~/android/system/vendor/cm, I get the
Code:
cd ~/android/system/vendor/cm bash: No such file or directory
I tried opening the location manually, but I find no "vendor" folder under the "android/system" folder. However, there is a "vendor" folder under "android" and that "vendor" consists of folders like "cm", "cyngn" and "sony", where "sony" is related to My phone.
Under system I have folders like "core", "extras", "keymaster", "media", "netd", "qcom", "security" and "vold".
Before You say that I might have not done repo sync properly, it did complete properly. I have attached the image of completion of first time the repo sync was complete. Then a log of second time when the repo sync was done to get the device specific related stuff. I used the -f since the download of source had been interrupted due to the error "error: Exited sync due to fetch errors".
Also, don't know if it matters, but I have built a ROM before on the same system, but it was by following the instructions as posted to do. The sources were all coded to suit My phone, and all I was doing was "repo sync" and building the ROM via source with commands build/envsetup.sh
and breakfast nozomi and used to get a working build.
So please help Me out where I went wrong as I do want to learn to how to build a ROM.
Edit:
I had also tried searching for "get-prebuilts", "envsetup.sh" too, but couldn't find them either, and yes, I was always in the root directory of the source code (~/android/system).
Same issue here. Ironically I can build AICP (which is Cyanogenmod based). I can build any AOSP Rom without compiling problems also. This is a Cyanogenmod thing. It's also frustrating that even if you do manage to compile it, you probably won't be able to flash it. That happened to me with 5.0
Just for kicks, what is your OS? I'm running Linux Peppermint. I wonder if that could be the issue, since Ubuntu is recommended?
Check your java & sdk version
Actually I have read so many topics about building Android Open Source Project for Intel based platform , they are such Android X86 , OS Remix and AOSP_IA (AOSP for Intel Architecture).
Now I want to build an AOSP for my tablet which is based on Intel Atom ( Z3735F), 10.1 inches display , 2 GB RAM and INSYDE UEFI bios type , device codename :inet_phone_32
My tablet runs Android 5.1.1_r1 (AOSP_AI TYPE) , there is no back up or rooting technique for this tablet ,so I decide to build an AOSP ROM for this tablet ,if the Android OS has a problem , I am able to flash it again and survive it.
I have tried in 3 ways to build an AOSP for my tablet but no one is correct so, I need an android developer or android expert to guide me and modify my mistakes .
According to google source :
these are steps for building AOSP for a device :
1. install , Java 8 ,git, curl , ($ sudo apt-get install "App")
2. Setting up ccache
3. install repo
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
4. creating working Directory
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
5.git configuration (name and email)
$ git config --global user.name "Your Name"
$ git config --global user.email "[email protected]"
6.inititilized repo and download the proper ROM
$ repo init -u https://android.googlesource.com/platform/manifest
$ repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r1
$ repo sync
7.$ . build/envsetup.sh
8. choosing the target
$ lunch inet_phone_32-userdebug
9.$ make(m) -j4-efi
Click to expand...
Click to collapse
unfortunately , it wont flash on my tablet !
According to Android X86 : these are steps for building an AOSP_X86
1. install , Java 8 ,git, curl , ($ sudo apt-get install "App")
2. Setting up ccache
3. install repo
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
4. creating working Directory
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
5.git configuration (name and email)
$ git config --global user.name "Your Name"
$ git config --global user.email "[email protected]"
6.inititilized repo and download the proper ROM
$ repo init -u http://scm.osdn.net/gitroot/android-x86/manifest
$ repo init -u http://scm.osdn.net/gitroot/android-x86/manifest -b lollipop-x86
$ repo sync --no-tags --no-clone-bundle
7.$ . build/envsetup.sh
8. choosing the target
as it was said on Android X86 instruction :
$ lunch android_x86-userdebug
9.$ make(m) -j4-efi
Click to expand...
Click to collapse
unfortunately , it also wont flash on my tablet !
According to Android on Intel Platform , these are below steps for building AOSP_IA:
Dependencies:
Follow initial steps from here: https://source.android.com/source/initializing.html
Additional Dependencies:
sudo apt-get install git-core gnupg flex bison gperf build-essential lunch zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip squashfs-tools python-mako distcc ccache python2.7 python-mako gettext mtools qt-sdk
Additional packages to be installed when developing in a Ubuntu chroot environment (created with debootstrap):
bc, dosfstools, mtools, libssl-dev
Github Account and SSH Keys:
Ensure you have your ssh key setup with your Github account:
https://help.github.com/articles/generating-an-ssh-key/
https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/
https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/
Setup CCache (Speeds up compilation):
https://source.android.com/source/initializing.html#setting-up-ccache
Downloading the source code
Using SSH protocol:
repo init -u [email protected]:android-ia/manifest.git
If you prefer using https:
repo init -u https://github.com/android-ia/manifest.git
Sync Code
repo sync
Building the OS image
. build/envsetup.sh
lunch androidia_64-eng
m -j4 android_ia-efi
Flash Image:
Unmount USB: sudo umount /dev/sdg* (Check where usb is mounted and change appropriately)
Flash the image: sudo dd if=out/target/product/androidia_64/androidia_64.img of=/dev/sdg (Check where usb is mounted and change appropriately)
Click to expand...
Click to collapse
which is not flashing on my tablet
Please kindly help me where are my mistakes , how can I modify it , if I dont know missing information , please contribute ,thank you