For those who want Android 4.0.3 compiled from source. Also has separate Gapps, Face Unlock, and SU root.
Not in development because I didn't develop this. I just compiled from Google's source. This is for people who want plain old Android 4.0.3 the way Google intended from source (not much apps, very plain).
You will need CWM already installed. If you do not have CWM, you can use fastboot to boot to it without installing just to install the ROM. The zip files must be copied to /sdcard. You can use ADB to push to /sdcard.
http://www.guytechie.com/articles/2012/1/13/truly-stock-android-403-from-source-code.html
I compiled for both the Nexus S and Galaxy Nexus (GSM version). GNex = Maguro, NexS = Crespo
I want to thank Shenye for writing the guide on how to compile ICS from source. I learned a lot, and I plan on learning more.
Note: I did not include root, but you can obtain root from Wug. http://www.galaxynexusforum.com/for...h-galaxy-nexus-root-toolkit-gsm-versions.html
Update: This is frustrating! The SU.zip just isn't working. I'm not sure why. I'm using the one from Wug. Still no dice. Not sure why that is. Oh well. At the very least, it's a straight AOSP Android 4.0.3 ROM.
Thanks, I was looking for an easy download link earlier.
I found a guide for compiling AOSP for 4.0.3, but I'd like to do it for 4.0.4. I'm more interested in learning about roms and stuff, but I don't want to use the rom kitchen. I have a working dev environment (ubuntu 10.04, followed the setup procedures on the AOSP site).
I have my repo sync'd and ready to build, but I read that I need proprietary libraries for my phone. Unfortunately I don't see anything about the cdma G nexus on this page (only maguro):
https://developers.google.com/android/nexus/drivers
So.. where do I find these? I've been doing a lot of searching but unfortunately I can't find any information on this. Thanks in advance.
The bottom of the page you linked has a few binaries for the CDMA Nexus. Other than those, use the extract-files.sh script in the device folder (device/samsung/toro) and if you run that with your phone attached and adb enabled/setup, it will pull the rest of the files that you need off of the phone.
Thanks! The files in that guide were from 4.0.3, would these be different from 4.0.4?
I have been in love with all things Android for years but there is a certain level of proficiency that I don't think I'll ever reach. I'm reaching out to anyone who can provide me with some assistance in this issue. I have a Nexus (my wife's) that constantly crashes the Talk and Camera apps. I've tried dozens of solutions posted online but I think the only one that actually addresses my issue is provided in the link below. Unfortunately, when it comes to compiling Android source code I get in over my head.
Could someone please give me instructions on how to implement this fix? I would like to run AOKP JB Milestone 1. It appears I need to swap out the binaries before compiling and flashing this ROM but that's about as much as I can tell.
Please help!
Link describing the fix -------------> http://anders.com/cms/435
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
See, this is where I'm confused. I'm not compiling the ROMs or any of the gapps myself. I'm flashing a copy of AOKP that I used on other nexus devices and had zero issues. For some reason this phone won't work quite right. I've wiped, clear data, fixed permissions, blah blah blah.
From hefty googling I have found a decent number of other threads with my exact problem but none of the threads actually have a solution.
mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
ANY AOSP rom should have these binary files.
http://forum.xda-developers.com/showthread.php?t=1386615
So in other words, it doesn't sound like this will solve my problems then, huh?
cartisdm said:
So in other words, it doesn't sound like this will solve my problems then, huh?
Click to expand...
Click to collapse
Check logcat/dmesg right after you reproduce the issue. (ref: http://forum.xda-developers.com/showthread.php?t=1812959)
We need more insight/details as to why it is failing.
Your wife's phone currently runs:
carrier: ______
rom: _____
rom build number: _____
kernel: _____
bootloader: ______
radio: ______
Have you tried starting fresh, flashing nexus factory image through fastboot, as per (ref: http://forum.xda-developers.com/showthread.php?t=1626895) ?
Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.
The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung
Hi everyone,
recently I have built and flashed on my sgh-t999 (galaxy S3 US tmobile version) CM11 Nightly. For my pro0ject however I need to modify two libraries of the Radio Interface Layer (RIL), libril.so and libreference-ril.so. I tried to modify the ones in the forlder /hardware/ril/ and build everything again with no results. Any change that I made to those files (such as ril.cpp in the folder libril) would not affect the functionality of the phone.
Finally yesterday I understood that when I build those libraries for the target cm-d2tmo-eng, those files that I have modified are not considered at all! When the libraries are built indeed, the system automatically takes the libril.so and libreference.so present in the vendor folder!
The problem is that those libraries in the vendor folder and already compiled and I cannot modify them. The question is:
Is there any way that I compile those libraries from the source code that I have modified?
Thanks,
brok85
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
Click to expand...
Click to collapse
Well, as fisrt I just wanted to insert some log to be able to follow the code execution from the logcat or do something similar.
Perseus71 said:
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
Click to expand...
Click to collapse
Sorry but I am kind of new on this things. I have already downloaded the source code from the device tree and made my modifications in the files ril.cpp contained in [path-to-android-source]/hardware/ril/libril/ril.cpp. What I did was commenting the whole code within the function RIL_onUnsolicitedResponse() and listenCallback() such that in theory, the phone is not able to display incoming calls for example. However after flashing the re-built android I am still able to receve calls. How can I "check in the changes if they boot ok on my device"?
Perseus71 said:
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
I tried to remove the libril.so in the vendor folder and compile again using
# . build/envsetup.sh
# lunch (and select d2tmo)
# mmm [path-to-android-source]/hardware/ril/libril".
The problem is that when I indicate the target after lunch, the compiler looks for the vendor libraries and stop the build. What I am doing wrong?
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
Perseus71 said:
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Click to expand...
Click to collapse
Actually this is what I get after deleting
libril.so in vendor/samsung/d2tmo/proprietary/lib/
and after executing mmm /hardware/ril/libril :
No private recovery resources for TARGET_DEVICE d2tmo
make: *** No rule to make target `vendor/samsung/d2tmo/proprietary/lib/libril.so', needed by `/home/brok85/Documents/android/system/out/target/product/d2tmo/system/lib/libril.so'. Stop.
make: Leaving directory `/home/brok85/Documents/android/system'
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
blackbeard said:
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
Click to expand...
Click to collapse
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
brok85 said:
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
Click to expand...
Click to collapse
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
And vendor-blobs.mk would be present in the vendor folder under your device folder
blackbeard said:
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
Click to expand...
Click to collapse
Well I have followed the guide in the following page
http://wiki.cyanogenmod.org/w/Build_for_d2tmo
The link from where I have obtained the repository is
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and then
$ breakfast d2tmo
blackbeard said:
And vendor-blobs.mk would be present in the vendor folder under your device folder
Click to expand...
Click to collapse
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
thanks a lot for the help guys
brok85 said:
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
Click to expand...
Click to collapse
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all
I have compiled CM11 as it is and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
The procedure I have followed is the following one:
1) Delete the llibril.so and libreference-ril.so from the vendor library. These are the pre-compiled vendor libraries that I need to modify.
2) commented the lines from the vendor-blobs.mk that were including those two precompiled libraries.
3) go to android/system/ and run "mmm /hardware/ril/libril" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so respectively.
4) copied the new libraries just obtained in the vendor folder where the pre-compiled libraries were
5) re-include the lines commented in point 2).
6) run brunch d2tmo
7) flash the .zip obtained
Any mistake?
Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all. Yes I have built everything out of the box and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
I followed the following procedure to include my modified libraries:
1) Eliminate precompiled vendor libraries: libril.so and libreference-ril.so from the vendor folder
2) comment lines in the vendor-blobs.mk that included those two precompiled libraries
3) from /android/system/ executed command "mmm /hardware/ril/librail" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so
4) copied the new libraries in the vendor folder in the same places were the precompiled libraries were positioned
5) re-include the two lines that were commented in point 2)
6) build everything again with brunch d2tmo
7) flash the .zip obtained
Any mistake?
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Perseus71 said:
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Click to expand...
Click to collapse
It cannot even find the network operators. It says that it is impossible to connect and to try later...
mine is the Tmobile version of S3. May this influence?
That would depend on the changes you made. But otherwise not really. The underlying Device tree is unified for all US S3 devices.