yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] forumache:
Solution (this is how I do it on Nexus S, I adapted for you for Galaxy Nexus)

- OEM Unlock

- Copy OTA file on sdcard

- Boot in bootloader mode

- fastboot boot clocworkmodrecoveryimage

- use the custom recovery to install OTA from sdcard

http://xdaforums.com/showthread.php?t=1357642

The only change from the link above is that you don't flash recovery (you can flash it if you want, but I prefer to send it via usb and boot from it anytime I need this, still keeping my original recovery intact).

Or you can just wait for OTA...
[Samsung Galaxy Nexus] bleets:
that's one thing i love about nokia...

I bricked my 6500 classic once, wouldnt do anything at all after a failed firmware update (because nokia software updater is/was crap.)

So i ran NSU again with the bricked phone plugged in...and it detected it, saw there was no firmware and flashed it with the most up to date version.

ahh i wish all devices would recover from a bricked state
[Samsung Galaxy Nexus] ferris2375:
I'm confused, I just downloaded it. Shouldn't it be put where it needs to be to work by default?

I'm flashing with CWM and it seems to be updating fine.

Does this mean if I'm rooted I won't get any OTA updates?

Any suggestions on how I can go back to stock?

Edit: Flashed fine via CWM. Back up and running and updated. Phew...
[Samsung Galaxy Nexus] marky9074:
Hmmm the recovery log below, and the zip has dissapeared....
[Samsung Galaxy Nexus] oscillik:
So far there have been quite a few people in this thread who have received the update,

yet no-one has mentioned whether it actually fixes the fault
[Samsung Galaxy Nexus] jmbillings:
I'd love to be able to confirm it does, but I couldn't ever get the fault to occur. Never saw it once. I think it's because I'm on Orange and they use 1800MHz?
[Samsung Galaxy Nexus] bleets:
you mean the questions listed below? :p

dont think it matters if it works in the bootloader or not...important part is a usable phone etc.
[Samsung Galaxy Nexus] oscillik:
Yup, Orange use 1800MHz so you're correct, you wouldn't normally be affected. Do you have access to a phone on O2 or Vodafone, where you can use the secondary phone to make a phone call to your landline, while holding the secondary phone close to the volume rocker? This would work as a test. The second phone must be forced into 2G mode, and also must be actively in a call.
[Samsung Galaxy Nexus] marky9074:
This works very well, thanks! I never thought to temp boot CWM before.. :D

---------- Post added at 08:36 PM ---------- Previous post was at 08:30 PM ----------

Im not sure... I'm rooted, and with the update.zip in /cache there was an attempt to update which failed.. then I temp booted a CWM img, installed the zip and all is good.. ITL41F goodness...
[Samsung Galaxy Nexus] forumache:
Glad to see that someone gave it a try. I was pretty sure it was going to work, but I had no Galaxy Nexus to test (it will come over here in December and I'll be the first in line to get one).

Usually I work with the phone as a surgeon works with a human body, trying to operate as little invasive as possible: why flash the custom recovery and loose the original, when you can get the same result without leaving a trace.

Anyway, thanks to all of you guys for the posts here, I now feel confident in buying my new Nexus...
[Samsung Galaxy Nexus] ferris2375:
Sorry to ask again but can a rooted phone be updated? My OTA update brought me to the dead Android screen. I had to pull the battery and update via CWM. Is that how I will have to do future updates as well?
[Samsung Galaxy Nexus] Skysurfer69:
Bah! Bloody hell! Why is it that you wait for what seems an eternity for this update to come out and then it gets drip-fed to a) those who never needed it in the first place, b) haven't been that interested, or c) overly concerned about it.

My mate just messaged me to say he's got the update and "reckons it's fixed the volume bug"...

Further digging from me however has yielded sweet FA as he's currently down the pub getting leathered.

Yours,

Sky

Frantically refreshing the "Check Now" button
[Samsung Galaxy Nexus] oscillik:
Must say, I'm not impressed with this trickle 'roll out'

The update is less than 1MB, and there cannot be any more than 10,000 handsets in the wild at the moment.
[Samsung Galaxy Nexus] macfre:
Successfully applied the update

I couldn't wait for the update to become available and I've just applied it manually via CWM recovery (by downloading it from google.com via the link posted earlier on this forum and applying it manually).

Seems that it fixed the issue, I couldn't reproduce the problem by enforcing 2G mode on two phones (Nexus and other samsung phone) and putting them close together. Earlier it worked (triggered the volume bug) 100% of the time. I'm on the 900Mhz network.

