yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Konceptz804:
Coming from the 4.0.4 that was leaked earlier I'm not noticing anything different.
[Samsung Galaxy Nexus] AdelosMeansUnknown:
I've had quite the opposite effect. Still 92% after 3 hours
[Samsung Galaxy Nexus] adrynalyne:
Could simply be a switch was flipped prematurely and removing it until ready is their idea of damage control. This was being actively pushed to a lot of devices (even if mostly corporate) unlike IMM30B.
[Samsung Galaxy Nexus] eman3316@optonline.net:
After flashing the new radios last night, my phone kept a 4G signal on the 1st floor of my house for the 1st time. Always dropped to 3G before. Don't if it was a fluke or things really improved. Did not have enough time to test.

I think people looking for a better dbm level might not see that but people who's phones were not holding 4G in certain areas where other phones do might be in for a surprise.
[Samsung Galaxy Nexus] flascrnwrtr:
Reception is great, but I had no problem before. Battery is about the same on Liquid with Franco M3.
[Samsung Galaxy Nexus] miketoasty:
This is what I was noticing as well. dbm is about the same as previous radio's, but I am able to keep 4G longer and get it in areas that I couldn't before.
[Samsung Galaxy Nexus] ProfessorAsian:
https://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/

Follow those directions. They do work, quite well. Phone is still locked and non rooted, but with this 4.0.4 update.
[Samsung Galaxy Nexus] lrs421:
Thanks...looks really simple.
[Samsung Galaxy Nexus] byrds8:
I didnt understand all the command lines and such as for what to do. I am backing up some files now and thinking about using the tool kit since you remain rooted and locked once done with that too. I just wish I knew for fact this is better than 4.0.2 and no other issues have been found since it is not on googles servers anymore.
[Samsung Galaxy Nexus] kangxi:
I'm getting more consistent 4G as well at work. Usually I would be on 3G with the occasional spurt of 4G. I've been on 4G since I've gotten here.
[Samsung Galaxy Nexus] efrant:
There is no way to access /cache without root access, so his comment about non-root method is wrong.

EDIT: Just because once does not copy the su file to the device doesn't mean that there was no root -- the build was rooted (albeit temporarily) to copy the file over to /cache, and then root rescinded.
[Samsung Galaxy Nexus] biggiestuff:
Not completely true. I was able to update to the leaked 4.0.4 a while back w/o rooting my phone or unlocking the bootloader. I guess the steps I performed gave a temporary root so I could access that folder but it wasn't a full root.

