yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] VolcyDX:
Just flashed back to 4.0.2 radios and then flashed new ones. Everything working fine for anyone who had concerns of breaking anything.
[Samsung Galaxy Nexus] idkwhothatis123:
http://xdaforums.com/showthread.php?t=1630438

Flash it. I was on the old 404 leak and I'm on the new radios. Signal about the same for me though. A little better
[Samsung Galaxy Nexus] DoctorSasquatch:
And like you said, it should work coming from ANY radio?

I'm on the leaked 4.0.4, so I WON'T need to revert to 4.0.2 then back right?

Just wanna be 100% sure
[Samsung Galaxy Nexus] wynnemelvin:
Yes revert then flash
[Samsung Galaxy Nexus] bucwylde23:
Just flashed the 4.0.2 radios then the new 4.0.4 radios and everything is working great. Thanks for posting the links.
[Samsung Galaxy Nexus] mwalt2:
You root the same way you did the first time. For me, I flashed twrp recovery, flashed chainfire's supersu .zip, rebooted to system, installed file manager to delete the restore recovery .p file in /system, rebooted into bootloader, and re-installed twrp recovery. I suppose you can use a rootkit as well, but what's the fun in that. The recovery portion is optional. You will retain root after flashing whatever superuser.zip you want.
[Samsung Galaxy Nexus] eyekyu:
so flashed the NEW IMM76K radio

-105dBm w/hybrid3 that was the BEST i could get for LTE

wiped cache/ dalvik cache

flashed 4.0.2 radios -111dBm LTE (stock radio was ****, but never dropped a call)

wiped cache & dalvik cache

flashed IMM76K radio -102dBm LTE / -83 dBm 3G

i know the bars do mean really anything but i was able to see what 3 bars look like, pretty cool lol. switching between 4G/3G was pretty quick. ill have to stream music to really test it out.
[Samsung Galaxy Nexus] tacosrdelicioso:
I515.10 is what mine says...everything else is the same tho
[Samsung Galaxy Nexus] eyekyu:
i wonder if there is any difference between I515.09 & .10?
[Samsung Galaxy Nexus] motcher41:
Worked great. Flashed over previous 4.0.4 radios . Thanks!

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] moosc:
Wonder y mine is different
[Samsung Galaxy Nexus] BlackHoleSlam:
Thank you my bars are awesome and so is the 4g

for me, by me and I love you
[Samsung Galaxy Nexus] moosc:
Where did u get yours from?
[Samsung Galaxy Nexus] tacosrdelicioso:
The zip on the first page..
[Samsung Galaxy Nexus] Vegasden:
Mine also say .10 instead of .09. Also got them from imnuts link in first page of this thread.

......
[Samsung Galaxy Nexus] mwalt2:
It's a hardware version of the phone. You can read about it here. Flashing things won't change it.
[Samsung Galaxy Nexus] jonstrong:
Question: I've got a VzW Galaxy Nexus - unlocked / rooted with Wug's toolkit, but still on stock 4.0.2. Hoping for OTA, I replaced CWM touch recovery with stock... rebooted and manually checked for OTA update many times, but I'm clearly not part of this "first wave" of VzW OTA updates. Getting anxious to try this though. I downloaded the 4.0.4 OTA update released today, and just about ready to fire up CWM (temporary) to install it...

After ready a bunch of threads here and on other sites over the past several weeks, I feel a bit silly asking this, but still can't find the answer:

Assuming I'm flashing this official (but leaked?) 4.0.4 update over the stock 4.0.2 (stock radios, etc), can I assume that user-installed apps and data will remain intact? (just as if I allowed a normal OTA update to run?).

I know backups are always a good idea, and already backed up all non-system apps and data via Wug's toolkit to my pc. But I'm just wondering if I should expect to have to restore them after applying the OS update. Would be lovely and quick to be able to simply apply the update via CWM recovery and not have to restore my installed apps, settings, etc.

Thanks in advance...

