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.
Related
...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
ok I got a real good deal on a GNEX on CL and the guy said it wasn't rooted and smart me believed him. Well from what I can tell the bootloader is unlocked, and it is rooted because I ran root checker and it has superuser and wifi tether.It does not seem to have a custom rom on it The problem I see is that it seems to have stock recovery but when I go from the bootloader screen to recovery it reboots the phone most of the time after sitting on the image of the android guy with a red triangle over him. I plan on doing the JB OTA update when it comes out . At this state I am just not sure what I should do to make my phone not mess up in the long run. I was thinking unrooting and locking the bootloadder and re flashing stock recovery would be a good idea kind of starting from scratch. Please let me know what yall think and thanks for your time oh and I am on Sprint
Yeah just Odin back to stock you should be fine. Also you'll be waiting a long time for an OTA of jelly bean at least on sprint. We already have a port of the preview OTA that the gsm version got. Only thing doesnt work is MMS for obvious reasons.
Sent from my Galaxy Nexus using xda premium
does odin happen to work on a Mac? also is their a SDK kit for mac?
also has anyone ran into this situation where recovery dosent work? can I flash stock recovery back on without being able to get to any recovery to begin with?
kal7467 said:
also has anyone ran into this situation where recovery dosent work? can I flash stock recovery back on without being able to get to any recovery to begin with?
Click to expand...
Click to collapse
U can come back to stock recovery without any problem u can use gnex toolkit u ll be fine i guess , However JB rom available now are also awesome it works great without any problem ,except some apps yet to be updated for JB update
Stay away from toolkits. You can Fastboot flash the .img for the stock recovery boot and rom it self.
Sent from my Galaxy Nexus using xda premium
kal7467 said:
does odin happen to work on a Mac? also is their a SDK kit for mac?
Click to expand...
Click to collapse
No, Odin only works on windows.
There is no need for the SDK, all you need are the fastboot and adb files for Mac.
Look at the "flash" link in my signature. It has all the instructions on how to revert you device to stock. Mac-specific instructions are linked to a little further down.
Sent from my Galaxy Nexus using Tapatalk 2
Ok so I got the GSM version today, I was using this http://www.youtube.com/watch?v=oSmd9ZbUH50&feature=player_embedded to help me unlock the bootloader, flash CWM, and flash the SU files. I unlocked the bootloader without a problem, just It did not delete all my data like the video said.
Once I try flashing CWM and looks like its fine, but after reboot when trying to boot into recovery, I get the Red Triangle with exclamation mark. I have tried flashing it a couple times, it still does the same thing. Can anyone help me please?
I just got mine today also, did you rename the stock recovery image before flashing cwm? I renamed it after and had the same issue so I reflashed cwm and all is good.
Sent from my SGH-T959V using xda premium
try using this tool http://forum.xda-developers.com/showthread.php?t=1400871
1) Play Store devices do NOT wipe when unlocking the bootloader. (We are still trying to figure out why.)
2) The Android with the red "!" IS the stock recovery. There are two files in you /system that reflash the stock recovery on every boot. If you want you custom recovery to stick, you need to delete/rename one or both:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Galaxy Nexus using Tapatalk 2
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
manuelsavino said:
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
Click to expand...
Click to collapse
Did you not read what I wrote? You NEED to rename one of those files for CWM to stay installed.
Sent from my Galaxy Nexus using Tapatalk 2
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
manuelsavino said:
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
Click to expand...
Click to collapse
Yup. Or if you reboot before renaming the files, just reflash cwm again once you delete then. No big deal.
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Thank you all! I will report back once I do it!
manuelsavino said:
Ok. Thank you all! I will report back once I do it!
Click to expand...
Click to collapse
This would have taken less than 5 minutes with the V7 Toolkit- boot loader unlock, root, rename recovery file, and install CWM/TWRP.
It is good that your trying other methods, though.
Sent from my Galaxy Nexus
bhowanidin said:
This would have taken less than 5 minutes with the V7 Toolkit
Click to expand...
Click to collapse
If he did it using a toolkit as you suggested, we would have learned nothing.
Sent from my Galaxy Nexus using Tapatalk 2
Mate I had the same problem. I got my device yesterday and unlocked my device with the tool Galaxy Nexus Root Toolkit v1.4. But it didn't allow me to root it. As I had ADB installed I tried to flash recovery trough it. But still no success. Here's how I did it.
Download Galaxy Nexus Root Toolkit v1.4. Enter the advanced settings.
Transfer su.zip to your internal memory and then "Boot into Temp CWM" trough that tool. Then you can root your device. Once it's rooted, download "ROM Manager" from the market. Accept the permissions it's asking for. And flash CWM recovery from it.
And voila. It worked for me.
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Ran into this version in a video I watched. So I just downloaded it.
Oh right you should check the development section for the newer version it is far more simple & self explanatory.
I'm done with rooting and unlocking. I did it already. Just explained how above.
No need for a tool no more.
Its useful if you want to relock your phone and go back to stock
replied..
ste1164 said:
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Click to expand...
Click to collapse
I'm guessing it just worked for him..:good:
If it anit broke why try to fix it
Ended up using the toolkit. One question, the two files that need to be renamed/deleted so it wont go back to stock recovery, on the toolkit it says rename, though once i go on root explorer to see if the two files are still there, they disappeared. So if I ever wanted to go back to stock recovery for any reason, are those two files available anywhere? Or is there a stock recovery image?
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
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250