Develop Bugs

GNex rejecting ALL 4.1

RIght, it seems my phone is rejecting all and any 4.1 OTAs and ROMs.
I have tried every combination of stock takju, yakju, OTA, ROMs, recovery, radios the lot.
My phone applies the update ok then when it starts it just sits in a boot loop getting hotter and hotter.
Does anyone know what the hell is going on and what it could be?
Or has anyone else had this problem?
I can happily flash stock Google images (4.0.4), 4.x.x ROMs no problem it just seems to be JB.
Thanks

How long do you let it boot?
Sent from my Galaxy Nexus using xda premium

gchild320 said:
How long do you let it boot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry, it won't let me post in Dev. (to new to the site)
I let it boot for a good 20-30 mins, iv literally tried everything... WIth root, without root you name it, i tried it

rparkerbsgg said:
Sorry, it won't let me post in Dev. (to new to the site)
I let it boot for a good 20-30 mins, iv literally tried everything... WIth root, without root you name it, i tried it
Click to expand...
Click to collapse
Have you tried super wipe?
Android revolution HD super wipe lite nexus or something of the sort. Its a flash able zip that may help you out.
Sent from my Galaxy Nexus using xda premium

gchild320 said:
Have you tried super wipe?
Android revolution HD super wipe lite nexus or something of the sort. Its a flash able zip that may help you out.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah i did try that to no avail.. its starting to p!ss me off now

Why dont you tell us what exact phone you have, and walk is through a typical ROM installation
Sent from my Galaxy Nexus using xda premium

Try locking then unlocking the bootloader (this should wipe all your data off the phone!). Then flash stock factory images via fastboot. If you still can't boot after doing that then something is wrong with your phone physically.
if you don't have the drivers and fastboot setup:
drivers: http://forum.xda-developers.com/showthread.php?t=1379875&highlight=naked+samsung
fastboot: http://www.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/ (just rename the fastboot and adb .exe's back to their original names w/o the -windows suffix).
factory images: https://developers.google.com/android/nexus/images
edit: or use the toolkit that sarni84 mentioned below - if your not comfortable manually doing it via a command prompt.

Yes I would flash a stock image with the toolkit it should wipe everything it will suck but it seems like your problems are deeper. Then after flashing the 4.0.4 IMG use efrants guide to flash to new 4.1.1

running_penguin said:
Why dont you tell us what exact phone you have, and walk is through a typical ROM installation
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have a GSM Galaxy Nexus from the UK, the day i got it i flashed the factory 4.0.2 image from google to bring it to clean yakju.
When i download a ROM or anything firstly i check the md5, assuming thats all good i follow the install proceedure to the letter (wipe data, cache, dalvik if needed) I have flashed many ROMs on my Nexus as well as my previous S2 and Nexus S before that.
I have literally tried everything from clean install of factory 4.0.4 yakju and takju, lock and unlock boot loader, root and un-root, OTA and custom ROMs but nothing seems to work.
I have even tried restoring a friends nandroid of stock 4.1.1 android via CWM just to see if that works but nothing.

well... so why not stay with 4.0.4 yakju and just wait for stock ROM 4.1.1 yakju to be available and/or working OTA update? why going through all this hassle?
https://developers.google.com/android/nexus/images

rparkerbsgg said:
I have a GSM Galaxy Nexus from the UK, the day i got it i flashed the factory 4.0.2 image from google to bring it to clean yakju.
When i download a ROM or anything firstly i check the md5, assuming thats all good i follow the install proceedure to the letter (wipe data, cache, dalvik if needed) I have flashed many ROMs on my Nexus as well as my previous S2 and Nexus S before that.
I have literally tried everything from clean install of factory 4.0.4 yakju and takju, lock and unlock boot loader, root and un-root, OTA and custom ROMs but nothing seems to work.
I have even tried restoring a friends nandroid of stock 4.1.1 android via CWM just to see if that works but nothing.
Click to expand...
Click to collapse
Sounds like something is broken or your nand flash is corrupted or bad. Probably best to RMA it considering you've tried everything that should have restored it if it wasn't broken.

Hannes The Hun said:
well... so why not stay with 4.0.4 yakju and just wait for stock ROM 4.1.1 yakju to be available and/or working OTA update? why going through all this hassle?
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I got the official OTA from our friends at google (i didn't do the framework services clear) it just came through.
i got the whole 145mb download, it verifies, reboots to the android guy with his front open, loads fine then on reboot, nothing, just the big X boot screen looping out.
It was after that didn't work that i explored the ROM route with the same results

Just got a galaxy nexus need some help.

Hey guys, I just bought a used galaxy nexus locally and need help.
The previous owner had it rooted but he asked me if I wanted it to stock before selling it to me. I agreed and he gave it to me with the locked bootloader and on stock ICS.
I'm having a small issue though, whenever I go to settings, I'm getting a ton of crashes.
is there any way that I can re-flash stock without rooting the phone again? I just want to wait for stock JB and root in the near future.
Thanks a ton
EDIT: Its a sprint Gnex

Man a odin flashable file?
Enviado desde mi Galaxy Nexus usando Tapatalk 2

coldrazor said:
Man a odin flashable file?
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Click to expand...
Click to collapse
Huh?

gab2012 said:
Huh?
Click to expand...
Click to collapse
Search ODIN flash
Sent from my Galaxy Nexus using XDA Premium HD app

I have a sprint nexus. If you would like I could remotely Odin your phone back to stock. Otherwise I can get you a video tutorial you can follow.
http://forum.xda-developers.com/showthread.php?t=1614922
Look for the link How to Unroot. Yes I know its not rooted but this does the same thing.
Sent From My Toro+ via SkyBlue Tapatalk

ÜBER™ said:
I have a sprint nexus. If you would like I could remotely Odin your phone back to stock. Otherwise I can get you a video tutorial you can follow.
http://forum.xda-developers.com/showthread.php?t=1614922
Look for the link How to Unroot. Yes I know its not rooted but this does the same thing.
Sent From My Toro+ via SkyBlue Tapatalk
Click to expand...
Click to collapse
Thanks for the tips I'll try my best and post up my results in a while

Did the whole process twice successfully and still get FC on settings What else can I try? I have insurance and might take it to sprint to have it checked out.

I just rooted the phone for the heck of it and flashed ACS Ru jellying rom and the problem is still there! settings keep FCing
I think I'm going to have to end up going to sprint and getting a refurb (not a problem but a big waste of time since the reps here don't know anything and keep you at the store for 2 hours while they try to reset it)

Anyone?

gab2012 said:
I just rooted the phone for the heck of it and flashed ACS Ru jellying rom and the problem is still there! settings keep FCing
I think I'm going to have to end up going to sprint and getting a refurb (not a problem but a big waste of time since the reps here don't know anything and keep you at the store for 2 hours while they try to reset it)
Click to expand...
Click to collapse
Something to try that's super helpful is the Galaxy Nexus Toolkit from the GNex dev pages, it can do literally anything:
http://forum.xda-developers.com/showthread.php?t=1392310
When you flashed the new ROM did you format /system in clockworkmod? When you have weird persistent problems what you probably need to do is boot into clockwork, do a factory reset, then go into 'mounts and storage' and format /system. To be extra thorough from the main menu go to advanced->format dalvik cache, then flash your new ROM (and flash gapps if the ROM needs it). What probably happened is that the previous guy neglected to format everything correctly and now your system apps are borked.
Also if you were waiting for JellyBean stock, you can get a stock JB ROM out of the GNex dev threads. I've been running a JB ROM for about a week and there's no reason to wait anymore.

Taboobat said:
Something to try that's super helpful is the Galaxy Nexus Toolkit from the GNex dev pages, it can do literally anything:
http://forum.xda-developers.com/showthread.php?t=1392310
When you flashed the new ROM did you format /system in clockworkmod? When you have weird persistent problems what you probably need to do is boot into clockwork, do a factory reset, then go into 'mounts and storage' and format /system. To be extra thorough from the main menu go to advanced->format dalvik cache, then flash your new ROM (and flash gapps if the ROM needs it). What probably happened is that the previous guy neglected to format everything correctly and now your system apps are borked.
Also if you were waiting for JellyBean stock, you can get a stock JB ROM out of the GNex dev threads. I've been running a JB ROM for about a week and there's no reason to wait anymore.
Click to expand...
Click to collapse
Thanks for the help!
I will format/erase and reflash and come back with the results!

I added my google credentials and everything seems to be working now. I'll keep using the phone for today and keep you guys posted.
Any nice battery saving tips? going on a trip to Miami tomorrow, planing on loading the phone with my albums today so I'm ready for tomorrow

Ok it happened again today while I was at the airport waiting for my flight. The settings froze when I pressed more in order to get to airplane mode.
I got frustrated and wiped the whole phone several times and re-flashed ru jellyin rom + gapps.
(went into twrp and wiped everything 3 times before flashing the rom + gapps)
Everything seems to be fine again. Can i take my phone in for service if its rooted? if not ill wait until i get home to unroot it (left my laptop) and take it in.
I think the thing that caused this for me was google wallet since I had it installed yesterday and installed it again this morning at the airport before the problems began.
Sent from my Galaxy Nexus using xda premium

