yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yearziro:
Looks like some people aren't going to be getting much sleep tonight
[Samsung Galaxy Nexus] Alton (Halo 2):
My aunts gnex didn't get the update , are they still pushing them out ?
[Samsung Galaxy Nexus] withbloodskies:
Just customization and better battery are enough alone to scream root lol. But I envy those who can stay stock and resist the goodness of the nexus community.

I bet once KeyIimePie arrives many will root ;)

I believe these are only for test phones that random number of people have gotten.
[Samsung Galaxy Nexus] tgyberg:
Your aunt is not alone. She is joined by oh, all of us! (this is a leak, no ota yet)
[Samsung Galaxy Nexus] RaymieHumbert:
So you're rooted, locked bootloader, and you applied two update packages to get here? How do you do that?
[Samsung Galaxy Nexus] PipeHitter:
You can temporarily boot into a custom recovery using fastboot. Think of it as using a boot cd or usb stick to try out linux on your windows pc without affecting anything on you hard drive.

The command would be: fastboot boot custom_recovery.img
[Samsung Galaxy Nexus] efrant:
Not if your bootloader is locked, like the poster has suggested.
[Samsung Galaxy Nexus] emcd4:
Flashed the JRo30o.zip file. Lost root and CWM but remained unlocked. What's the easiest way to get back to root?
[Samsung Galaxy Nexus] ProDriver77:
ADB push su.zip to /sdcard/

Flash custom recovery in Fastboot, then install su.zip.

Once rooted, use a file explorer to remove the android recovery from /system.

Then re-flash CWM for it to stick.

Sent from my Galaxy Nexus on Verizon Wireless
[Samsung Galaxy Nexus] alemad:
Very cool.
[Samsung Galaxy Nexus] tailsthecat3:
Fastboot flash a recovery, flash su, boot and disable or rename the install.recovery.sh file. Then flash recovery again. Think that's it.
[Samsung Galaxy Nexus] oldblue910:
Just because I've seen it asked a hundred times...you cannot flash this manually if you have stock recovery and a locked bootloader. You MUST have a custom recovery installed in order to flash this manually, and you cannot get a custom recovery installed without an unlocked bootloader. If you unlock it, that means you will lose everything on your phone.

Also, just as a reminder, as of this moment, JRO03O is a test build, similar to the 4.0.4/IMM30B build that leaked out back in February. JRO03O may, or may not, end up as the final Jelly Bean OTA for the VZW Galaxy Nexus. It all depends on if VZW approves this or not. If they do not approve it, you probably won't see any further updates to this, and will need to flash back to stock IMM76K in order to get onto the official upgrade path and get whatever the official Jelly Bean OTA ends up being. However, in the event that this IS approved by VZW and Google rolls it out globally, we get bragging rights saying we were running it way before the official rollout. ;)
[Samsung Galaxy Nexus] efrant:
Just to add one thing to what oldblue910 said:

For those of you who have a locked bootloader and a stock recovery, but do have root, you can also flash this. As long as you have either a) an unlocked bootloader OR b) a custom recovery, OR c) root, there are ways to flash with losing your data. For those that have none of the three, you can use adb backup to save your data, and then proceed to get one of the three.
[Samsung Galaxy Nexus] emcd4:
Thanks, I have tried that but continue to get the "waiting for device" note and nothing happens. I have followed all procedures as I have performed in the past successfully for unlocking and rooting and flashing ROM's including the most obvious which is connecting the phone when it is in recovery mode. But this one has me stymied because it just sits there in "waiting for device" mode.
[Samsung Galaxy Nexus] efrant:
That's because you don't have the drivers set up properly for your device.

http://xdaforums.com/showthread.php?t=1814266
[Samsung Galaxy Nexus] emcd4:
Thanks but I believe I do have the drivers set up properly and have been successful in the past with this same setup.
[Samsung Galaxy Nexus] efrant:
So what steps are you taking exactly?

Download the superuser zip to your phone from the net, reboot into fastboot mode, boot cwm, then select install zip from sdcard.
[Samsung Galaxy Nexus] Ravenbf:
I am having an issue now with Jelly Bean. I flashed it on Wednesday and everything was good that day and yesterday....I was getting like 16 hours of battery life....which is what I normally get. The only thing was I was in a non 4G area, so I had CDMA only selected. Today I got back to my home area and I have 4G.....I have 3 to 4 bars, but my battery life turned to garbage. I am getting maybe 7 or 8 hours of life. I have checked Better Battery Stats, GSam Battery Monitor Pro and the battery stats in settings. I have no rogue apps, my wakelocks are normal, my awake time is normal.....It's just like all of a sudden my battery has lost half of its capacity. On ICS I was getting 15-17 hours of 4G, but now I am getting half that. I am rooted, and running the new stock JB leak, no kernels or anything else. Again, not sure what is happing since on 3G my battery life was normal, but now on 4G its half, and on ICS I was getting the 15-17 hours on 4G. I do have better signal strength, but I hope that is not what is killing my battery.
[Samsung Galaxy Nexus] emcd4:
Yes, I have tried that. I have rebooted into fastboot mode but am not able to boot CWM. Still getting "waiting for device". Maybe I am missing something, but I don't think that I can boot CWM from within the phone itself. Both CWM and Titanium Backup error out since I no longer have root.

