yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] georgiapi:
Called Verizon, told them about the post OTA animation looping. The V-tech activated a 3-way call with a Samsung rep that heard the story. The S-rep immediately went into telling me to ship the phone in for repairs and of the estimated 9-day turn around time line. The V-tech interrupted her and let her know that will not be necessary that Verizon will take it from there.

I'll have the replacement tomorrow. My good-ole OG Droid is back in action till then. I have had offers to buy my OG that I turned down. It's in like new condition.:good:
[Samsung Galaxy Nexus] withbloodskies:
Lol that's awesome, glad Verizon went to do something. Dunno why Samsung rep would say that :confused:

Confused as to why you got a boot loop.. very odd.
[Samsung Galaxy Nexus] hawkeye680:
I just prefer to do it without the additional software. I only use root for wireless tethering and a few other apps.
[Samsung Galaxy Nexus] georgiapi:
As soon as the Sammy rep heard the OTA broke the phone there was no hesitation in granting a return for repair. No questions, no - try this, trey that, nothing, just gimmie the device.
[Samsung Galaxy Nexus] efrant:
You don't have to flash CWM -- you just use it to get root access so that you can copy the "root files" over to system. See the "root" link in my signature.
[Samsung Galaxy Nexus] fearstyle:
working on getting my self flashed... doing a backup now....
[Samsung Galaxy Nexus] glennj99:
I am glad the OTA is good for you!

I want to warn people with unlimited data plans though. The OTA makes any kind of tethering impossible now without you subscribing to an additional $30 per month "service" from Verizon, so if you are still unlimited and need tethering you might want to avoid this OTA for now.

I am hoping to get some help about how to undo this OTA, personally. Help? Unrooted stock, no nandroid for this particular phone.
[Samsung Galaxy Nexus] blackhand1001:
Just flash cm10 if you want tethering. Or a pure aosp ROM. Works fine on mine. If your on rooted stock you can run the patch that removes the tethering plan check. Its always been this way. Its not new to this ota.
[Samsung Galaxy Nexus] segv11:
There are also root apps that work on a stock ROM that do a good job.

Sent from my Jelly Beaned "toro" Galaxy Nexus.
[Samsung Galaxy Nexus] glennj99:
I have been looking into this and I am finding that I probably made a mistake loading the Samsung galaxy nexus drivers from Samsung into win7 32bit which did not give me fastboot access, just adb. Then I went ahead and installed the Android SDK from Google, but still no fastboot access. I'll figure this out, without a one-click tool, but I'm stuck with unrooted stock 4.1.1 until I do. Sounds like the easiest thing to do is root then patch to avoid the subscription check with stock tethering. Not sure where to find that, but I will eventually. Got to root first though.

I was just using FoxFi before, on this device. Easier than applying the tbh-radiohack was on my D3...should have looked into GNexus tethering a little more closely before now. When FoxFi broke under JB I was not ready with an alternative method.

Thanks for all the help so far.
[Samsung Galaxy Nexus] georgiapi:
What about PdaNet viua USB until you get where you want to be?
[Samsung Galaxy Nexus] 2ksilverbullet:
Pm sent...
[Samsung Galaxy Nexus] glennj99:
Got to support multiple laptops off and on for the next few days via WiFi and 4g. Might spend the $30 for that. Thanks though !
[Samsung Galaxy Nexus] hawkeye680:
efrant, please forgive my ignorance, but using your instructions, is that boot image the most up to date version?
[Samsung Galaxy Nexus] mbrown3460:
Which apps?
[Samsung Galaxy Nexus] tailsthecat3:
I've been using PDANet for years. I've never not been able to tether through all the carriers I've used and all the different phones. Great program.
[Samsung Galaxy Nexus] jordache16:
Finally received the OTA update this morning. Loving me some JellyBean.
[Samsung Galaxy Nexus] georgiapi:
In short - PdaNet is a great App to have in your arsenal. No regrets here

I have used lots of tethering apps and PdaNet is one of the, if not the most stable. Rather you be USB or wireless it will run @ 0 latency if a system was capable. In other words, no bottle necks.

Wireless is nice but USB lets you keep your battery up. I have seen folks wireless tethering with a wall charger connected to the phone, HuH?
[Samsung Galaxy Nexus] PipeHitter:
Which patch for the rooted stock ROM are you referring to?
[Samsung Galaxy Nexus] DLCPhoto:
I'm having the opposite problem. I was on Stock Verizon 4.0.4, and never had any problems with my 3G Network Extender.

