Database Info

Any guides on how to create/compile custom roms?

I am a linux user...
Anyone can share the howto or if there are any guides?

+1 bumping this thread

Second that...
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html#links
He seems to have a script to compile the Kernel...
I don't know to what extent this would help us but it is a start. I dont quite know how the apps are installed on a new ROM....
It would be nice if someone can explain what is needed and what is optional in the kernel and some of the mods that other people are doing and how they integrate in the OS.
I see a lot of improvements in the new ROM's but no how-to on doing it your self. I thought that was the point of having open source OS.

I would quite like this as well =o)
Have made a bit of a start by following this:
http://source.android.com/download
Shows you how to get all the code and do a build.
I believe the next thing would be to pick the required files from the output folder of the build, dump the boot.img and replace the kernel with 32B or 32A one, add the Magic model config file (to ramdisk) and recreate the boot.img
Replace/Add any modules required like maybe wifi or bluetooth, then need to change the build.prop file and put it all in to update.zip and sign the file.
Haven't had time to test this out but seems kind of logical...maybe?

Hello!
I'm following the android.com tutorial, but I want to ask: how can I download the donut branch? There's no mention in the entire site about it... Also, the cyanomod's multitouch and so on, where does it come from? Is it made by himself or it's somewhere in the net?
Thanks

Learn how to use GIT to get the donut branch from here: http://android.git.kernel.org/

Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it

L10nH34Rt said:
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
Click to expand...
Click to collapse
Code:
git branch -a
in any local git directory

Ok, then so far I've downloaded the donut branch, and compiled too. What now?
1. how to create a ROM from the made files?
2. how to compile the kernel / how to replace the one created with the make command with the one I'm running on?
3. is there any option I can configure to fit my phone? (HTC Magic 32A)
4. how can I root my ROM?
thanks

there is this guide that i have found:
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html
'make' finished with success but i can't find how to transform it into 'update.zip' file...
anyone?

It says that in the link you have posted yourself.

[Q] I Need Help Compiling apk's to use with CM7 theme chooser

Hi,
I'm having issues compiling a new apk to use with the tmobile theme chooser and could really use some help.
I started by creating a new project in eclipse using the information from the Cyanbread theme to get the right androidManifest.xml, package format, and xml files. The problem I've run into is that, when I try to apply the theme (through CM7 emulator or my own phone), I get an error saying the package is improperly compiled and cannot be applied.
I looked into the source code for the theme chooser and found that "DIALOG_MISSING_THEME_PACKAGE_SCOPE" is what generates that text string. I found tmobile's theme wiki at hxxp://code.google.com/p/tmobile-themes/wiki/NewGlobalThemeEngineDesign (sorry, I cannot post links yet). On that page, I found this:
Resources are generated in the 0x0a package scope. This is designed to separate them in the AssetManager's ResTable. The framework currently uses 0x01 while application packages normally use 0x7f. The aapt tool was modified to support assigning arbitrary package scopes and so you must use the aapt tool found in the themes tree for building your own themes.
Click to expand...
Click to collapse
I installed the repository on my system and found the aapt at ~/prebuilt/sdk/tools/linux/aapt. I tried renaming my "standard" aapt to aapt.old in my android sdk platform-tools folder and putting the modified aapt in its place. I deleted my gen folder in eclipse and made it rebuild it using the modified aapt.
Having done all that, I still get the same error saying the package is improperly compiled. This is all pretty new, and I haven't been able to find any info here on xda or elsewhere that helps. Any help that anyone can give would be really appreciated. Thanks!

UPDATE:
A guide was just posted at forum.xda-developers.com/showthread.php?t=942203 that gave me all the other info I needed to make this happy. If your searching and found this thread, hopefully the guide can help you.

UpwardSpiral said:
UPDATE:
A guide was just posted at forum.xda-developers.com/showthread.php?t=942203 that gave me all the other info I needed to make this happy. If your searching and found this thread, hopefully the guide can help you.
Click to expand...
Click to collapse
Thanks a lot! I've been having the same problem

[Q] compiling htc one s android 4.2 on any rom really

Hello
I am having troubles getting my roms to compile. I keep getting the same error in each one. If someone could let me know what I am doing wrong that would be great. I am using linux ubuntu 12.10 and go through all the instructions on building the roms. Even on ones where it says that it is completely set up I get the same error. Here it is.
make: *** No rule to make target `/home/paulg/android/rootbox/out/target/product/ville/obj/lib/libmmjpeg.so', needed by `/home/paulg/android/rootbox/out/target/product/ville/obj/SHARED_LIBRARIES/camera.msm8960_intermediates/LINKED/camera.msm8960.so'. Stop.
I guess the solution would be to take the file from another rom and put it into the directory but there has to be another way to do this besides doing that.
I also have another error where it says the libril directory from hardware/lib/libril is conflictin with the direcory msm-8960-common/libril ( not excatly like that but close enough). To fix this I just erase the hardware/lib/libril directory and leave the msm8960-common intact and let it compile from there. I don't know if this is right or not. If someone knows this one let me know.
Thank you.
Paul