Now i'm just thinking how I'm gonna get to this new 4.0.4 update w/o having to start from scratch. I don't think that's gonna be possible :(
[Samsung Galaxy Nexus] efrant:
My statement IS completely true -- there is no way to access /cache without root access. What's the difference does it make if it is temporary or not? ("Full" root as you so call it, is just a file copied to your device.)

There is no way without a bootloader unlock.
[Samsung Galaxy Nexus] byrds8:
How do you get into recovery mode? I hit the power button and volume button and its sitting there wiht the android saying downloading do not turn off target. doesnt do anything else.
[Samsung Galaxy Nexus] miketoasty:
You need to hit volume up and down at the same time while powering on. You are in mobile ODIN, so just battery pull and try again.
[Samsung Galaxy Nexus] ProfessorAsian:
Well sure I could have said temporary root access I guess. I just think that is confusing. If you say root, most people think they have super user access on the OS itself...

But whatever, let us all be sticklers.

You have to root to update. But the boot loader can remain locked, just use the default recovery.
[Samsung Galaxy Nexus] byrds8:
After I get in can someone explain how I do what this guys says on his site?

http://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/

I really dont want to unlock my bootloader and such so id like to do what he says but I dont really understand.
[Samsung Galaxy Nexus] efrant:
It's not about being a stickler, it's about getting your point out clearly, so that those who don't have the same in-depth knowledge as you won't get confused. This will avoid the: "really?? I thought you needed root? Cool..." posts from n00bs.
[Samsung Galaxy Nexus] ProfessorAsian:
Ha. These are mobile phones. Everyone and anyone has them.

I treat online as I do real life, I do not go around correcting technicalities, no one likes those people (I don't). I've given up on telling people that their storage is not memory or ram.

Do not do stuff to your phone people if you do not fully understand what you are doing. Just about anything other than waiting for the OTA update pushed from Verizon will require some type of work around.

In any case, this 4.0.4 has been great. The radios are quite improved as well. I do wonder if there will be another revision though, since Google has pulled the update.
[Samsung Galaxy Nexus] adrynalyne:
I do.
[Samsung Galaxy Nexus] centerwaters:
do I hold the volume buttons first and then press the power button?

or do I need to press/hold all three simultaneously?

thanks!
[Samsung Galaxy Nexus] pennie57:
All same time
[Samsung Galaxy Nexus] efrant:
Well, I treat it as real life as well. And maybe what I said before came across as correcting technicalities, but that was not / is not my purpose. The intent was to clear something up that can easily be confused in a one or two line post. I thought we are all here to learn and help each other understand, and make things better no? Maybe with this back-and-forth banter that we just had, it will spark some n00b's curiosity, and he may actually lookup what "temporary root" is or "super user access on the OS itself" and learn something new <- The whole point of this online community, in my opinion, of course...

---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------

Hold the vol+ and vol-, and then press and hold power.
[Samsung Galaxy Nexus] Greg525:
Question

So, I have a quick question. I unlocked/rooted/flash 4.0.4 last night, but stupidly I forgot to install root keeper first. I think I've now lost root, since I can't boot into clockworkmod recovery. When I try to boot into recovery manually, I get the android on his back.

I found a droid-life post (which I can't link to yet due to post count) and it said to flash a new superuser zip? Thanks for the help.

These were the instructions for droid-life:

1. Download this su.zip to your internal storage.

2. Download Clockwork Recovery and place in in your SDk/Tools or Platform-Tools folder.

3. From you Tools or Platform-Tools folder, open a command prompt.

*Wherever your adb.exe and fastboot.exe files are.

4. Type the following commands:

adb reboot bootloader

–wait for your phone to boot to the bootloader

fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img

–wait until the command prompt tells you it has finished

5. On your phone, scroll down to “Recovery Mode” and press the power button.

6. Your phone should boot into Clockwork Recovery.

7. Select “install zip from sdcard.”

8. Find the su.zip file that you downloaded earlier. Choose it and flash it.

9. Reboot your phone and you should now be rooted.
[Samsung Galaxy Nexus] efrant:
This will work -- you will have root access. However, CWM will not stick -- the stock recovery will automatically replace CWM. If that is what you were going for then - yup all is good.
[Samsung Galaxy Nexus] Greg525:
How I can I get root back and make CWM stick? I'd like to be able to flash rom's in the future.
[Samsung Galaxy Nexus] efrant:
Do what you had posted. Now that you have root access, go and delete these two files:

/system/recovery-from-boot.p

/system/etc/install-recovery.sh

Then do steps 1-4 again in your post. Done.
[Samsung Galaxy Nexus] Cozmosis:
Running AOKP M5 and flashed 4.0.4 bootloader and radio last night. Getting fantastic signal inside the hospital now - all bars full and mid 80s dbm. Can't be happier with it.
[Samsung Galaxy Nexus] spectrumfox:
Non root, locked bootloader instructions.

EDIT: Oops, my bad.. unlocked bootloader required.

http://xdaforums.com/showthread.php?t=1630349
[Samsung Galaxy Nexus] efrant:
Here we go again: that method requires an unlocked bootloader. You CANNOT flash/boot CWM (using fastboot) with a locked bootloader.........
[Samsung Galaxy Nexus] adrynalyne:
Having fun yet? :D
[Samsung Galaxy Nexus] lrs421:
LOL, I knew that temp root was required. Looking at the adb commands it's pretty straight forward.

Noobs: Learn adb, it's very valuable. Or just wait for the OTA.
[Samsung Galaxy Nexus] spectrumfox:
Very true, my bad.
[Samsung Galaxy Nexus] efrant:
Always! LOL :D
[Samsung Galaxy Nexus] lrs421:
All the toolkit does is perform the commands for you but flashing a new recovery requires temp root or root.
[Samsung Galaxy Nexus] spectrumfox:
I have been corrected. :)
[Samsung Galaxy Nexus] adrynalyne:
Please describe the science behind a bootloader locked, cwm temp boot.

Thanks :)

Fastboot is 100% disabled on bootloader locked devices. So how does it work?
[Samsung Galaxy Nexus] lrs421:
Yes, the root is temporary....so in the end you will still be locked and unrooted.
[Samsung Galaxy Nexus] adrynalyne:
I get temp root. I don't get the temp cwm.
[Samsung Galaxy Nexus] efrant:
You really think so? Please explain to me how the "Galaxy Nexus Toolkit" allows you to boot into CWM with a locked bootloader?

Yes, you can flash CWM: fastboot flash recovery cwm.img

Yes, you can boot CWM without flashing it: fastboot boot cwm.img

But both of those, require an unlocked bootloader.
[Samsung Galaxy Nexus] byrds8:
So using the toolkit doesnt unlock the bootloader and wipe the phone?
[Samsung Galaxy Nexus] spectrumfox:
Hah, you're the developer, you should know. All I know is I'm hearing nothing but success cases and not one person has complained about the method not working. Maybe they all have unlocked bootloaders, who knows.

Besides, isn't it better to have your bootloader unlocked anyway, especially if you like tooling around with your phone?
[Samsung Galaxy Nexus] jonsgirl:
Loving the update so far. I can definitely see a huge improvement in the signal. I'm going to get a full charge on the battery and see how it does. I charge this dang thing daily but I am a heavy user.
[Samsung Galaxy Nexus] efrant:
Then maybe you should write "non-root, locked bootloader" instructions.

Yup, I totally agree with you.
[Samsung Galaxy Nexus] reggie14:
Really? That's odd. I just tried on my locked, not-rooted Galaxy Nexus and I couldn't get it to work. GNex Toolkit and fastboot both gave me error messages indicating that I couldn't do that with a locked bootloader.

Did I do it right? I installed GNex Toolkit, installed the drivers (which I had to do manually), then I went into fastboot and verified the drivers worked (which ended up requiring another manual driver update process). The drivers seemed to work after that. But, with the phone still in fastboot, I tried to one-time boot into CWM, but it gave me the error messages.

Out of curiosity, has your phone ever been unlocked?

It seems like a locked phone shouldn't let you even temporarily boot into CWM. I thought Android phones did signature checking on the bootloader on every boot- not just when the bootloader is flashed. A CWM bootloader won't be signed correctly (or at all), so for security reasons I would think the phone would block it from executing.
[Samsung Galaxy Nexus] lrs421:
Good point.
[Samsung Galaxy Nexus] efrant:
Go figure. That is because it doesn't work with a locked bootloader.

Yes, you did it right. It's just that you need an unlocked bootloader to use that method.

I posted a bunch of different methods you can use in each case (root, no root, unlocked bootloader, not unlocked, etc.). See here.

Edit: Or use the instructions that were posted a few posts ago: https://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/
[Samsung Galaxy Nexus] adrynalyne:
It was a rhetorical question.
[Samsung Galaxy Nexus] El Daddy:
Efrant you are a trooper.
[Samsung Galaxy Nexus] efrant:
;)