edit: creating a Nandroid now on internal pseudo SD card, in addition to the apps/data backup I did to the PC via Wug's toolkit. Assuming I should be safe and ready to go applying the OTA via CWM after Nandroid finishes...
[Samsung Galaxy Nexus] Mr_Beefy:
Anybody else having issues with this guide? I have a rooted stock rom with stock recovery. Phone is booted into android and usb is connected. When i launch the toolkit and select my build (8) it shows my device as connected. When i go to option 9 and select standard cwm it just sits there at <waiting for device>. Anyone else have this issue?

Bootloader is unlocked. I used an earlier version of this toolkit to unlock bootloader and root phone.
[Samsung Galaxy Nexus] DirgeExtinction:
You have to turn off your phone(while connected) and boot into bootloader(fastboot).
[Samsung Galaxy Nexus] Mr_Beefy:
Did this, my phone is sitting at the fastboot mode says so in red. Toolkit still says < waiting for device >

Got it, drivers were installed correctly when booted into Android but not in fastboot. Manually installed drivers while in fastboot and it came right up.

---------- Post added at 09:29 PM ---------- Previous post was at 09:05 PM ----------

So what is the safest way to regain root?
[Samsung Galaxy Nexus] mwalt2:
Just flash a superuser.zip. I like the new one by chainfire. You can find the flashable .zip in the first post here. You'll need a custom recovery installed though. You can probably use your toolkit as well to root (if it can do that).
[Samsung Galaxy Nexus] krazie1:
How yall liking this new update? I was surprised when people were able to get the url address from the logcat pics I posted. Good job!
[Samsung Galaxy Nexus] Mr_Beefy:
Skipped using the toolkit because it didn't have an option for the latest 4.0.4 build

used adb to push and flash root.
[Samsung Galaxy Nexus] mttfrog13:
I can get the drivers installed while in windows, but toolkit won't recognize my phone while in fastboot, and windows won't automatically install any drivers while I'm in fastboot. What am I doing wrong. I'm pretty sure this guide requires unlocked bootloaders. If anyone gets installed while being unrooted with locked bootloaders, let me know how you did it.
[Samsung Galaxy Nexus] DroidFamily:
File has been pulled where can I get it now. Please help
[Samsung Galaxy Nexus] kevdog:
Shoot -- where is the file?? Its been pulled
[Samsung Galaxy Nexus] eyekyu:
AWESOME...

whats even better is you doing this in store hahahaha
[Samsung Galaxy Nexus] siberslug:
Link does not work
[Samsung Galaxy Nexus] krazie1:
Whoever has downloaded it upload it and post the link pleaase.
[Samsung Galaxy Nexus] Pithism:
does anyone know the new boot loader version.
[Samsung Galaxy Nexus] mwalt2:
Here's a mirror for everyone.

http://min.us/mhhv9ahG4
[Samsung Galaxy Nexus] DirgeExtinction:
Here's a question aimed at those in the know:

Since this is a new build number, can we still flash the current roms on here? Or would we have to wait until they're updated to IMM76k?
[Samsung Galaxy Nexus] kevdog:
Im running 4.02 with 4.02 radios (which I flashed). I tried installing the zip from the mirror and I'm getting:

Verifying current system....

