[Q] How do I put together a AOSP pure KitKat ROM? - HTC One X

I need to know how to put together a pure AOSP 4.4.2 ROM, my build environment has been collecting dust and I've only just updated the build tools. Can someone tell me what repositories I have to sync and what the make/build command is for this device? Cheers.

Related

[Question] AOSP build from Cyanogenmod Source buildspec?

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.

[Request] Stock N2E Kernel

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?

[Q] How to build custom rom

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.

[q] vzw vk810 roms?

I am very interested in getting CM11 or Mahdi onto the Verizon version of the G Pad. I have no experience compiling code for Android and haven't compiled a Linux kernel in ages. Can someone point me to any how-tos on compiling ROMS? What needs to happen to make a ROM work on the VK810?
idk
I don't know but I would love one. I like the tablet, but I can't stand the skin.
Here is a very good tutorial > http://wiki.cyanogenmod.org/w/Development
once I (or someone else) brings up the cm11 devicetree for the vk810, then you can usually take the devicetree+kernel+proprietary libs, and build for any ROM that has open sources...

changing base of rom

So I made a rom a while back for my old s3 back when 4.1.2 was new and I don't remember how to change the base of the rom to a different android version I want to make it 4.4.2 based anyone wanna help please and thank you
Well I know nothing about coding but maybe if you based it on a ROM like cyanogenmod you could merge with the latest repository
Any mods you made to one version will have to be redone using the new version. And it isn't as easy either. Seems like with every new update modifying the existing code gets more and more difficult. This is for stock TW though, I have no experience with cm/aosp bases so I'm not sure if it would be any easier.

Categories

Resources