yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] paladin82:
I got my rooted stock Nexus updated to 4.0.4, but lost root. Thanks to your post I am back to rooted!!

Thanks:)
[Samsung Galaxy Nexus] adrynalyne:
I wouldn't normally either, but I went to stock recovery so I could get signature checking in.
[Samsung Galaxy Nexus] bfroehlich:
So true. Didn't even think of that :)
[Samsung Galaxy Nexus] Laynee1:
And what about GSM GNexes? Are they getting some updates soon ? :)
[Samsung Galaxy Nexus] 105437:
The OP said he received an update message on his GNex. Shouldn't we have heard from others who received the message too? I'm glad we got the update but I'm left wondering about the OTA update message.
[Samsung Galaxy Nexus] a1exus:
is anyone else is getting ota notification for update? i want to update, but i want to get ota from verizon/google/samsung
[Samsung Galaxy Nexus] xnuxer:
in indonesia still 4.0.2 :(
[Samsung Galaxy Nexus] adrynalyne:
This update is not being pushed at this time.

If you want it, you can have it, but its not official until it starts to push.
[Samsung Galaxy Nexus] 105437:
That's my question... how did the OP get the OTA update message???
[Samsung Galaxy Nexus] adrynalyne:
Unicorns?

Who knows. Random mess up or maybe he was just a lucky random person. Either way, official links are posted in the general forum. Its real.
[Samsung Galaxy Nexus] KWKSLVR:
My understanding is that OTA's will sometimes get released out into the wild in random, small test batches. I know there are people that have gotten OTA's on devices in the past before the masses get them.

---------- Post added at 11:53 PM ---------- Previous post was at 11:44 PM ----------

Looks like a good guess from myself. http://www.androidcentral.com/verizon-galaxy-nexus-android-404-ota-package-now-available
[Samsung Galaxy Nexus] xguntherc:
hmm.. Any tips for flashing this on the stock recovery?

I'm on stock 4.0.2 and I'm rooted and unlocked, but stock recovery. Just gets an error though when I try to flash through recovery. I get the red warning sign.

Thanks!
[Samsung Galaxy Nexus] matt30:
Get the file, name it update.zip, place it in /cache.

Reboot into recovery. Once in recovery you will see the red exclamation point. Press power and Vol+ to get to the menu. Flash update.zip. All done!
[Samsung Galaxy Nexus] strifejester:
Anyone seen a link from https://android.clients.google.com/ yet? Once I see that link I will dive in but until then no dice.
[Samsung Galaxy Nexus] adrynalyne:
The front page...or a search might be fruitful.
[Samsung Galaxy Nexus] strifejester:
Read 22 pages didn't find it all I find are media fire links that is why I asked but thanks for being a tool. Spent an hour this morning searching threads with no luck so thank you for wasting more of my time having to reply to this.
[Samsung Galaxy Nexus] efrant:
http://xdaforums.com/showpost.php?p=22215086&postcount=258
[Samsung Galaxy Nexus] akanatrix:
He's not being a tool. He's pointing out the fact that you did not try very hard when it's on the first page of threads. People need to grow some thicker skin.
[Samsung Galaxy Nexus] strifejester:
Thank you I missed that one. At least you were not a **** about it.
[Samsung Galaxy Nexus] adrynalyne:
You know what? I put in the legwork and spent the time (a couple hours) to get those URLs when nobody else did/would. The least you can do is look at the titles of the threads on the first page and read up some. I don't post things for people to not read or search.

Stop being so damn inconsiderate. The couple of hours it took for me to find them and get my phone back to where it was before is a lot more time than it takes for you to look at the threads on the first page.
[Samsung Galaxy Nexus] strifejester:
Really I missed it on the first page for me and Nexus Google Links does not work or a few other searches. Maybe if this site actually utilized Stickies properly in half the threads it would be easy to find.

---------- Post added at 10:20 AM ---------- Previous post was at 10:17 AM ----------

Which is why instead of being a tool and posting for a search you could have just linked again I said I overlooked that one. **** happens. In the time it took you to tell me to search better you could have just posted the link you think I am the only person here who read about 15 pages and got sick of it because there was 0 useful information provided about it in those pages? And I was trying to figure out the link myself, legwork as you call it but I was having a hard time finding my original update info and forgot they call this verizon_prime.
[Samsung Galaxy Nexus] efrant:
Easy to overlook. There's no need to be a ****. :)
[Samsung Galaxy Nexus] adrynalyne:
I worked hard to get those URLs, and for free. Stop being so damn selfish and just look next time. Typical me me me attitude.
[Samsung Galaxy Nexus] nhizzat:
typical my-time-is-more-valuable-than-your-time attitude.
[Samsung Galaxy Nexus] jhollon:
i downloaded the update and tried to flash this a number of ways and it aborts everytime. I have tried to rename and do other stuff to no avail. It keeps complaining about apply_patch_check not liking /system/app/launcher2.apk. i cant figure it out. the only thing i have done besides unlocking and rooting is to do the hack for removing the permanant google search bar and be able to use the space it left behind as blank. Now if that is what caused it, then i am not sure how to reverse it to get the update.

Please help me. I really don't want to take it back to stock and have to loose everything even if i do use TiBU.

thanks Again
[Samsung Galaxy Nexus] adrynalyne:
You need to be 100% stock to get this working. I cannot stress this enough.
[Samsung Galaxy Nexus] efrant:
Get a stock launcher2.apk from someone and restore it. Otherwise, you can try removing the assert for the launcher2.apk from the updater-script file in the update, and try again using CWM (although I would recommend the former instead of the latter.
[Samsung Galaxy Nexus] jhollon:
any idea on where i could get one online?
[Samsung Galaxy Nexus] shoman24v:
How does one put the OTA in the cache folder? Im 100% stock
[Samsung Galaxy Nexus] efrant:
Nope, but I'm sure it's floating around somewhere. Maybe try asking in the thread that you got the modified one from...

You cannot unless you have either: an unlocked bootloader, CWM installed, or root.
[Samsung Galaxy Nexus] diverbelow:
Currently on my stock 4.0.2, GN I have the following:

*Does it have the random reboot, like it currently does on 4.0.2; or too soon to say?

*On 4.0.2 while connected to WiFi and you select the WiFi sleep to never, when waking up the phone the WiFi was off. On 4.0.4, does the WiFi stay on?
[Samsung Galaxy Nexus] matt30:
Not true.

Go to the FAQ thread. You don't even need to be unlocked.
[Samsung Galaxy Nexus] akanatrix:
The FAQ says you must be unlocked, but you don't have to be rooted.
[Samsung Galaxy Nexus] efrant:
I'll say it again. You need ONE of the following:

An unlocked bootloader;

A custom recovery installed;

Root access.
[Samsung Galaxy Nexus] matt30:
ninja

...
[Samsung Galaxy Nexus] RW-1:
One issue I've noted, and wondering if anyone else can duplicate or has a fix for is this:

Seems the selected ringtone for the unit doesn't start at the beginning when the phone rings anymore, it starts in the middle (Only way I can describe it. I had the stock "Ariel" tone, which plays up in volume, when the phone rings now it blasts the middle part descending tones, then begins again) ...

Anyone else? Have rechosen another tone and same thing, wondering what I might have to clear data or cache et. to clear that out if possible or wait for next update.
[Samsung Galaxy Nexus] :
I haven't been able to recreate the ringtone issue above. However in my quest to do so I just logged in to a website to download a ringtone, where my user name is part of the dictionary. So I chose the correct word from the predictive text menu to speed things up. It entered that word in the user name box and then went to move the cursor to the password box and it placed a duplicate user name in the password box? Was able to replicate it over and over? Tried all clearing all browser settings (cache, stored passwords etc) and it happened again? Not sure what is going here but I'll take a look when I have some time later.

Anyway I downloaded a ringtone and confirmed it does in fact start from the beginning when my phone rings. So I'm not sure what is going on there......
[Samsung Galaxy Nexus] Tomson74:
Can anyone tell me if the muted mic during phone calls has been fixed?
[Samsung Galaxy Nexus] Pupalei:
Sadly, it has not.
[Samsung Galaxy Nexus] Tomson74:
That truly sucks.
[Samsung Galaxy Nexus] blomgren:
Question- I haven't seen this anywhere, but has anyone rooted a nexus without unlocking it? Or even just temp root?
[Samsung Galaxy Nexus] efrant:
I don't think so. I have no idea if zerg rush would work (I highly doubt it).

It hasn't really been necessary as the GN has an unlocked bootloader.
[Samsung Galaxy Nexus] martonikaj:
Not sure why you'd want to do this?
[Samsung Galaxy Nexus] blomgren:
Because I didn't unlock prior to loading pictures and music on the Nexus. I don't really want to reload everything. Not the quickest transfer process with the Nexus.
[Samsung Galaxy Nexus] sblantipodi:
is there someone else who received the 4.0.4 ota update here?
[Samsung Galaxy Nexus] Blakeman:
Can you download this to a GSM galaxy nexus to update or does it have to be rooted etc?
[Samsung Galaxy Nexus] martonikaj:
You're gonna have to unlock. So copy your stuff over and copy it back after you're done. Just part of the deal.

Its not rolling out. No one else has it officially. Its not an official OTA yet.

NO YOU CAN'T. You will severely mess up your device. You must be rooted and flash a GSM ROM that has implemented the 4.0.4 tweaks.
[Samsung Galaxy Nexus] Blakeman:
Does anyone know, can you update to 4.0.4 by downloading this directly to your phone?
[Samsung Galaxy Nexus] pchoi94:
hi all, i created a poll to track the issue by location, if you have time to participate that would be great! thanks!

http://xdaforums.com/showthread.php?t=1545621
[Samsung Galaxy Nexus] iPathik:
No OTA for GSM Nexus?? :( I am frustrated at Google right now...
[Samsung Galaxy Nexus] sblantipodi:
no update till now, I will not buy a google phone next time, I bought a nexus for the google experience but here there is no google experience.
[Samsung Galaxy Nexus] neoKushan:
How is there no "google experience"? So what, the CDMA variant has a 0.0.1 lead on the GSM one, are you actually getting shafted in ANY way? Is there a single other device out there running anything newer? Grow up.
[Samsung Galaxy Nexus] miketoasty:
You're an idiot. "Google Experience" is having a pure Google installation on your phone from the get go. Which you have just by owning a GNexus. Please don't talk about things you don't understand.
[Samsung Galaxy Nexus] arvylas:
You can allways buy a sony and run froyo if you don't like 4.0.3
[Samsung Galaxy Nexus] adrynalyne:
I will put it in big easy to read words for you.

GOOGLE EXPERIENCE REFERS TO A PURE VANILLA OS.

I know it is difficult to comprehend.
[Samsung Galaxy Nexus] :
So you're going to get another brand of phone? HTC, Motorola? You'd be in a worse position than you are now regarding updates.
[Samsung Galaxy Nexus] supernova_00:
Has google put any information out regarding our Nexus since the phone was released? I haven't seen any blog posts with status updates, seen a comment in any bugs regarding ICS bugs, nadda.
[Samsung Galaxy Nexus] champers:
The Xoom and GS II are updated to 4.0.3 I believe.
[Samsung Galaxy Nexus] adrynalyne:
A .01 variant. Thank you for proving his point.
[Samsung Galaxy Nexus] josteink:
It's not a big difference, but people buying Nexus phones expect to receive the updates first.

When the ICS Nexus reference-device doesn't even get "baseline" ICS (which is 4.0.3 according to JBQ), before stock, normal vendor-phones get it, I can see why he gets upset. Heck. The source has been out for months. What's the problem here? Where is our OTAs?

GSM Galaxy Nexus devices are not on baseline ICS. They are technically "unsupported" for ICS apps on the market.

As for being a "small" 0.0.1 update, it's also the update enabling USB OTG storage. So yeah.

We should have had it before everyone else, pretty much by definition. Somehow Google decided to release the source but not push any updates. And now vendor-phones and devices are walking past the Nexus in updates.

And Google haven't really been very clear as to why they are doing this. I think that is the biggest problem we are experiencing here.
[Samsung Galaxy Nexus] adrynalyne:
4.0.1 was baseline ICS for all devices other than the Galaxy Nexus.

Which was updated to 4.0.2. You are taking things out of context.

Uh...no it doesn't. 4.0.3 users have to use Stickmount was well.
[Samsung Galaxy Nexus] josteink:
In that case, my bad.

I still say that JBQ announced 4.0.3 as baseline ICS. When other phones are receiving it, it looks weird that the Galaxy Nexus doesn't.

Again, I think the biggest issue here is not the digits, but the lack of communication from Google.

Edit: And I guess our complaints are just silly-putty compared to those of the Nexus S owners.
[Samsung Galaxy Nexus] adrynalyne:
JBQ is correct. 4.0.3 is baseline for all non Galaxy Nexus devices. To be clear though, JBQ only speaks in terms of AOSP, ever. He does not speak outside of what he does and knows (which is purely AOSP).
[Samsung Galaxy Nexus] AdamLange:
As in mine understanding, if we got phone from google, and as they stated, this is their phone, so where is google support in that? where i can call instead of samsung and ask for update?

As my understanding is , if AOSP official is 4.0.3 then with release of this branch we should get OTA and factory images at the same time.

Samsung just released ICS update for SGS2 , it's 4.0.3 !!

After SGS, SGS2 and now nexus should i go for apple ****? really? :/
[Samsung Galaxy Nexus] adrynalyne:
Incorrect. Images and OTAs are built from a private branch, not AOSP. The only reason 4.0.3 is on AOSP is because it was pushed out to some devices and JBQ was given authorization.
[Samsung Galaxy Nexus] AdamLange:
So brands like samsung and htc are using AOSP sources for their shipping images?

if not then 4.0.3 is complete and tested, so why first-in-line phone didnt get it?
[Samsung Galaxy Nexus] adrynalyne:
No....

This is a common misconception amongst users.

There are many private branches. There is only one public branch.
[Samsung Galaxy Nexus] AdamLange:
Lets make it clearly, main and latest branch is 4.0.3 and its pushed to AOSP.

Vendors (in their branches) are using 4.0.3 (they cant change version, just make tweaks and addons for it before release to customers)

We still got 4.0.2 , even if 4.0.3 was pushed to vendors and to public branch.

I dont see a point here to NOT release this as OTA/factory images. Everyone is using it now, why we as first-in-line as google says dont have this update yet?
[Samsung Galaxy Nexus] adrynalyne:
Maybe because it does not fix the bugs that Google knows needs fixing?

Just a thought.
[Samsung Galaxy Nexus] matt30:
I believe it's possible to use an insecure boot img to gain temporary root access to push update.zip via adb.
[Samsung Galaxy Nexus] adrynalyne:
You would have to use an exploit to do so.
[Samsung Galaxy Nexus] virtualcertainty:
Just because it was ready for vendors doesn't mean it was perfect and bug free for every device on the market. Vendors still need to test it on every device AND put their tweaks and addons in. That can take months to test and certify for each device they are upgrading to ICS. That's why it takes so long for non-nexus devices to get updates. Well, that and the vendors are cheap and lazy.

Same goes for Nexus S. Google obviously thought they had a build tested well enough to push it out. That didn't go so well and the update was stopped. Was it a problem with AOSP itself or just getting it to work on the Nexus S? Who knows.

Perhaps the same deal with the Galaxy Nexus. Just because AOSP source is 'ready' for vendors to begin work on doesn't mean it fits like a glove on the Galaxy Nexus. Yeah, many dev teams have been able to grab the source and produce some roms, but that isn't the same as getting an official OTA through certification for consumption by hundreds of thousands of stock devices. A modder has a problem with a custom rom and he switches roms. Google has a problem with an update that affects just 2% of users and there is mass hysteria which damages the Android brand.

It obviously isn't ready or it would have been OTA'd by now.
[Samsung Galaxy Nexus] efrant:
It has now been done: http://xdaforums.com/showthread.php?t=1531865

---------- Post added at 12:03 PM ---------- Previous post was at 11:58 AM ----------

How would you boot that insecure boot image with a locked bootloader? Can't be done.
[Samsung Galaxy Nexus] matt30:
It was my understanding that a locked bootloader only had NAND protection and would allow you to directly load different boot instructions directly into ram.
[Samsung Galaxy Nexus] adrynalyne:
But how would you do that? Fastboot is not fully functional unless unlocked.
[Samsung Galaxy Nexus] efrant:
To echo adrynalyne, you cannot use fastboot commands to flash or boot unsigned images, so trying to boot an unsigned boot image will not pass the bootloader's signature check if the bootloader is locked. A locked bootloader will disallow fastboot commands if the image is not signed.
[Samsung Galaxy Nexus] Dookert:
Ridiculous problem

Okay, so I recently flashed this rom. Works great, nice and fast, noticeable improvements all around.

Before I flashed it I was running stock 4.0.2 rooted

Upon flashing it Ive lost root privilages. So I go to reroot using a terminal in ADB "adb reboot bootloader"

I get to fastboot, hit recovery, and I get the freakin exclamation point. After scouring around for an answer one such solution seems to be to delete the file /System/boot.p

I hit mount as R/W in root explorer, attempt to delete the file with a press and hold and tapping delete. I get the message that the file cannot be deleted because it is read-only. Im guessing I cant delete it because Im not rooted(hence mount as R/W) but I cant boot into CWR and root SO i can remove it.
[Samsung Galaxy Nexus] ATnTdude:
Yeah, just boot into CWR and reflash the SU.zip.
[Samsung Galaxy Nexus] efrant:
Here's the deal:

1) Every OTA update changes the permissions on the su binary, so you effectively lose root access.

2) Every OTA update to date places 2 files on your ROM that are responsbile for re-flashing the stock recovery (which is what you are seeing, i.e., "the freakin exclamation point") on EVERY boot. As long as these two files exist on your ROM, your CWM recovery will disappear after a reboot.

What you need to do is re-boot you device into fastboot mode and flash CWM, then boot into CWM, delete those 2 files, then change permissions on the su binary, and you are all set.

Here's a step-by-step (which assumes you have the drivers for your device installed):

1) Download the attachment and extract it to a directory on your computer.