assert failed: apply_patch_check{"/system/build.", "long number", "long number')

E: Error in /sdcard/12f767e7a5d0.signed-mysid-IMM-76K-from-ICL53F.12f767e7.zip

(Status 7)

Installation aborted.

Suggestions. Are my radios borked?
[Samsung Galaxy Nexus] siberslug:
It says file does not exist
[Samsung Galaxy Nexus] spectrumfox:
Mirrors have been posted.
[Samsung Galaxy Nexus] DroidFamily:
I'm getting same error please help
[Samsung Galaxy Nexus] theineffablebob:
I was having that problem.

I don't know exactly how I fixed it, but it was a combination of following the directions of returning the phone to factory stock ( http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/ ) and flashing the 4.0.2 Radios zip.
[Samsung Galaxy Nexus] JayBeezy802:
I used OTA Rootkeeper, did a CWM backup, downloaded the new zip, renamed to update.zip, flashed in CWM, and then restored root. Everything appears to be working okay right now.

On first start-up however I did have a "IMF-framework has stopped working" dialogue come up. I restarted the phone and so far haven't had any other issues.

Thanks all.
[Samsung Galaxy Nexus] jonstrong:
Hmmm... still not working for me... still getting (Status 7) error -- also an assert failed, but mine refers to "apply_patch_check("/system/build/prop" and appears to be comparing two long (really long) hex values --

Aside from installed APK's, rooting and unlocking, and installing/using CWM 5.5.0.4,this is stock VzW 4.0.2 -- original radios, etc.

This time I tried it by downloading again from mirror link, renaming to update.zip, copying to sdcard root and using CWM option to flash update.zip... same result.

Any ideas most welcome!
[Samsung Galaxy Nexus] spectrumfox:
I haven't seen that error yet on any devices. It could be caused by something Rootkeeper is doing.
[Samsung Galaxy Nexus] spectrumfox:
Having the CWM installed over the stock recovery could cause the update process to fail as that's not stock.
[Samsung Galaxy Nexus] jonstrong:
ok -- next I'll try replacing CWM with stock, use Wug's to boot temporarily into CWM and see if that works...
[Samsung Galaxy Nexus] spectrumfox:
You can also use the Galaxy Nexus Toolkit to initiate CWM for a one-time use in order to install the update.
[Samsung Galaxy Nexus] dmmarck:
As stated, please make sure your recovery is updated to the latest possible version (Status 7 = possible recovery error). Remember, touch is 5.8.0.2, regular is 5.5.0.4.
[Samsung Galaxy Nexus] mike216:
Anyone know where to get the old 4.0.4 leaked radio without the boot loader? I appreciate the link but getting worse signal? Bummer but don't know unless you try. Radios are a hit and miss for us all:rolleyes:
[Samsung Galaxy Nexus] open1your1eyes0:
Any chance when we can expect a deodexed version of this leak?
[Samsung Galaxy Nexus] mwalt2:
Here's the radios from the IMM30B 4.0.4 update. The bootloader is there, but it's the same in both IMM30B and IMM76K and won't matter if you flash is again. There's also a thread here with hybrid radios and has a link to the IMM30B radios with no bootloader, but it didn't flash correctly for me (ended up with no radios). I've flashed this with no problems, but that doesn't guarantee anything for anyone else.
[Samsung Galaxy Nexus] jonstrong:
Thanks... not sure what I've screwed up...but I'm still getting the same error.

Made sure I replaced stock recovery in phone (stock-402-lte-vzw-cdma-recovery.img);

Made sure I've got latest versions of CWM as noted above, on PC.

Used Wug's Galaxy Nexus Root Toolkit 1.3, and verified drivers / recognized device by listing devices first via adb and then via fastboot.

Still have stock 4.0.2 on phone - never reflashed ROM, never replaced radios, etc.

Only tried temporary use of CWM recovery, as per GNex Root Toolkit option - only trying the two latest versions above (first touch, then regular).

Even uninstalled SetCPU and rebooted before trying the last time.

Under Developer Options, I have USB debugging and Stay Awake checked...

Baseband i515.09.V.EK05 / i515.EK02

Kernel 3.0.8-gaaa2611

android-build@apa28#1

Build number ICL53F

Can't imagine what else is creating this (status 7) aborted update error...

Have to sleep now - up for work at 6am... will check back in tomorrow.. Want to get this working!
[Samsung Galaxy Nexus] spectrumfox:
Make sure you're using the system image from here as its the only one guaranteed to be stock.

https://developers.google.com/android/nexus/images
[Samsung Galaxy Nexus] dalumberjack:
So I formatted to stock 4.0.2 on my phone. Now I am getting this error message every time I try to do the update. Anyone know what to do?

All I did with my phone was unlock it and install cwm so I could side load some programs and stuff. I never used a custom rom or anything. Always stayed stock so I could do OTA.

Click to enlarge:

EDIT: I see the poster above is having the same issue. Ill try that image to see if it helps. Any other ideas is greatly appreciated.
[Samsung Galaxy Nexus] VaporCloud:
Getting 4g Signal in Area where i used to get 0 Bars

I live in between two apartment buildings, Usually get terrible 3g and never even latch on to 4g Before this 4.0.4 Update.

Now i get 2 bars of 4g In The very same spot! .... So far no "data network unavailable" errors either... Double win!.
[Samsung Galaxy Nexus] kspeaksster:
My reception is great after the update but now my phone takes forever to switch from 3g to 4g
[Samsung Galaxy Nexus] kevdog:
The error complains about the file /system/build.prop. Can anyone post the original build.prop file from 4.0.2? I don't it can't be as simple as replacing this file but who knows.

Here is my build.prop:

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=ICL53F

ro.build.display.id=ICL53F

ro.build.version.incremental=235179

ro.build.version.sdk=14

ro.build.version.codename=REL

ro.build.version.release=4.0.2

ro.build.date=Thu Dec 8 01:28:56 UTC 2011

ro.build.date.utc=1323307736

ro.build.type=user

ro.build.user=android-build

ro.build.host=vpbs6.mtv.corp.google.com

ro.build.tags=release-keys

ro.product.model=Galaxy Nexus

ro.product.brand=google

ro.product.name=mysid

ro.product.device=toro

ro.product.board=tuna

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=samsung

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=omap4

# ro.build.product is obsolete; use ro.product.device

ro.build.product=toro

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=mysid-user 4.0.2 ICL53F 235179 release-keys

ro.build.fingerprint=google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys

ro.build.characteristics=nosdcard

# end build properties

#

# system.prop for toro

#

rild.libpath=/vendor/lib/libsec-ril_lte.so

rild.libargs=-d /dev/ttys0

telephony.lteOnCdmaDevice=1

# Ril sends only one RIL_UNSOL_CALL_RING, so set call_ring.multiple to false

ro.telephony.call_ring.multiple=0

# Turn on IMS by default

persist.radio.imsregrequired=1

persist.radio.imsallowmtsms=1

# Default ecclist

ro.ril.ecclist=112,911,#911,*911

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.com.google.clientidbase=android-verizon

ro.com.google.locationfeatures=1

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.setupwizard.mode=OPTIONAL

ro.cdma.home.operator.numeric=310004

ro.cdma.home.operator.alpha=Verizon

ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83

ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000

ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000

ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000

ro.cdma.otaspnumschema=SELC,1,80,99

wifi.interface=wlan0

wifi.supplicant_scan_interval=15

ro.opengles.version=131072

ro.sf.lcd_density=320

dalvik.vm.heapstartsize=8m

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=256m

ro.config.ringtone=Girtab.ogg

ro.config.notification_sound=Proxima.ogg

ro.config.alarm_alert=Cesium.ogg

ro.com.android.dateformat=MM-dd-yyyy

ro.com.android.dataroaming=false

ro.com.android.wifi-watchlist=GoogleGuest

ro.error.receiver.system.apps=com.google.android.feedback

ro.setupwizard.enterprise_mode=1

keyguard.no_require_sim=true

drm.service.enabled=true

camera.flash_off=0

dalvik.vm.dexopt-flags=m=y

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Samsung Galaxy Nexus] Konceptz804:
Is there any real reason to install this if your already running the leaked 4.0.4 a few months back?

