Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,657 Members 43,521 Now Online
XDA Developers Android and Mobile Development Forum

[Q] aosp initramfs/ramdisk source

Tip us?
 
koe1974
Old
#1  
Senior Member - OP
Thanks Meter 550
Posts: 1,424
Join Date: Oct 2007
Question [Q] aosp initramfs/ramdisk source

I am working on building from aosp 4.4.2. I have built it with the pre-built kernel without any problems. Then, I managed to get a custom kernel code in place and it builds. Now the only thing left to do is the initramfs/ramdisk for the custom kernel I have in place. Currenlty my build will not boot. I suspect it is using the initramfs/ramdisk from aosp.

Can someone point me to the source files or files that handle the initramfs/ramdisk? I have found bits and pieces strewn throughout the source code but cannot pinpoint the indivitual files or the script/mk file that produces the ramdisk found in the out folder after my system finishes building.

I kinow I can change the initramfs/ramdisk manually by repacking the boot.img, but I would prefer everything be completed in the updatpackage.
I'm reckless with my devices. I'm just warning you!
 
broodplank1337
Old
#2  
broodplank1337's Avatar
Recognized Contributor / Recognized Developer
Thanks Meter 10,021
Posts: 4,940
Join Date: Nov 2011
Location: Nijmegen

 
DONATE TO ME
what device do you have?

Anyways, just decompile the working boot.img with dsixda's kitchen, and replace the zImage, build it again and done
Device: Samsung Galaxy S4 (i9505)

Latest Development:
 

Roms:
AOSP v4.4.4 (KTU84P) from source for I9505 (Github)
- Cleanest ROM available for i9505. along with up-to-date stock kernel, also forms a perfect base for ROM developers.

Apps:
Galaxy S4 Glove Mode App (Playstore link)
- Do you want the Glove Mode of the S4 but your ROM doesn't support it? Use this app to enable/disable it easily.

Latest Scraps:
Proprietary Lib Cleaner / Silent proprietary libs / Live Thermal Monitor / GIT Conflict Fixer

Projects in development:
 

broodROM KitKat "Aiming for perfection"
- Custom ROM with really high standards, more info soon

For sources you can visit my Github. Or take a look at all my projects

 
koe1974
Old
#3  
Senior Member - OP
Thanks Meter 550
Posts: 1,424
Join Date: Oct 2007
Quote:
Originally Posted by broodplank1337 View Post
what device do you have?

Anyways, just decompile the working boot.img with dsixda's kitchen, and replace the zImage, build it again and done
I have a Nexus 5. I'm trying to avoid the, "build it again."

I would like to envsetup, lunch, make clean, make updatepackage, flash and done.

So, I'm still trying to figure out, how make knows where to get all the files and create the ramdisk in the out directory.
I'm reckless with my devices. I'm just warning you!
 
nizammoidu
Old
#4  
Junior Member
Thanks Meter 12
Posts: 22
Join Date: Jan 2011
Location: Dubai
Default AOSP radisk

I am no expert but I think this is how ramdisk is built and it worked for me al the time. ramdisk is composed from the directory 'root' in the product build output folder. the contents are coming from different part of the build tree, mostly from the device source, vendor source. for eg:- check hammer head tree for omni https://github.com/omnirom/android_d...lge_hammerhead in the device.mk you can see PRODUCT_COPY entries to the root similar thing goes with vendor makefiles. If you are looking for executable built from source you can set
LOCAL_MODULE_PATH := $(TARGET_ROOT_OUT) so that they will end up in initrd
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes