yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] John Markley:
Our gratitude is boundless, nearly beyond contemplation - i.e., thank you!!
[Samsung Galaxy Nexus] ironside2011:
Congrats! Now how do I apply this ? Its downloading as I speak?
[Samsung Galaxy Nexus] GohanBurner:
Quick, someone learn me how to dump radios!!111!!
[Samsung Galaxy Nexus] El Madhatter:
Oldblue910, thank you very much for your patience and assistance. Until next time...

El Madhatter and Oldblue910
[Samsung Galaxy Nexus] animal24:
You are a god.
[Samsung Galaxy Nexus] Winesnob:
Stock recovery - USB or via ADB.

Custom recovery, just install the zip file.
[Samsung Galaxy Nexus] oldblue910:
Now that this is done, I shall duck out and finish watching some classic Tom Baker-era Dr. Who. G'night gents.
[Samsung Galaxy Nexus] ironside2011:
I just have an unlocked boot loader. Without the custom recovery. So can it be applied through the phone its self or do I need a computer?
[Samsung Galaxy Nexus] animal24:
Boot into recovery (bootloader by holding both volume keys, then selecting recover)

assuming you have the latest ADB on your machine

"adb sideload (really long ota filename"
[Samsung Galaxy Nexus] GohanBurner:
I was going to just ADB the radios but it seems that only the CDMA radio was included in this file. Is this correct? I thought there were 2.
[Samsung Galaxy Nexus] mwalt2:
Here's a post with a little more instructions: http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
[Samsung Galaxy Nexus] ironside2011:
By machine do you mean computer or nexus? Sorry if I sound really stupid. Applying ota's for my old dinc 1 was just a file name change and flash as normal
[Samsung Galaxy Nexus] Easton999GS:
i was thinking the exact same thing! where the heck is the lte radio
[Samsung Galaxy Nexus] cms5423:
The LTE portion is in the form of a patch, just like previous OTAs have been. Give it some time and someone will post a zip for just the radios :)
[Samsung Galaxy Nexus] mwalt2:
It's radio.img.p in the .zip. It patches your current lte radio.
[Samsung Galaxy Nexus] veritas718b:
flashing over the ota .zip file now so excited :D
[Samsung Galaxy Nexus] GohanBurner:
Well here goes nothing. My common sense is telling me to remove the ".p" on the end, but I'm going to try and flash it over anyway just the way it is.
[Samsung Galaxy Nexus] Easton999GS:
http://sphotos-a.xx.fbcdn.net/hphotos-snc7/1080_10151813088163782_380058964_n.jpg
[Samsung Galaxy Nexus] donnyp1:
What are you guys flashing it over? Just a stock rom?
[Samsung Galaxy Nexus] mark manning:
I'll pull the right now for you guys
[Samsung Galaxy Nexus] veritas718b:
for me ya, i just used the gnex toolkit and downgraded then flashed it over to plain stock.
[Samsung Galaxy Nexus] animal24:
The cdma radio
[Samsung Galaxy Nexus] DroidBurgundy:
THANKS :D
[Samsung Galaxy Nexus] animal24:
second try at uploading the lte radio. It came as a .p so i assume its a patch?
[Samsung Galaxy Nexus] cms5423:
.... isn't that just the CDMA radio? :o
[Samsung Galaxy Nexus] spillytime:
radios...brains...radios