For those interested, uname -a before and after the update:

Before:

i.imgur.com/Qx2tA.png

After:

i.imgur.com/sUsnD.png

Oh, and yes, I lost root access somehow mysteriously. Anyone know how it's possible? It didn't overwrite entire /system after all, su should remain there with suid..
[Samsung Galaxy Nexus] Nebucatnetzer:
I have something for you mate. Prevents your F5 button from getting broken ;).

Auto Refresh Plus plugin for Google Chrome

Edit: sorry read it wrong.
[Samsung Galaxy Nexus] spences10:
Cheesed off that the NFC hasn't been fixed!

Wasn't really bothered by the volume bug although I did suffer with it
[Samsung Galaxy Nexus] oscillik:
I think he meant the "check now" button on Android in Settings > About phone > System Updates
[Samsung Galaxy Nexus] Garner:
Could also try *#*#checkin#*#* to make sure ur device is syncing with google servers peope :)
[Samsung Galaxy Nexus] oscillik:
the Check Now button in Settings > About phone > System Updates does exactly the same
[Samsung Galaxy Nexus] FISKER_Q:
As far as i know the script will automatically do new permissions on all files in the system directory, including removing the permissions from su.

Have you tried to see if the bug persists in fastboot or recovery? Does seem like it patched atleast the recovery.
[Samsung Galaxy Nexus] jms.flynn:
Thanks, but didn't help. I'm still not on Google Christmas card list..... they are not on mine either. :mad:
[Samsung Galaxy Nexus] neovisage.HD2:
Boo still nothing for me boo,but anyway i wanna swap GN for motorla razr !i was lost trust to Samsung
[Samsung Galaxy Nexus] braingravyuk:
I was thinking this too..

On a side note, turning the phone on with volume down pressed, taking me into Odin mode, is there anything you can actually do here? Just seems stuck on Downloading... and if I press the power button again it just boots up.
[Samsung Galaxy Nexus] marky9074:
As I said before... it doesnt seem to.. it failed for me, albeit I was trying to manually force the update by putting the zip in /cache
[Samsung Galaxy Nexus] Rubu:
As Paul O'Brien confirmed it was the same patch he released earlier, we kind of already knew it was going to work -what I'm more interested in though, is whether you can detect a spike in CPU load when you attempt to induce RF interference.

Anyone lucky enough to have already received the OTA willing to try this out?
[Samsung Galaxy Nexus] macfre:
I didn't try fastboot.

My recovery image is broken now (it displays Android with red triangle, nothing else). I had CWM recovery image installed earlier, and I believe this update applied binary patch to the recovery partition as well, expecting stock recovery image there, and thus it broke my CWM image. I need to flash it again.

Speaking of which, does anybody have (or know where it can be found) stock recovery image?
[Samsung Galaxy Nexus] burk3:
My update failed. Here is the output:

-- Installing: /sdcard/11bbbccb08d5.signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
Finding update package...
I:Update location: /sdcard/11bbbccb08d5.signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
Verifying current system...
file "/system/app/NfcGoogle.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/NfcGoogle.apk", "a04648dbbac0f4abe8ed2ed858aa0f1354d5b1b9", "567fe6219b90801ba149e51a6e8091b6a4d939f2")
assert failed: apply_patch_check("/system/app/NfcGoogle.apk", "a04648dbbac0f4abe8ed2ed858aa0f1354d5b1b9", "567fe6219b90801ba149e51a6e8091b6a4d939f2")
E:Error in /sdcard/11bbbccb08d5.signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
(Status 7)
Installation aborted.

Modifications I have applied:

CWM (obviously)

Superboot r3

Google wallet flashable

Any suggestions?
[Samsung Galaxy Nexus] macfre:
Certainly not CWM. My update succeeded and I had CWM installed.
[Samsung Galaxy Nexus] LadFromWales85:
Flashed the update with clockwork, corrected permissions for su. The update will not blindly patch over clockwork as the md5sum won't match. Held an on call o2 phone near my Nexus, no craziness. Not going to bother checking for CPU spikes, as if this fault were fixed before launch we'd never have known or looked for it.

To the people asking if they will have to jump through hoops whenever an OTA comes around if they are rooted...yes! Though if you are simply rooted and haven't flashed over recovery, it's as simple as letting the OTA run, then booting clockwork and correcting the permission for su.

