Voices Of XDA: Orbiting The Earth With Android

Editor’s note: This week’s feature has been written by forum … more

CloudPlayer: DIY HiFi Music Streaming Solution

In our Helpful Guide to Music Streaming Services, we mentioned several different services … more

Optimize Battery Life with This Useful App

Battery life is an important aspect of your smartphone, especially if you use it for more … more

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

[Q] aosp initramfs/ramdisk source

1,562 posts
Thanks Meter: 710
Post Reply Subscribe to Thread Email Thread
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.
4th January 2014, 05:53 AM |#2  
broodplank1337's Avatar
Recognized Contributor / Recognized Developer
Flag Nijmegen
Thanks Meter: 10,153
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
4th January 2014, 07:19 AM |#3  
OP Senior Member
Thanks Meter: 710
Originally Posted by broodplank1337

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.
5th May 2014, 08:33 AM |#4  
Junior Member
Flag Dubai
Thanks Meter: 17
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 in the 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
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes