yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] byrds8:
What will clearng cache do for you? Someone mentioned rebooting it if i hadnt since the install. I did that so guess we will see. Although even after the reboot I couldnt keep Google+ disabled
[Samsung Galaxy Nexus] matt30:
Probably nothing. Until the root cause of the glitch is known the reboots will keep happening.
[Samsung Galaxy Nexus] reggie14:
Thanks for the clarifications. I really appreciate your help. I think I know how to do everything in your list of steps except #2. How would I flash CWM before I unlock my bootloader? I can't find any tutorials on that, and the general idea confuses me. It doesn't seem like it should be possible to flash CWM without first unlocking the bootloader, even with root.
[Samsung Galaxy Nexus] xXTERMIN8RXXx:
My GNex was acting real funny for the past day and a 1/2... wouldn't pick up 3G or Wi-Fi... historically speaking for myself, I knew that was a sign an update was coming soon... I'm so glad this is confirmed. Don't have to root (yet)!
[Samsung Galaxy Nexus] efrant:
Once you have root, you can do pretty much anything.

The easy way would be to root using this method and then install ROM Manager, which will flash CWM for you. I would recommend this way.

Otherwise, download CWM, rename it to cwm.img and place it in the root of your /sdcard. Then obtain temporary root access (by doing only steps 1-6 in the link above). Then type the following command in the terminal window:

dd if=/sdcard/cwm.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery

Then reboot into the bootloader and select recovery. It should work.
[Samsung Galaxy Nexus] The_other_ray:
Anyone else getting random reboots where it goes through an automatic activation process with this new update?

But when I reboot manually, it doesn't do an activation.

It's happened to me twice now. It's the only bug that I've noticed so far. I'm on stock rooted.
[Samsung Galaxy Nexus] Rnd0209:
Nothing here been running this for about a day 1/2. What your experiencing is possibly the PRL update issue. How is your signal?
[Samsung Galaxy Nexus] adrynalyne:
PRLs don't cause hot reboots.
[Samsung Galaxy Nexus] byrds8:
I had this happen once yesterday. I rebooted manually after cause I dont think I did after the initial boot up of installing the update. Hasnt happened since though. The only other thing Ive noticed is I cant keep Google+ disabled anymore
[Samsung Galaxy Nexus] slickrickstyles:
Its been doing that for me on Milestone 5 and the new radios...It will just reboot on its own and activate and then things are normal again...Happened twice yesterday
[Samsung Galaxy Nexus] Aerocaptain:
Just flashed the new BL & radios. Coming from the 4.04 leak. Signal reception is marginally to decently better. 4G reception does hold better. Inside my house, I've averaged throughout the 4 months I've owned the device, -120dBm and barely received 3G much less 4G. (Good thing I have wifi)

Now I'm getting -111 to -119dBm when 4G is holding. However, the 4G speeds are where 3G speeds should be (once again inside my house). If I lose 4G, 3G picks up and my signal increases to -93dBm to -100dBm.

Oddly enough, in the past 3-6 days, I've received a 3G signal and better reception then I've ever received inside my house. Now that could be Verizon increasing there signal in my area or Verizon making an adjustment to the signal output across the board in preparation for the Galaxy Nexus update.....and possibly the whole chain of ICS roll outs this month for various devices. I wonder if ICS software hinders the reception or radios (CDMA). Idk, just speculating.

BTW, I live in a major city that has had 4G since the first few 4G roll outs. My previous HTC device averaged -83dBm, and always held 3G in the same house.

Edit: No reboots or other negative effects btw

