yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Sparx639:
Yeah, I'm not getting an output, adb detects my phone but I get waiting for device. I thought I needed to fully boot and add my computer to the list of devices that can perform adb operations. And yeah I didn't think that it was a kernel problem because I knew that if it reached the boot logo then it was a ROM problem, yet, the only mods I've made to the ROM were adding the proprietary binaries and changing the default backup transport server to Google
[Samsung Galaxy Nexus] beekay201:
Does the ROM fully boot without the custom kernel? Which gapps package do you use? Is this a custom kernel you compiled yourself? Maybe try diff the config against the default config?

a maguro sent this.
[Samsung Galaxy Nexus] Sparx639:
I've tried it both with gapps and without gapps, and the gapps package doesn't seem to make a difference. Its not a custom kernel, its the aosp kernel that you would get out of the compiler on your first build. As in I haven't touched any of the kernel sources yet. The ROM boots with the kernel it compiles with, but does not boot when I try a custom one. I didn't have this problem on 4.2.2 aosp and its a little weird.
[Samsung Galaxy Nexus] beekay201:
ramdisk conflicts perhaps?
[Samsung Galaxy Nexus] Sparx639:
When I was getting the bootloops, I tried using the stock Google kernel hoping it would boot, but it didn't only the kernel that was built with the ROM would make it boot. I'm not sure if the Google nexus kernel has a different ramdisk, but if it doesn't then thats not the problem. Maybe its because I was using the latest repo updates and the changes somehow disallowed the Google kernel from working, but I'm still testing
[Samsung Galaxy Nexus] beekay201:
Cool, report back. One more thing: on your previous post, you refered "the kernel that you get from the compiler after your first build". Actually, the kernel image you get, is the already compiled zImage, aka the kernel doesn't get compiled there, it's just a binary which will be included with the build. It would take much longer to build the Android platform, because of one component which isn't even part of the Android OS platform. ;)
[Samsung Galaxy Nexus] Sparx639:
*boot.img :p so the kernels are already prebuilt? How do people mod them them?
[Samsung Galaxy Nexus] beekay201:
You grab the source, make your changes and build.

a maguro sent this.
[Samsung Galaxy Nexus] Sparx639:
I see, another question, when I add koush's superuser to my build, just the app, not the integrated settings, I get an error that says there are undefined values LOGE LOGD and LOGW in the su.c and db.c files. How would I work around these? I haven't added busybox into the ROM and I'm not sure if its mandatory for it, but that's what I was suspecting. Any insight? I can't find any results on the web for it
[Samsung Galaxy Nexus] Carlos_Manuel:
Edit:Deleted
[Samsung Galaxy Nexus] :
I and my friend have a problem with a Cyano successfully compiled from source

We have no probloems during compilation, and build boots up

Here is our problem:

1) I connect my device to PC:

2) Click on Connected as Media device... bla bla

3) and I open this submenu... normal :)

BUT

4) When I uncheck MTP

5) and I came back

"Connected as Media device.. bla bla" from point 1) Will disappear forever and I'm unable to connect to PC

Can someone give me an hint? :)

Have We miss something?

[MENTION=4022928]Carlos_Manuel[/MENTION], I know You compile Cyanogen from sources... ;) can You help me to figure this out?

Thank You everyone

Regards,

Enrico
[Samsung Galaxy Nexus] Carlos_Manuel:
Hi, same thing happens here...

But you can go back to USB connection settings and then to enable MTP again and then everything is working correctly.

What seems to happen is that when you have disable both USB connection types from USB connection settings and after that you connect your Nexus to PC via USB then CM does not use either MTP or PTP and that's why you are unable to connect to PC...
[Samsung Galaxy Nexus] :
OK. :) gonna try new build soon and see what happens ;) now i'm on stock again.. thank You for quick reply, i was getting worried for nothing :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Ok, Np. :)
[Samsung Galaxy Nexus] vinek14:
thanks man .. great work
[Samsung Galaxy Nexus] beekay201:
anybody having the following issue when getting the manifest?