how long will it take to dump the radios so we can flash them?
[Samsung Galaxy Nexus] animal24:
ya, it took a couple of tries for the LTE patch. its a .p so be careful with it.
[Samsung Galaxy Nexus] refthemc:
So a "fastboot flash radio radio-cdma.img" wouldn't work because of the LTE right?
[Samsung Galaxy Nexus] cms5423:
That's because it's just a patch, I don't think you can flash it as you would the cdma-radio img
[Samsung Galaxy Nexus] wavedashdoc:
Eagerly awaiting a zip that can be flashed in recovery for both radios!
[Samsung Galaxy Nexus] OSully:
Out of curiosity - is Google Wallet included? Also, is the stock browser still in place, or has Chrome been included now?
[Samsung Galaxy Nexus] ironside2011:
So it can't be flashed without a computer or custom recovery?
[Samsung Galaxy Nexus] El Daddy:
No.
[Samsung Galaxy Nexus] DirgeExtinction:
This is pretty much what I'm waiting for. I'm also grateful for such amazing people we have doing things for us out of their free time.
[Samsung Galaxy Nexus] wavedashdoc:
Yeah big shout out to El and Old for teaming up and bringing us this early leak!
[Samsung Galaxy Nexus] krazie1:
Hey I took a guess on the first page and said March 2013 and was right. I'm actually shocked that I guessed right, congratulations fellow galaxy nexus owners. Enjoy them new radios ;)
[Samsung Galaxy Nexus] ironside2011:
Then how do I flash it without a computer or custom recovery
[Samsung Galaxy Nexus] animal24:
You can pretty much count on wallet never being there unless you put it there. The WebKit browser is still here. I like it better than chrome for a handset. And it supports flash.
[Samsung Galaxy Nexus] Easton999GS:
If no one uploads this by morning I'll just upload a zip myself
[Samsung Galaxy Nexus] animal24:
Disregard
[Samsung Galaxy Nexus] jsprake1:
Thanks everyone. Updated through the tool kit without root or unlocking ........

and running smooth.
[Samsung Galaxy Nexus] animal24:
You wait for the nota to be officially pushed ;)
[Samsung Galaxy Nexus] OSully:
Thank you for responding.

If you don't mind... Is any bloat included? Sorry, I haven't been on stock since.. Well close to the phone release.:)
[Samsung Galaxy Nexus] El Daddy:
I meant no, it cannot be flashed without using a computer or a custom recovery. There isn't a way to flash it with stock recovery.

However, if you are rooted you can download ROM manager. Flash cwm recovery from there. Put the ota.zip on your phones storage and flash from your custom recovery.
[Samsung Galaxy Nexus] mwalt2:
If by bloat, you mean the 9 extra files (or approximately 900 files in a ROM) that are not part of aosp, yes they are there.
[Samsung Galaxy Nexus] ironside2011:
Ok so can a custom recovery be put in the phone without a computer
[Samsung Galaxy Nexus] El Daddy:
If you are rooted yes. I wrote how to do it in my last post.
[Samsung Galaxy Nexus] DirgeExtinction:
If you're rooted, you can download Clockwork Mod. Not sure if you need to have your bootloader unlocked, though.
[Samsung Galaxy Nexus] Winesnob:
Yes there is a way to flash without custom recovery. Beginning with 4.1.1 stock recovery included options to update via USB or ADB. And I know it works because I used it on my Xoom for 4.1.2 and just used on my locked GNex to install this update.
[Samsung Galaxy Nexus] El Daddy:
I know that. He asked without a computer :)
[Samsung Galaxy Nexus] ironside2011:
I guess I'll have to wait then... hopefully not too long
[Samsung Galaxy Nexus] Winesnob:
Yes, that's what USB is for. Downloaded the update on my Xoom, transferred to a USB drive via otg cable, plugged into GNex, installed update. No PC required.
[Samsung Galaxy Nexus] donnyp1:
Anyone have a link for stock rooted 4.1.1? Or do i have to pull out the toolkit?
[Samsung Galaxy Nexus] El Daddy:
Interesting. I know about adb sideload, but that method is news to me. I haven't had the gnex since the N4 launch and the N4 doesn't support otg so I'm out of the loop I guess.

Thanks for the info.
[Samsung Galaxy Nexus] mwalt2:
Radios posted here. I did it the same way as I did for the 4.0.4 radios. I pulled the lte radio with

adb shell dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio.img

and just put it and the cdma radio in a flashable .zip. It flashes fine for me using a custom recovery. I did not test fastboot, but the lte radio may not work using that method (it did not the last time I pulled them this way).
[Samsung Galaxy Nexus] DirgeExtinction:
Wait, what? No USB OTG on the N4?
[Samsung Galaxy Nexus] El Daddy:
Nope. It doesn't supply enough voltage.
[Samsung Galaxy Nexus] ironside2011:
So how do I do this USB method? I have a Samsung Galaxy tab
[Samsung Galaxy Nexus] formula84:
Has the bootloader been updated as well?

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Nephilim:
There is no new bootloader.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] wavedashdoc:
Flashed new radios, everything's working great! so far I have 3 bars where I normally only have 2 and my dbm is -90 instead of right before the flash where it was at -103. Seems like a decent improvement. Will see how the battery life is in the coming days. (Running MMuzzy build 3.1.13 and FK 366)
[Samsung Galaxy Nexus] Flapjack:
I flashed the new radios and got an repeating "System UI" FC upon rebooting.

I rebooted into recovery and flashed my old radio, but it's still happening.

I'm thinking it isn't radio-related.....
[Samsung Galaxy Nexus] Nephilim:
New radios working no prob here.

Sent from my AK Cylon Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] JPBeard21:
I don't have before/after signal readings, however I live in an area with very weak 4g and only slightly stronger 3g. My phone would always fluctuate between 3g and 4g but now it seems to stick to 4g much better. Even when it reads 0 dbm. So far so good.

---------- Post added at 12:05 AM ---------- Previous post was at 12:02 AM ----------

Not sure if you are in a custom ROM or recovery or what. Try fixing permissions or dirty flash your ROM.
[Samsung Galaxy Nexus] Flapjack:
Yeah, I just wiped the cache and dalvik and am rebooting now. If that doesn't work, I'll try permissions.

EDIT

That didn't work. Trying permissions, then dirty flash.
[Samsung Galaxy Nexus] Redflea:
Also flashed, no issues, radios updated.

I feel faster, stronger, and better looking with the new radios.
[Samsung Galaxy Nexus] Flapjack:
Fixing permissions didn't help either.

Any suggestions before I dirty flash the rom again?
[Samsung Galaxy Nexus] JayR_Themer:
Will these radios make my phone 5 times faster and signal ten times stronger? Or will they just change my soft keys like all the rest? If not, can i whine about them not working afterwards because i truly dont understand how radios work? Also, how do i flash them? Can i flash them without being rooted? Im so happy right now i think i tinkled my pants. Also, will these radios work in germany?
[Samsung Galaxy Nexus] mark manning:
Are you on 4.2 or 4.1?
[Samsung Galaxy Nexus] Flapjack:
4.2.2, with matching kernel and binaries.

This is the rom I'm using:

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

**EDIT**

Reflashing his ROM now. :(
[Samsung Galaxy Nexus] The_other_ray:
I'm getting a status 7 error. Failed to install.
[Samsung Galaxy Nexus] JPBeard21:
Probably a bad download.
[Samsung Galaxy Nexus] The_other_ray:
The file I downloaded is 88 megs. Is that right?
[Samsung Galaxy Nexus] mwalt2:
Stock, rooted, deodexed version of the Verizon JDQ39 ROM here.
[Samsung Galaxy Nexus] JPBeard21:
For the update, yes. But check your md5 or redownload.
[Samsung Galaxy Nexus] efrant:
Aside from what Winesnob suggested, there is also another method to flash with a stock recovery and no computer that should work (assuming you have root): download the update file and move it to /cache. Then either wait, or click on the check for update button in settings.
[Samsung Galaxy Nexus] Winesnob:
There should be a failed assert message with that error, identifying the problem. Have you changed any of the system apps on your device or using different radios than came with 4.1.1?
[Samsung Galaxy Nexus] The_other_ray:
I didn't change any system apps. The only thing I can think of that might have changed it is Cerberus because when rooted you can add Cerberus to the system so it remains on your phone even when wiped.
[Samsung Galaxy Nexus] shag_on_e:
That'll do it man. The updater script uses a bunch of assert checks to make sure every app is in place before patching.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] The_other_ray:
Thanks for the help.
[Samsung Galaxy Nexus] Big ZD:
I understand that the nexus gps performance/capabilities are heavily related to hardware, however, folks over on the sprint nexus noted improvements in this area after receiving 4.2.1.

Are their observations placebo? Has anyone running stock 4.2.2 noted an improvement with gps lock times?

Sent from my Verizon Galaxy Nexus
[Samsung Galaxy Nexus] efrant:
Adding files to /system will not make the update fail. Modifying or deleting files in /system will, but not adding.
[Samsung Galaxy Nexus] shag_on_e:
Gotcha, I don't dwell on stock long so I don't see these problems often, but looking through the zips updater I assumed it would cause a problem not having an odex file along with the app in /system. Live and learn.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] treoo0_1:
Fastest GPS lock I've ever seen, with this Verizon leak! Wow.
[Samsung Galaxy Nexus] oldblue910:
So...after playing with this for a while...I have to say the new radios seem better in terms of 3G/4G switching. Where I live, signals sucks in buildings but it's generally OK outside. Inside, my phone will only pick up a 3G signal. On the IMM76K and JRO03O radios, a lot of times, I'd walk outside and my phone would stay on 3G sometimes five minutes or more before it would finally switch to 4G. This seems much better on these new radios. I did a few tests this morning and the switchover happened in a much more reasonable amount of time...normally 30-45 seconds.