Sent from CDMA V6 SC GNexus w/Liquid & Franco.kernel
[Samsung Galaxy Nexus] cwoggon:
Are you implying that your phone has some kind of update-ESP?
[Samsung Galaxy Nexus] The_other_ray:
My signal actually has gotten better. More bars in more places.
[Samsung Galaxy Nexus] blipp:
Sorry, moved this to the Q&A thread, dont wanna piss anyone off (Flash back from IMM30B to 4.0.2 for new leak http://xdaforums.com/showthread.php?p=25623228#post25623228)

Im summary, unlocked bootloader, temp boot CWM to get IMM30B leak few weeks ago, now i cant temp boot into CWM or flash back to 4.0.2 using toolkit or command prompt b/c of "failing" to boot into bootloader or "failing" to download boot.img
[Samsung Galaxy Nexus] spectrumfox:
After using my phone like I normally would for a day, I'm finding battery life to be slightly better than 4.0.2, but also slightly worse than the 4.0.4 build that was leaked earlier this year.

I have a Seidio 3800mAh extended battery w/ NFC and I'm finding that with the leaked 4.0.4 build that was leaked earlier this year, I was easily able to get from approx 7:20a to 7:00pm without the battery meter dipping into orange.

But with the 4.0.4 build that was released this week, I'm into the orange zone before 6:30pm.

I'm doing to perform the same test today to see if I get the same results, but I'm thinking there may be a reason why they halted the OTA on this one.
[Samsung Galaxy Nexus] Beamer9408:
Simple it used fastboot boot .img not fastboot flash .img
[Samsung Galaxy Nexus] adrynalyne:
Which is not relevant to what I was discussing. Not to mention that no, you did not use fastboot with a locked bootloader.
[Samsung Galaxy Nexus] efrant:
Here we go again...

"fastboot boot" will NOT work if your bootloader is locked...
[Samsung Galaxy Nexus] stevessvt:
Im definitely using more battery now compared to the last 4.0.4
[Samsung Galaxy Nexus] porlo:
The new radio tends to hold on to a certain band (3G or LTE) longer than the previous leak. Battery is slightly worse.
[Samsung Galaxy Nexus] spencer88:
I had to revert back to the previous 4.0.4 radios. Every time I would get a text message my connection would drop and come back 1-5 seconds later.
[Samsung Galaxy Nexus] adrynalyne:
RIL crash. Have you tried wiping data since upgrading?

https://twitter.com/#!/adrynalyne/status/198115903345410048
[Samsung Galaxy Nexus] madcow706:
Has anyone else noticed issues with GPS taking a long time on this update? On the previous IMM30B update I did not have this issue. GPS takes considerably longer in the same place as on 4.0.2 and 4.0.4vIMM30B. Also, the battery life seemed much worse then on IMM30B.
[Samsung Galaxy Nexus] adrynalyne:
Locked 8 seconds flat.
[Samsung Galaxy Nexus] madcow706:
Hmm, it locks like that on IMM30B update. I went back to the factory image of 4.0.2, with unlocked bootloader and updated to IMM76K, the same way I update to IMM30B before it. Maybe something didn't go right. I will flash again and retest.
[Samsung Galaxy Nexus] spectrumfox:
Haven't noticed the GPS issue. Have noticed the battery issue. Still, it's better than 4.0.2.
[Samsung Galaxy Nexus] matt30:
If there is no aGPS data stored on the phone the first fix will take some time.
[Samsung Galaxy Nexus] Beamer9408:
I thought he was asking how it booted without flashing recovery the simple answer was it boots not flash and I understand that fastboot doesn't work if you are locked.

I guess what I said may have been confusing to some I apologize I wasn't saying you could do it without unlocking but was saying you can boot without flashing.

Edit adrynalyne..I'm pretty sure I didn't mean to quote you on that some one asked how the "toolkit" booted cwm without flashing it.
[Samsung Galaxy Nexus] Rnd0209:
Locked on very quickly and I'm in a car with cloud cover.
[Samsung Galaxy Nexus] spencer88:
I haven't wiped anything.
[Samsung Galaxy Nexus] ATnTdude:
Neither cloud cover or your car should really affect GPS. Go inside of a steel frame or masonry building then talk about GPS reception.
[Samsung Galaxy Nexus] Rnd0209:
Obviously......
[Samsung Galaxy Nexus] spectrumfox:
After a second day of testing, I've found complications with battery drain as well as some trouble obtaining 4G once coming out of an underground tunnel where I only got 3G reception. It took about 5-10 minutes for my Gnex to re-obtain 4G.

Looks like we can expect yet another 4.0.4 sometime in the future.
[Samsung Galaxy Nexus] ATnTdude:
Then why mention the clouds? Did you see a cloud that looked like an animal? A car? Boobs?
[Samsung Galaxy Nexus] oldblue910:
Being a little harsh on the guy, aren't we? Come on, man. Chill.
[Samsung Galaxy Nexus] Greg525:
Ok, so I got root back. Then I went to try and delete those two files. Here are the files I see in /system

recovery-from-boot.p

recovery-from-boot.p.bak

I don't see the install-recovery-sh. Also, using "Root Browser" it won't let me delete those files. Any ideas? CWM Recovery is still there and I'm able to boot to it through ROM Manager. Thanks for the help!
[Samsung Galaxy Nexus] xXTERMIN8RXXx:
Sorry, shoulda clarified... on my OG Droid, it did that... haha

I guess it did have ESP... since there's only been one version update for the VZW GNex, I didn't notice it (since I did the update immediately after I bought the phone, like right out of the store immediately).
[Samsung Galaxy Nexus] Rnd0209:
Its alright kiddo i have thick skin, keep it coming. ;)
[Samsung Galaxy Nexus] matt30:
You need to mount the system partition. If install-recovery-sh isn't there don't worry about it.