I got upgraded OTA this morning to 4.1.1 and was initially pleasantly surprised to see "Network Extender" showing when I turn the phone on, at the bottom of the display, and also at the bottom of the notification page when it was swiped down. Pretty slick!

But unfortunately, I have found that it will show connection to the Network Extender for a few seconds or longer, and then will revert back to "Verizon Wireless" and I lose my NE connection. This is confirmed by calling #48 to test if the connection is there.

I have reset the Extender. I have powered down the phone, pulled the SIM, and rebooted. Nothing changed. I called Verizon Tech Support and they didn't have other reports of this problem, and are supposed to get back to me tomorrow.

Am I the only one with unstable Network Extender connectivity with JB?

Any other suggestions on how I might resolve this?
[Samsung Galaxy Nexus] georgiapi:
I am using one and it is like yours but it stays. No issues on mine.
[Samsung Galaxy Nexus] DLCPhoto:
Thanks for the report. I wonder what the problem is on mine.

I also find the boot time is extremely long: about 2 1/2 minutes before the "Google" label disappears, and another 30 seconds with the small multi-colored "X" in the middle of the display before it boots in. I did a little searching and found that some have this problem for file system checking with an irregular shut-down, but there was nothing out of the ordinary when turning my phone off that I could see.

Could these issues be related?
[Samsung Galaxy Nexus] DLCPhoto:
Quick update:

The phone booted at normal speed this morning, but still won't connect properly with the Network Extender, so that is apparently a separate issue.

Anybody else with NE problems after JB update, or any suggestions on what I can try that might fix this? I guess a full reset might be in my future, but I hate to have to reinstall/reconfigure everything!
[Samsung Galaxy Nexus] Winesnob:
I can't speak for network extender problems, but I was having random reboots after installing updates from the Play Store, and ridiculously slow boot times. Once the 4.1.1 factory image was posted, I wiped all of the partitions clean using fast boot and then laid on the fresh image. Lo and behold, it doesn't hang at the Google logo on boot, and the post- Play Store reboots also stopped. And for the first time on any Android device, all of my apps immediately started installing from the Play Store. Factory wipe/reset is a pain, but it has fixed my few issues with JB.
[Samsung Galaxy Nexus] DLCPhoto:
Thanks for the reply.

If I do go ahead with factory reset, is there a way to get an *image* of my current setup, in case that doesn't fix it?

What I mean is that I use Casper (like Acronis, or Norton Ghost) to create a complete image of my computer's hard drive, which can be used to completely recreate it should a problem arise.

Is there an equivalent way of doing this with an Android Phone?

That way, I could quickly restore where I am now in case a factory reset doesn't in fact solve the problem.
[Samsung Galaxy Nexus] Winesnob:
If you are rooted (which I am not) I believe you can do a nandroid backup which is a full image that can be restored. If not, you can use a toolkit or direct adb commands to backup your apps and data (and system apps and data if you desire), which will allow you a total restore after installing the clean image. This has it problems, in that if bad data is backed up and restored on a fresh image, you're right back where you started. I went for the full reset and started over. Painful, but seems to have worked. Same thing on my Xoom wifi when JB rolled out. Started fresh after a few hiccups and all has been well since.

And if you are using Google Wallet, be sure to do a reset in the app itself before doing a factory reset/clean install or you risk bricking the secure element (unless they've fixed that issue in later Android or app updates)
[Samsung Galaxy Nexus] DLCPhoto:
Thanks. Yeah, if a factory reset fixed the problem, it would be stupid to do a restore, since that would more likely bring back the original problem. My thought was that if the problem persisted, then at least I would save time and just quickly go back to where I was before.

But the more I think about it, it probably just makes sense to reinstall everything - less likely to create problems. Oh well....
[Samsung Galaxy Nexus] tailsthecat3:
I'm sort of in the same boat. I've had issues with jb in that the phone always locks up when I access the apps list in settings. Sometimes right away, sometimes after I force stop something, and only on jb has this happened. I was thinking of going back to ICS until I get a new phone which I'm certain won't be long. But I am rooted with cw, and have also contemplated doing a factory reset within cw. My computer is down and out at the moment so I can't flash the factory images. Since I have a bunch of junk removed from /system, I think a recovery reset may be a good starting point. Opinions, input? Thanks!!! :)

P.S. Haven't found a way to get factory images on it w/out a computer?
[Samsung Galaxy Nexus] DLCPhoto:
For what it's worth, this problem seems to have fixed itself. The only change I see is that the PRL is now 14613 whereas before it was either 14602 or 14603.

I am on a grandfathered Alltel plan, so perhaps that has something to do with it.

FWIW.
[Samsung Galaxy Nexus] serty4011:
I would start by flashing the Verizon Jelly Bean system image.. Backing up everything before hand, of course.
[Samsung Galaxy Nexus] tailsthecat3:
For one, I can't find it via the xda app. Two, I'm ridiculously tired and my brain is hot. You must mean the factory image? Cause as noted, my PC is down atm so unless I can achieve this without one, cw is my only option, for that anyway... or I do a reset from within cw
[Samsung Galaxy Nexus] serty4011:
Google search "nexus factory image" and select the first search result. Yes, you will need a PC.
[Samsung Galaxy Nexus] tailsthecat3:
Oh, I know all about it. Best part about the nexus s was flashing those images in fastboot. Jw if there was a "PC free" option. Zoinks.
[Samsung Galaxy Nexus] serty4011:
The closest thing to a PC free option that I know of would be to download and install someone else's Nandroid backup.
[Samsung Galaxy Nexus] tailsthecat3:
It's cool. I did a factory reset, got it back to how I like it and the thing *still* locks up in the apps screen of the settings. This absolutely never happened with ICS so I may go back to 4.0.4 before I start throwing bricks though the windows of my local vzw store. So incredibly frustrating to have to do a battery pull. Worse is that I've never experienced this with any phone, including the nexus I had on sprint. I'm slowly isolating jb as the issue.
[Samsung Galaxy Nexus] bozzykid:
I've had the apps screen lockup only twice. Once on ICS and once on JB. Both required pulling the battery. However, I rarely go to the apps settings page except after a factory reset (or new ROM install), so it isn't a big deal for me.
[Samsung Galaxy Nexus] tailsthecat3:
womp womp

So last night I loaded the factory images of JB(radios and all) and *still* encountered the lock up while in the apps section of settings. I locked it up, unlocked it, everything was wiped, etc. Ive since reverted back to ICS and havent had an issue with the phone locking up. Plus I can remove that annoying quick search box while retaining the voice input of the stock keyboard, something that couldnt be done in JB. If I wanted to remove the search box, it would remove google search which disabled the voice input for the keyboard. So, I got a half solution here...gps still sucks and Im far too lazy to struggle with verizon for a replacement/exchange whatever.
[Samsung Galaxy Nexus] Winesnob:
Not to discount anything you did, but did you erase the various partitions via fast boot? When I reloaded the factory image I did a 'fastboot erase userdata' and the other partitions I knew of (system, boot) that might have retained bad bits. Not having the issues any longer.
[Samsung Galaxy Nexus] oldblue910:
Just make sure you don't do fastboot erase on bootloader or radio! Only do it on recovery, boot, system, userdata, and cache.
[Samsung Galaxy Nexus] Winesnob:
Thanks for adding that info!
[Samsung Galaxy Nexus] tailsthecat3:
Tonight I'm gonna try erasing all that via fastboot. Then I'll restore 4.0.4 and take the ota to jb. After doing fresh installs of factory images, etc., settings still becomes unresponsive while I'm in the apps section. It will eventually, after about three minutes, tell me that settings is not responding and asks if I'd like to wait or close it. Quite troubling but I did revert to ICS a couple of times during long nights and didn't experience any lockups.

I've still got some testing and work to do but I'm slowly isolating jb as the culprit. Stupid work getting in the way of precious Android diag time.
[Samsung Galaxy Nexus] efrant:
Not sure why you are having the issues you are having. As long as you flash the following Jelly Bean images in fastboot, you should be ok. (I know you probably have done that already, but others have reported to have to do it more than once:

bootloader

radio

radio-cdma

system

boot

userdata

recovery

And erase the cache.
[Samsung Galaxy Nexus] tailsthecat3:
Thanks! All the "guides" state to reboot the bootloader after every command, something that wasn't necessary on the nexus s in my experience. Do you think it's vital to do? And do you think if I restore to 4.0.4 then take the ota, that that would be a good process?

I can tell you that when I type the command to flash image, it has told me failed :"unknown partition". Which I found odd. The factory images I got from Google don't seem to have all those components, also. When I get home, I'll take some detailed info of the .img and .zip files I have. If I could download the components you say I need to my phone while at work, that'd be convenient. I don't suppose you could provide a link? Seeing as how y'all are trusted...frankly if you link the files, I'd trust that more than the files I got and extracted myself. Thanks, efrant
[Samsung Galaxy Nexus] efrant:
Follow the instructions in the second how-to link in my signature and flash JB right away. It is pointless to flash ICS and update to JB.
[Samsung Galaxy Nexus] tailsthecat3:
Awesome. Thank you. That looks more like what I was used to with the nexus s. Right off I can see...I was using something other than 7zip, which could have been a problem. I didn't have userdata, system, etc. I had the radios, a file named image and the bootloader, if I'm not mistaken. Thanks, man. Now if only this silly work day would end, I could tend to more important matters. I'm literally just sitting, managing. boring but worth the money. Five hours to go. Thanks again.
[Samsung Galaxy Nexus] Anthonok:
Mine locks up as well. Stock vzw jb. I flashed the images from Google. Didn't happen on any other ROM just the stock image. I never use that part of the settings so it doesn't bother me but it is strange
[Samsung Galaxy Nexus] tailsthecat3:
Process complete. Still locks up on that apps screen in settings. It will bring itself back after a few moments. However, I swiped over to running apps just at the right moment to see SystemUI restarting. I haven't found a logcat that works on JB. Does it exist? Now I'm beginning to believe that the jb systemui apk could very well be the culprit. Thanks, guys.
[Samsung Galaxy Nexus] Anthonok:
Interesting. Do you use the apps menu enough for it to really bother you though? It is very strange that it being an official ota that a main setting would go non responsive.... so much for the ota rollout taking so long being verizons "thorough" testing.
[Samsung Galaxy Nexus] tailsthecat3:
Yeah, I'm usually in there shutting things down. Maps mostly. But yes, I hate when things lock up. I received a replacement device and it suffered from the same symptoms. Even without any apps installed. So I'm sending them the replacement that they sent me and keeping my original. I really have an issue with carriers replacing devices purchased new with used, refurbished devices. The only real preference for jb over ICS is project butter. For me anyway. I'm waiting on a callback from a rep who was talking about getting me into a "different 4G device". We shall see what happens when they call back. If vzw doesn't get the next nexus, I'm out.
[Samsung Galaxy Nexus] svtfmook:
have you tried a factory reset?

have you tried installing cwm and formatting cache/dalvik?

i received 2 new vzw gnex's friday, turned them on, activated, found the update, installed and everything works fine on both devices. it could be left overs causing problems. in fact, i would even factory reset, downgrade, factory reset, then reinstall the upgrade.
[Samsung Galaxy Nexus] Winesnob:
Maybe some of the processes you are shutting down are causing the lock up? Ever since GB (former Fascinate owner), I've just let Android manage the processes and done quite well. Recently I've been cleaning apps from my devices, eliminating redundancies, stuff I really don't use, etc. and already noted performance improvements. ICS was great, but JB has been spectacular. Outside of a buggy install after the VZW leak was posted, did a full wipe and laid on the factory image from Google, and after that no issues.
[Samsung Galaxy Nexus] Anthonok:
I have the problem with a clean Install of the factory image for 4.1.1 I dont even have to close anything n the menu and it does It. Just have to sit in the screen for a few seconds and it does it.
[Samsung Galaxy Nexus] tailsthecat3:
This is exactly true.

---------------

Yes, previous posters, I have done everything possible.
[Samsung Galaxy Nexus] PipeHitter:
Not erasing bootloader makes sense - if the device gets rebooted, it wont know what to do. Although I thought I read somewhere that there was a fail-safe to prevent that from happening. Might try to find the reference.

However, whats the danger in erasing radios? Could you not simply flash a new radio?
[Samsung Galaxy Nexus] efrant:
Although I've never tried it myself, someone here on XDA did report that trying "fastboot erase bootloader" and "fastboot erase radio" return errors.

As for why, if I understand correctly, the radio is also part of the boot chain, so that may be the reason.
[Samsung Galaxy Nexus] WormDoes:
Really hope this includes radios :D
[Samsung Galaxy Nexus] blaine07:
Oooh exciting
[Samsung Galaxy Nexus] krazie1:
Haha i said JRO030 when its actually JRO03O, too Excited
[Samsung Galaxy Nexus] Dragn4rce:
Anybody report this to android central or android police or something???

I emailed AC about this.

-------------------------------------------------

If I have helped you.... hit that sexy thanks button. ^_^
[Samsung Galaxy Nexus] WormDoes:
^^ I read about this on Droid Life so I'm sure all the blogs know about it
[Samsung Galaxy Nexus] agalvin13:
i have refreshed this thread so many times. NEED this update.zip
[Samsung Galaxy Nexus] jova33:
radios? :)
[Samsung Galaxy Nexus] floobmonsrake:
Yes, please.
[Samsung Galaxy Nexus] oldblue910:
Guys unfortunately it looks like he's out for the night so I think this will have to be continued tomorrow...
[Samsung Galaxy Nexus] withbloodskies:
Some interesting Vzw news be brewing a storm :beer:
[Samsung Galaxy Nexus] RW-1:
I could care less about this update, if only the first of what is likely several soak tests, besides the ROM dev's are way further along in AOSP than anything VZ will push out.

But the radios hold promise.
[Samsung Galaxy Nexus] DirgeExtinction:
Well, what most people are wanting are newer radios and a newer build with fixes and enhancements.
[Samsung Galaxy Nexus] withbloodskies:
Exactly if we get the ota source jb ROMs made from these will make them more stable and so forth.
[Samsung Galaxy Nexus] oldblue910:
OK gentlemen, this is definitely a testing build. It requires you first install the IMM76Q update. So you need to flash to IMM76K, upgrade to IMM76Q, then to JRO03O. The link is here:

http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76Q.4a91da6c.zip

All the thanks goes to El Madhatter. I'm mirroring the file at randomphantasmagoria.com as I speak.
[Samsung Galaxy Nexus] MarkGbe:
awesome, thanks. Can't seem to fine IMM76Q anywhere though.
[Samsung Galaxy Nexus] Christopher3712:
Good stuff, thanks for posting the link. Will click that button for both of you. Time to play.

Oooo! I see radios!
[Samsung Galaxy Nexus] spencer88:
Yeah I think that was the update that disabled local search, which I didn't install.
[Samsung Galaxy Nexus] kecknj:
This day keeps getting better and better! First I get the tracking number for my 64gb champagne infinity pad, now this!

So if I am already on IMM76Q, I can just flash the zip? Also, will root be affected?
[Samsung Galaxy Nexus] MarkGbe:
cool, thanks
[Samsung Galaxy Nexus] yearziro:
+1 on the root.... also dont know if im being paranoid but reading about the snitch moto is deploying on there phones to show if the device has been rooted or not will somehow be included in this for some reason per vzw....and last but not least for the 100th time radio??? sick of dropping signal every 20 mins
[Samsung Galaxy Nexus] txyaloo:
A new radio isn't going to fix that.
[Samsung Galaxy Nexus] efrant:
EVERY OTA update disables root. But just flash an su zip before rebooting. Too easy.
[Samsung Galaxy Nexus] MarkGbe:
about to flash this, will report on how it goes in a few minutes.
[Samsung Galaxy Nexus] oldblue910:
Looks like it includes a new bootloader (PRIMELC03) and new radios (FF02 CDMA/FG02 LTE). Hopefully this will fix the issues that IMM76K has with 3/4G switching and hanging onto a 4G connection. We'll see...
[Samsung Galaxy Nexus] Winesnob:
Installing now...patched LTE radio and new CDMA...
[Samsung Galaxy Nexus] withbloodskies:
Good stuff :D
[Samsung Galaxy Nexus] biggiestuff:
I'm still on IMM30B. which route would I take to get to this build?

Thanks!!!
[Samsung Galaxy Nexus] kecknj:
So I'm flashed; clockwork gave me the option to fix possible losing recovery and root. It appears we've got a new boot animation and upon start up it optimizes apps and databases (takes some time).

Build: JRO03O

Version: 4.1.1

Radio (CDMA): I515.10 V.FF02

Radio (LTE): I515.FG02

EDIT: Thanks El Madhatter and oldblue910!
[Samsung Galaxy Nexus] efrant:
While the LC03 bootloader may be new for toro devices, it has been out for a while already. (The bootloaders are identical among all devices - maguro, toro, and toroplus.)

---------- Post added at 08:46 AM ---------- Previous post was at 08:45 AM ----------

Have a look at this thread. There is no upgrade path from IMM30B. You need to flash a different build first, then upgrade.
[Samsung Galaxy Nexus] MarkGbe:
flashed and running well. Thanks again to oldblue910, El Madhatter

Also, efrant for the excellent thread
[Samsung Galaxy Nexus] droidrage2010:
Has anyone seen a flashable zip for just the radios? Would love to get my hands on that..

droidrage
[Samsung Galaxy Nexus] kecknj:
Probably too early, the update was posted about and hour ago
[Samsung Galaxy Nexus] Christopher3712:
Was just thinking that. Will try to put one together real quick.
[Samsung Galaxy Nexus] dansan382:
yea definitely looking out for those new radios as im already on AOKP
[Samsung Galaxy Nexus] jweigel:
How to Flash

Can one just copy the zip to your Download folder and then boot into recovery, super wipe, flash this new zip and then GApps????

or do you have to flash back to stock and then do the above?

jjw

ND
[Samsung Galaxy Nexus] kecknj:
has to be from IMM76Q