If you've flashed clockwork, then chances are you'll be flashing custom ROM's that'd get OTA's included within them anyway!

Liking my Nexus so far, hoping to love it soon! ;)
[Samsung Galaxy Nexus] forumache:
Yes, restore NfcGoogle.apk from backup. I hope you made one before flashing Google Wallet.

Otherwise, try to flash the original system.img and then apply the update.
[Samsung Galaxy Nexus] burk3:
Anyone feel like posting theirs? :o

EDIT: nevermind, going to use this as an excuse to try the modaco rom. Thanks anyways!
[Samsung Galaxy Nexus] winwiz:
Software Update versions:

Phone issue resolved

Kernel: 3.0.1-GA052F63

Build: ITL41F

---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------

update has fixed the volume problem
[Samsung Galaxy Nexus] spences10:
You need to reflash cwm recovery once you have flashed the update it restores the recovery to the stock one

I used these instructions to get root back: http://xdaforums.com/showthread.php?p=19465384&posted=1#post19465384
[Samsung Galaxy Nexus] marky9074:
I don't think you have a broken recovery.. I had the same graphic when I was farting around with the phone completely stock, before my first boot... seems like you have reverted back to a stock recovery..
[Samsung Galaxy Nexus] macfre:
Well, it certainly did something to my clockwork image because it was working before applying the update, and is not working anymore now.

What's the fastest way to correct su permissions? I just booted insecure boot image and did it manually via adb, but maybe you know a faster way?
[Samsung Galaxy Nexus] rojach:
Has anyone that is on O2 got the OTA yet?

Can't believe orange (not on GSM 900mhz so don't have issue) have the update before O2 (900mhz Major issue!!!!) wtf?
[Samsung Galaxy Nexus] bleets:
somehow i doubt they're rolling updates out based on network
[Samsung Galaxy Nexus] forumache:
Yes, it did something, it removed it at put back the default recovery. It's all written in the update-script in folder /META-INF/com/google/android/ of the downloaded OTA zip file.

A faster way to get root would be to boot into custom recovery (no need to be root for this, see my previous post) and flash the superuser from the developer of superuser here: http://androidsu.com/superuser/

I guess (since I don't have yet the Galaxy Nexus) that the last version should work, after all the theory is the same: copy a file to /system/bin, link to it from /system/xbin, done. You can check the update-script included in the superuser zip file just to see what it will do when flashed from custom recovery.
[Samsung Galaxy Nexus] macfre:
Uhm in that case.. how stock recovery is supposed to work? It just displays that weird graphic and soon reboots itself automatically.
[Samsung Galaxy Nexus] marky9074:
That's a good question... as I don't have CWM installed, and have stock recovery, I expected it to work by putting the zip in /cache but it didn't :confused: but I could see from the log that it did try and do something..

As for the recovery all I can say is that is exactly what I had with the stock recovery with the phone straight out of the box...
[Samsung Galaxy Nexus] rojach:
Any O2 GN With OTA Yet?

I know, frustration is getting the better of me, :mad:
[Samsung Galaxy Nexus] macfre:
So, you did flash via clockwork only to get the update faster, and you believe you would have the OTA normally if you simply waited?

Sorry, I'm learning how various Android internals work. My understanding was that since rooting basically requires only putting a few binaries to /system and giving them special permissions, it shouldn't affect OTA updates in any way, but other people here got me confused.
[Samsung Galaxy Nexus] mehalaktas:
What about the sim free ones. I bought it as sim free from Phones4u.
[Samsung Galaxy Nexus] jms.flynn:
Updates won't be sent like that, its when your IMEI is flagged for the update.
[Samsung Galaxy Nexus] mehalaktas:
Thanks for the information but I am really wondering why it takes that much time to update these mobiles. I think they did not sell a lot because of this problem so it should be faster I guess
[Samsung Galaxy Nexus] gregounech:
Anybody got a backup of the original framework-res.apk ?

It does not want to update because of Paul's backlight mod.
[Samsung Galaxy Nexus] jmbillings:
I'm sure someone will have answered already, but to people who are asking about if you will get the OTA if you're rooted, the answer is "yes".

I had *only* applied the superboot root process (see the dev forum) and I hadn't applied CWM or Paul's modifications though, if that makes any difference.
[Samsung Galaxy Nexus] samizad:
Apologies if this has already been asked before but I would like to know whether the OTA update would happen if I am abroad. My UK network is O2 but I am in South Korea. Or do I have to wait until I go back to the UK and establish connection with O2 network before I get the update?

Screw it. I'll just wait for a ROM that has the official fix and I'll flash that.
[Samsung Galaxy Nexus] LadFromWales85:
I flashed the update using clockwork because I have flashed clockwork so the ota would likely fail to run if I let it occur.

Flashing ota's onto rooted phones or is generally frowned upon as they can remove things you had, like root, or overwrite your recovery. In the case of other phones, it could lock you out of gaining root again, or leave you with an unbootable phone.

Its for this reason that ota's are generally disabled on custom ROMs.

But with the Nexus you will always have fastboot which can flash system images or a new recovery etc.
[Samsung Galaxy Nexus] macfre:
Thanks. Due to what I learned today, I'm not going to flash CWM anymore, instead I will boot it on-demand, without flashing it, via fastboot. That should keep me enabled for future OTA updates.

Also, apparently there's another shortcoming of flashing CWM on ICS devices: if you encrypt /data (new option in ICS), you won't be able to do factory data reset from the phone menu. You will have to do factory reset manually, neither the one from menu, nor the one in CWM works if device is encrypted. ;)
[Samsung Galaxy Nexus] Chirality:
I think I figured out the bug in Google's ITL41D kernel.

