yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dcp:
Appreciate the help, but the problem I am having is that I can't get into CWM. All I get is the cayanogenmod animation, and it never gets pass this. I've also tried to manually go into recoevry by holding the power button and volume down button and when I do this all I get is a big green arrow that says 'start here', pointing to the power button. Touchscreen doesn't respond to do anything else, and when I do press the power button, the blue animation starts again.

To clarify, I'm just looking for a way to get into recovery. Any other suggestions are welcomed.

Thank you
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
That's the boot loader. Use the volume rocker to select recovery and then hit the power button.
[Samsung Galaxy Nexus] refthemc:
Try reflashing recovery from fastboot and boot into it.
[Samsung Galaxy Nexus] dcp:
It does not give me that option, and volume rockers do not work. All it says is "downloading in progress, do not disrupt."

Could you please let me kow how I can do this.
[Samsung Galaxy Nexus] mark manning:
How goes it?
[Samsung Galaxy Nexus] chazzdjr:
Google it.
[Samsung Galaxy Nexus] nitsua98:
Well goes it.
[Samsung Galaxy Nexus] marc11284:
Kind of surprised no one caught this yet....Holding the volume down + power button brings up the download mode. What you want to do is hold down both the volume up and volume down buttons at the same time while powering on. Kind of press the volume rocker in the middle, you'll feel it click.

You'll be in the bootloader mode, use the volume rocker until you get to recovery. Then you should be good. Wipe and reflash a ROM, or restore a ROM that you've backed up.
[Samsung Galaxy Nexus] nalanotae:
Power off hold volume down while pressing and holding the power when it vibrates let go of both buttons. This will take you to the screen you were previously on with the green android and the big button that says "start". This is the bootloader press the volume button until it days recovery then press the button that says recovery. Should reboot you into recovery.

Sent from my Galaxy Nexus that has been flashed more than a Mardi Gras tourist
[Samsung Galaxy Nexus] dcp:
Thank you both. This is exactly what I needed to know. Phone has been restored. Much appreciated.
[Samsung Galaxy Nexus] nalanotae:
Glad you got it just remember any time some one helps you to hit the thanks button. I know how it is to have your phone messed up and that helpless feeling. I know some members are quick to give a sarcastic answer this forum is here for people to help one another out. I would suggest downloading the nexus tool kit just in case something ever goes really wrong you can always get it back to stock then reroot, it is a must have for gnex owners.

Sent from my Galaxy Nexus that has been flashed more than s tourist at Mardi Gras
[Samsung Galaxy Nexus] tshelby73:
I would also recommend learning how to restore factory image using fastboot commands.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
So I've been on the 8-18 build for awhile and decided to try some other ROMs. Did a full wipe (lock/unlock boot loader) and reflashed the 8-18 build, and now I can't customize notification sounds. I can select the notification, but all my apps just use the default sound (they also display the ringtone name for some reason). Is there any way to fix this?
[Samsung Galaxy Nexus] swyecso:
Interestingly enough I just realized that I made a typo in the build prop and the fix still works. Or at least I haven't been getting any more data drops. On the 9/18 build.
[Samsung Galaxy Nexus] hotrodwinston:
8/18 was pre mms /prl /phone Id fix - HOW THE HECK HAVE YOU NOT HAD MAJOR ISSUES WITH THAT BUILD LONG TERM?

This person, my friends, has the patience of Job.

Edit: or was 8/18 a 4.2.2 build - too lazy to go check
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
8-18 is 4.3

No new features were added since then and I wasn't having any issues, so I saw no need to update. I just got bored and wanted to try something new. Got a little full of myself and didn't nandroid.

I went ahead and clean flashed again and all is well, but now TB won't restore any apps. I changed the backup to the legacy folder but everything still hangs. Not sure what I did before to get it working.

Does it work on the newer builds without having to jump through any hoops? Maybe it's time for me to update...

Edit: 8-18 was pre all those issues btw
[Samsung Galaxy Nexus] hotrodwinston:
I never got tibu to work - ended up using nandroid manager and helium to restore the few I need to restore.

