Develop Bugs

[Q] I think I now own a galaxy nexus paper weight lol

I was on the latest codename and everything was working fine, but wanted to see how 4.0.4 was running as is. I downloaded the stock AOSP build that was flashable by nikademus, downloaded gapps/root files as well. Followed instructions so far so good. Booted up and noticed that the ICS animation was gone and was replaced by just the "android" with the lighting going through it animation. Didn't really care about that so i let the phone do its thing, once it was done and i completed the account setup i rebooted like i normally do when flashing roms. when the phone came back I went into the settings to verify i was on the current version. I noticed that it said 4.0.4 0 4.0.4, thought that was odd and then something else that was odd was that my market was completely blacked out and the only way to see anything was the select something and then it would become visable. By then I knew something was wrong so i tried to boot into recovery via rom manager but it would not do anything. I tried to flash a custom recovery image again and it didnt let me because of su commands ? or something like that. At this point im freaking out because I have no SU permissions apparently, no CWM recovery, and the rom that im using is clearly messed up(not saying its the rom, it was probably something i did wrong) so i tried to use the galaxy nexus root toolkit program by WugFresh. I was going to try to go back to stock+unroot and then root after. I downloaded 4.0.2 and followed the command prompts and everything seemed to be working fine but when the phone was supposedly booting up it just got stuck on the Google screen with the unlocked padlock for a long time. I didnt see no boot animation or anything for about 10 min.
So I have no clue how to recover from this =(
Is my phone a paper weight now ? or can it be fixed ?
someone help me please lol

Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806

Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
but i cant even get adb to see my device?
in order for me to use fastboot dont i need adb setup ?
I had adb setup but after this issue i cant go no further then the google screen

Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
^^^ what he said.
I have yet to see a bricked Galaxy Nexus.
Sent from the future.

okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?

AnthonyAldrete said:
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
Click to expand...
Click to collapse
Yes you're completely stock.

No more wugs for you sir.
You need to learn how to do this manually.
Check my sig.

All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA

halifaxjesse said:
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
10 chars.

Got OTA notification but....

...I downloaded the 4.0.4 update and went to install and reboot. But the phone got stuck at the screen with the android belly up and a exclamation point. Pulled the battery and rebooted and was at 4.0.2 still. Haven't gotten another OTA notification. Do I get another OTA alert or do I have to update manually.
I have a GSM Nexus, rooted but with stock 4.0.2. And I activated OTA RootKeeper before downloading the update. Any help will be greatly accepted.
Sent from my Galaxy Nexus using Tapatalk

Besides root and maybe unlock your bootloader, did you change anything in your system (install mods, different radio etc. or rename system files)? If you are not completely stock your OTA will not work and you will have to update manually or get back to Stock first.
Sent from my Galaxy Nexus using xda premium

Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk

Well the screen you were looking at (Android belly up) is the stock recovery. If you see that: no need to pull battery. Simply push volume up + power simultaneously and you'll get into the recovery menu. Scrolling through the options can be done with the volume buttons, select with the power button.
That said: I think no one knows for sure but I myself would not wait and update myself. There are a lot of guides here on how to do that and if you flash the stock images you will have the same as anyone who had the OTA. Make a proper backup first (you allways should)! You will lose all your data if you have to unlock your bootloader.
Sent from my Galaxy Nexus using xda premium

jrodsep said:
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus

stuu.f said:
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Is it possible to get the Stock Recovery Screen when you have CWM installed? Didn't think that was possible... that it would just boot into CWM recovery. That is why I didn't mention it (trying to learn here).

Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?

Lex_Michdeandroid said:
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Click to expand...
Click to collapse
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents

Viridis Draco said:
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Click to expand...
Click to collapse
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA

Lex_Michdeandroid said:
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section

Viridis Draco said:
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Click to expand...
Click to collapse
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Edit: would it be easier if I just get the stock recovery back and then try to get the OTA to turn up again?
Sent from my Transformer TF101 using XDA

Lex_Michdeandroid said:
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/

Viridis Draco said:
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Click to expand...
Click to collapse
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA

Lex_Michdeandroid said:
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
i agree, take your time and you wouldn't regret it

I want to manually flash 4.0.4 and stay unrooted. Should I use the GNex Toolkit to flash 4.0.4 directly or do I need to flash the same version I have on my phone?
Sent from my Galaxy Nexus using Tapatalk

I had the same issue described by the OP, the belly up android when trying to update to 4.0.4 from the OTA notification. I had previously changed to 4.0.2 yakju using efrant's instructions from the first post in this thread: http://forum.xda-developers.com/showthread.php?t=1391881
However, I had skipped the optional sections. In particular step 12 to flash the recovery partition. I went back and just executed step 12 (fastboot flash recovery recovery.img) and rebooted. Then I was able to update to 4.0.4 successfully from the OTA notification.
I'm guessing I didn't have the "stock recovery" because I previously had the default Samsung version?

Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA

Lex_Michdeandroid said:
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I had the same issue just now with my phone (unlocked, rooted, stock revcovery), but a quick reboot allowed the update to complete and I'm now on 4.0.4. Did you check the version number again after this latest attempt?

Yes, still 4.0.2.
And of course, my phone says I'm up to date. Lovely, NAAAAAT!
Sent from my Galaxy Nexus using XDA

Jb 4.1

To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.

Jpcsilva said:
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Click to expand...
Click to collapse
Flash your phone back to stock... then do the ota update... profit...
Sent from my Galaxy Nexus using xda app-developers app

Everything must must be bone stock to install an ota.
Jellin' like a felon

The issue at hand here is that you have a custom recovery. I can't say that if you remove CWM that you'll be able to OTA update, but that's at least what was the problem there. Now, if you want to keep all your apps and update to the OTA jelly bean instead of the Google I/O preview build, you can flash this here: http://forum.xda-developers.com/showthread.php?t=1737849
Follow the instructions on that post to update. This is what I did and it worked perfectly.

Camera not working after JB update!
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?

nishantbhatia84 said:
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
Click to expand...
Click to collapse
What Rom? Custom or stock
What kernel? Custom or stock
Sent from my Galaxy Nexus using Tapatalk 2

And how do i do that? I really dont know how to flash it
Sent from my Galaxy Nexus using xda app-developers app

Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium

nishantbhatia84 said:
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
first try factory reset, otherwise yes go back to stock ics and check.

Jp182
atifsh said:
first try factory reset, otherwise yes go back to stock ics and check.
Click to expand...
Click to collapse
But going to factory reset will not remove the cwm recovery... right? If i go to factory data reset on my phone ( remember i am using a 4.1 rom) will it go back to ics and delete all roms / root? Cause this sounds like the best way to do it, but you were the first one that said that. Bought my phone from Amazon unlocked ( do you guys think it is gonna update?)

I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium

I don't get it. What did you do? Factory reset? Installed the stock?
Sent from my Galaxy Nexus using xda app-developers app

HELPPPPPP
nishantbhatia84 said:
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PLZ, tell me!! If I do the factory reset is it gonna remove CWM, and all stuff i have installed?

You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895

ok
phazerorg said:
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Sorry man, I know i am not giving a lot of information, but that's cause i really don't know. I did a random "how to update your galaxy nexus to 4.1" tutorial, and i don't even remember where...... I just know the links i download were from here.
So what i am going to do:
1: Factory data reset
2: I think it's going back to ICS
3: Just do the normal system update that should just pop up.
My only fear is if the phone does not ask for update.

If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)