Just trying to help out!
[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.
[Samsung Galaxy Nexus] efrant:
Where did you get that photo of me? Stalker.
[Samsung Galaxy Nexus] adrynalyne:
/me pulls out the duct tape
[Samsung Galaxy Nexus] spectrumfox:
You are correct. I humbly apologize for my overlooking this. :)

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

You are correct. I humbly apologize for my overlooking this. :)
[Samsung Galaxy Nexus] lrs421:
shouldn't you be working on a BAMF update, slacker.

:)
[Samsung Galaxy Nexus] adrynalyne:
I did, until 1:30am this morning :(

Mostly repo maintenance, but some fixes too.
[Samsung Galaxy Nexus] spencer88:
How long have you been developing for Android?
[Samsung Galaxy Nexus] adrynalyne:
A little over two years. I dabble though. Not as hardcore as some. Recognized Modder is probably a better title for me.
[Samsung Galaxy Nexus] spencer88:
That's cool. I think I would love to be able to develop for Android I just have no idea how to. Between my full time job and running my own business I don't have a lot of free time to sit and learn something like that, especially when I don't have any coding experience at all.
[Samsung Galaxy Nexus] adrynalyne:
As time goes on, I have less time for it. Eventually, I will be completely behind the scenes on stuff, because I won't have time to mingle. The stunt I pulled yesterday was dumb. Worked on stuff until 1:30 am, and had to get up at 5:30am. I am getting old, and my body doesn't appreciate stuff like that.
[Samsung Galaxy Nexus] hurley1718:
I second that. I keep trying to stay up to get a little work done and it always sucks when the alarm goes off in the morning.
[Samsung Galaxy Nexus] DragonPhyre:
So has this update been pulled or what? All the Google links are dead...
[Samsung Galaxy Nexus] efrant:
Or Recognized Taunter... :D:D

---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------

oldblue910 is hosting them on his site: http://www.randomphantasmagoria.com/firmware/galaxy-nexus/
[Samsung Galaxy Nexus] adrynalyne:
Yes, that would work too :D
[Samsung Galaxy Nexus] spencer88:
It has been pulled. That's why the links are dead. As far as I know, nobody else is getting the OTA.
[Samsung Galaxy Nexus] adrynalyne:
I wouldn't be too surprised if it resumes in the next week or two. I think it went out to more people than they would have liked.
[Samsung Galaxy Nexus] DragonPhyre:
Flipping fantastic.
[Samsung Galaxy Nexus] KillerQ:
Hey all,

What is it about the official OTA push that's pushed from Google that allows the update to apply on our locked and unrooted phones that we cannot replicate outside of that push? Just curious.

It would be interesting if there was some way to simulate an OTA push from a PC, for example, that would allow installation onto a 100% stock device.

Thanks,

Matt!
[Samsung Galaxy Nexus] Greg525:
Thanks, I'll give it a shot tonight.
[Samsung Galaxy Nexus] DragonPhyre:
The base level system apps have access to the things that root gives you access to. That is what SU gives us.
[Samsung Galaxy Nexus] reggie14:
Maybe I'm missing your point... Temp CWM makes sense to me. It's sort of like a network boot. You're using a bootloader that is sent to the device during the boot process, rather than using a bootloader stored in flash.

Now, that potentially creates a big security vulnerability, which is why it makes sense you can't do that without unlocking the bootloader (turning off secure boot).

Sure, but there's something nice from a security point of view about keeping keeping the bootloader locked. Now, as far as I know, there isn't any malware out there taking advantage of that attack vector, so maybe I shouldn't be concerned about that (since persistent rootkits are often possible even with a locked bootloader, since secure boot doesn't extend to the OS kernel).

