I've been studying how to build my own LineageOS or AospExtended, but one thing always bothers me: every guide that explains the need of extracting blob files tell to extract them from an official nightly zip or from a repository called "TheMuppets" (https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-14.1/athene).
The question is: where do these blobs came from in the first place? Where were they compiled (like libxml.so)? The Nougat stock rom doesn't have all the blobs presented in proprietary-files.txt, so I can't just export them from a stock image extracted using TWRP, since a bunch of .so are still missing. How can I compile all .so not available at the stock rom or where are the official channels for obtaining the blobs?
Related
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
So i pulled stock system folder and deodexed, zipaligned and signed.
Wanted to try flash it by twrp. So i copied one of custom roms meta inf folder but i get sysmapfile error.
Created certificates with signapk but there is no update-binary and update-script file. So i searched and learnt sth about update-script but what is exactly update-binary do? How can i edit for my rom or create one? can i use one of them with all devices rom?
Btw editing update-script didnt solve my sysmapfile error. Can someone guide me about meta-inf folder? All other articles just tells using another roms meta inf but it simply didnt work for me.
The update-binary file is different from one ROM to the next. For example, a CyanogenMod binary will be different from one in a custom ROM based off stock. In general, look at http://wiki.cyanogenmod.org/w/Doc:_About_Edify for an explanation of what the binary is. You will need to pull a binary from a custom ROM based off stock, preferably from the same version of Android.
I am using Android Image Kitchen from this thread, and I don't understand what I'm doing.
Basically, what I'm trying to accomplish, is editing this ROM so that it is compatible with my sm-G386W (ROM is for the sm-G386T). The recents fix doesn't work on my phone (security settings still crashes), so I got the keymaster files from my old ROM on my phone (kitkat), and pasted them after I flashed the new ROM, all using FX File Explorer. Fixed the recents issue perfectly.
So now I want to edit the CM 12.1 ROM to put the keymaster files right on there, and that is where I get lost.
I am able to successfully unpack the boot.img that I got from the flashable zip for the CM 12.1 ROM, but when I go to \ramdisk\system, the system folder is blank. Where in the world can I find system\vendor\firmware\keymaster and the keymaster files so I can replace them?
Like I said, I'm new, so I'm sure I'm missing something obvious. If someone can point me in the right direction on how to properly edit a custom ROM, that would be great!
Problem Solved. I use MTK THAI Development Tools unpacker/packer. Can be downloaded directly here.
I see a few roms asking to update to the latest vendor and I have no idea where to find a file I can install through TWRP and no idea what to look for. Can someone help me out a bit? I've been looking on Google and fell on a few pages where I get a bunch of GitHub packages with no install instructions with a list of a bunch of sh, mk and other files.
I am trying to build a ROM, however I am missing a couple files, I need a vendor tree of hi6250-8-common so I can start building the ROM, does anyone have a copy of this folder? or even a GitHub link? I am still fairly new to this and I don't mind trying other options to fix my missing file issue.
I've found just a hi6250 vendor, device and kernel, I am no longer looking for the trees