In drivers/gpio/gpio-omap.c, lines 482-485:

static inline void _set_gpio_irqenable(struct gpio_bank *bank, int gpio, int enable)
{
_enable_gpio_irqbank(bank, GPIO_BIT(bank, gpio));
}

"enable" is passed in as a boolean to either enable IRQs or disable them. But this code is not checking the value of enable, it's always calling _enable_gpio_irqbank, and never calls _disable_gpio_irqbank. This results in a situation where if you try to disable interrupts, you actually end up enabling them.

Note that I was only able to find this because an earlier commit in the source tree fixed this bug. But this commit was reverted before the code was built for release. This suggest that there's some deeper problem with the GPIO interrupt masking code, which forced Google to release the broken version that never masks interrupts. Hopefully the new kernel fixed the root cause of this bug. Guess we'll find out once the new code is pushed to the source tree.
[Samsung Galaxy Nexus] matt2053:
Actually, it's Maguro, Yakju, AND Tuna. From build.prop:

model=Galaxy Nexus

brand=Google

name=Yakju

device=Maguro

board=Tuna

For reference, on the Nexus S we had:

model=Nexus S

brand=Google

name=Soju

device=Crespo

board=Herring
[Samsung Galaxy Nexus] rs20:
Regarding the assumption about level of interference, it's worth noting the distinction between the button down (button line is shorted hard to ground) and button up (button line is weakly pulled up by a large resistor.) So while the interference might cause the signal to swing wildly and look insane when the button is up, I find it hard to believe that the signal wouldn't be pure, clean digital zero when the button is down. Adjust the software/firmware to work around this principle, and it's all good. Edit: But yes, I concede that this is based on another assumption, that the button-press is strong enough to pull the noise to ground, but I feel very confident about this assumption.

You were doing so well until you said "other phones can cause the interference therefore this isn't a software bug." This stunning false dichotomy seems to be the core of all this confusion. Yes, the problem has its roots in hardware, but the best solution might be in software. There's no contradiction there.

Regarding the iPhone, as I alluded to in my original post, engineers are concerned with fixing the problem 100% in the most inexpensive way possible, not fixing every problem at the root cause. Solving the problem at the root cause is, of course, generally 'elegant' and 'beautiful', but this isn't what the end consumer would (normally) want. Some xda members excluded :P

Probing traces with EMI is notoriously difficult because the oscilloscope loads down the EMI and makes it disappear -- but it's still definitely worth a shot.
[Samsung Galaxy Nexus] kristovaher:
Seems like we are at the end stretch. I still haven't gotten the update, I truly hate how slow this small fix is rolling out since I still can't use my phone for calls and persistent data connection.

But I'll be updating the first post to close things off.
[Samsung Galaxy Nexus] marky9074:
Whilst I'm not going to dissagree with you.. I can say that this is not what happened to me. I had stock recovery, and superboot, the update ran, the log was produced, then when I booted up nothing had happened...

I therefore temp booted CWM, flashed the zip, and all was well.. I too am very interested to see if this would have worked OTA. To be honest I am accepting blindly the information here that all you need to do is place the update.zip file in /cache, which I must say did get picked up and the install attempted, but on reboot no beans...