So, if I take a backup of my apps and app data using the GNex toolkit (basically, of everything except system files), and then I unlock my bootloader, what will I have lost after I restore the app/appdata backup? Will I keep my saved game state from games on my phone? Will my home screens come back? Will I have to reconfigure anything in the OS or individual apps to get things back how they were before I unlocked the bootloader?
[Samsung Galaxy Nexus] spencer88:
I don't get it. Google launches the OTA, then pulls it...and we're left wondering why. And it wasn't even officially announced like when the 4.0.4 OTA for the GSM model was available.
[Samsung Galaxy Nexus] spectrumfox:
Something tells me it was only supposed to be a small test at first, to make sure the build didn't take down phones or their network. It wasn't meant to be as widespread as it got.
[Samsung Galaxy Nexus] efrant:
Yes.

No.

Probably.

Assuming that you are running 4.0.2, this is what I would suggest if you want to unlock your bootloader and keep everything as is:

1) Gain temporary root access using mempodroid.

2) Flash CWM.

3) Boot into CWM and do a nandroid backup.

4) Pull that backup off your device, along with everything that you want to keep in /sdcard.

5) Unlock your bootloader.

6) Copy all the stuff (from step 4) back to your device.

7) Boot into CWM and restore your backup.

8) Done. Everything will be exactly the same, but you will have an unlocked bootloader.

Using the ADB backup feature of ICS (which is what the toolkit you mentioned is using) will not capture everything.
[Samsung Galaxy Nexus] byrds8:
Woot using that website worked. Only took a little pain on figuring it out and asking questions rofl. Now im rocking 4.0.4
[Samsung Galaxy Nexus] adrynalyne:
Yup.
[Samsung Galaxy Nexus] omegafritz:
I updated without an unlocked bootloader!!! I used this site

http://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/

I followed the instructions to a "T" I used the galaxy nexus toolkit and put the 2 files into that folder and instead of using the adb command wherever I saw adb I wrote adb-toolkit since that is what it's named in the galaxy toolkit.
[Samsung Galaxy Nexus] adrynalyne:
Yes, we know. The debate earlier was using temp clockwork with a locked bootloader, which is not gonna happen. Wanna hear the irony of it? If this update isn't official, you will have to unlock to roll back to other images. Plus, you can't do this again if another ota leaks.
[Samsung Galaxy Nexus] Gahh Its Lee:
Someone get it and post it up for us lol
[Samsung Galaxy Nexus] nocarsgo:
Does that mean that I can use a nandroid backup that I have from when I was on stock 4.0.2 and I could get the update? (Currently running the leaked 4.0.4 from a few months ago)
[Samsung Galaxy Nexus] Gahh Its Lee:
As long as its 100% stock yes.
[Samsung Galaxy Nexus] dmmarck:
Update from the Droid-Life article ==>
[Samsung Galaxy Nexus] nocarsgo:
Great. I am doing another backup, but will resume my old 4.0.2 stock. If I get the update I will grab it and post it somewhere tonight.
[Samsung Galaxy Nexus] Skrazz:
I'm on 4.0.4 (IMM30B) locked and unrooted. Think I'm eligible for OTA?