Anybody try the nightlies from the past few days?
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Pretty sure it has something to do with root. I flashed supersu on my previous build and it worked, but that's when I started having the ringtone issue, so I don't want to flash it again.

If it really is root, I'm surprised Koush hasn't fixed it yet.
[Samsung Galaxy Nexus] johnhimm:
10.1.3 stable build is out.
[Samsung Galaxy Nexus] litobirdy:
First On Cm In A While. Can't Customize Nav Bar And Status Bar?

I've been on AOKP for more than a year, but decided to give CM a try since they seem really good too. Well today I'm on 10.1.3 stables on my verizon Nexus. But wow, barely any customization for the Status Bar and Nav Bar.

The Status bar I would just want at least transparency. But for Nav bar, man I am too used to AOKP's options. The default Nav bar is HUGE!!!!

I need to customzied the width, height etc. Put more buttons as well besides the default 4.

Is there anyway to customize the nav and status bar to make it look awesome like aokp's? Am I not seeing the option? or maybe a 3rd party app can do it? much appreciated guys.
[Samsung Galaxy Nexus] christianpeso:
CM is really not about a ton of customization options. If you want that, u need to use pretty much any other ROM.
[Samsung Galaxy Nexus] litobirdy:
Which would you recommend that's like a combo of cms smoothness with aokps customizations?
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
CM isn't any smoother than any other ROM. If you need the crazy AOKP features, just use that instead.
[Samsung Galaxy Nexus] refthemc:
I moved back to CM because of the smoothness.
[Samsung Galaxy Nexus] Enter The Nexus:
Fork My Life rom, user MWIsBest, is working on CMKP (Cyanogen Mod + AOKP) it'll be coming soon and crDroid's CM 10.2 Builds have been amazing for me, customization wise. SlimRom is good too as it has Inverted GAPPS and PIE. There are now unofficial AOKP 4.3 builds...
[Samsung Galaxy Nexus] scubastevegk:
Commit coming to the next nightly that may have some promise relating to the handoff issues - I don't have enough posts to provide an outside link, but check out the changelogs for "Update Operators.java with more VZW operator ID's found in apns-conf-cdma.xml"
[Samsung Galaxy Nexus] Reginald476:
The commit in question is here: http://review.cyanogenmod.org/#/c/50699/ it looks as if it was merged at 9:40 this morning!
[Samsung Galaxy Nexus] johnhimm:
Merged in the 9/25 build, booting it now.

Edit: still a no go, slow 3g/4g switching, when coming off airplane mode doesn't reconnect data.
[Samsung Galaxy Nexus] Reginald476:
Well dang, have you tried any of the other fixes? 4.0.4 radios, build.prop edit, ect.
[Samsung Galaxy Nexus] johnhimm:
No, reflashing 10.1.3 stable. It has been running flawless.
[Samsung Galaxy Nexus] Reginald476:
I can't blame you, I am still on LiquidSmooth 2.9, I had been using a ton of 4.3 ROMs but the latest CM gave me a ton of trouble even switching between WiFi APs (with the same SSID) at that point I figured if I had to flash something, might as well flash stable for now.

Thanks for checking the merge, let's hope they have something else that went with it to fix the hand offs.
[Samsung Galaxy Nexus] kklops:
Has group messaging been fixed yet? I'm still on 8/18 nightly and stopped paying attention for a few weeks.
[Samsung Galaxy Nexus] na2rboy:
Was it merged in 9/25? CyanogenROM Downloader says it is in the next build. I am cautiously optimistic it will fix the problem based on some comments on the commit.
[Samsung Galaxy Nexus] johnhimm:
According to http://10.2.cmxlog.com/?device=toro it was merged in the 9/25 build.
[Samsung Galaxy Nexus] Droid_JD:
Maybe I'm reading too much into it, but might this resolve our problem? It's being merged into today's build - 9/27:

http://review.cyanogenmod.org/#/c/50930/
[Samsung Galaxy Nexus] Reginald476:
I am not sure, I am about to leave for the weekend so I can't test it but it looks like someone is digging in to the Telephony folder to resolve the issues with 4.3 and Verizon. I hope they get it.
[Samsung Galaxy Nexus] hotrodwinston:
I just flashed 9/27 will test on my trip home this evening.
[Samsung Galaxy Nexus] johnhimm:
I need to stop being the guinea pig. Same issues still on 9/27 with the 3g/4g and airplane mode. Back to 10.1.3
[Samsung Galaxy Nexus] hotrodwinston:
Switching airplane mode is not a real world test though - need to switch towers multiple times to really test handoff.
[Samsung Galaxy Nexus] General Crespin:
I'm round tripping GRR : DTW this morning, I'll give it a shot.
[Samsung Galaxy Nexus] hotrodwinston:
It's better but not fixed - one trip required a airplane mode toggle to connect and another connected after a little longer than normal wait - so we are getting closer
[Samsung Galaxy Nexus] General Crespin:
My verdict as well. I felt like it was holding onto 4G more than before, but that could be wishful thinking. It always reconnected to 3/4G eventually, but not quickly enough, sadly.
[Samsung Galaxy Nexus] Droid_JD:
Well this is both promising and reassuring: http://review.cyanogenmod.org/#/c/51062/ - SamsungQualcommRIL: fix handoff for good.
[Samsung Galaxy Nexus] digitallure:
Had some crazy issues with connectivity this weekend. I went to Atlanta and during the trip driving, my data would either not work or would show a connection but nothing would happen. I tried all of the recent nightly builds from Thursday 9/25 with either lean kernel or the stock cy kernel.
[Samsung Galaxy Nexus] hotrodwinston:
Very much so. (fingers crossed)
[Samsung Galaxy Nexus] General Crespin:
Merge, baby, merge!

---------- Post added at 04:14 AM ---------- Previous post was at 04:13 AM ----------

Welcome to our world, you might wanna read the last few pages. ;) tldr known problem.
[Samsung Galaxy Nexus] digitallure:
OK, I thought it was just switching from 3g to 4g...didn't read thoroughly LOL
[Samsung Galaxy Nexus] meth0dGSX:
So this was merged and included in the 9/28 nightly, anyone try and test yet? The replies in ROM Manager are not looking good. I cant test since i need a stable phone at all times.

And on a side note, the last time i posted on here i had the phone in my sig...ha
[Samsung Galaxy Nexus] hotrodwinston:
It will be included in next nightly - it merged to late to be in 9-28. Terrible data on 9-28 due to partial fixes merged in.
[Samsung Galaxy Nexus] meth0dGSX:
Sweet, thanks for the info.
[Samsung Galaxy Nexus] ExodusC:
Am I mistaken that there was no 9/29 build for toro?
[Samsung Galaxy Nexus] calvinistmac:
You are not mistaken, there was indeed no 9/29 build for our beloved Toro.
[Samsung Galaxy Nexus] ExodusC:
Sadly that's the build that had finally gotten a commit that might just fix our data handoff...

Maybe tonight is the night.
[Samsung Galaxy Nexus] jlvlawrence:
You could try the euroskank build. He posted a new build this morning.
[Samsung Galaxy Nexus] blackhand1001:
Data and WiFi are definitely still broken in this build. Actually even worse than before the tried fixing the handoff.
[Samsung Galaxy Nexus] hotrodwinston:
But did it build with all patches? Cm team has been adding telephony patches all day today so I really hope the next build fixes things.
[Samsung Galaxy Nexus] jaredsleboeuf:
Looks like 10-1 finally pushed through. Anyone flash it yet that can comment on the data issues?
[Samsung Galaxy Nexus] steve229h:
Still borked. Won't reconnect after entering airplane mode.
[Samsung Galaxy Nexus] jaredsleboeuf:
Ah, well that's unfortunate. Thanks for the response though.
[Samsung Galaxy Nexus] johnhimm:
Thanks for testing this
[Samsung Galaxy Nexus] AuroEdge:
It seems like it may be broken till the 4.3 OTA gets posted
[Samsung Galaxy Nexus] johnhimm:
I don't think the phones will last that long!
[Samsung Galaxy Nexus] ironfisted:
Is that from a clean flash or dirty flash?
[Samsung Galaxy Nexus] chazzdjr:
I agree with ironfisted. Clean flash would be the only true way to be sure.
[Samsung Galaxy Nexus] hotrodwinston:
Airplane mode toggle is still not real world. You need to travel thru a mixed coverage area so it switches technology and towers to truly test. Also what radios are you using - did you use the build prop edit posted earlier in this thread ?

