How to build AOSP or Cyanogenmod for zte N881F - General Questions and Answers

I need help to build Cyanogenmod or AOSP ROM for my device(zte N881F), that is not yet supported by anyone.
I search keywords like "android build" or "android port" etc.but just couldn't find the result i want.
My questions is:
now i have official ics based rom and kernel open source code,also i have downloaded android4.0.4 and cm9 using repo, compile the cwm recovery and it works well on my device.so if i wanna compile AOSP or cm9 for my device what should i do next? a device tree is enough?
I am terribly sorry for my poor English, i would be glad to see anyone wanna guide me into android developerment world,thx!

Related

[Q] Kernel Compile

Hey guys, I want to install a custom kernel, razrqcom-dev-team kernel, on my XT925 - Carbon ROM(0614) but I dont find any information about how to procede.
I downloaded the repository android_kernel_motorola_msm8960-common(razrqcom-dev-team). Someone has a good instruction or know a good tutorial to share?
My apologies about my poor english
Cheers,
Just to clarify: Are you looking for the pre-compiled kernel or do you want to learn how to build android from source?
If you only want a precompiled kernel, then you shouldn't worry, as the right one is already built in line with the rom you chose.

[Q] Help Building unofficial ROM

I'm trying to build unofficial Dirty Unicorns for the TF300T. I've been using this tutorial to set up my build environment:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I've managed to sync their repos and all that, and I've come to the device tree. I wasn't able to find an equivalent tree on Google's website like the Nexus 7. So my question is, where can I find the tree(s) for my Transformer? Is building for a device really as simple as combining the repo, device trees, and blobs? That's what this tutorial implies. Or am I likely to end up with a crappy build?
Wow.
you might be able to find the device tree from the omni rom guys. Last time I tried to do this it was for my ME301. I was able to download the device tree from the Omonirom gerrit page. Poke around the Omnirom guys site and thread and see if they have it. Here ya go. This is the cyanogen github page. it looks like they list both the tf300t kernel and the device tree for cyanogen mod ROM
https://github.com/CyanogenMod?utf8=✓&query=tf300t
That might be a start
Here is the wiki page for building Cyanogen Mod for the tf300t and it might explain some steps better

[Completed] How to get proprietary blobs!!

how to build a cyanogenmod from source for unsupported devices.All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the first proprietary blobs came from??
How can we get the proprietary blobs for other devices for the first time build?
I dnt understand anything...I'm trying to build a fresh cm12.1 rom for my device galaxy j5..plz guide me in ryt way if am wrong
ganesh varma said:
how to build a cyanogenmod from source for unsupported devices.All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the first proprietary blobs came from??
How can we get the proprietary blobs for other devices for the first time build?
I dnt understand anything...I'm trying to build a fresh cm12.1 rom for my device galaxy j5..plz guide me in ryt way if am wrong
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
You can take a look at [GUIDE][COMPLETE] Android ROM Development From Source To End
Also read http://www.netmite.com/android/mydroid/development/pdk/docs/
___
v7
XDA Assist

Questions about building a custom ROM from AOSP

Hi, I am currently building custom rom for my Lenovo a7000-a (aio_row) and I have a few questions regarding the device section of the AOSP build.
1. I have seen that to build the custom ROM for a device, I would need the following .mk files from topic "Android device configuration AOSP" in Stackoverflow.
However, from the device configuration/device-tree(?) from user rohantaneja in Github, I see that I would also need files that look like drivers for the devices based on the files on that github. May I ask how would I obtain these files?
2. Would flashing an arm64 generic build of custom AOSP into any Android device work or not? If so, why?
Seems like the amount of knowledge that I faced off with confused me a lot.
Any help is appreciated.
Thanks in advanced.

How to port rom from HTC sensation?

I have an One s with S3 processer(villeC2).
Its specs are similar to sensation(with same cpu and screen resolution),but sensation has Android 7.1 ROM and one s only 4.4......
I would like to port a ROM for it from sensation.
Does anyone know how to do that?
Or if it is possible ?
(sorry for my bad english)
(my first post)
Some info !
Hi,
Actually I'm new in building roms and kernels, too. But i can share some info with you.
For starting this tutorial may be helpful: [Guide] Compile 4.2 & 4.3 & 4.4 Roms for villec2
As you can see, you will need "device", "vendor" and "kernel" source to build a rom.
Usually you can find source code of roms and kernels in xda threads and can start from those.
For example for Android 7.1 you can use RROS vendor and VilleC2 device and kernel sources. (Note: i don't know are these examples compatible or not?!)
And for kernel, maybe you has to upstream the kernel source to be compatible with new version of android that you want to build.
Good luck.
-----------------------------------
Edit:
After Compiling for myself, i figured out Vendor files for choosed rom (Lineage, RR, ..) will be included by their manifest files automatically. so for "Vendor" part in "local_manifest.xml" (or newer "local_manifests/roomservice.xml") we need to assign "proprietary_vendor" files related to our devices. "proprietary_vendor" files can be extracted manully if there isn't any online source.
one more useful guide: [GUIDE]Building any ROM from source for HTC One S aka ville!

Categories

Resources