Overall, I'm very satisfied. I've been enjoying 4.2.2 on my Nexus 4, but it's really nice to have it on that beautiful, vivid, oversaturated, color-inaccurate Super AMOLED display on the Galaxy Nexus. :D
[Samsung Galaxy Nexus] The_other_ray:
Anyone's Foxfi /pdanet or wireless tether for root not working?
[Samsung Galaxy Nexus] Big ZD:
Is this sarcasm or pure elation? Not trying to be picky, I simply can't tell.

Thanks for the response if it's the latter!

Sent from my Verizon Galaxy Nexus
[Samsung Galaxy Nexus] y2jdmbfan:
Anyone else having problems with Mobile Hotspot not working on 4.2.2? I pay extra to Verizon per month, and I can connect, but something is wrong with the routing to the internet.

Thanks,

Y2J
[Samsung Galaxy Nexus] oldblue910:
Funny, I actually had that problem with connecting my N7 and N10 to my Gnex on 4.1.1/JRO03O but the 4.2.2/JDQ39 ROM seems to have fixed it for me.
[Samsung Galaxy Nexus] mechapathy:
Two things I've noticed. In Google Now I can no longer say "Google" to search, and iWNN IME is gone. The emoji isn't a big deal, as I've simply taken it from my N7 and installed it on my GN.

Anyone else notice the issue in Google Now?
[Samsung Galaxy Nexus] keyslapper:
Actually, I've only ever had one problem with routing in my GNex, and it had nothing to do with tethering - that always worked fine. The problem I had was with my mail setup. I currently have my work email (Exchange) set up, and no problems there, but my personal email account (which I run myself on a Linode VPS) won't connect using the primary domain. The only way I could work around it was to set it up using another email domain that points to the same server. Since it worked, I never bothered investigating much, so I have no clue why this happens. :confused:

So far no problems, and I'm really liking this update. 3G signal seems much better - and stable, and I like having the lock screen widgets on the phone.

Cheers!
[Samsung Galaxy Nexus] oldblue910:
Google Now still has working hotword detection for me (saying "Google"). I don't use iWNN IME so I'm not sure how to check that.
[Samsung Galaxy Nexus] mechapathy:
Hmm guess I'll do some safe mode investigation. Thanks again for your work with El Madhatter!

Edit: Yup, it's an app breaking hotword detection. Not sure which, but it works in safe mode.
[Samsung Galaxy Nexus] Manofthehr:
I just flashed the new radios as well... so far, so good!
[Samsung Galaxy Nexus] oldblue910:
As a hint, any app that plays sound, such as music apps or something like that, can break hotword detection. Basically any app using the speaker for something. Don't know if that helps, but that might be a place to start.
[Samsung Galaxy Nexus] mechapathy:
Thanks. I figured it out. It turned out to be Aging Booth (ugh). I just started uninstalling my most recently installed apps til it came back. I definitely won't miss that app lol
[Samsung Galaxy Nexus] kb8no:
So somebody please be so kind as to help me with understanding and tell if I got this right.