If you have adb you can use 'adb remount' to mount the system partition.

To remove recovery-from-boot.p type 'adb shell', then type 'cd system' then 'rm recovery-from-boot.p'

---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------

Or download something like Root Explorer from the play store.
[Samsung Galaxy Nexus] Greg525:
Thanks. But am I deleting both of these? Buying root explorer seems like the easier option.

recovery-from-boot.p

recovery-from-boot.p.bak

Edit: Pretty sure I created the .bak file when I was trying to get CWM on my phone, so I'm guessing yes, I delete both?
[Samsung Galaxy Nexus] matt30:
recovery-from-boot.p.bak is a backup file. It's harmless but it wont hurt if you delete it.
[Samsung Galaxy Nexus] Greg525:
Ok, so I deleted the files and rebooted to the bootloader to fastboot "recovery-clockwork-5.5.0.4-toro.img" but when I do, nothing happens. The fastboot script runs, but it doesn't flash CWM. But I get the error message: "error: cannot load 'recovery-clockwork-5.5.0.4-toro.img'"

Thoughts?

Edit: Well that's weird. I tried a few more times and it worked....odd.
[Samsung Galaxy Nexus] efrant:
Sorry, typo. The two files are

/system/recovery-from-boot.p

/system/etc/install-recovery.sh
[Samsung Galaxy Nexus] adrynalyne:
I am only quoting this because I approve of seeing boobs in the clouds.
[Samsung Galaxy Nexus] ATnTdude:
Don't say something questionable and then act high and mighty when someone questions you about it.

I generally approve of seeing them everywhere, except on a man.
[Samsung Galaxy Nexus] Greg525:
No worries, I got root back. But do I need to go and delete install-recovery and then re-flash CWM and then the superuser zip again to make it sure it sticks this time?
[Samsung Galaxy Nexus] efrant:
Yes, except that you will not have to re-flash the superuser zip. That will stick regardless if those two files are there or not.
[Samsung Galaxy Nexus] Greg525:
Ok, thanks. I will do that tonight. Hopefully I get the CWM .img to flash without issues like that last night. Thanks again for the help.
[Samsung Galaxy Nexus] Rnd0209:
Have a drink and simmer down there. :beer: ;). Its all in good fun.
[Samsung Galaxy Nexus] oldblue910:
Put 'em in the clouds. *****es love clouds.
[Samsung Galaxy Nexus] boe:
Shame this never really got released and solved the issues.
[Samsung Galaxy Nexus] adrynalyne:
Never say never. It might still be released.
[Samsung Galaxy Nexus] spectrumfox:
There are some battery drain issues with this build that weren't present with the leaked 4.0.4 from earlier this year. I doubt this will be the official update.
[Samsung Galaxy Nexus] axne1:
Yeah that one I think is being scrapped! The radios sucked for me too. Hence the battery drain.

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] stevessvt:
Well, lets not rush them people. They've only had 6 months to try and get decent performing radios.
[Samsung Galaxy Nexus] miketoasty:
This is one of the funniest jokes I have seen on this website.
[Samsung Galaxy Nexus] VinceT3:
LOL.. agreed.. I will say for me the radios on the last halfassed release seems pretty good thus far..
[Samsung Galaxy Nexus] boe:
Exactly. I'm sure they'll get the kinks worked out of it within 3 or 4 years...5 years tops!
[Samsung Galaxy Nexus] adrynalyne:
Humor moment was good for only one of these comments;)