Can somebody confirm any real changes?
[Samsung Galaxy Nexus] axne1:
Which prl is everybody on?

would like to get the latest one

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] miketoasty:
Yes, this has new radio's which, at least for me, get's much better 4G and holds it longer than it did before.
[Samsung Galaxy Nexus] kspeaksster:
I am running PRL 52686
[Samsung Galaxy Nexus] scope666:
Same here. (NYC area)
[Samsung Galaxy Nexus] Rnd0209:
Ok so everyone is just here talking about how to download this update etc but no one is really posting any RESULTS....

How is this update IMPROVING our device?

Is the Reception BETTER?

Is the battery not draining as fast?

Lets see some info on what is being improved.

Thanks!
[Samsung Galaxy Nexus] DirgeExtinction:
15119...
[Samsung Galaxy Nexus] hogowner:
Hi Guys....I am on 4.0.3......radio FA02

if I flash the 4.2 radios....then update to the new 4.4 radios...will it work on the 4.0.3?

I did not upgrade to 4.4 yet...will the 4.4 radios workd with 4.3?

Thanks in advance
[Samsung Galaxy Nexus] Konceptz804:
I was running the leaked 4.0.4, reverted back to 4.0.2 and then installed this official 4.0.4. Try as I might, I cannot notice anything different other then the version numbers. I've always had great 4g reception .
[Samsung Galaxy Nexus] kspeaksster:
Performance seems to be a little better. I haven't noticed any improvements to the battery. Volume level doesn't seem to be any louder. The 4.0.4 leaked radio seems to work better for me in regards to reception. With these new radios, my phone seems to have a big issue when going from 3g to 4g; takes forever. When I can connect to 4g, it only sticks for a few mins then switches back to 3g.
[Samsung Galaxy Nexus] bc760:
Probably been asked but this is only way to get a quick answer as I'm ready to revert to stock in order to get the update. Once updated will I be able to go and install a ROM or do I have to wait until the Dev updates?