Google released OTA 4.2.2 android update for GNex. We have Google general released 4.2.2 and are using it on this phone already but the OTA release has GNex specific goodies such as binaries, drivers, and radios. What everyone has been eagerly anticipating is the new radios and the cause of the excitement. Deficiencies in the GNex radios have been problematic so far. You have extracted the radios from the OTA and put them in a separate flashable format with the zip being flashed in recovery being the easiest to apply for most people.

Yes ? No?
[Samsung Galaxy Nexus] diobando:
Yes

http://xdaforums.com/showthread.php?t=2176895
[Samsung Galaxy Nexus] diobando:
Can I update a complete stock VZN GNX running JRO03O to JDQ39 without unlocking bootloader or rooting?. Can I use the method described here: http://xdaforums.com/showpost.php?p=28181832&postcount=2? is JRO03O considered newer than JRN84D with a new stock recovery?
[Samsung Galaxy Nexus] El Madhatter:
Very true, oldblue910 - too funny!
[Samsung Galaxy Nexus] :
sorry im new to the gnex toro, but typically how long after the leak does it take for the OTA to hit?
[Samsung Galaxy Nexus] oldblue910:
Historically, about a month.
[Samsung Galaxy Nexus] ironside2011:
I'm gonna agree! Specially since they're still quite as a clam on they're Twitter support forum

However we all could be wrong and see it in a week

---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------

On another note. Has anyone adb sideloaded the update?
[Samsung Galaxy Nexus] oldblue910:
Yeah who knows. IMM30B leaked but was never released publicly. IMM76K took about a month from leak to release. JRO03O was the same... about a month.

I did last night. Worked perfectly.
[Samsung Galaxy Nexus] ironside2011:
Cool! Read through most of the flash guys here. Some had a Lotta problems but didn't see any side loaders
[Samsung Galaxy Nexus] oldblue910:
Everyone who has problems flashing an OTA does so because they lose sight of two simple facts: One, you have to be running the stock ROM with the right radios, the right kernel, and absolutely no file in the system partition can have been deleted or modified in any way. Second, if using a custom recovery, you cannot auto-flash OTAs. You have to flash them manually. Period, the end.

If those conditions are met, there will never be an issue flashing an OTA. But alas, it has become too easy for people to root and mod their devices without having any real concept of what it is they're doing and what the repercussions could be. It's both a blessing and a curse.
[Samsung Galaxy Nexus] ironside2011:
I learned that one the hard way with my Dinc . I forgot I had installed busybox and deoxed it and had CWM. so I couldn't receive the ota for until 4 hrs of swearing and a few soft bricks were solved
[Samsung Galaxy Nexus] El Daddy:
No, it's just a curse. :)
[Samsung Galaxy Nexus] oldblue910:
Been there. My first experience with rooting was on an HTC/T-Mobile G2. Getting back to stock after deciding I didn't really like CM7 was full of expletives and sweating bullets. From there I went to a Nexus S and was amazed at how simple this stuff was when you had an unlockable bootloader.
[Samsung Galaxy Nexus] oldblue910:
You got the OTA?
[Samsung Galaxy Nexus] ironside2011:
I 2nd that question? !!
[Samsung Galaxy Nexus] oldblue910:
Hardly any Nexus devices saw 4.0.3. The only ones that did was the 900 MHz (T-Mobile) unlocked GSM Nexus S and the WiFi-only Xoom. No Galaxy Nexus device saw it, nor did the VZW Xoom, nor the 850 MHz (AT&T/Rogers) unlocked GSM, Sprint, or Korea Nexus S.
[Samsung Galaxy Nexus] Winesnob:
I stand corrected on takju/yakju. Did these variants stay on 4.0.1 until 4.0.4?
[Samsung Galaxy Nexus] oldblue910:
No, they got 4.0.2/ICL53F in December just like VZW, then didn't see another update until 4.0.4/IMM76D in March. IMM76D was stopped about a week after initial rollout due to a lot of phones losing all radio functionality when the screen was powered off. IMM76I fixed this and was rolled out in very early April. Obviously VZW stayed on 4.0.2/ICL53F until late May when 4.0.4/IMM76K rolled out.
[Samsung Galaxy Nexus] oldblue910:
Someone with the know-how should make "interim" ROMs for the VZW Gnex. Like right now, someone should create a 4.2.1/JOP40D ROM that exactly mirrors a Verizon build. Give it a mysid build siguature along with the yakju or takju 4.2.1 release keys number (which are identical), release the ROM odexed with absolutely zero customizations whatsoever. And when I say zero customizations, I mean none. Leave the WiFi-tethering check in there, leave in the Verizon apps, non-rooted, stock kernel, etc. Basically provide mysid until Google is able to roll it out. I bet you'd have a $h1+ ton of people that would use it. I think even *I* might use it.
[Samsung Galaxy Nexus] stephenwdaniels:
Q2 at best - Verizon hates customers