Edit : also have you done a manual prl update? Dial *22899 and let it run thru till it hangs up then wait till data tries to reconnect and reboot - do this on LTE if possible.
[Samsung Galaxy Nexus] steve229h:
Dirty flashed. Will try a clean install this evening. Using the 4.2 radios. The build.prop edit never worked for me, but I haven't tried applying it to this latest build.
[Samsung Galaxy Nexus] eriscentro:
Just clean flashed the latest build, it's taking forever to get a radio connection. I'm trying to find something w/ a working radio since cm 10.1.3 stable is just as bad as the previous 4.3 nightlies

Update: Coming out of airplane, I can send texts although data doesn't appear to be coming back

2nd Update: Confirmed, no data after airplane mode
[Samsung Galaxy Nexus] mrdunn:
For verizon lte phones, to update towers, calling that number doesn't work. You need to remove the battery and sim card for 30 seconds, then put them back in and reboot. Verizon told me that, and it has helped my coverage when traveling to a different state.
[Samsung Galaxy Nexus] hotrodwinston:
Actually it works now but it has to be 22899 not 228 and you have to be on vzw network not "extended"
[Samsung Galaxy Nexus] eriscentro:
Do you guys know of a ROM without radio issues? 4.2.2 (CM 10.1.3) has radio issues, where the radio shows signal, although can't make calls, send texts, or access the internet. The preferred network under phone info in *#*#4636*#*# says "unknown" when this happens
[Samsung Galaxy Nexus] hotrodwinston:
Sounds like what my wife's gnex did right before the sim card went out.
[Samsung Galaxy Nexus] eriscentro:
Interesting. Did you have a new one sent out? I feel like this is far surpassing the regular gnex data issues. People here say they can't reconnect to data, I can't reconnect to anything
[Samsung Galaxy Nexus] hotrodwinston:
I just stopped in a vzw store while it was doing it but I had tested with my card in her phone and vice versa the night before so they just popped one in
[Samsung Galaxy Nexus] eriscentro:
And it was all good? Also, do you know of a ROM without radio issues? CM 10.1.3 stable does have them

---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------

Also, as soon as I go to make a call, the radio drops out completely (sometimes)
[Samsung Galaxy Nexus] nalanotae:
I have been using cm 10.1.3 stable since it released and I have had no radio issues