Galaxy Nexus - This is not just a phone
[Samsung Galaxy Nexus] axne1:
What's the # code to check prl update?

And I'm rooted and on Aokp M5

Will it cause problems??? :confused:

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] impulse101:
I had the same problem to fix I had to flah back to 4.02 radios then flash the new 4.0.4 and it worked fine
[Samsung Galaxy Nexus] Rouxe41:
It's a patch. Sounded like you needed the old ones.
[Samsung Galaxy Nexus] bigknowz:
Battery fix?

Is there anything in 4.0.4 that improves battery life?
[Samsung Galaxy Nexus] kspeaksster:
*2289
[Samsung Galaxy Nexus] axne1:
That didn't work?

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] winner00:
You should be updating you prl like that. It can fry your sim card.
[Samsung Galaxy Nexus] spectrumfox:
I don't understand your question.

Since you're on 4.0.3, the only way to get to the new 4.0.4 is to revert to stock, then install the OTA. The instructions can be found at the beginning of this thread.

http://xdaforums.com/showthread.php?t=1630349
[Samsung Galaxy Nexus] spectrumfox:
There are newer radios, which can assist with battery life.
[Samsung Galaxy Nexus] bc760:
I just ended up updating the radios and bootloader, I was already on the leaked 4.0.4

Galaxy Nexus - This is not just a phone
[Samsung Galaxy Nexus] Arhtard:
I'm on 15109 prl.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] reggie14:
Has anyone been able to perform this manual update on a phone that is still locked and not rooted? I tried the OP's instructions without any luck. I wasn't able to temporarily boot into CWM. Error messages were displayed both in GNex Toolkit and fastboot indicating I needed to unlock the phone for that to work. If it would be helpful, I could try again again and copy down the messages, but I'm guessing this isn't a big surprise. For security reasons, it doesn't seem like the phone should let you boot into CWM without unlocking the phone first.

Still, I'd love to find a way to flash this update without unlocking the phone. If there isn't a way then I'll have to think more seriously about unlocking it and figure out how to backup/restore my apps and app data.
[Samsung Galaxy Nexus] impulse101:
Just root and unlock. its easy, and fun and worth it
[Samsung Galaxy Nexus] Arhtard:
Or unlock - update - lock.

Or wait for Verizon.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] spectrumfox:
Okay everyone, I apologize for the mixup and misunderstanding.