Factory reset factory reset
phazerorg said:
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Click to expand...
Click to collapse
I want to restore it VIA FACTORY RESET. Cant i?

Jpcsilva said:
I want to restore it VIA FACTORY RESET. Cant i?
Click to expand...
Click to collapse
No, that will just wipe data. You'll have a clean phone, but with the same ROM you currently have. The phone doesn't keep a copy of the stock firmware hidden away or anything like that. Efrant's guide is the proper way to restore everything back to stock.

[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.

Custom rom flashed. Boots 1st time not 2nd

I have lots of experience flashing android roms and this may be a first for me.
Flashed latest MMuzzyrom 4.3 vanilla. Originally had latest stock rooted.
Everything worked flashed full gapps for 4.3 right after it and booted right into android. Everything was previously wiped clean. rebooted soon after and it stick on "google" with "unlock"
screen for half an hour before giving up.
Tried second time and booted right into the new rom. I forgot about the previous reboot issue. spent all day getting most of my apps installed and everything setup. Went to reboot and same crap . Tried clearing cache and dalvik no help.
Wish I would have not wasted my time. I only wish their is a way to salvage this before flashing another rom or a stock image.

wseyller said:
I have lots of experience flashing android roms and this may be a first for me.
Flashed latest MMuzzyrom 4.3 vanilla. Originally had latest stock rooted.
Everything worked flashed full gapps for 4.3 right after it and booted right into android. Everything was previously wiped clean. rebooted soon after and it stick on "google" with "unlock"
screen for half an hour before giving up.
Tried second time and booted right into the new rom. I forgot about the previous reboot issue. spent all day getting most of my apps installed and everything setup. Went to reboot and same crap . Tried clearing cache and dalvik no help.
Wish I would have not wasted my time. I only wish their is a way to salvage this before flashing another rom or a stock image.
Click to expand...
Click to collapse
I have lots of experience as well and this is the first time I've run into this issue. The same **** has been happening to me on all 4.3 ROMs. I had to wipe everything, including internal storage, and reflash a 4.2.2 ROM to solve it. Wish I knew the issue here.

I decided to try flashing a different 4.3 ROM and it hung up for some reason during booting. I then decided to flash the factory image. Then tried the different ROM I downloaded. Seems to be good now. I still don't know what caused it but life is good now.
Sent from my Galaxy Nexus using Tapatalk 2

Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out

playpolo4life said:
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
Click to expand...
Click to collapse
Sorry not sure. Had it saved on my hard drive for a while. Try to download galaxy root toolkit I think it has the ability to download it for you if I remember right.
Sent from my Galaxy Nexus using Tapatalk 2

playpolo4life said:
Can I ask where you found the factory image? I just picked up a Gnex so I'm still figuring everything out
Click to expand...
Click to collapse
wseyller said:
Sorry not sure. Had it saved on my hard drive for a while. Try to download galaxy root toolkit I think it has the ability to download it for you if I remember right.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Wow.
GOOGLE!
Literally Google hosts the damn images for you.
Search for galaxy nexus factory images.
Did everyone forget who gives us this OS? A search company.
Sent from my Galaxy Nexus

What I can't understand is that I have no issues on stock. Zero. Is my device the best device in the world?
Why are you people flashing 4.3 "vanilla ROMs" through a custom recovery when we've got FACTORY IMAGES.
Is it really that hard to root a stock rom? Just follow the whole situation going on with su and you'll know!
Oh and drop the damn toolkit.

Pirateghost said:
Wow.
GOOGLE!
Literally Google hosts the damn images for you.
Search for galaxy nexus factory images.
Did everyone forget who gives us this OS? A search company.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
beekay201 said:
What I can't understand is that I have no issues on stock. Zero. Is my device the best device in the world?
Why are you people flashing 4.3 "vanilla ROMs" through a custom recovery when we've got FACTORY IMAGES.
Is it really that hard to root a stock rom? Just follow the whole situation going on with su and you'll know!
Oh and drop the damn toolkit.
Click to expand...
Click to collapse
You guys need to chill out, that's for damn sure.