Like most Verizon customers, I got impatient waiting for VZW to push out Android 4.2, so I used Wug's Toolkit to unlock and root my previously unrooted VZW Galaxy Nexus. The unlock and root worked fine, I then installed CyanogenMod 10 and the Google Apps package, and that's where my problem is.
Cyanogen loaded fine, but I apparently used an incompatible version of gapps, so what happens now when I fire up the phone is I get the Google logo with the unlock icon (so far so good), then I get the Cyanogenmod boot screen (so far so good again), but then after that I get a message saying "the process com.google.process.gapps has stopped", which I cannot get out of; I dismiss the message and it reappears, I dismiss it reappears, etc. The only way to stop this loop was to yoink the battery out. After I took the battery out, I started back up in recovery mode, cleared all data/cache (including the dalvik cache), and tried again - and got the same problem.
I believe Cyanogenmod is installed correctly, but that gapps isn't; if my troubleshooting is correct, I think what I need to do at this point is to load the right version of the gapps .zip file (which I have now) onto my phone and install it from there. That's my second problem, though - my computer(s) won't recognize my phone. I've tried my XP machine, I've tried my iMac, and neither of them will recognize my phone at this point, and I don't know why.
So at this point, I have a completely unusable phone about which I'm panicking a little bit, because I have no idea how to get it to a point where it's usable again. I am extremely new at unlocking/rooting and not particularly technical, so if you could explain things to me like I was five I would really appreciate it. Thanks all.
Can you get into recovery? Unfortunately I'm at work and not a expert.
If you can get to the boot menu (hold both volume buttons and turn on phone I think)
Select fastboot, Wug's "should" recognize the phone in fastboot. From there, I would choose "restore to factory" or whatever it is and start over.
Sorry I can't give you "better" info. I'm not real, familar with it.
I will say this. Your phone almost certainly IS recoverable
Hopefully some of our more experienced members will chime in. (at worst this evening when folks get off work someone will be on)
Boot into recovery by powering down the phone (battery pull if necessary), then press and hold both volume buttons, then press and hold power. Use the volume keys to select recovery, hit the power button to choose it.
When in recovery...do a factory reset, and also wipe the system, reinstall cyanogen...and then boot the phone. Download the correct gapps for 4.2(or 4.1 depending which cyanogen you are trying to use). Install in recovery and you'll be fine
*Remember cyanogenmod 10.0 is android 4.1 and cyanogenmod 10.1 is android 4.2 *
Last edited by sdrawkcab25; January 23rd, 2013 at 12:06 PM.
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
Boot into recovery by powering down the phone (battery pull if necessary), then press and hold both volume buttons, then press and hold power. Use the volume keys to select recovery, hit the power button to choose it.
When in recovery...do a factory reset, and also wipe the system, reinstall cyanogen...and then boot the phone. Download the correct gapps for 4.2(or 4.1 depending which cyanogen you are trying to use). Install in recovery and you'll be fine
*Remember cyanogenmod 10.0 is android 4.1 and cyanogenmod 10.1 is android 4.2 *
^^Exactly. If you do in fact have a good running version of CM, do another wipe and then load only the rom. Once up and running, download the correct gapps via the browser. Then when flashing, it will be located at location /sdcard/Download.
I had this happen to me once, turned out I had to redownload my ROM/Apps again, and reinstall. Not sure where, but something in my first download (which loaded fine til I rebooted), was wonky. Worth a shot, if you haven't tried yet.
Also did you do a backup of stock-rooted before you flashed anything? You could always flash that as well to get you by until you get everything together.
Since you're a noob here are some things to remember when rooting.
Always keep a CWM backup or TWRP backup saved on your home computer.
Always check the MD5 of anything you download an put on your phone.
Invest in TiBu Pro
Some people don't but i always did this: If i was going to try a new Kernel i would make a backup then flash the kernel. If something went wrong i could go instantly back to my working backup.
Also please when you get some time research using ADB. Try not to rely totally on a Toolkit. If you get in a bind where the toolkit is useless you're going to need some ADB knowledge. But then again someone on here will always help you out should you get in that position.
__________________
I used to be Android all the way but bought an Iphone 5 in October. Feel free to ask me how it's going via PM.
GO BRONCOS AND ROLLLLLLL TIDE!!!
For now I will just subscribe to this thread and see what more the OP has in the way of answers to the questions already posed and any further question(s). Quick thought, I wonder if the toolkit flashed a custom recovery compatible with 4.2.x . . . could get messy if not.
Turns out my problem was much simpler - when I tried to troubleshoot at work, my work machine (which is newer and more powerful than my crappy home machine) recognized my phone just fine, so I was able to get a fresh CM10 and gapps installed just fine. I appreciate all the tips and I'm sorry I wasn't around more yesterday to be more responsive but I was at work and got busy with, y'know, work stuff.
Anyway, thanks again.
The Following User Says Thank You to pdebruler For This Useful Post:
Help a noob rooter get his phone working again!