I have good results with the radios, for what it is worth.
[Samsung Galaxy Nexus] miketoasty:
I too had good performance, but switched back this morning due to my phone running hotter over the last week, which I presume was the radios but could have been any number of other things. If same heat issues stay then I will try something else but, yea, the update was pulled for a reason I guess.
[Samsung Galaxy Nexus] boe:
I still keep coming here hoping there will be some official patch from Verizon.
[Samsung Galaxy Nexus] fenris117:
I still haven't received this....well, last time I checked
[Samsung Galaxy Nexus] sbrownla:
Did anyone get the OTA 4.0.4 update yet? I saw it in store a month ago. Only the store phones got it. My hotspot service is so intermittent it is hardly useful.
[Samsung Galaxy Nexus] oldblue910:
The update only went to a very small number of phones before Google physically deleted the file from their OTA server. They don't normally delete those files unless there is something major wrong with it, so I wouldn't recommend flashing it.
[Samsung Galaxy Nexus] jonstrong:
I haven't read of any major problems with this VzW release/leak for IMM76K / 4.0.4, and it's been working extremely well for me - snapper, and definitely more stable than 4.0.2. No spontaneous reboots with this version, unlike 4.0.2 which rebooted itself about once a week. Very happy so far with 4.0.4.
[Samsung Galaxy Nexus] oldblue910:
It seemed to run fine for me too, but all I'm saying is that history shows that Google never deletes OTA update files off that server unless there is some kind of major problem found with it. For instance:

The 2.3.3/GRI54 -> 2.3.4/GRJ22 update for the worldwide (I9020T/I9023) Nexus S was deleted because it didn't work. It was expecting the wrong baseband and always failed during the patch. A week later they released a full 95MB ROM update for GRI54.

The 2.3.6/GRK39C update for the Canadian Nexus S (with AT&T/Rogers/Bell bands) came out and broke tethering for a bunch of users. That update was deleted within a day.

Note that when the 4.0.4/IMM30B update for the VZW GN came out, that too was only pushed to a handful of people before they stopped the update. That file still lives on Google's server and can still be downloaded via direct link. IMM76K was deleted after a few hours of being live. Just examining history, I'm erring on the side of caution and assuming they found something wrong with it.
[Samsung Galaxy Nexus] MMcCraryNJ:
And for all we know, it could also be that they found a major security hole or something else that we wouldn't see in day to day usage.
[Samsung Galaxy Nexus] miketoasty:
Or it could be that it read battery stats wrong, there is no way to know and I don't think we ever will. If you want to use it go ahead, but of course it is at your own risk.
[Samsung Galaxy Nexus] oldblue910:
Absolutely right.
[Samsung Galaxy Nexus] jonstrong:
I hear you - quite possible you're right, and I never assume an unreleased version is 100% correct (or a release version for that matter!). Went through this for years with leaked Blackberry firmware -- locking up my phone, worrying that I bricked it, recovering and swearing to be more conservative next time...and doing it all over 2 weeks later when the next leak appeared... IMM76K just "felt" like it reached whatever my threshold is for seemingly acceptable risk, so I've been giving it a try.