I've tried "fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img" in command mode (win7) and no joy.
[Samsung Galaxy Nexus] Winesnob:
Had the same problem, used workaround. Due to other issues, decided to start over with a clean device - flashed the IMM76K image and then the OTA leaks. When I reinstalled the My Verizon app, it logged in on the first try.
[Samsung Galaxy Nexus] efrant:
That would suggest to me that you have the ADB driver set up but not the fastboot driver. Can you post a screen shot of your device manager when booted in fastboot mode?
[Samsung Galaxy Nexus] animal24:
Thats funny, because 4g wasn't really working for me before this update. Now things are stellar, though i notice it waiting for better signal before swapping to 4g, which i guess makes sense. I have a hw version 10 device. Wonder if there actually is a difference?
[Samsung Galaxy Nexus] jimmyhook:
From the testing I've done so far, when I'm on wifi my battery is a tad better than other JB versions (speaking of the update as a whole) but when I'm on 4G I have better signal and faster downloads, however, it is draining my battery faster than previous radios. I still have more testing to do for more concrete opinions.
[Samsung Galaxy Nexus] ProDriver77:
Also, check in Android SDK and make sure "Google USB Driver" is installed. You may need to manually update the Android 1.0 driver in Device Manager (on your PC) to get Fastboot to recognize the device.

Also, make sure you wait for the drivers to fully install when you reconnect your device to the PC before attempting to send ADB or Fastboot commands.

Sent from my Galaxy Nexus on Verizon Wireless
[Samsung Galaxy Nexus] Ravenbf:
Solved my issue. I reflashed the leak and now everything is back to normal. I did a dirty flash but cleaned Dalvik cache and now I am back to what looks like my normal 15+ hours on 4G.
[Samsung Galaxy Nexus] emcd4:
Device Mgr shows unknown device when I connect in fastboot mode. I think Efrant is correct in that I am not getting the fastboot driver to load. I have checked Android SDK and can't find "Google USB Driver". I have tried to update the unknown device several different ways and it can't find the driver. I have loaded the Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe and have even tried the Kies program with no luck. I must be missing something - never had this problem in the past even though I have flashed several different ROMs. It is interesting that the recovery mode is showing the phone as being unlocked. I wonder if that is keeping it from being a known device.

I can take it into recovery mode from fastboot mode and it shows CWM v 6.0.1.0. From there I have flashed the SU.Zip but I still can't get Titanium Backup or ROM Mgr to work without error. So it still appears that I am not rooted.

Device Mgr screen shot below:
[Samsung Galaxy Nexus] efrant:
1) You didn't use the instructions I gave you for the drivers. Un-install all your old drivers and re-install the one's I linked to. 2) Do not use the driver package from Samsung.

3) What su zip file are you flashing? Use one from the 'root' link in my signature.
[Samsung Galaxy Nexus] weirddan455:
Just flashed this and it's working great so far. Just sent an MMS over wifi which I was having trouble with on some custom ROMs. Also, what I found interesting was that it shows I'm on a network extender, which I've NEVER seen in any other ROM, custom or offical.
[Samsung Galaxy Nexus] animal24:
Loving this. Only found 2 glitches in the webkit. Highlighting words is sometimes impossible, and everyonce in a while i get render errors. Other than that its fantastic. The new radios make my cellular performance phenominal. It doesn't switch over to 4g till the signal is sufficient, 3g comes on instantly after killing wifi. no hangs. calls are ridiculously fast. love it.
[Samsung Galaxy Nexus] emcd4:
Thanks so much for your help. I finally got it rooted. It appears that the su.zip file (CWM-SuperSU-v0.94.zip) that you steered me to worked better than the one I had.

Thanks, again.
[Samsung Galaxy Nexus] ProDriver77:
Finally installed this last night. Definitely feels smoother. Google Now is a nice touch. I wouldn't call the radios perfection, but definifely an improvement over the IMM76Q build that came with the phone.

