Are there any specific files that work together with the kernel (in boot.img)?
Any files in system/ folder or anything? (modules?)
Thanks.
Related
If I pull a system dump from any stock phone, can I just replace the system folder in the working folder (from a ROM that I already had) in my Kitchen with the system folder that I pulled from the stock phone, then add root permissions? Will I then have to build another boot.img? Will this even work, or am I barking up the wrong tree?
I am trying to take a keyboard that somebody made into a flashable .zip file, and implement it into a rom that I am working on. What I did was flash the .zip through cwm, then found the apk, backed it up, and then placed it in the /system/app folder on the new rom. The problem is as soon as the rom boots, I get a force close error. So I took a look at the .zip file, there are two folders meta-inf and system. inside system there is an app folder and lib folder. My question is can I just take the apk and lib file out and place them directly into /system/app and system/lib on the new rom? and if so do i need to do anything with the META-INF folder? any ideas would be GREATLY appreciated!!!
thanks
the META-INF folder may have some script that does some other manipulation of the filesystem or runs helper apps during installation. See what's in META-INF/com/google/android/update-script.
in http://forum.xda-developers.com/showthread.php?t=1058809
It says: "Download, unzip to your rom folder, restart twice.."
Is this just for that ROM or will it work for all?
What exactly do I do?
After unzipping, there are several levels of folders. which level goes where and does "rom folder" mean "Android" folder?
Download, unzip, copy "root" & "update" & "zImage" to your Android folder, reboot twice, have fun !
ROM folder = "Android" (or whatever your ROM's folder is called)
Just copy the folders and the file to the top level of your folder .
And a Kernel (technically) should work with all ROMs.
Your sd card should look like this:
G:/SDCARD/Android/root/
G:/SDCARD/Android/update/
G:/SDCARD/Android/zImage
Well it depends on your build, what build are you using?
because some builds have different path than Android, and others don't support putting new files in the folder build as far as I can remember.
so some require you to put these files manually using ADB push commands, or root explorer and apps of the like.
Not all builds support different kernels, so make sure you check if the kernel you want is compatible with the build you have.
and make a backup before you do anything or you might regret it.
manual kernel installation means:
copying the zImage to the build folder to replace the original, run android then push/copy-paste kernel files each to it's respective folder on the device. it's not that hard to be done.
Hey guys,
I just started the long journey of android rom development/cooking using an app called Android Kitchen, and I'm looking for some help from the more experienced. I extracted a custom rom folders (for personal use), and started to edit some of the extracted files (replacing and deleting), but I'm quite lost when it comes to merging flashable .zip folders (like lockscreens and mods) with the extracted rom file.Should I copy and paste whats inside the flashable zip into the rom file? Or should I use note editor to copy what's inside the mod file itself, copy the text, and add it to the original one? I really want to add these mods through this app rather than recovery mode. And can I emulate edited roms on my computer rather than risking my phone?
Thnx...
I have some original C code, which I have compiled successfully, and like to put on my phone, SM-N900P. I downloaded a copy of stock firmware and used unmkbootimg to unpack the boot.img. What do I do from here on? I have searched online and this site. I believe I have to put my files in the ramdisk directory. What I do not know is what files go in there? Can I put .img files in there? Is there a specific order in which directory to use within the ramdisk? I read someone's post instructing me to put the .ko files in ramdisk/lib/modules directory. But the ramdisk directory I have does not have a /lib directory. Should I create one? I only ask because each phone seems to have a different setup. I basically have a zImage, dt.img, and a couple of other img files.
Even if you can not help, I appreciate if you point me to relevant useful information.
Thanks
sansari123 said:
I have some original C code, which I have compiled successfully, and like to put on my phone, SM-N900P. I downloaded a copy of stock firmware and used unmkbootimg to unpack the boot.img. What do I do from here on? I have searched online and this site. I believe I have to put my files in the ramdisk directory. What I do not know is what files go in there? Can I put .img files in there? Is there a specific order in which directory to use within the ramdisk? I read someone's post instructing me to put the .ko files in ramdisk/lib/modules directory. But the ramdisk directory I have does not have a /lib directory. Should I create one? I only ask because each phone seems to have a different setup. I basically have a zImage, dt.img, and a couple of other img files.
Even if you can not help, I appreciate if you point me to relevant useful information.
Thanks
Click to expand...
Click to collapse
boot.img contain: ramdisk, zImage (kernel compressed with modules), dtb (device tree binary) and some time have name dt.img.
When you compile kernel from source, you will get zImage and dt.img (if you use dtbTool to merge all device tree rev). Use xiaolu's unmkbootimg to extract stock kernel to get ramdisk and modify it, replace zImage and dt.img then repack it to become boot.img and ready to flash it.
You should create thread in Q&A box
hiepgia said:
boot.img contain: ramdisk, zImage (kernel compressed with modules), dtb (device tree binary) and some time have name dt.img.
When you compile kernel from source, you will get zImage and dt.img (if you use dtbTool to merge all device tree rev). Use xiaolu's unmkbootimg to extract stock kernel to get ramdisk and modify it, replace zImage and dt.img then repack it to become boot.img and ready to flash it.
You should create thread in Q&A box
Click to expand...
Click to collapse
Thanks. I'll move to Q&A