I have altered the method I posted to include the fact that you need an unlocked bootloader to proceed. I did not have this data when I first posted the method, totally my bad.

However, may I say if you're going to be playing around with your Nexus device, you should really unlock your bootloader. It'll save you a lot of hassle down the road and the many benefits are worth having to back up your data and wipe your phone, since you only have to do it once.

Added note to listed method:

PLEASE NOTE: My apologies for the flip-flopping. It appears the booting into CWM Recovery Step (#4) will NOT work if your bootloader is locked after all. You will first need to unlock your bootloader to use this upgrade method. PLEASE PLEASE PLEASE BACKUP YOUR ENTIRE PHONE BEFORE PROCEEDING. Unlocking the bootloader wipes ALL data on your phone and it is NOT recoverable.
[Samsung Galaxy Nexus] spectrumfox:
I have edited my steps to include the fact that your bootloader must be unlocked before proceeding. I apologize for the mixup.

If you want to proceed with a locked bootloader, please see this thread for assistance.

http://xdaforums.com/showthread.php?t=1629590&page=35
[Samsung Galaxy Nexus] cmbeid:
Error 404 while trying to download

Looks like the URL was pulled.
[Samsung Galaxy Nexus] spectrumfox:
Yup, but there are mirrors.
[Samsung Galaxy Nexus] jonsgirl:
Much improved signal since the update! Not sure on battery life yet. I'm going to get a full charge and see how long it lasts.
[Samsung Galaxy Nexus] cmbeid:
Ah, I didn't see any mirrors listed in the thread. Ill have to do a more through search after work.
[Samsung Galaxy Nexus] m.s.johnson:
Noob, please don't yell at me.

Ok I am stock 4.0.2 ICL53F. I am not unlocked or rooted. I was trying to use the Galaxy Nexus Toolkit and I think I messed up. Whenever I hold the volume and power buttons it goes into "Odin". Can anyone help me get 4.0.4 IMM76K loaded and still stay stock and not flash my phone so I don't lose all of my data/apps. etc? I don't want to wait another day for VZW. Thanks for any suggestions!
[Samsung Galaxy Nexus] spencer88:
The toolkit won't work with a locked bootloader. I believe you can put the update.zip on the root of your USB storage, boot into the stock recovery and flash it that way.
[Samsung Galaxy Nexus] spectrumfox:
Nope, can't do this anymore, Google blocked it. :(

You have to apply this OTA ZIP from CWM, which means you need an unlocked bootloader, which means you will need to backup your data and wipe just once to accomplish this.

This thread has some advice on how to accomplish this using ADB, but its going to require some legwork on your part.

http://xdaforums.com/showthread.php?t=1629590&page=32
[Samsung Galaxy Nexus] m.s.johnson:
So I have the file on my "sdcard" and renamed it update.zip but you are saying that I would need to move it the root of my usb storage, is that different? Then how do I boot into stock recovery? Sorry for what must appear to be such basic questions.

---------- Post added at 01:52 PM ---------- Previous post was at 01:51 PM ----------

OK, thanks...
[Samsung Galaxy Nexus] spectrumfox:
The instructions I have provided at the beginning of this thread require an unlocked bootloader to proceed because you need to boot into CWM using the Galaxy Nexus Toolkit to apply update.zip. Stock recovery will not allow you to apply update.zip
[Samsung Galaxy Nexus] spencer88:
You press and hold the volume up and down buttons, then press and hold power until it boots. It'll boot into the bootloader, fro there you press the volume down button either one or two times and it'll say "recovery" from there press the power button and it'll boot into the recovery you have installed. From what you say it sounds like you're totally stock...so it'll be the stock recovery with minimal options.

I was sure you could apply the update.zip from the stock recovery with a locked bootloader...
[Samsung Galaxy Nexus] spectrumfox:
You used to be able to. Now it requires a bit more finesse and use of ADB.
[Samsung Galaxy Nexus] spencer88:
When did that change?