it's not on my end (i've even tried adding gpg key here, no dice - http://source.android.com/source/downloading.html)

Please, come back JBQ!

edit: cool. 4,500 posts.
[Samsung Galaxy Nexus] rubikqj:
Wow, thank you for this tutorial. I thought I couldn't compile a ROM on my computer. Even though it took some time, it worked from the first try! So happy xD
[Samsung Galaxy Nexus] beekay201:
It was on my end. 2 repo versions installed, it was using /usr/bin/repo.

So, the example:

~/.bin/repo init -u <aosp manifest URL here> -b kitkat-dev

~/.bin/repo sync

Works!

a manta wrote this.
[Samsung Galaxy Nexus] quantan:
Hi,

I'm a newbie. I just built a custom rom successfully for gnex (4.3, AOKP based). Everything is OK except GPS. The GPS cannot lock, it cannot find my location. I know there are many issues about GPS on 4.3, but some ROMs I flashed before don't have. How do I fix this from source?

Thanks so much. Your help should be appreciated.
[Samsung Galaxy Nexus] Carlos_Manuel:
You can try this:

Copy sirfgps.conf from JB 4.3 ROM (/system/vendor/etc/)

and place it to /*/vendor/samsung/maguro/proprietary/

Now from:

/samsung/maguro/proprietary/

Open and edit: Android.mk

include $(CLEAR_VARS)
LOCAL_MODULE := sirfgps
LOCAL_MODULE_OWNER := samsung
LOCAL_SRC_FILES := sirfgps.conf
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_SUFFIX := .conf
LOCAL_MODULE_CLASS := SHARED_LIBRARIES
LOCAL_MODULE_PATH := $(TARGET_OUT_VENDOR)/etc
include $(BUILD_PREBUILT)

add the following lines to the Android.mk

Now check:

vendor/samsung/maguro/device-partial.mk

If it doesn't have this line:

sirfgps \

in device-partial.mk then add that line after

PRODUCT_PACKAGES := \

...

Build again..
[Samsung Galaxy Nexus] quantan:
Hi Carlos,

Thank you so much. I just check again and It doens't have the line sirfgps \. I'll add and build again.

In addition, could you advise me where to get proprietaries for custom rom based on AOKP? I've tried some from Google binaries, AOKP, CM github. I just want to make sure what I'm doing are correct :D
[Samsung Galaxy Nexus] desalesouche:
i all does someone know how i can fix that error?

hardware/qcom/gps/loc_api/libloc_api/loc_eng.cpp:44:21: fatal error: rpc/rpc.h: No such file or directory

compilation terminated.

build/core/binary.mk:432: recipe for target '/home/desalesouche/beanstalkk/out/target/product/u8800pro/obj/SHARED_LIBRARIES/gps.msm7x30_intermediates/loc_eng.o' failed

make: *** [/home/desalesouche/beanstalkk/out/target/product/u8800pro/obj/SHARED_LIBRARIES/gps.msm7x30_intermediates/loc_eng.o] Error 1

make: *** Waiting for unfinished jobs....

thank you...
[Samsung Galaxy Nexus] djmatt604:
Here's your answer...

rpc/rpc.h: No such file or directory

The file you are compiling is attempting to call that library. Perhaps try syncing your repo again and make sure you have the repo commands all correct per the owner of the source. Good luck!

remember, remember...
[Samsung Galaxy Nexus] poozza:
Thanks man!
[Samsung Galaxy Nexus] leonevo:
Thank!!

Paya va con tapatalk
[Samsung Galaxy Nexus] faber_93:
Tnx for this fantastic tutorial! it's very simple!! :good: ;)
[Samsung Galaxy Nexus] opssemnik:
modify buildenv.sh
[Samsung Galaxy Nexus] DashMK:
Hi,

Is there an updated version of this in the last year or two ?
[Samsung Galaxy Nexus] shenye:
You want to flash the system and boot. You don't wanna erase your custom recovery.

fastboot flash #partition# file.img

#partition# can be:

system

boot

recovery

etc.

Just don't include the #'s
[Samsung Galaxy Nexus] superlj:
thanks, so the boot.img is like the bootloader-maguro-X.img? system.img is the image-yakju-Y.zip?
[Samsung Galaxy Nexus] shenye:
NO! BOOTLOADER AND BOOT ARE COMPLETELY DIFFERENT. Flashing it the wrong way round WILL brick your device. All the partitions will be ordered into .img files, NOT .zip. You should find the boot.img in the .zip.

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

ETC.
[Samsung Galaxy Nexus] superlj:
thanks again!

So, there is no bootloader or radio generated from source code?
[Samsung Galaxy Nexus] RogerPodacter:
No recovery or radio from compiling i dont believe. And the boot.img is basically the kernel if i'm not mistaken.
[Samsung Galaxy Nexus] caslca:
Thanks, I'll give it a try
[Samsung Galaxy Nexus] PaulW21781:
Any idea on what file within android_build needs editing to stop the recovery image being included when using "make otaupdate"? Or do I need to edit the device config itself (ie, device/samsung/maguro) ?

Cheers
[Samsung Galaxy Nexus] sate86:
building a lte device ROM for gnexus

i'd like to follow this tutorial to build a pure aosp rom for my galaxy nexus. following the link for the device specific binaries, i see only the binary for the graphics (no radio binary). in comparison, the GSM entry has binaries for the graphics and the GSM radio.

i've found links to a "leaked" version of 4.0.3 lte gnexus radio file. (i cant post links yet as a new user but search for "verizon nexus radio" or something similar). the link mentions that the radio leak is in a .zip format and would be flashed via recovery. in contrast, this tutorial mentions extracting the radio binary before building the ROM.

my question is this: how do i go about building the ROM i want to build? can i build w/o the radio binary and then just flash the leaked version afterwards?
[Samsung Galaxy Nexus] naddie:
I've finally got ADB to work! Found out you had to adb kill-server, then adb start-server as SU.

I have a Vibrant (SGH-T959) which is a T-Mobile US version of the Galaxy S. Anyways, found the binaries here:

https://github.com/CyanogenMod/android_device_samsung_vibrantmtd

Yadda yadda yadda... lunch.. vibrantmtd appears! Yay!

Then I get this after choosing full_vibrant-eng (choice #11)

Which would you like? [full-eng] 11

build/core/config.mk:138: *** No config file found for TARGET_DEVICE SGH-T959. Stop.

** Don't have a product spec for: 'full_vibrantmtd'

** Do you have the right repo manifest?

Any ideas?

Edit: forgot to mention I currently have ICS Passion v10 on my VibrantMTD. During the extract-files.sh process, it didn't find certain files. Is this causing the problem?

Here's an example:

remote object '/system/lib/libsamsungcamera.so' does not exist

remote object '/system/vendor/lib/libsensorservice.so' does not exist

remote object '/system/vendor/lib/libsensorservice.so' does not exist

remote object '/system/cameradata/datapattern_420sp.yuv' does not exist

remote object '/system/cameradata/datapattern_front_420sp.yuv' does not exist

remote object '/system/firmware/CE147F00.bin' does not exist

remote object '/system/firmware/CE147F01.bin' does not exist

remote object '/system/firmware/CE147F02.bin' does not exist

remote object '/system/firmware/CE147F03.bin' does not exist
[Samsung Galaxy Nexus] Ichibahn SLC:
I did all the steps with success for a CWM flashable zip and when i tried to flash it it came up with status 6 error.

Any help?
[Samsung Galaxy Nexus] naddie:
Well, I flashed CM7 on my Vibrant and tried again, and this time no errors. However, this lead me to believe I'm going about it the wrong way. Even if it grabbed all the files, methinks they are the wrong files for ICS (since CM7 is a gingerbread rom).

I tried to do a "make clobber", but now I have a different error which I totally didn't expect:

Checking build tools versions...

************************************************************

You are attempting to build with the incorrect version

of java.

Your version is: java version "1.6.0_20".

The correct version is: Java SE 1.6.

Please follow the machine setup instructions at

http://source.android.com/source/download.html

************************************************************

build/core/main.mk:131: *** stop. Stop.

I did an apt-get remove --purge sun-java6-jdk, and then a apt-get clean but even after that, when I type "java -version" it returns "1.6.0_20". Of course, i reinstalled the package because I didn't want to break anything.

Any ideas why or how it got updated? I don't recall doing any updates in Ubuntu. How do I revert back to Java SE 1.6?

Thanks.
[Samsung Galaxy Nexus] naddie:
SOLVED: I installed OpenJDK from a guide on installing ADB on Linux. After uninstalling OpenJDK and Sun Java, I reinstalled Sun Java 6 JDK by itself, rebooted, and all is well.

Since I don't know what the packages are called to the letter, I actually used the GUI app "Ubuntu Software Center" found under the Applications menu. I just searched for "java" under Installed Software and removed anything to do with OpenJDK and Sun Java.

Makes me wonder if this would break ADB... I hope not.

EDIT: ADB still works. Whew! Probably because it was already installed. Not sure why OpenJDK was required (or maybe the person who wrote it up wanted to use everything open source).
[Samsung Galaxy Nexus] dave_t321:
build.fingerprint

I'm trying to override ro.build.fingerprint with this in a makefile in my vendor folder:

PRODUCT_BUILD_PROP_OVERRIDES := PRODUCT_NAME=yakju BUILD_ID=ICL53F BUILD_FINGERPRINT=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys PRIVATE_BUILD_DESC="yakju-user 4.0.2 ICL53F 235179 release-keys" BUILD_NUMBER=235179

The makefile is definitely being read because the other parts in there are being done properly. The entry in build.prop after compiling is

ro.build.fingerprint=google/dave_maguro/maguro:4.0.3/IML74K/eng.david.20120105.194138:userdebug/test-keys

Do I have to disable the auto-generated fingerprint somewhere before I can override it?
[Samsung Galaxy Nexus] Mandelbrot.Benoit:
I am set up with 10.04 LTS 32 bit and can confirm this works. Only change needed is where he says its for 64 bit only:

apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown libxml2-utils xsltproc

Source: http://source.android.com/source/initializing.html

Awesome tutorial! Thank you.
[Samsung Galaxy Nexus] meego-nexus:
Thanks for the guide.

I'm still having problems, though. Building and flashing works fine, and the phone (Galaxy Nexus) boots. However, then it gets stuck on the splash image (which is the Android logo, with a repeating highlight moving over the letters). I can adb shell into the phone, and look around. Output from logcat shows several failure messages repeating in a loop. The most interesting seems to be:

I've tried building both full_maguro-eng, and full_maguro-userdebug. Same thing happens. I sync'ed the repo before new year, but also yesterday; no difference. When I revert to the Google issued recovery images, everything works fine.

Any tips or ideas would be appreciated.
[Samsung Galaxy Nexus] killlabyte:
I had the same issue after making an otaupdate.zip and flashing it. I'm not sure if this is what fixed the problem or if it was dumb luck, didn't wait long enough, etc, but after reflashing everything and getting it back to good I went into CWM and then mounts and partitions and formatted data, cache, and system.

Then I reloaded the zip and after looking at that ugly logo for a couple mins it booted up. As mentioned I am not sure if that had anything to do with it or not. I did not recompile the image or change anything. I just recalled from flashing other roms in the past that, depending on the conditions, you needed to format those.
[Samsung Galaxy Nexus] Snylter:
I'm a total newbie at this..

How can I set up and compile ICS with root included? (su and superuser.apk)

Is it possible for me to add other software like Handcent SMS in the build?
[Samsung Galaxy Nexus] meego-nexus:
That was the problem! Thanks a lot!

I used fastboot flashall to transfer the image files, however, flashall only affects boot, recovery, system. To format userdata, cache you need to add the -w flag.

The full command is then:
[Samsung Galaxy Nexus] Snylter:
May anyone please tell me the size of your files?

My files:

system.img ~158MB

userdata.img ~137MB

boot.img ~4MB

recovery.img ~4MB

The reason for my question is quite simple.. The 4.0.2 image from Google has a system.img file with the size of 176009KB.

The zip-file from Google has a size of 184MB

My zip-file has a size of 96MB, and gives the following error:

Whoops: didn't find expected signature

read_central_directory_entry failed

error: failed to access zipdata in '§!·♫ð¸Érã<¬Q5¶~#ò♥¹◄ùA▀{Ìıkéc☼®,öSmÑ╦Mï╩ëı¹+

↓¯»☼9═Î╠÷←¾f¸«GÞ♫ªÃ♫;(OW`9æµïþëµ(∟½☼òËÏ╬ê%C§¶=ö■CXÆÙ½☼x╦¸×¡♫╚+┐ »|ÍË®î;‗╩ú¨D¦èÛ╠

R¦è┌ÉÑ║ı▼=³┴¶øK®º>Þ5Ë╦→↓/méÏ▀L¾A■´·Çñ♣K☺■▲«}ıî=▀UvD┌ðÅ¤ç¸▄nz?þv░ú↔G~╬¸zÝh´♂■

╬(ªÅH1>↓Ò¹õ¨}ÿé_fÊ²Cg93<S¦´¢¹ºÎ]£W¸ƒ:Â┼yc¹ÕËîÝWèì×▒§Í1░'▲

:².§O┌ÀØ±ªL╔ÀqõÅÜ╬ú╠‼╣▄º*þÍ╝rp▬‗ç│öÒ═q1X¶Ùb÷╦à~=ôi4]\

¨∟ÂzÊ)ûBª©æ}îgf◄â¢0´∟¿æ«ÅÍÂÍÑÒÞ¸♀╬²;ôs█Ó£♥<▼±"▀8£;öªÙ│Þ■ÅÚ←<óë¥☼y×♥vä!¥WFTc~UHÖ─

♥«→B┐_¸<_+╣b♂=¤╗¸*┼▬^Ê¤¢Å║r=©dôêGÿFÑ╦╦§│╩¹¼§×~vp?Õý¾♂ªP?¸VWH«É~¯5è]<È¤=S┌m÷soÇ┤┼

Î¤¢s╦uÖÕ²▄█*û~»└s¤{♫╚z©Ïß]←'
[Samsung Galaxy Nexus] dave_t321:
for anyone interested PRODUCT_BUILD_PROP_OVERRIDES is a command from the cyanogenmod build system, not aosp. This commit fixed it:

https://github.com/CyanogenMod/android_build/commit/a32605759a792fe5d15ad63566acd664d6eada3e
[Samsung Galaxy Nexus] PaulW21781:
It appears that the compiled .apk's are all being odexed, so there is the .apk and .odex file present in /system/app. Same with framework.

Could this be due to building via Master branch?
[Samsung Galaxy Nexus] meego-nexus:
My files:

4.1M boot.img

315K ramdisk.img

646K ramdisk-recovery.img

4.4M recovery.img

155M system.img

135M userdata.img

135M userdata-qemu.img

Maybe add a bit more detail to what you are doing, which commands, which OS your working on, etc., and it will be easier to help out.
[Samsung Galaxy Nexus] PaulW21781:
Not at home right now, so can't confirm .img sizes, however the .zip file created from make otapackage is 196.6MB, but I did build it with gapps too.

Only other issue I'm getting with my built ROM now is gallery2 force closing all the time (not working at all) and as mentioned above when building its odexing all the apk's and frameworks.
[Samsung Galaxy Nexus] gekkekoe123:
Anyone know why bluetooth isn't working after build?

Everything else is working. I'm usung ubuntu 11.10

I use this setup to build cm7 roms without any problems.
[Samsung Galaxy Nexus] Snylter:
I've tried to follow the guide here command by command.

I've also tested the guide at androidworld command by command.

No matter which version I try, the result is the same..

The .zip-file should be able to flash with fastboot when I've created it? (make otapackage -j8) (8 because I gave the machine 4 cpu cores)

I'm using Ubuntu 10.04, 64 bits version.

80GB HDD, 8GB RAM, 4 cpu cores. (i7, 2. generation)

Ubuntu is running in an virtualized environment, I've tried with both VirtualBox and VMware Workstation.

In both configurations, the network interface is set to Bridged mode.
[Samsung Galaxy Nexus] PaulW21781:
You flash the zip via cwm.
[Samsung Galaxy Nexus] Snylter:
How do I flash without cwm? I do not want to install cwm.
[Samsung Galaxy Nexus] killlabyte:
So... obviously you would use fastboot to flash the img files instead of cwm to flash the .zip.
[Samsung Galaxy Nexus] meego-nexus:
I believe you can use fastboot update?

From this page:

http://www.gotontheinter.net/content/fastboot-cheat-sheet

(However, in that case, you might as well flash the individual partitions separately, or use fastboot -w flashall).
[Samsung Galaxy Nexus] Snylter:
When trying to use fastboot update myzipfile.zip

The system img gave an WriteFail.

When trying to do the same with boot, recovery and system separately (fastboot flash system system.img), the system image still failed.

When updating with the image from google (4.0.2), everything worked just fine.
[Samsung Galaxy Nexus] jess086:
If everyone wants an easier time at this u need to find and download the updated repo from the cyro site. It makes sync a lot easier
[Samsung Galaxy Nexus] meego-nexus:
So, does that mean that the boot and recovery images flashed correctly, while the system image did not? And are you able to flash the separate images from Google, including the system.img; not just using the zip-file?

And when you say "WriteFail", is that from transferring the system.img (or zip) file from the computer to the phone, over USB, while in fastboot mode? Do you get an error on the in the terminal which you can copy in on your message?

If it's only the system.img you've built, maybe try to re-do the make step, possibly after a repo sync, and see if that helps.

Finally, you could also try to extract the system.img, and see if that shows any issues. I haven't tried this, so maybe others can help, but this looks interesting:

http://code.google.com/p/unyaffs/
[Samsung Galaxy Nexus] Snylter:
I tried again, this time using an dedicated physical computer.

This time, everything went way better..

Now, how do I include Google-apps in my AOSP-build?
[Samsung Galaxy Nexus] shenye:
merge it with a premade ICS gapps package.
[Samsung Galaxy Nexus] PaulW21781:
Well I've got mine working and running on my phone now :) Only took a week or two to fully figure out what was needed!

Merged with GAPPS-IML74K-010112, seems to be going ok so far! I've done a few mods too, based a vendor off peteralfonso's one (Here), modified it a fair bit and it's running pretty well!

Also avoided in using various Cyanogenmod repo's for things like android/build, frameworks/base and such, so only what I want modifying is done.

Quite impressed :) Certainly a different beast to when I used to build 2.2/2.3 ROM's!

Compile time is also down to just over 40 mins for building a new ROM. (source build/envsetup && lunch 11 && make clean && make otapackage -j6) and this is on my laptop too. I don't have a dedicated building machine as such...

Just need to spend some time adding a few other little tweaks and such here & there, and I'll be sorted!
[Samsung Galaxy Nexus] scratch42069:
So to merge the GAPPS with an already built OTA zip, you just take the contents of the GAPPS zip and paste them within the OTA zip or system folder in the build directory/out and use the make snod command?
[Samsung Galaxy Nexus] Snylter:
I used the script in the gapps-zip with some modifications of the paths in the different commands.

It worked perfectly :)

So now I'm running AOSP 4.0.3 with Google apps and Market..

But I'm still in need of a way to root.. The superroot from Paul don't seem to work.
[Samsung Galaxy Nexus] Snylter:
Also, I just found out that my GPS is not working after installing the AOSP 4.0.3..