...edited: Actually now I think about it, my rooted and CWM Xoom has had many OTA updates pushed to the tablet, but none of them have installed, all of them falling over in recovery.. but that maybe was because I had CWM as recovery.
[Samsung Galaxy Nexus] rbs_uk:
I got my phone from Handtec yesterday and I have this volume bug :mad: Phone saying system is up to date and no updates available :(:mad:
[Samsung Galaxy Nexus] Terrahawk104:
Well the stock being held back so Samsung could flash the devices was a lie as expected. I live in a place where 3G is almost non-existent (indoors anyway) and as soon as I turned wi-fi off after the initial setup the volume went absolutely nuts. The Android version is still 4.01 and the kernel version is the same as people who bought the phone day one. No OTA update notification yet either and I've tried 'Check Now' in the settings under About Phone.
[Samsung Galaxy Nexus] bleets:
yeah we've already established earlier in the thread the handsets werent getting pre-flashed. retailer has said that already. just wait for the OTA to roll out, it isnt going to all handsets at once. rolling firmware releases are normal.
[Samsung Galaxy Nexus] Terrahawk104:
With all due respect that was pure speculation though. Because of the nonsense they put out there about different batches being shipped we've had to wait and see how these newly shipped phones turned out in terms of the kernel version based on fix that was put out there and the newly released/shipped German devices for example which had the same kernel version as the fix out of the box.

I'm not panicking anyway by any means, it's a gorgeous device and I'm loving ICS so far. Looking forward to the OTA for sure. :cool:
[Samsung Galaxy Nexus] marky9074:
Paul just posted the stock updated ROM:

http://xdaforums.com/showthread.php?t=1371054

---------- Post added at 10:51 AM ---------- Previous post was at 10:48 AM ----------

How do wifi only devices receive OTA updates then :confused: (tablets?)

---------- Post added at 10:52 AM ---------- Previous post was at 10:51 AM ----------

Stock image from Paul here:

http://xdaforums.com/showthread.php?t=1371054
[Samsung Galaxy Nexus] kristovaher:
It is highly unlikely that IMEI is what is used to push updates. Android devices carry other means of identification:

http://android-developers.blogspot.com/2011/03/identifying-app-installations.html
[Samsung Galaxy Nexus] Fpad77:
Yeah still waiting here too.
[Samsung Galaxy Nexus] qwerp_:
news from android central.

google has release official bug fix.

http://m.androidcentral.com/how-manually-flash-ota-your-galaxy-nexus

download it here stright from google.

http://android.clients.google.com/p....signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
[Samsung Galaxy Nexus] kristovaher:
This is already posted pages ago already. And that covers the same thing as already discussed before, you cannot apply the fix easily yourself.
[Samsung Galaxy Nexus] darkoroje:
You can apply the fix yourself like this:

1. Get ROM manager from Market and flash ClockworkMod recovery

2. Download the update from Google and copy it to your \sdcard

3. Boot into recovery (from ROM manager)

4. Select "Apply an update from sdcard", then select the update file
[Samsung Galaxy Nexus] Terrahawk104:
I'm an Android noob in that I've never rooted an Android phone before or done anything outside of stock, I'll wait for the OTA update myself.
[Samsung Galaxy Nexus] qwerp_:
i don't think so, for those that has not unlock, they should just need to rename it to update.zip, reboot into recovery and apply update from update.zip and everything should be on track.

how hard can that be?
[Samsung Galaxy Nexus] ref1ux:
Still waiting on the update here. A mate who's on 3 got his last night, which sucks because he doesn't even need it :(
[Samsung Galaxy Nexus] bleets:
thats not entirely true since the fault would affect him if somebody was using a 900mhz phone nearby. he would indeed need it, you're just too selfish to see that.
[Samsung Galaxy Nexus] kristovaher:
We all need it. This is unbelieveable that an OTA that is in size less than 1MB takes so long to roll out. Imagine when next version of Android comes out, you'd be waiting for months if this is any sign.
[Samsung Galaxy Nexus] bleets:
considering the fact that google (apparently/supposedly) rolled the update out to 1000 updates initially and it's been said the updates will be rolled out over the course of a week, it's safe to assume they're doing limited releases to see if any issues arise etc. google do limited user beta tests on other products, why not OTA android updates? :)
[Samsung Galaxy Nexus] oscillik:
This requires you to unlock the bootloader, something that some of us are not willing to do due to it erasing the entire phone.

This doesn't work, I have already tried it. Recovery only allows you to flash an update from the /cache directory, and you need root to be able to write to this directory.