Database Info

[Q] Procedure to the build the code for crespo aka Nexus S

Hi,
I have seen a lot of posts and threads, but was unable to find the procedure to build the source code for the device.
I am a junior android developer and I would like to learn from the experts here.
I have got the latest gingerbread source code from git repo and I would like to make my own changes to the code, add new icons, build it and then flash onto my Nexus S.
Please let me know the detailed procedure.

The procedure is documented on the google homepage.
You can start here:
source.android.com/source/download.html

Thanks for the reply.
I tried all this and had built the code successfully too. But when am flashing with -w flashall option, its saying radio must be below I9020XXKB3 version.
I tried to flash individually boot.img and system.img, but lost root and also google apps are not present ( like maps, navigation.. ).

superatmos said:
I tried all this and had built the code successfully too. But when am flashing with -w flashall option, its saying radio must be below I9020XXKB3 version.
Click to expand...
Click to collapse
Can't really help you here. AFAIK KB3 is the latest radio available.
I don't know, why the latest android version shouldn't support it.
superatmos said:
I tried to flash individually boot.img and system.img, but lost root and also google apps are not present ( like maps, navigation.. ).
Click to expand...
Click to collapse
boot.img is the kernel and initramfs.
system.img is the root partition.
The radio is another partition again, AFAIK (again).
Google Apps are not present, because they are not part of the Android open source project, but are closed source.
They are licensed by Google to device manufacturers under some conditions.
One condition is to conform to the android compatibility document (hxxp://source.android.com/compatibility/index.html).
You can find the google apps around the internet somewhere though. I remember seeing them for download on the cyanogenmod homepage.
EDIT: Root is gone because it is a modification of the system (in system.img) in the first place. Unless you integrate it into the build process it won't be there.

Blob utility for AOSP-based ROMs

https://github.com/JackpotClavin/Android-Blob-Utility
The purpose of this program is to help AOSP-based ROM developers quickly and easily find out which proprietary blobs need to be copied into the ROM's build, or built using source. How the program works is you do a /system dump into a folder on a Linux computer. Then you make the program using the 'make' command; then you can run it.
First off, the program will ask you what the sdk version of the /system dump you pulled happens to be. For example, if your /system dump is Android 4.3, and intend port a 4.3-based ROM, then enter 18 and press enter.
When it prompts you for location of the /system dump you pulled, if the location of the build.prop of the /system dump is under:
Code:
/home/user/backup/dump/system/build.prop
then just use:
Code:
/home/user/backup/dump/system
The program will now ask you for your device's manufacturer's name, and the device's name. For my Verizon LG G2, I entered "lge" and "vs980" respectively.
The utility then will ask you how many files you wish to run through the program. In the case of my LG G2, the KitKat build requires two main proprietary camera-related libraries to run (/system/bin/mm-qcamera-daemon and
/system/lib/hw/camera.msm8974.so).
So I typed in 2 and pressed enter (because I'm running two proprietary files through the program)
Then simply typed in:
Code:
/home/user/backup/dump/system/bin/mm-qcamera-daemon
and pressed enter and it printed out *every* file needed to get /system/bin/mm-qcamera-daemon running (the file might be proprietary, or it can be built from source).
Then it asked for the final proprietary file, so I simply typed in:
Code:
/home/user/backup/dump/system/lib/hw/camera.msm8974.so
and pressed enter and it printed out *every* file needed to get /system/lib/hw/camera.msm8974.so running (the file might be proprietary, or it can be built from source).
An example usage of this program can be found here: https://raw.githubusercontent.com/JackpotClavin/Android-Blob-Utility/master/Example_Usage.txt
That's 106 proprietary blobs done in a flash!
The beauty of this program is that it's recursive, so if proprietary file 'A' needs proprietary file 'B' to run, but proprietary file 'B' needs proprietary file 'C' to run, which in turn needs 'D' to run, then simply entering proprietary file A to run will print out all A, B, C, and D nicely formatted so that you can simply copy the output and place it in a file under vendor/manufacturer/codename/codename-vendor-blobs.mk file in your AOSP build source tree's root.
Another great thing about this program is that it doesn't just catch the libraries needed to satisfy the linker, but rather, it will also print out those libraries that are called within the actual code of the library itself, like:
Code:
dlopen("libfoo.so", RTLD_NOW);
libfoo.so is not marked as a shared library, so the linker won't complain that libfoo.so is missing, and there might be no sign that libfoo.so missing and needed, but when it's time for the daemon or library to run, it won't show any sign that something is wrong, until you see that it doesn't work. This program will catch and display that libfoo.so is needed.
So basically:
1. Extract /system dump image
2. Tell program the SDK version of your /system dump
3. Tell program the location of your /system dump
4. Tell the program your device's manufacturer's name
5. Tell the program your device's codename
6. Tell program how many files you wish to run through the utility
7. Tell program the location of the file(s) you wish to run through the program.
8. Copy the output of the utility to a text file under vendor/manufacturer/codename/codename-vendor-blobs.mk

reserve

Hi,
I'm a noob and don't worry about my silly question.
I'm trying to build my first cm-rom and tested your tool. Thanks a lot for your work, it worked for me.
I'm a little bit curios about your point 5. Where can I find all the files I need for my own source-tree/device?
It would be nice if you can give me a hint.
Thanks a lot and greetings from germany

Greetings from the US
Do you mean the device folder the ROM? You can look at similar devices to your device and see what they did and make the changes to build Android.
This is the device folder for the Nexus 5 -> https://android.googlesource.com/device/lge/hammerhead

This tool is under-recognized. I think it's a really great way to find which blobs are dependencies!

Codename13 said:
This tool is under-recognized. I think it's a really great way to find which blobs are dependencies!
Click to expand...
Click to collapse
Thanks! Are you developing a ROM? Let me know if it helps!
Sent from my LG-VS980 using XDA Free mobile app

Could this be updated to Lolipop?

2GigayteSD said:
Could this be updated to Lolipop?
Click to expand...
Click to collapse
What do you mean? I added support for SDK version 20 if that's what you're asking.
Sent from my LG-VS980 using XDA Free mobile app

Does that mean I can port AOSP to any device just by getting all the necessary blobs? I'm not sure but I'm trying to port Lollipop to my device but I don't really have a clue how to do it/what's needed to do it. Will this be useful for me? Thanks.

cikoleko said:
Does that mean I can port AOSP to any device just by getting all the necessary blobs? I'm not sure but I'm trying to port Lollipop to my device but I don't really have a clue how to do it/what's needed to do it. Will this be useful for me? Thanks.
Click to expand...
Click to collapse
It helps with making ROMs for devices that don't have support (either the model is brand new or the device never gained AOSP ROM support for whatever reason)
Basically, in the early stages of porting ROMs, certain things won't work (graphics, camera, radio) and this is mostly due to not having the correct proprietary files needed for the OS to interact with the hardware. The proprietary files have dependencies (they rely on other libraries, which in turn may rely on other libraries, and so on and so forth until all proprietary libraries are satisfied).
In the case of my LG G2, there were a total of 92 proprietary files that needed to be pushed to the device in order to get just camera working. Instead of pushing one library at a time and getting a logcat or strace dump of what the daemons are calling or depend on, I wrote this program to recursively search for all proprietary libraries needed to satisfy a proprietary library (or in the case of the camera for my G2, there were two proprietary libraries needed that required those said 90 other proprietary blobs).
So rather than pushing libraries, (then gathering logs and stracing) and hoping that the one you just pushed is the one that will get your camera, radio, etc to work, you run your known proprietary daemons or libraries through this program and it will print out the necessary libraries to get it working, in a fraction of a second

Can you go through the actual "porting" process because from what I understand you have done it? If I'm correct to port a ROM you need to have working ROM from other device? If yes, does that device have to be same manufacturer? Lets say I do have working AOSPA kitkat for my device so I need to get AOSPA lollipop and exchange the certain files and then I'll able to run it? Once again if it's like that then I use your tool and get necessary blobs? I don't have a clue about this stuff, I only build ROMs but now time has come that my device is unsupported so can you give me some tips, thanks.

This is interesting. Going to have to try this out tomorrow.

cikoleko said:
Can you go through the actual "porting" process because from what I understand you have done it? If I'm correct to port a ROM you need to have working ROM from other device? If yes, does that device have to be same manufacturer? Lets say I do have working AOSPA kitkat for my device so I need to get AOSPA lollipop and exchange the certain files and then I'll able to run it? Once again if it's like that then I use your tool and get necessary blobs? I don't have a clue about this stuff, I only build ROMs but now time has come that my device is unsupported so can you give me some tips, thanks.
Click to expand...
Click to collapse
If you don't have a clue then dont do it, please! Work your way up. First step in this hypothetical is to wait for aospa 5.0

Thanks a lot for this tool
just one thing.. i cant get the blobs for my wireless (wl12xx)
Rest all done

andynoob said:
Thanks a lot for this tool
just one thing.. i cant get the blobs for my wireless (wl12xx)
Rest all done
Click to expand...
Click to collapse
Is it possible that each wl12xx library only relies on AOSP libraries (has no dependencies?)
See if they can be built from source!
Sent from my LG-VS980 using XDA Free mobile app

JackpotClavin said:
Is it possible that each wl12xx library only relies on AOSP libraries (has no dependencies?)
See if they can be built from source!
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Manufacturer hasnt provided the source code(Kernel) . Anyways thanks a lot for this tool :good: :good:

how to use it?

by reading the detailed instructions?
Sent from my LG-VS980 using XDA Free mobile app

JackpotClavin said:
by reading the detailed instructions?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
should we adb pull /system first?
*edit
I did it! but where is the directory out?

J,
You are a life saver ! Subscribed. Will add link of thread to my signature. Will dance happily for some hours! :good:
Will seek therapy. :silly:
m

ROM COPPERHEAD OS - info

No one have tried the new ROM Copperhead OS ?
Can i try to install it as secondary rom in MultiRom ?
I'm on Cyanogen CAF 12.1 now...
thank you all

chickygamon said:
No one have tried the new ROM Copperhead OS ?
Can i try to install it as secondary rom in MultiRom ?
I'm on Cyanogen CAF 12.1 now...
thank you all
Click to expand...
Click to collapse
Hi! I've installed it in multirom with a stock 5.0.1 as primary and it works, just tried it for few minutes.
just be sure to have the latest bootolader (HHZ12h) or installation will fail.

Flashing a bootloader
Hi,
I have a Nexus 5 and I use Multirom with it. My default ROM is Lollipop 5.1.1 and a secondary ROM, which I mostly use, is Marshmallow 6.0 (xTraSmooth). I want to install CopperheadOS, but it says when installing, that I must have HHZ12h bootloader in order to install (as stated in a previous post). My current bootloader is HHZ11k. If I install HHZ12h bootloader by flashing a zip file which includes LMY48B_Radio+Bootloader-HHZ12h will it cause anything that prevents Lollipop or Marshmallow to work properly?

ithippi said:
Hi,
I have a Nexus 5 and I use Multirom with it. My default ROM is Lollipop 5.1.1 and a secondary ROM, which I mostly use, is Marshmallow 6.0 (xTraSmooth). I want to install CopperheadOS, but it says when installing, that I must have HHZ12h bootloader in order to install (as stated in a previous post). My current bootloader is HHZ11k. If I install HHZ12h bootloader by flashing a zip file which includes LMY48B_Radio+Bootloader-HHZ12h will it cause anything that prevents Lollipop or Marshmallow to work properly?
Click to expand...
Click to collapse
You don't need to downgrade the bootloader, just modify the updater script of the rom ( deleting the string containing the bootloader version or replacing with your current version), then it will install just fine.

Can anybody provide link on COPPERHEAD OS ? CHEERS!

Pretoriano80 said:
You don't need to downgrade the bootloader, just modify the updater script of the rom ( deleting the string containing the bootloader version or replacing with your current version), then it will install just fine.
Click to expand...
Click to collapse
Thanks! I haven't tried that yet, but I will. First I thought I can just replace HHZ12h with HHZ11k using text editor, but then I noticed there are guides which suggest that it isn't quite that easy. I might be wrong about that, will see when I have enough time to read up on the subject.
Sent from my Nexus 5 using XDA Free mobile app

ithippi said:
Thanks! I haven't tried that yet, but I will. First I thought I can just replace HHZ12h with HHZ11k using text editor, but then I noticed there are guides which suggest that it isn't quite that easy. I might be wrong about that, will see when I have enough time to read up on the subject.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It's easy, just extract the rom, go to Meta-Inf/com/google/android and modify the "updater-script". That's all, rebuild the zip and flash in recovery.
Edit: you can do it without using a PC, by using a file manager on your device.

Ross Korolov said:
Can anybody provide link on COPPERHEAD OS ? CHEERS!
Click to expand...
Click to collapse
here it is
https://copperhead.co/android/

....

Is this rom any good?

bonedriven said:
Is this rom any good?
Click to expand...
Click to collapse
Just installed it on a Nexus 5x and it works flawless. It has most of the standard stuff but is different from the rest in that it is supposed to be security oriented. That means no default root (but rooting should be possible).
I didn't try to add Google stuff yet and probably won't even try to add that spyware but it does have the F-Droid app store.
There are some extra options to secure the memory if required, and the documentation is (so far) very good (for example the install guide and the technical overview).

Currently running it on my Nexus 5x and N5. works great. Anything you are missing you can find on F-Droid. I find the lack of data usage to be delightful; when facebook or ebaum videos auto load on other software, they are stopped on copperhead. very happy with the security.
The only thing i can not make work is voice to text, and I have a ticket in with copperhead. who cares, I have fast thumbs.
Nexus + Copperhead = Happy Gopher!

mg.degroot said:
Just installed it on a Nexus 5x and it works flawless. It has most of the standard stuff but is different from the rest in that it is supposed to be security oriented. That means no default root (but rooting should be possible).
I didn't try to add Google stuff yet and probably won't even try to add that spyware but it does have the F-Droid app store.
There are some extra options to secure the memory if required, and the documentation is (so far) very good (for example the install guide and the technical overview).
Click to expand...
Click to collapse
happy_gopher said:
Currently running it on my Nexus 5x and N5. works great. Anything you are missing you can find on F-Droid. I find the lack of data usage to be delightful; when facebook or ebaum videos auto load on other software, they are stopped on copperhead. very happy with the security.
The only thing i can not make work is voice to text, and I have a ticket in with copperhead. who cares, I have fast thumbs.
Nexus + Copperhead = Happy Gopher!
Click to expand...
Click to collapse
Thanks for the feedback. I guess manual apk installation is also possible?

I'm thinking about picking up a Nexus 5 as a backup device, and CopperheadOS seems like something fun to play with, instead of just installing CM13. Can I install TWRP as recovery on devices like the Nexus 5 that don't check for locked bootloaders? Can I run it as basically another ROM –*unlocked developer options, root, TWRP, etc.? I realize the OS exists for enhanced security, but I'd like to make a few tradeoffs.

Unfortunately, you can not run TWRP with copperhead, it wants full control of the phone for security reasons. Its not meant to be a developer OS with access to all the bits, so you kind of need to want a OS in a box that you can deal with.
But I have to say, despite its shortcomings of not having google services, it works pretty much flawless on my 5 and 5x. i miss google maps app, but it works 100% via chromium browser as a favorite, and I have only found 2 apps I can not import via apkmirror, one being Waze, the other is my local public transportation app. other than that, i feel like I'm safe from prying eyes.
Hg

happy_gopher said:
Unfortunately, you can not run TWRP with copperhead, it wants full control of the phone for security reasons. Its not meant to be a developer OS with access to all the bits, so you kind of need to want a OS in a box that you can deal with.
But I have to say, despite its shortcomings of not having google services, it works pretty much flawless on my 5 and 5x. i miss google maps app, but it works 100% via chromium browser as a favorite, and I have only found 2 apps I can not import via apkmirror, one being Waze, the other is my local public transportation app. other than that, i feel like I'm safe from prying eyes.
Hg
Click to expand...
Click to collapse
Thanks for your response. I'm a fan of CyanogenMod, and I'm not unhappy their security or features, but I wanted to play around with CopperheadOS. I understand the tradeoff between security and convenience, but I'm not willing to sacrifice TWRP in the mix. Oh, well – if I ever have need of an OS solely for its security track record, I know where to go.

It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.

NewDayRising said:
Thanks for your response. I'm a fan of CyanogenMod, and I'm not unhappy their security or features, but I wanted to play around with CopperheadOS. I understand the tradeoff between security and convenience, but I'm not willing to sacrifice TWRP in the mix. Oh, well – if I ever have need of an OS solely for its security track record, I know where to go.
Click to expand...
Click to collapse
Switch debugging OFF and don't lock bootloader after CopperheadOS install and u will be able to boot TWRP via
fastboot boot recovery.img [TWRP]
I'm currently experimenting with root privileges on CopperheadOS on Nexus 5X. Still haven’t tried xposed framework.
Security features r quite good, especially different lock code && encryption password and memory protection, but, there is a lack of fine privacy control (Privacy Guard) as in CyanogenMod and firewall, hence the need for root.

CopperheadOS on Nexus5
dnaod said:
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
Click to expand...
Click to collapse
I've been using CopperheadOS for a few weeks now on the Nexus5. Received the latests OTA a few days ago and applied without issue.
Installed it via TWRP. Have rooted the device with SuperSU, though have to re-root after re-flashing recovery after each OTA.
It's been working great.
Unfortunately I don't have the img any more
The one I flashed was https://builds.copperhead.co/builds/hammerhead-factory-2016.08.09.06.24.33.tar.xz

download link
dnaod said:
It doesn't look to me like Copperhead is supporting the Nexus 5 anymore. Can somebody confirm or is there a link I'm missing somewhere to the ROM?
EDIT: Yep, I knew it was deprecated for a while now but they've even removed the deprecated ROM from the site now. I'd appreciate it if anybody has the last ROM if they could pass it my way.
Click to expand...
Click to collapse
https:// builds.copperhead.co /builds/hammerhead-factory-2016.09.07.19.27.04.tar.xz
Remove spaces. I'm a new member and can't post links.

Is sources from the vendor required?

If the vendor (in this case Vodafone) don't provide sources, does it mean I'm unable to create a ROM for it?
Put it another way, is it possible to create a ROM using only a running device?

The Original Leppa said:
If the vendor (in this case Vodafone) don't provide sources, does it mean I'm unable to create a ROM for it?
Put it another way, is it possible to create a ROM using only a running device?
Click to expand...
Click to collapse
Yes, if you want to build a "true" custom ROM you will need the stock source code for your device.
If you can root, you can use adb or Terminal Emulator to do a "ROM dump", or dump just a copy of your system.img, then modify that system.img and then use adb to push the modified system.img to your device. It will be considered a modified stock ROM, it won't be a "custom" ROM but you can modify it quite heavily with things like Xposed, Gravity Box, and a few other good mods and themes.
Or you can get a copy of your stock firmware(not the same as source code), then find other devices with the exact same hardware that have a better version of Android than yours, then use your stock firmware to port the better version to work on your device.
Building a true custom ROM is "possible" without stock source code but it would require VERY extensive programming and developer knowledge to do it because you'd have to do every bit of it from scratch with no resources to work with.
Sent from my SM-S903VL using Tapatalk

So, I'm screwed, in terms of porting?

The Original Leppa said:
So, I'm screwed, in terms of porting?
Click to expand...
Click to collapse
It would help if you had stock firmware for your model then you can find another device with the same hardware architecture(chipset), if they are similar enough you can port it.
It's possible to port between devices that aren't exactly the same chipset but that also requires extensive developer knowledge.
If you aren't experienced then you're pretty much out of luck.
If you want to customize android devices then you need to get less obscure devices. Next time, research the device first to see if there is a known rooting method for it and whether there is custom development available for it before you get it. Or if you get a device that just came out, get a device that you are certain that developers will support, typically a flagship/popular device.
The cheap low-mid range devices usually don't get support from developers and the ones that do get support are not supported by real develoers, they are supported by members that took it on themselves to learn how to build android just so they can update their device but their work usually isn't exactly right due to their lack of experience.
Sent from my SM-S903VL using Tapatalk

Question AOSP rom for S22U Snapdragon ?

Hello
I will perhaps keep my S22U instead of upgrading to s23u , I will then most probably root it as my warranty will soon come to an end and I won't care about knox flag. But is there any AOSP based custom rom for the S22U snapdragon ? If yes can you use Expert Raw app?

The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.

V0latyle said:
The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.
Click to expand...
Click to collapse
Thanks
Though it looks like an update thread for Pixel phones no?

vegetaleb said:
Thanks
Though it looks like an update thread for Pixel phones no?
Click to expand...
Click to collapse
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com

V0latyle said:
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?

vegetaleb said:
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?
Click to expand...
Click to collapse
I don't think so - I'm pretty sure features like that are not core Android mechanics, so they wouldn't be included in AOSP. I don't know for sure. Keep in mind that the whole idea behind a GSI - Generic System Image - is that it can run on pretty much any device. Google has been using this model since the Pixel 3 - instead of having different system builds for each device, they use a generic common system image, while device specific features are contained in other partitions such as /product. This way, when they provide the monthly update for Pixels, they don't have to completely rebuild the firmware; they can just use the AOSP GSI for the "core", and any device specific changes are separate in /system_ext and /product. It's a modular design that really helps streamline the update process; it also means that devices that no longer receive updates can still potentially run the latest AOSP core.
I imagine you could extract the product.img from the Pixel 7 factory zip and flash it to /product on your device, but because it's device specific, it most likely wouldn't work properly.