Weird that Google took it down...but in light of Samsung and Vlingo interceding to block S Voice, and VzW's apparent control over OTA releases even on a Nexus device, I'm wondering if it wasn't taken down simply because VzW didn't want it up there yet...
[Samsung Galaxy Nexus] oldblue910:
I have thought about that too, but then why would they have allowed IMM30B to stay up? Meh, who knows. We'll never know the answers so hey, run what makes you happy and keep on truckin'! :cool:
[Samsung Galaxy Nexus] jonstrong:
We may be giving VzW too much credit for having thought this through. I've seen (and lived through) so many knee-jerk "executive" decisions over the years that sort of sound like they're aimed at accomplishing a sharply defined objective, but in practice don't pass the most rudimentary analysis. Maybe VzW *thought* they would be blocking the version aimed at the LTE / CDMA GNex and thought that taking down the one version was sufficient... But as you say...who knows? Too many other things to do than worry about this... It's all good.. :)
[Samsung Galaxy Nexus] NTolerance:
I'm still using the radios from IMM30B since that build is still hosted on Google's servers.
[Samsung Galaxy Nexus] boe:
I'll admit I foolishly thought when I bought the phone "what the hey, the phones been out a few months, how long could it be before they release a fix"?
[Samsung Galaxy Nexus] martonikaj:
Then you flipped over the phone, and the battery cover had a Verizon logo on it!

Shock! Horror! NOOOOOOOOOO!
[Samsung Galaxy Nexus] boe:
I'm new to Verizon - had Sprint. With Sprint this was also and issue - is this common with Verizon?
[Samsung Galaxy Nexus] El Daddy:
Its an issue with every carrier. Unlocked GSM devices is the way to go if you want to avoid it.
[Samsung Galaxy Nexus] flintfirewalker:
Here's what confuses me. When rumors like this come out, a lot of people get extremely excited and impatient (wrongly so, but nevertheless). And when updates don't come out, it just frustrates those people.

This is just not good for Android's image. Why doesn't someone from Google/Android come out and just remove rumors, or keep people posted with timelines? It's almost like Android is lacking accountability.
[Samsung Galaxy Nexus] martonikaj:
Well Google doesn't know, that's why. It's not up to them right now. And giving timelines is inherently flawed. They either set a timeline too far off in the future and people get mad, or they set it too soon and they miss it, again people getting mad. No one wins.
[Samsung Galaxy Nexus] tomyboombotz:
Um

Sent from a paranoid rom!
[Samsung Galaxy Nexus] flintfirewalker:
I guess that makes sense.

It's crazy how this particular rumor came and went without much fanfare.

I'm still on stock waiting for updates to fix everything. Gnex is my first Android (use to be Apple user) and I'm just absolutely turned off by the way Apple runs business. To sum my path, I'd say I escaped a country run (and run very well) by a dictator and came to the democratic land of freedom. As much as I'm loving my life in the Android ecosystem, I'm bothered by little bugs here and there and just wishing so bad Android can smooth out those rough edges and fulfill it's true potential.
[Samsung Galaxy Nexus] adrynalyne:
Please....tell us more.
[Samsung Galaxy Nexus] spencer88:
Quoted because this is the same guy that told us to post new radios for him.

I can't find that thread anymore btw. I wonder if it was deleted.
[Samsung Galaxy Nexus] El Daddy:
I was very disappointed when I woke up this morning to see that thread was gone. It was one of my proudest moments... :)
[Samsung Galaxy Nexus] oldblue910:
Looks like IMM76K is going to be our 4.0.4 OTA. Google put the file back on their OTA server. It's the same file that was pushed to some corporate devices and a handful of end customers back on May 1.
[Samsung Galaxy Nexus] spectrumfox:
I will be disappointed if that turns out to be the OTA. Battery life on IMM76K is horrible.
[Samsung Galaxy Nexus] oldblue910:
For me, the battery life was much better on IMM76K than it is on ICL53F.
[Samsung Galaxy Nexus] spectrumfox:
It is better than ICL53F, yes... but worse than IMM30B.
[Samsung Galaxy Nexus] oldblue910:
I'll give you that. IMM30B was awesome for battery.
[Samsung Galaxy Nexus] Dan76:
I too would expect the reason for it being pulled a couple weeks ago was for further updating and changes... so the OTA would be newer. Any chance they'd use the same build# but with fixes?
[Samsung Galaxy Nexus] spectrumfox:
Microsoft does it. Maybe Google would too. :)