Sent from my Galaxy Nexus that has been flashed more than a tourist at Mardi Gras
[Samsung Galaxy Nexus] hotrodwinston:
All good - and I never had radio issues on the first few 10.1 stable roms
[Samsung Galaxy Nexus] eriscentro:
I wonder why I have such problems...I guess I'll have to get a new SIM sent out. 10.1.3 for me was just as bad as 10.2
[Samsung Galaxy Nexus] aggrophobik:
Same here, 10.1.3 is rock solid on my gnex, no radio/handoff issues.
[Samsung Galaxy Nexus] johnhimm:
I agree, 10.1.3 has been rock solid for me as well. No radio issues like I had on 10.2.
[Samsung Galaxy Nexus] hotrodwinston:
Data handoff seems to work - slow but it works (in real life most data handoff happens while driving so it's not noticed )but airplane mode toggle kills data so there is a bug in that.
[Samsung Galaxy Nexus] atrophis:
Has anyone messaged the toro device maintainer? He is readily available on google+.
[Samsung Galaxy Nexus] EvanVanVan:
Damn very disappointing to read about the recent problems with 10.2, I was preparing to finally clean update from 10.1(.0) last night. Now I'm not sure if I want to clean update to 10.1.3 instead... Maybe I'll do that, nandroid and then update to 10.2 to try it...
[Samsung Galaxy Nexus] JeeperDon:
Why bother with 10.2, really? People want it because "it's the next version! Gotta have it! ... no matter what!" In truth, there is nothing really gotta- have in 4.3 or 10.2.

I drank the kool-aid and played with 10.2 like you are thinking of doing. It was all frustration going from rock solid 10.1.2 to any version of 10.2. I'm back on 10,1,3 and will likely stay there until my next phone, and I have no plans on getting a next phone for months at best, not impressed by anything on the Verizon horizon.
[Samsung Galaxy Nexus] hotrodwinston:
18 hours with no data drops 10/1
[Samsung Galaxy Nexus] ironfisted:
The major issue is going from airplane mode. Or from a complete loss of signal. Go into airplane mode for a few mins then back off of it and see what happens.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
I really like the WiFi scanning. I use Llama for a lot of location based stuff and it is exponentially more accurate using the WiFi location than cell towers. Using cell towers, it would think I was at home when I was 10 miles away at the gym...

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

I can confirm toggling airplane mode. Just tried it at work after updating to 10/1. Went from 3 bars of 4G before toggling to 2 bars of no data after. Rebooted and back to 3 bars of 4G.
[Samsung Galaxy Nexus] hotrodwinston:
But does the airplane mode bug affect normal use? And I reconnected fine coming out of no signal yesterday on my way home (have a 15 mile dead zone between my home and work)
[Samsung Galaxy Nexus] ExodusC:
I'll make it short and say handoff is not fixed. I'm still getting the exact same behavior I had with every build.
[Samsung Galaxy Nexus] johnhimm:
Thanks, 10.1.3 for now.
[Samsung Galaxy Nexus] CosMiiK:
First time coming back to a stock CM in a while.
[Samsung Galaxy Nexus] hotrodwinston:
Are you using a third party kernel? Any mods? Build prop edit? Have you done a prl update? I have now had one data drop coming back from no signal using stock with Franco 391 kernel and a manual prl update. No other drops in over 48 hours.
[Samsung Galaxy Nexus] chazzdjr:
Data drop and hand-off are two very different issues. I don't have data drop per say. But when moving from a 4G to a 3G area and having the radio automatically reconnect to data. That's the issue most everyone is experiencing on 4.3 based ROM's on toro.. It can take up to 10+ minutes to turn blue again at times without giving a quick airplane mode tap. Even after toggling APM it can still take a minute or two to reconnect to blue.

I'm not a true android developer but couldn't someone (that knows what they are doing) just take all of the stuff related to telephony from 4.2.2 and just replace what's in 4.3 with it?
[Samsung Galaxy Nexus] AuroEdge:
No.
[Samsung Galaxy Nexus] chazzdjr:
Any detailed insight on this or just no?
[Samsung Galaxy Nexus] AuroEdge:
The Radio Interface Layer is closed up tight like a submarine. There are elements within Android OS that can be moved from 4.2.2 to 4.3, which I bet other developers have done, to help alleviate problems. However they are stacking a bad fix into a newer Android version. What could go wrong?!
[Samsung Galaxy Nexus] hotrodwinston:
I consider any lack of connection to be a data drop - not going back to blue on 3g/ 4g switch or losing data completely - if you are in a data signal and have to toggle anything or reboot to get data I consider that a data drop - I have had only one issue with that and that was yesterday coming out of no signal would not connect - showed data but would not turn blue - only issue in 48 hours.
[Samsung Galaxy Nexus] chazzdjr:
I actually work in 4G blackhole. So I basically use just CDMA while at work. Then switch LTE /CDMA back on when I leave the area. I'm in Dallas so LTE is pretty strong around town. Just some spots really stink. 3G is pretty much strong everyplace. But if I rely on the radios switching automatically that's where I'm affected most.

AuroEdge thanks for the info!
[Samsung Galaxy Nexus] ExodusC:
I'm also running franco.Kernel, but that should have no impact on RIL issues.

Anyways, I am still getting handoff issues, data drops, unreliable 3G, etc.

I'm pretty sure it's all the exact same root cause, the RIL.
[Samsung Galaxy Nexus] PrettyPistol555:
I haven't gotten blue data (cell or WiFi) in 2 to 3 nightlies. Is it just me?

If so I'm gonna try clean install.

Thanks
[Samsung Galaxy Nexus] meth0dGSX:
Are you even reading this thred?
[Samsung Galaxy Nexus] tyween:
I drove from DC to Atlanta yesterday and had no data issues on 10/02. Went out of Wi-Fi range upon leaving my apartment, got data immediately. Didn't need to reboot all day or attempt airplane mode.
[Samsung Galaxy Nexus] drumst1x:
I'm still on 10/1, and as long as I turn LTE off, i've got fairly reliable data. I once had to disable mobile data and then re-enable it to get it back, but other than that, 4 days no problem. Obviously I'd prefer to have LTE, but in opposition to what i've heard so many people say ("there are no real differences between 10.1 and 10.2 / 4.2.2 and 4.3), my phone runs MUCH better on 10.2/4.3 than it did on 10.1/4.2.2

Here's hoping that in one of the next few nightlies they'll get this RIL/data handoff issue fixed.
[Samsung Galaxy Nexus] JeeperDon:
In reading the past few days comments on those nightlies, is it true that the only known issue on 10.2 is the data/3g/4g switch problem? ... and one guy on the east coast says that's been ok for him? Anything else I missed?
[Samsung Galaxy Nexus] atrophis:
I'm on the 10/4 build and I switched airplane on and off, I got data back.

ETA: I lied. I was on WiFi, my bad.
[Samsung Galaxy Nexus] hotrodwinston:
I'm in the south and only have issues if coming out of no signal and only sometimes then - still have the airplane mode switch bug.
[Samsung Galaxy Nexus] Droid_JD:
I'm in Boston and have had these data issues. I've gone back to 10.1.3 because I do a lot of driving and rely on navigation. Too paranoid to risk 10.2 and get lost.

Best of luck to those working hard to try and fix this!
[Samsung Galaxy Nexus] Whompy:
I haven't really had any noticeable issues lately with data switching in southern Michigan with lots of sketchy service. I haven't done much with airplane mode though.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Anyone having backup issues with titanium backup? For the past few weeks, it has been telling me that there is insufficient storage space when I go to backup, despite me having plenty of room for backups.

I can temporarily fix it by switching the backup location between the emulated/0 and legacy locations, but the error eventually comes back and I have switch the folder again. This happens on my Gnex and nexus 7, so it isn't device-specific.
[Samsung Galaxy Nexus] jakaro:
I am having problems with Instagram which will not open at ll. Also my Chaton app will not show pictures inside the app that get sent. IS this a CM issue or Nexus Issue, on the Cm stable release
[Samsung Galaxy Nexus] JeeperDon:
Oh, yeah, there's that too. So the PITA prob list is...

1) The data/3g/4g problem.

2) Whatever is 'off' with TiBu for 4.3.
[Samsung Galaxy Nexus] flytechguy:
Hope the drive went well brother man. ;) Mines been acting fine, even on 10/4.
[Samsung Galaxy Nexus] HTCF4N:
Here's how I manage to fix the TI Backup issue. Before you run a backup, open the recent apps page and close all active apps. It took a while to figure this out, but apparently some app is preventing full access to the SD. Try that and see if it works if you've already tried changing backup directory.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Thanks, but that's not really possible when it's doing an automatic backup when I'm sleeping :/
[Samsung Galaxy Nexus] HTCF4N:
Lol, you can always do a manual backup.