Sent from my Galaxy Nexus on Verizon Wireless
[Samsung Galaxy Nexus] sevron:
Just installed on my less than 3 hour old GNex lol. I just wanted to make sure I did everything correct though.

Unlocked, rooted and flashed CWM first. Then made sure no OTAs were up there, none, was on IMM76Q. So I put the .zip on my sdcard, booted to CWM and wiped data, cache and dalvik (though dalvik said error on sdcard-ext or something liek that, is that fine?) and then after I installed from .zip and went to reboot it said it may flash stock recovery so I said yes to fix it and then asked about fixing root so I checked yes to that as well.

Was that everything I was supposed to do?

And also, where's the sdcard folder when I view it in windows explorer? I had to use adb to push it there.
[Samsung Galaxy Nexus] jova33:
Windows explorer can only see the SD card partition. When you open internal storage, that's the SD card partition.

I would've done a clean flash, wipe user data. But if it works, then whateves.
[Samsung Galaxy Nexus] Winesnob:
Looks like the Sprint GNex just received JRO03U with radio FH05 for both CDMA and LTE. Kernel date 8/28. Given that both are CDMA/LTE devices, can we assume that Verizon has yet another version of JB in testing?
[Samsung Galaxy Nexus] DirgeExtinction:
I wouldn't doubt it. Remember how the Verizon Gnex saw that 4.0.3 leak that never became official? I'm sure that's what's happening now.
[Samsung Galaxy Nexus] oldblue910:
Nope, apples and oranges. The Sprint Gnex has a kernel that's built by Samsung, not Google. Notice the se.infra@SEI-29 and the build date being in KST (Korean Standard Time). That's because the Sprint Gnex gets updates from Samsung, not Google. Verizon gets updates direct from Google and uses the AOSP kernel. So an 8/28 build date on the kernel only means that's when Samsung built it. It doesn't mean Google has done a new build for Verizon.

IMM30B is what you're talking about. That was actually an early build of 4.0.4. But another IMM30B is probably not what we're seeing here. Keep in mind that every single Google-updated Nexus device (including the WiFi-only and VZW Xoom) are getting JRO03(X) builds for Jelly Bean:

JRO03C (GSM Gnex)

JRO03D (Nexus 7)

JRO03E (GSM Nexus S worldwide except Telstra Australia)

JRO03H (WiFi Xoom and VZW has approved this for their Xoom and will hopefully be rolling it out soon)

JRO03L (GSM Nexus S on Telstra Australia)

JRO03O (VZW Gnex Testing Build)

JRO03R (Nexus S 4G on Sprint)

The only one we still don't know about is the Korea Nexus S, though my money is on JRO03E.

If Jelly Bean had an IMM30B case, it would have probably been JRN84D which shipped on the Nexus 7 and was also released to those GSM Gnex devices that they gave away at IO 2012. That was the one that let them work out the bugs.

If 4.1.1/JRO03(X) builds weren't intended for every Google-updated Nexus device, they would have done a limited rollout to one or two devices, a-la 4.0.3 and made everyone else wait for a 4.1.2 release. Also, historically, whatever updates the GSM Gnex gets, Verizon gets too eventually. They both got ITL41(X) builds for 4.0.1, they both got ICL53F for 4.0.2, they both got IMM76(X) builds for 4.0.4. The GSM Gnex never got 4.0.3 and neither did Verizon.

The only devices that got 4.0.3 were the 900 MHz (T-Mobile) GSM version of the Nexus S and the WiFi-only Xoom. All other Nexus S devices, as well as the VZW Xoom and all Galaxy Nexus devices stayed put on whatever their most recent firmware was until 4.0.4 came out. There was much ire out of the Nexus S camp that the AT&T and Sprint devices were stuck on Gingerbread until 4.0.4 came out, while the T-Mobile camp got to have all their ICS goodness. What they didn't realize was that the 4.0.3 build for the Nexus S was anything but "ICS goodness". It was absolutely craptastic and most of us who ran it as a daily driver hated it. There were more problems with that build than I could possibly list. haha Apparently the 4.0.3 build for the WiFi-only Xoom (IML77) was much better and I remember being really bummed that VZW didn't get it...and to pour salt on the wound, we got a system update a month after the WiFi Xoom got ICS...but the VZW update wasn't ICS...it was a Honeycomb update that did nothing but fix an issue with restoring data connectivity after coming out of airplane mode. haha
[Samsung Galaxy Nexus] Winesnob:
Thanks for the explanation. Didn't even look at the kernel signature or time zone. Good to know that last week's OTA leak might actually be the final.