2) Download CWM, rename it to cwm.img and place it in the same directory.

3) Reboot your device into fastboot mode and plug it into your computer.

4) Open a command prompt in the same directory and do the following:

1) Flash CWM: fastboot flash recovery cwm.img

2) Boot CWM: fastboot boot cwm.img

3) Open a shell: adb shell

4) Mount the /system partition as r/w: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system

5) Change permissions on su (you will need the right path. mine is in /system/bin): chmod 06755 /system/bin/su

6) Change permissions on Superuser.apk (not sure this is needed, but it wont' hurt): chmod 0644 /system/app/Superuser.apk

7) Remove the first file: rm /system/recovery-from-boot.p

8) Remove the second file: rm /system/etc/install-recovery.sh

9) Mount the /system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system

10) Exit shell: exit

11) Reboot: adb reboot

12) Done.

EDIT: I like posting the manual way of doing things, as people learn when they do them that way. But yes, as ATnTdude said, once you boot CWM, you can just flash the su zip file, and it automatically does steps 4,5,6 and 9 for you. You still have to remove the two files yourself.
[Samsung Galaxy Nexus] Dookert:
Driver problem

Ive been trying to do this but when Im in fastboot I lose my phone as a device. It just comes up as an unknown device and that the driver installation has failed. Like the terminal comes up as "waiting for device" and it never gets any further because it doesnt see it. Like I said I can use a terminal to reboot the phone with adb but it loses it in fastboot, aka it doesnt see the phone. I will try rebooting my computer but all the drivers are correctly installed as well as fastboot and adb.
[Samsung Galaxy Nexus] efrant:
You need to re-install the driver for fastboot. Follow these steps.