They already made their money on this handset and are not motivated to collaborate with hardware or software vendors to test and release this version. I gave up on VZW long ago and spend my money on donations to Cyanogen. They do more to extend the lifespan of handsets than any other group in the Android ecosystem. I am already running the 10.1 nightlies and it is pretty good two builds in.
[Samsung Galaxy Nexus] Winesnob:
You should really take a few minutes and read this thread, not to mention oldblue's blog on randomphantasmagoria. He's pretty much spot on with the Verizon update process and timetables. We will get 4.2, but just not right now. BTW, Verizon is still selling brand new GNex's in a new 16GB model - it isn't dead quite yet.
[Samsung Galaxy Nexus] ironside2011:
I can't believe the OG Droid RAZR and MAXX are getting 4.1.2 from Verizon today. Verizon clearly doesn't know the concept of the whole nexus program
[Samsung Galaxy Nexus] Winesnob:
Keep in mind that 4.2 probably isn't a glimmer in the eye of these devices yet, and we have to assume that Verizon has skipped 4.1.2 on the Nexus since well likely jump directly to 4.2.x.
[Samsung Galaxy Nexus] DirgeExtinction:
Considering we've officially been on 4.1 for a while now, before any other Verizon phone had it, I'm not that bugged about it.
[Samsung Galaxy Nexus] 063_XOBX:
I don't follow that logic. 4.1 is still 3 builds behind.
[Samsung Galaxy Nexus] Winesnob:
Your are technically correct. However...

4.1.2 was a bug fix, adding single finger notification expansions, patched the root without unlocking exploit, and other minor fixes.

4.2 added new camera, lock screen widgets, and overall enhancement to functionality.

4.2.1 added December back, patched some Bluetooth issues.

4.1.2 doesn't really enhance 4.1.1 all that much. 4.2 added some nice upgrades, particularly with the photo sphere camera. Multiuser on tablets is spectacular in my opinion, but doesn't do anything for the GNex. 4.2.1 fixed early bugs. In all, we're functionally 1 build behind.
[Samsung Galaxy Nexus] oldblue910:
This man gets it. Well stated, sir. People get so caught up in build numbers and Android version numbers that they lose sight of the big picture.
[Samsung Galaxy Nexus] oldblue910:
I'm perfectly content to wait on 4.2 for my Verizon Gnex. 4.2 for the N7 introduced a ton of lag and hiccups, and 4.2 for the N10 suffers from random freezes and subsequent reboots. I'm in no hurry for my Gnex to end up with whatever issues guys with GSM yakju/takju installs are running into. 4.1.1/JRO03O, on the other hand, runs absolutely beautifully on the Verizon model.
[Samsung Galaxy Nexus] darklordofthesith:
Been running Mmuzzys 4.2.1 for a bit now. Flawless so far. Man really knows his ****.
[Samsung Galaxy Nexus] zerocool79346:
Root and ROM it. It isn't like the majority of us have a warranty anymore anyway, as if it matters either way.
[Samsung Galaxy Nexus] oldblue910:
Except some of us actually like the stock ROM. Personally I don't want all the features and customizations that custom ROMs provide, plus I don't like having my bootloader unlocked because it decreases device security substantially. I don't buy Nexus devices to root and mess around with them. I buy them for the quick updates and the stock Android experience.