With the radios, I'm now guessing these are also specific to Sprint since they operate on a different block of the LTE spectrum?
[Samsung Galaxy Nexus] oldblue910:
Yeah, those radios are definitely Sprint specific. Flashing those on a VZW device would be pointless and could possibly result in not being able to make calls or have any mobile data. I don't know for sure because I would never have the balls to try it. :D

Even more than the JRO03O VZW Gnex leak, I was happy to have the JRO03H VZW Xoom leak. My only annoyance is that the VZW Xoom leak is a nandroid backup, not an official OTA ZIP like the Gnex leak. That Xoom update includes a new CDMA radio (LTE remained the same), but since the leak is a Nandroid backup, the radio isn't included. Further, due to the way Motorola did the partitions on the Xoom, the radios and bootloader somehow share a partition and wherever that happens to be isn't easily accessible to the filesystem...something to that effect. Either way, that means you can't just dump the radio into an IMG file to flash, like you can on Samsung phones. So even though we have the leak, anyone running it (other than the guy who leaked it) has to use the older ICS CDMA radio. We won't get the new one until we have a real OTA ZIP file.
[Samsung Galaxy Nexus] tailsthecat3:
On the Xoom, you mean...?
[Samsung Galaxy Nexus] oldblue910:
Yeah
[Samsung Galaxy Nexus] jimmypader:
my reception and call quality on the network extender seems to really have improved.

how about yours?

before this flash, call on the extender were choppy and would drop after 4-6 minutes.
[Samsung Galaxy Nexus] ProDriver77:
Same here. 4G holds better, no signal drop-out, and have had MUCH fewer dropped calls.

I don't think this one will be the official release. VZW is pretty tough when it comes to updates, and I expect some tweaks to be performed before an official OTA is made.

Sent from my Galaxy Nexus on Verizon Wireless
[Samsung Galaxy Nexus] Ravenbf:
I am really liking this update...other then the battery hit from Google Now, Project Butter (I am going to assume the battery is taking a hit to get the smoothness) and the improved radios. The battery hit isn't huge now that I figured out the issues (and did a reflash), and I love having almost constant 4G. I think the update is a huge improvement...even if it is the "unofficial" or test release. I do remember ICS 4.04 leak though. I had that almost a month and a half before Verizon did their official release.....and it was exactly the same. I think if there are no serious issues....which I haven't seen any yet (been on it since it leaked) this will be the same build as the real OTA. I am curious to see though.
[Samsung Galaxy Nexus] Winesnob:
Definitely a big improvement, though am skeptical if it will be the final. The 4.0.4 leak (IMM30B) was good from the Android side, but we did get another iteration of radio updates with IMM76K.

Out of curiosity - what were the battery issues that you resolved with the reflash? My main issue is the enormous amount of 'awake' time the media scanner is taking after a boot/reboot. Not that I have to boot often, but if I change a battery out I lose a good amount of power just getting the phone started again.
[Samsung Galaxy Nexus] Ravenbf:
My original battery issue was I was only getting 7 hours of battery, even with the phone just sitting there. I turned on the screen for all of 2 minutes and lost 12% battery life. My battery monitors weren't showing anything out of the ordinary, it was just like I lost half my battery life. So after a day or two of seeing really crappy life I reflashed and now I am back to what I consider tolerable battery life.

I do have the issue that if I reboot I lose like 10% battery life though, not sure what is up with that, but it is fixed the next time I recharge.
[Samsung Galaxy Nexus] Winesnob:
That's the media scanner running through all media files at boot. Don't know why it doesn't build a cache file to reference after a reboot. Definitely would save power if it only looked for changes. Just did a battery change to the extended battery and lost 6% at startup, and only because I finally cleared old photos and videos off the device since they were already sitting in Drop box.
[Samsung Galaxy Nexus] thorrules:
Jb is here
[Samsung Galaxy Nexus] oldblue910:
http://xdaforums.com/showthread.php?t=1889046
[Samsung Galaxy Nexus] thorrules:
Thanks.
[Samsung Galaxy Nexus] thorrules:
Hey oldblue, i m still on imm76k, and a little lazy to go 2 step, 76q to jrO03O. I checked a couple of times for upgrade on my nexus, it still not shwoing anything. Apparently, vz says they will notify on my phone. Is there anyway to force the update, other than the 2 step process of 76q to jr? Sorry just being lazy, was working overnight!
[Samsung Galaxy Nexus] sbrownla:
No there is not unless you flash the ROM yourself.
[Samsung Galaxy Nexus] efrant:
Just download the JRO03O-from-IMM76K file and flash that in recovery...
[Samsung Galaxy Nexus] tailsthecat3:
Anybody having GPS issues? Using GPS only, not Google location, obtaining a lock is nearly impossible. I updated a long time ago with the leaked update file and have had issues since. I've tried seemingly every single fix available and nothing seems to work well.