And I personally would use this driver.
[Samsung Galaxy Nexus] Dookert:
Got it rooted

Ok. Got it rooted, it was a driver issue for fastboot. So I got my phone rooted again under this ROM, however, if I use quickboot or ROM manager to boot into recovery. I am still getting the exlamation point! I just wanted to make a nandroid backup of this with everything working and its still messed up. I deleted boot.p in the /system/ folder cause I read that that can keep resetting the factory recovery mode. What is up with this?

---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------

For now it looks like i have to resort to using the gnex toolkit to flash CWR and then I can get it to load. Very frustrating. Im researching this one as I've seen this problem comming up for people but if anybody wants to chime in and give me a shorcut its appreciated.
[Samsung Galaxy Nexus] efrant:
I already told you which two files to remove in this post: http://xdaforums.com/showthread.php?p=23662380
[Samsung Galaxy Nexus] Dookert:
Those files have been removed

Those files have been removed, specifically boot.p which I stated in the previous post has been removed. I do thank you for the help though.
[Samsung Galaxy Nexus] efrant:
My mistake. I was confused, because you referred to a file called boot.p in the /system directory, when the actual file is recovery-from-boot.p

By the way, if you had rebooted your device before removing the files, you would need to reflash CWM again.
[Samsung Galaxy Nexus] ZaelFaroe:
After having gotten sick and tired of waiting for Verizon I installed the version linked to in this post. I have noticed that my phone now has Trebuchet installed. I am 99.9% positive that I only had Nova and the default Home installed before this update. Has anybody else noticed any other apps that were installed with this update?