I haven't tried it yet myself. May give it a go tonight.
[Samsung Galaxy Nexus] oldblue910:
It's the exact same file. The MD5 and SHA1 hashes are identical between the may 1 file and the may 23 file. Sorry to bust your bubble guys. :)
[Samsung Galaxy Nexus] spectrumfox:
Booooo hissssss. :P
[Samsung Galaxy Nexus] tunerfreak:
I am having a problem trying to flash this file, I get an error during

"Verifying current system"

assert failed: apply_patch_check("/system/app/Gmail.apk"

I am running a modified version of Gmail to open up the database again so I tried uninstalling that and downloading the market version but that wouldnt install. Is there anything I can do or is a factory reset my only option here?
[Samsung Galaxy Nexus] oldblue910:
A factory reset won't help either. You'll need to flash system.img from the 4.0.2 factory images package available at http://developers.google.com/android/nexus/images. Once you do that, the OTA should work.
[Samsung Galaxy Nexus] flintfirewalker:
I'm sorry guys, but I'm really new to this, but how do I manually run this update? Completely stock Verizon galaxy nexus.
[Samsung Galaxy Nexus] tunerfreak:
will i lose all my information with this too or no?
[Samsung Galaxy Nexus] oldblue910:
Not if you only flash system.img.
[Samsung Galaxy Nexus] efrant:
No, but you will lose root, busybox, as well as any apps you installed in /system.

Instead of flashing the entire image, I would rather suggest you just pull the Gmail.apk from the image and replace your current one with the original one. Then the update will work.
[Samsung Galaxy Nexus] oldblue910:
Except you can't pull individual files out of a fastboot .img file... or can you?
[Samsung Galaxy Nexus] spectrumfox:
Try this, though I haven't personally verified it works.

http://rants.strifejester.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/
[Samsung Galaxy Nexus] mwalt2:
dsixda's kitchen will extract it for you (or you could probably use the same tools the kitchen uses to do it if you knew how).
[Samsung Galaxy Nexus] efrant:
Yes you can. If you look at my ota update thread (link in sig), I explain how to do it in the part in blue (I think it is under the heading how to flash). Essentially you need to convert it to an ext4 image and then mount it. Then you can pull out whatever you want.
[Samsung Galaxy Nexus] efrant:
Check out the "update" link in my signature.
[Samsung Galaxy Nexus] axne1:
Already left android after spending tons of cash and time waiting for greatness! It never happened so I figured why not try the competition...
[Samsung Galaxy Nexus] mwalt2:
Cool story.
[Samsung Galaxy Nexus] miketoasty:
But you still come here... Guess you are missing the terribleness of android.
[Samsung Galaxy Nexus] jimmyhook:
You spent tons of cash waiting for an update to 4.0.4? I could have sold you the update for 50 bucks :-)
[Samsung Galaxy Nexus] tonker83:
Your still going to be waiting.
[Samsung Galaxy Nexus] bL33d:
Oh that's cute my mom has an iPhone also.
[Samsung Galaxy Nexus] stevessvt:
Wow, this is the crap we get after waiting 5 months? My battery drains worse than 402, my bluetooth volume needs to be turned up every time I connect, I still get crappy reception....
[Samsung Galaxy Nexus] TheLurg1687:
Something needs to be pushed out. This is ridiculous. This better be it.
[Samsung Galaxy Nexus] oldblue910:
:rolleyes: Ever heard the old phrase "Buy a phone for what it does when you buy it, not what they promise it'll do later?" Just sayin'.
[Samsung Galaxy Nexus] spencer88:
Since the OTA file is back up, are people actually getting the OTA notification?