Anybody pull the gps.conf file and post it here, maybe that will help? Thanks.
[Samsung Galaxy Nexus] shizat63:
My GPS didn't work till I enabled "Google's Location Services" where they track the hell out of you.
[Samsung Galaxy Nexus] tailsthecat3:
Yup. Annoying. GPS status from the play store grabs a lock every time. But foursquare and maps takes absolutely forever and that's if it grabs a lock at all. Not to mention that Google location isn't accurate enough
[Samsung Galaxy Nexus] shizat63:
After 50+ attempts to force the update, I woke up this morning and JRO03O was waiting for me. Maybe having a battery at 100% helped? Probably not.

Do I need to re-root? FoxFi wifi tethering isn't working anymore. Or should I be using another tethering app?
[Samsung Galaxy Nexus] tailsthecat3:
Foxfi stopped working for me, too, after I applied the leaked update weeks ago. Just like GPS satellite locks. Gaaaaah!! Need a fix!!
[Samsung Galaxy Nexus] Winesnob:
FoxFi is now marked as currently not working with JB by the dev, don't know if there is a fix/workaround coming.

GPS is working fine for me, but keep in mind you may need to give it a few minutes to get a first lock with the update and then it will pick up quickly. A good tool is GPS Test from the Play Store. You and send an assist request which uses your cellular location and GPS to find your location faster. I can pick up GPS signals inside the house with my VZW GNex stock unrooted.
[Samsung Galaxy Nexus] 2ksilverbullet:
The Elixir hot spot widget still works, just tested it (i'm stock on VZW).
[Samsung Galaxy Nexus] a1exus:
What's that?
[Samsung Galaxy Nexus] 2ksilverbullet:
An app in the market.
[Samsung Galaxy Nexus] tailsthecat3:
I could also get GPS locks in my house, on ICS, without Google location services selected. Since jelly bean it just hasn't worked. Well, let's say it very rarely works, almost never and if it does work, it takes forever to get a lock. My GPS.conf file looks like this.

NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin

XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin

XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin

SUPL_HOST=supl.google.com

SUPL_PORT=7276
[Samsung Galaxy Nexus] georgiapi:
I'm one of those that cannot successfully flash a JB ROM because it hangs at the animation. I have ran some ADB commands for some kind folks over on Android Forums and my time stamps are just one of the things they see.

Anyway, did I read there is a member here in the same boat that the OTA cured this?

Thanks
[Samsung Galaxy Nexus] blackhand1001:
Fastboot the stock images. If you don't know how to do that download the toolbox.
[Samsung Galaxy Nexus] ProDriver77:
I flashed the leaked build from Google Servers a few weeks ago. Are there any differences between this and the official version, and will flashing the leaked version (left unrooted, relocked the bootloader) stop me from receiving future OTAs?

Sent from my Galaxy Nexus on Verizon Wireless
[Samsung Galaxy Nexus] Rydis:
sigh..now my phone just consistantly freezes on google logo..update been nothing but awful for me :(
[Samsung Galaxy Nexus] Winesnob:
Let it go - be patient. Sometimes the JB boot (appearing stuck at the Google screen part) is taking longer due to the bootloader. The file structure of the device is being verified. This may take several minutes, but should eventually change to the Nexus logo and continue booting.
[Samsung Galaxy Nexus] tailsthecat3:
No and no. So long as you have a stock /system partition and recovery.
[Samsung Galaxy Nexus] ProDriver77:
Still have stock recovery, as I only loaded CWM in Fastboot and didn't flash it after flashing the new ROM. Thanks.

Sent from my Galaxy Nexus on Verizon Wireless
[Samsung Galaxy Nexus] georgiapi:
Took mine back to stock locked, it OTA's the MM76K immediately. I go to Apps and clear cache and stop on Google Services Framework and reboot. It OTA's again but loops @ JB logo.

Got phone 12/11. Going to Verizon in a bit to see what happens.
[Samsung Galaxy Nexus] Winesnob:
Loops or appears to be stuck at the Google logo? If appears stuck let it go for several minutes. Its part of the JB boot process.
[Samsung Galaxy Nexus] georgiapi:
Heh! Give me a little credit on that one. I have been flashing since the OG Droid.:good:
[Samsung Galaxy Nexus] hawkeye680:
Has anybody found the insecure boot image for this yet? Trying to reroot stock again and the previous image isnt working. Thanks.
[Samsung Galaxy Nexus] efrant:
Why not use CWM to root?