atrus5 said:
Hello
I am having troubles getting my roms to compile. I keep getting the same error in each one. If someone could let me know what I am doing wrong that would be great. I am using linux ubuntu 12.10 and go through all the instructions on building the roms. Even on ones where it says that it is completely set up I get the same error. Here it is.
make: *** No rule to make target `/home/paulg/android/rootbox/out/target/product/ville/obj/lib/libmmjpeg.so', needed by `/home/paulg/android/rootbox/out/target/product/ville/obj/SHARED_LIBRARIES/camera.msm8960_intermediates/LINKED/camera.msm8960.so'. Stop.
I guess the solution would be to take the file from another rom and put it into the directory but there has to be another way to do this besides doing that.
I also have another error where it says the libril directory from hardware/lib/libril is conflictin with the direcory msm-8960-common/libril ( not excatly like that but close enough). To fix this I just erase the hardware/lib/libril directory and leave the msm8960-common intact and let it compile from there. I don't know if this is right or not. If someone knows this one let me know.
Thank you.
Paul
Click to expand...
Click to collapse
Never mind I figured it out and compiled rootbox for Htc One S

atrus5 said:
Never mind I figured it out and compiled rootbox for Htc One S
Click to expand...
Click to collapse
What was your solution for the libmmjpeg.so error? I'm having the same problem for another device
Thanks,
Mike

mikshepard said:
What was your solution for the libmmjpeg.so error? I'm having the same problem for another device
Thanks,
Mike
Click to expand...
Click to collapse
You can get this file and all the other proprietary files by entering extract-files.sh from your device/devic_company/device_name directory from whatever rom you are trying to build. If you have done this then there should be a file that will automatically copy it or else you will have to copy it to the out/target/product/device_name/system/lib directory. You might want to also check that you have the correct manifest files in local_manifest for whatever device you are trying to build. usually there is a cm.dependencies file in the device/device_company/device_name directory that will tell you exactly what manifest to use. If you have any other questions let me know. I hope this helps.

atrus5 said:
You can get this file and all the other proprietary files by entering extract-files.sh from your device/devic_company/device_name directory from whatever rom you are trying to build. If you have done this then there should be a file that will automatically copy it or else you will have to copy it to the out/target/product/device_name/system/lib directory. You might want to also check that you have the correct manifest files in local_manifest for whatever device you are trying to build. usually there is a cm.dependencies file in the device/device_company/device_name directory that will tell you exactly what manifest to use. If you have any other questions let me know. I hope this helps.
Click to expand...
Click to collapse
oh wow, hahaha, I was in such a hurry, I completely missed that. I never used the extract-files.sh as all the proprietary files for my htc devices used to be hosted on github but recently got pulled due to a legal problem with the camera drivers. I had the files backed up on my old computer but forgot to copy them over to the new one. Wow, amateur mistake but one that would have taken me a while to catch. Many thanks man!!
-Mike

mikshepard said:
oh wow, hahaha, I was in such a hurry, I completely missed that. I never used the extract-files.sh as all the proprietary files for my htc devices used to be hosted on github but recently got pulled due to a legal problem with the camera drivers. I had the files backed up on my old computer but forgot to copy them over to the new one. Wow, amateur mistake but one that would have taken me a while to catch. Many thanks man!!
-Mike
Click to expand...
Click to collapse
No problem.
I had the same problem with ville. Got the files pulled so made up my own repo with all the files that are needed.

How do I go on getting propietary blobs?

Hey!
So I wanted to create a device tree for my device. An LG.
I know how to get those BoardConfig.mk Android.mk and those original mk files, but when I look at other device trees, they have a whole lot more. They have vendorsetup, extract-files.sh and some folder like Bluetooth, wifi, etc...
Do I include those is my tree? If so, how do I get them? I don't have a stock zip, LG doesn't provide one for some reason, just the source code to their kernel and firmware. Could I get it from there?
Thanks for reading! Hope to hear back soon!

where to obtain propertiary blobs for my OnePlus 8?

hello! i have been trying to find my properitary blobs for my phone for a long time now. i extracted a vendor.img from an OTA update but i dont know if this is all i need in the form of binary blobs.
i dont know either about how to find this out. any help would be greatly appreciated