[Q] How do I ditch cm10?

alrighty then. I have been playing with my phone for about 2 hours now trying to figure out how to get rid of CM10 so I can flash a new ROM. (had to find dev options etc.) I tried flashing a recovery image through the SGS tool kit, still had CM10. I tried re-rooting (not advised, had a small stroke while figuring out if I bricked or soft bricked) I just did a system wipe, also ill advised, it warned me that I had no OS (thats why we make nandroids like good lil boys and girls.)
For the love of Jeebus someone please tell me how to get CM10 off of my phone so I can flash a new ROM. can I un-root and re-root and start from scratch that way? is that proper? is there an easier way? Why am I asking all these questions?! (because no matter what, I will always be a NooB -.-')
I appreciate any insight you guys can give me, thanks in advance!

gorealmighty said:
alrighty then. I have been playing with my phone for about 2 hours now trying to figure out how to get rid of CM10 so I can flash a new ROM. (had to find dev options etc.) I tried flashing a recovery image through the SGS tool kit, still had CM10. I tried re-rooting (not advised, had a small stroke while figuring out if I bricked or soft bricked) I just did a system wipe, also ill advised, it warned me that I had no OS (thats why we make nandroids like good lil boys and girls.)
For the love of Jeebus someone please tell me how to get CM10 off of my phone so I can flash a new ROM. can I un-root and re-root and start from scratch that way? is that proper? is there an easier way? Why am I asking all these questions?! (because no matter what, I will always be a NooB -.-')
I appreciate any insight you guys can give me, thanks in advance!
Click to expand...
Click to collapse
Fairly simple just download another non cm10 ROM as you did to install cm10 in the first place. If you are unsure of what to do read the instructions in the OP of the ROM you want.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

mjg688 said:
Fairly simple just download another non cm10 ROM as you did to install cm10 in the first place. If you are unsure of what to do read the instructions in the OP of the ROM you want.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the reply, im hesitant to flash over cm10 though. I seem to remember always having to reflash back to stock (root) before flashinga new ROM, I never encountered any problems when doing so.

gorealmighty said:
I appreciate the reply, im hesitant to flash over cm10 though. I seem to remember always having to reflash back to stock (root) before flashinga new ROM, I never encountered any problems when doing so.
Click to expand...
Click to collapse
Just wipe data, cache and dalvik then flash new rom. No reason whatsoever to flash another stock rom to flash the one you want
I like to break stuff!

-EViL-KoNCEPTz- said:
Just wipe data, cache and dalvik then flash new rom. No reason whatsoever to flash another stock rom to flash the one you want
I like to break stuff!
Click to expand...
Click to collapse
this so goes against every instinct. I guess Ill give it a try though, I cant see another way around it. thank you!

gorealmighty said:
this so goes against every instinct. I guess Ill give it a try though, I cant see another way around it. thank you!
Click to expand...
Click to collapse
Idk who told you you needed to go back to stocm b4 flashing another rom but they were wrong. I've been flashing roms for a few years on 7 different phones and 5 tablets and never once went back to stock before changing roms
I like to break stuff!

-EViL-KoNCEPTz- said:
Idk who told you you needed to go back to stocm b4 flashing another rom but they were wrong. I've been flashing roms for a few years on 7 different phones and 5 tablets and never once went back to stock before changing roms
I like to break stuff!
Click to expand...
Click to collapse
its a habit from the Vibrant. flashing back to stock prevented the possibility of "ghost files." it just kind of ensured everything rolled along smoothly. The reality is that flashing over CM10 is looking like my only option without having to break out good Ol' Command Prompt lol. I appreciate your help guys.!

gorealmighty said:
its a habit from the Vibrant. flashing back to stock prevented the possibility of "ghost files." it just kind of ensured everything rolled along smoothly. The reality is that flashing over CM10 is looking like my only option without having to break out good Ol' Command Prompt lol. I appreciate your help guys.!
Click to expand...
Click to collapse
Just wipe in recovery to get rid of the last roms data and files. You could always odin to stock if you really wanted to but its just extra steps that aren't needed
I like to break stuff!

-EViL-KoNCEPTz- said:
Just wipe in recovery to get rid of the last roms data and files. You could always odin to stock if you really wanted to but its just extra steps that aren't needed
I like to break stuff!
Click to expand...
Click to collapse
got stuck n a boot loop a dozen times, finally said to hell with it and found a stock .tar.MD5 and Odin'd this pig. Again, I appreciate y'alls' help.

Don't forget to nandriod before flashing. It will help you when you need it most.
What recovery were you using? I have used twrp with no problems
Sent from my SPH-L710 using Xparent Green Tapatalk 2

loumoli said:
Don't forget to nandriod before flashing. It will help you when you need it most.
What recovery were you using? I have used twrp with no problems
Sent from my SPH-L710 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
TWRP. I was trying to flash Jellybam over CM10 . I got stuck in a boot loop, soft bricked it twice and removed my OS once (able to recover from TWRP) im playing around with it tonight.

[Q] Lag after root

I rooted my Gnex GSM yesterday using Nexus Root Toolkit. After doing this I found that my pull down menu lags annoyingly when I'm in an app. Does anyone have any idea what the problem could be. I've cleared my cache and dalvik cache as instructed by my friend. But that hasn't done anything to my phone really. Thanks:good:

First, post in the right section.
Superuser/root access has nothing to do with "lag".
a maguro wrote this.

beekay201 said:
First, post in the right section.
Superuser/root access has nothing to do with "lag".
a maguro wrote this.
Click to expand...
Click to collapse
what section would that be? I didn't see a rlevant section so I just posted in the general section. So how would one explain that before I rooted, my pull down menu was a smooth transition, and after rooting it isn't?

The Q&A section obviously since your asking a question.
Sent from my Galaxy Nexus using xda premium

And now comes that part: OP, are you using superuser or supersu?
a manta wrote this.

beekay201 said:
And now comes that part: OP, are you using superuser or supersu?
a manta wrote this.
Click to expand...
Click to collapse
wouldnt know, used a toolkit.

I'n using SuperSU. It is really annoying to see that when I use my pull down menu that it's not a smooth transition

I have same problem many times, than i wiped all even system and flash custom ROM. After few months and few flashing problem was back. So wipe all internal memory if you ask me. Install custom ROM. If you wipe all andcan`t boot phone use QtADB while in recovery to copy zip and gapps to your phone. Google it...

Alienns said:
I have same problem many times, than i wiped all even system and flash custom ROM. After few months and few flashing problem was back. So wipe all internal memory if you ask me. Install custom ROM. If you wipe all andcan`t boot phone use QtADB while in recovery to copy zip and gapps to your phone. Google it...
Click to expand...
Click to collapse
thanks but this process seems so long. there must be a direct thing that's affecting it

I flashed JDQ39 through fastboot, rooted it, I see no such lag.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

beekay201 said:
I flashed JDQ39 through fastboot, rooted it, I see no such lag.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, I flashed that too and rerooted. Still there, but it's less frequent. I'll see what happens

Tez_Nexus said:
Yeah, I flashed that too and rerooted. Still there, but it's less frequent. I'll see what happens
Click to expand...
Click to collapse
I guess the real question is what ROM you flashed and what Kernel is running.
Some ROM's run faster on Gnex than others.
Personally I have been running AOKP and XenonHD back and forth for some time and have a little lag here and there, but that is because I am able to add and change so much on the ROM. Sometimes changing the kernel helps as well.
At the end of the day it's all about what you are doing and what ROM/Kernel combination give you the user experience you like.
Sorry to say, what you are asking is more of an Art than an exact science when it comes to use and feel.

[PLEASE READ] 4.3 Update Crashes Phone!!

PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin

Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.

Carlos_Manuel said:
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Click to expand...
Click to collapse
Did you even read the post? He's never rooted and 100% stock.

Sdobron said:
Did you even read the post? He's never rooted and 100% stock.
Click to expand...
Click to collapse
Whoops. Sorry I read that quickly... Anyway flashing JB 4.3 factory images should fix that...

His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..

ferozfero said:
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
Click to expand...
Click to collapse
Since he didn't root his Galaxy Nexus, this method should make him lose all apps data or even internal storage since he has to unlock his bootloader for root.
But it seems to be the only method.

It's time for a full wipe.
Sent from my Nexus 4 using Tapatalk 4 Beta

I had exactly the same problem so I did factory reset from phone settings 2 days ago and now is just like a new phone working great.
There are just too many changes google did in ~6 months so full wipe is necessary.
Sent from my Galaxy Nexus using xda app-developers app

Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium

teddy_irish said:
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Please don't use a toolkit.
Just use fastboot commands.

Beauenheim said:
Please don't use a toolkit.
Just use fastboot commands.
Click to expand...
Click to collapse
Right, and it's safe.
Please backup all your data before you do it.