Nevermind. I was in error. Amazing the things we think we remember.
[Samsung Galaxy Nexus] EP2008:
4.0.4? Pffff... I'll be happy when I get 4.0.2 :rolleyes:
[Samsung Galaxy Nexus] jonnyg1097:
Oh I see. I had no idea.
[Samsung Galaxy Nexus] adrynalyne:
I didn't either until Google updated their branch documentation.
[Samsung Galaxy Nexus] joshnichols189:
The link in the OP says the update is 29mb. The second link in the thread says the update was 25mb.
[Samsung Galaxy Nexus] adrynalyne:
on a Samsung update channel eh?

Bummer.
[Samsung Galaxy Nexus] cshort0982:
"i think i should clarify that i have no technical skills which may be required for this.

i have a very basic understanding of root. i believe the app i use to explore, "andexplorer", is a root explorer as i can open the root folder. were it not for the easy gui of wug's rootkit, i probably would not be rooted.

basically, i have no idea what "adb shell" is. i'm sorry if i've started a something that i can't finish, but i can only assume that people far smarter than me will start to get this notification as well.

if i can find the file i'm happy to post it, but i'd just like to set some expectations here in case i can't. "

This is where we stand right now. Trying to walk the guy through it.
[Samsung Galaxy Nexus] adrynalyne:
Ok. Give me a few minutes to type something up.

I am banned from AC, so I can't help.