kieran_buffet said:
hello! i have been trying to find my properitary blobs for my phone for a long time now. i extracted a vendor.img from an OTA update but i dont know if this is all i need in the form of binary blobs.
i dont know either about how to find this out. any help would be greatly appreciated
Click to expand...
Click to collapse
I personally don't know but you can ask in the dedicated OP8 forum: https://forum.xda-developers.com/oneplus-8

kieran_buffet said:
hello! i have been trying to find my properitary blobs for my phone for a long time now. i extracted a vendor.img from an OTA update but i dont know if this is all i need in the form of binary blobs.
i dont know either about how to find this out. any help would be greatly appreciated
Click to expand...
Click to collapse
If you're speaking of the vendor specific device drivers then those all are contained in vendor.img you mentioned.
How to extract them is shown in this video:
https://www.youtube.com/watch?v=ivyrq_aDf58&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp

jwoegerbauer said:
If you're speaking of the vendor specific device drivers then those all are contained in vendor.img you mentioned.
How to extract them is shown in this video:
https://www.youtube.com/watch?v=ivyrq_aDf58&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp
Click to expand...
Click to collapse
i checked TheMuppets github page and looked at the blobs for the OnePlus 7/7T and i saw similarities between what i had extracted from the vendor.img using 7zip, but there seems to be a lot more data in the vendor img i extracted (1GB) than what is on the github page. i feel like i have no choice but to go ahead with what i have got, and hope it works..
i checked out the video you linked in full and the way he does it is with vendor file extract shell scripts through adb. he admits that because its not for the same specific phone (or something similar) not all files will be included but that it'll be close. i want to ensure the phone is going to work completely so i have taken that video and what im going to do is match my extracted vendor.img files to the content on the phone, and find a way to adb pull everything to see if i can find exact similarity. then hopefully i can move forward with inputting the kernal and getting a beautiful build. if i cannot adb pull everything then i will tediously go through the directories.
i withhold giving advice to other people until my own success can be measured, but i dont seem like the only individual to have issues and i will report instructions and the level of success if and when reached. thank you for your help!

jwoegerbauer said:
If you're speaking of the vendor specific device drivers then those all are contained in vendor.img you mentioned.
How to extract them is shown in this video:
https://www.youtube.com/watch?v=ivyrq_aDf58&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp
Click to expand...
Click to collapse
okay so i obtained a root adb instance, and i copied the vendor folder on there and everything else for the sake of learning that was pullable. i came across 2 vendor folders, /vendor, and /system/vendor. They both were the same size, but much, much bigger than the vendor.img i pulled from a system update. i want to double check, should i use the vendor files that were on my phone versus the OTA update vendor.img extraction?

kieran_buffet said:
okay so i obtained a root adb instance, and i copied the vendor folder on there and everything else for the sake of learning that was pullable. i came across 2 vendor folders, /vendor, and /system/vendor. They both were the same size, but much, much bigger than the vendor.img i pulled from a system update. i want to double check, should i use the vendor files that were on my phone versus the OTA update vendor.img extraction?
Click to expand...
Click to collapse
/vendor is vendor.img and the size discrepancy is normal. The IMG can be quite a bit larger than the actual data itself. I would use the ones that you pull from the device. Make sure you look at the other GitHub mentioned because there may be files outside of /vendor that are required for the system to work.

Scott said:
/vendor is vendor.img and the size discrepancy is normal. The IMG can be quite a bit larger than the actual data itself. I would use the ones that you pull from the device. Make sure you look at the other GitHub mentioned because there may be files outside of /vendor that are required for the system to work.
Click to expand...
Click to collapse
hello Scott! thank you for taking your time to reply to me in this thread. i will go ahead with the /vendor folder found on the phone itself. i looked at the github link again and went through the repositories and "vendor" and "opensource" are repeated regularly, yet i dont know how i am to know if i need those files. any ideas?

kieran_buffet said:
hello Scott! thank you for taking your time to reply to me in this thread. i will go ahead with the /vendor folder found on the phone itself. i looked at the github link again and went through the repositories and "vendor" and "opensource" are repeated regularly, yet i dont know how i am to know if i need those files. any ideas?
Click to expand...
Click to collapse
I would look for the script extract_files.sh. Is that what you are using or are you trying to pull them one by one?

Scott said:
I would look for the script extract_files.sh. Is that what you are using or are you trying to pull them one by one?
Click to expand...
Click to collapse
no, i do not know where this is. i used a rooted adb instance and pulled everything that didnt give me some kind of error