I should mention I'm on VZW...
[Samsung Galaxy Nexus] zephiK:
Most likely not because the latest is 4.0.3. It's a 4.0.3 update to 4.0.4.
[Samsung Galaxy Nexus] patalo:
I'm in the same boat as this buy but I'm rooted and I'm not afraid to lose root because I can reroot on my own. I need to get the stock kernel back because I am on Franco's kernel. Any way to do that without reverting? And if I do get the stock kernel back for 4.0.4 will the update come to me anyway? Or will it only come to 4.0.2?
[Samsung Galaxy Nexus] adrynalyne:
Latest is 4.0.2. That said, they will probably have an upgrade path from IMM30b as well.
[Samsung Galaxy Nexus] miketoasty:
Also reverting to stock and checking as well, *fingers crossed*.
[Samsung Galaxy Nexus] patalo:
If they do will I have to have a stock kernel? Or will it just write over the kernel?
[Samsung Galaxy Nexus] adrynalyne:
You have to be stock whatever update version you are on.

Not AOSP, not modified.
[Samsung Galaxy Nexus] patalo:
I'm not aosp. Everything on my phone is stock except for the kernel. How can I get my stock kernel back?
[Samsung Galaxy Nexus] axne1:
This is exciting!!

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] dmmarck:
You're telling me! ;)
[Samsung Galaxy Nexus] mwalt2:
If you have a custom kernel, it's likely you also have a custom recovery. You'll have to restore both to stock before having a chance at getting an OTA update. You can get to stock using the 4.0.2 ICL53F factory image from Google here at the bottom of the page. You can also extract the .zip inside of the .tgz and probably take what you want as well. boot.img is the kernel and recovery is recovery.img.
[Samsung Galaxy Nexus] patalo:
Thank you! Now after I find the boot.img where would I put it? And can I use root explorer to place it in the correct folder?
[Samsung Galaxy Nexus] miketoasty:
Use this guide: http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/

Has worked wonders for me since the day I got the phone.

---------- Post added at 01:35 PM ---------- Previous post was at 01:32 PM ----------

System up to date. As of 1:35 P.M. EST.
[Samsung Galaxy Nexus] patalo:
Thank you for that but I dont want to reflash anything. I just want a way to put my stock 4.0.4 IMM3OB kernel back so I can get the update. I just need the steps to reflash my stock kernel or where to place it using root explorer. I'm phone savvy, I just haven't figured out android completely. Thank you for the help thus far everyone!
[Samsung Galaxy Nexus] efrant:
Clicking the "Check now" button in System updates does nothing.

---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------

If you have the boot image you want to flash, just reboot your device into fastboot mode, plug into a computer, and type: fastboot flash boot boot.img
[Samsung Galaxy Nexus] spectrumfox:
The moral of the story is bite the bullet and unlock your bootloader. Yeah, it will wipe your device, but you only have to do it once ever. Then you have much more freedom to do whatever you want with your phone without wiping your data again.

It's kind of a double-edged sword, but the payoff is worth it. Also, familiarize yourself with restoring factory 4.0.2 because you'll be doing it a lot to get back to a clean slate.
[Samsung Galaxy Nexus] omegafritz:
I wonder if i can use same steps to go back to stock if i have stock image?
[Samsung Galaxy Nexus] byrds8:
True but if this is the real update then we have nothing to worry about. I may unlock my bootloader one day, just not today lol. I already had stuff on my phone before I thought about unlocking it.
[Samsung Galaxy Nexus] adrynalyne:
'If' is such a malleable word in the Android world :p
[Samsung Galaxy Nexus] adrynalyne:
The locked bootloader-temp root method only works for 4.0.2 and below. It is fixed in later kernels.
[Samsung Galaxy Nexus] byrds8:
Noticed my first quirky thing this evening. Had a random reboot when swiping between home screens. I usually never had them then when it booted back up it wanted me to activate the phone. I hit next and it went in like normal. Also Google+ wont stay disabled now either.
[Samsung Galaxy Nexus] spectrumfox:
You might want to try booting into Recovery Mode and clearing the Cache, then rebooting.