Hi,
I would like to learn how to create my own custom ROM. Any reference you have on the topic would be great. I have successfully built my own kernel from source and have made a guide here: http://forum.xda-developers.com/showthread.php?t=1516051
Now I would like to build my own custom ROM. I noticed that when I downloaded the kernel source code from Samsung it also included the platform source code. I have read somewhere that I wouldn't be able to compile the Stock ROM just because a lot of the stuff is proprietary (like touchwiz). If this is the case, how are developers including the proprietary stuff?
Is it possible to build stock ROM from source?
Are custom ROMs more about tweaking existing configurations and apps, as oppose to compiling from scratch?
Thanks for helping a noob. I really want to learn the stuff.
Related
First off, I would like to say that I love this phone. I've built a couple takes of CM using the Cyanogenmod source, and am quite aware that it is based off of AOSP along with other custom modifications etc. I may be wrong, but from what I can infer, the buildspec.mk file that you must copy to the root of the source folder determines the build when you make. If CM is made from AOSP, and already contains a full working AOSP setup/configuration, how would I go about building a straight AOSP rom from the source without any external additions?
Sent from my HTC Vision using XDA App
thrice43 said:
First off, I would like to say that I love this phone. I've built a couple takes of CM using the Cyanogenmod source, and am quite aware that it is based off of AOSP along with other custom modifications etc. I may be wrong, but from what I can infer, the buildspec.mk file that you must copy to the root of the source folder determines the build when you make. If CM is made from AOSP, and already contains a full working AOSP setup/configuration, how would I go about building a straight AOSP rom from the source without any external additions?
Click to expand...
Click to collapse
Everything is based on AOSP. Everything. If you want to build pure AOSP, you need to download AOSP from AOSP. You can't build pure AOSP from source that IS NOT pure AOSP because it HAS BEEN CHANGED.
Moved to Q&A
dhkr123 said:
Everything is based on AOSP. Everything. If you want to build pure AOSP, you need to download AOSP from AOSP. You can't build pure AOSP from source that IS NOT pure AOSP because it HAS BEEN CHANGED.
Click to expand...
Click to collapse
Well, I pulled the files from AOSP git but I have no other build/make files to go off of other than Cyanogen's. How would I know what lines to comment out and what lines to keep?
Sent from my HTC Vision using XDA App
I think you will have more to do to get something built from scratch. From a software engineering perspective you will have to use some code that was built to bridge between the hardware (G2 specific) and the stock operating system. This is a classic UNIX paradigm - the source is portable, but you have to have the interfaces to the hardware to hook in and create a complete set.
I'm finding that my phone has a Froyo WiFi calling app, and this is being used under Gingerbread because I'm using CM7.0.3 (Gingerbread based ROM). Not a clean combination.
I'm working from the CM source tree... Take a look here: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vision
Tommy.
Hi, could someone upload the stock N2E kernel? I would like to tinker around with building my own kernel but I cannot figure out how to extract it from a running N2E.
P.S. I've already tried /proc/config.gz and /boot/config-...blah blah and have had no luck.
The source code is available here :
NOOK 1.0 OSS Release
NOOK 1.0.1 OSS Release
One of my frustrations with rooting my nook is I do not ahve a clean rom in case I need to return it to B&N. Is there anyway I could use source code to load a clean rom and undo the rooting?
Hello
I came from black berry so little confused on everything. Can somebody help me understand some of this.
Sent from my Galaxy Nexus using Tapatalk 2
They're branches of ROM development. Different individuals and teams work on their own ROMs and distribute them regularly. They each have their own features, looks and performance tweaks that they think are best.
As a quick start, "AOSP" is the Android Open Source Project. Google maintains the open source Android code, and individuals can pull from it and build their own ROMs off of that. So when someone says their ROM is "AOSP based", they're saying that they pulled the source from Google then modified it.
And like-wise with CM10/AOKP they provide their own source code.
CM10 = Cyanogenmod team. A very popular ROM. They do have their own ROM but also provide their own source code for those wanting to start with an already modified base. As an example CM10 based ROMs usually come with certain additional features like the CM kernel, profiles, etc.
AOKP = Android Open Kang Project. As the name suggests it is also the same idea. A source code provided by a developer of a Popular ROM (AOKP) for other users to use. Also comes with features not included in the base AOSP ROM
If any of that is wrong someone will correct me I'm sure
Hi guys and girls,
I want to experiment with building ROMs just for educational means. BUT, I have no experience in developing whatsoever . For instance I want to build a rom from Lord Clockan's source but where do I start? Can someone help setting things up from scratch/point me in the right direction?
Thanks in advance!
The only ROMs built from source are CM and AOKP, everything else is just modified stock (which you can't build).
With that in mind, read this: http://wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Compile_CyanogenMod_9_(Linux)
Wrong phone, but it's step by step.
Rusty! said:
The only ROMs built from source are CM and AOKP, everything else is just modified stock (which you can't build).
With that in mind, read this: http://wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Compile_CyanogenMod_9_(Linux)
Wrong phone, but it's step by step.
Click to expand...
Click to collapse
So how could I use their work for building a ROM?
Well if it's a CM based ROM, you would need to get the CM source, then use local_manifest to bring in others repos when you sync.
Hi,
since some people seems to have made new MCU Firmwares and Android,
where is the source of that to improve it further?
They havent made new MCUs, theyve simply modded existing ones. No source code for ROMs, again devs mod factory ROMs.