Develop Bugs

GNex Bricked?

My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?

ShotgunSam said:
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
Click to expand...
Click to collapse
How did you get there? Did it "just happen" ?

What happens if you pull the battery and hold all 3 buttons to boot into bootloader?

Unless you were flashing a bootloader and it crashed, it isnt bricked. Boot to bootloader (vol down + vol up + power) and flash a stock image with fastboot
I use fastboot for everything, i'd rather not touch ODIN.

ShotgunSam said:
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
Click to expand...
Click to collapse
It's not bricked unless it's a brick, as in it won't power on at all.
Give us some more info and we can try to help. What have you done to it so far? What were you doing when it got to this point?

Ok all I was trying to do was root it using birdmans instructions on rootzwiki. Unlocked the bootloade.r fine, tried to flash cwm and it pushed it fine. But when I rebooted it would bootloop, I could get into cwm but not mount anything.
So I tried some instructions here to odin back a stock image, I had a charge, so I am comfortable with odin, it wrote everything, but failed. Now I get the screen described above and can't get to any other screen no matter what I press.

ShotgunSam said:
Ok all I was trying to do was root it using birdmans instructions on rootzwiki. Unlocked the bootloade.r fine, tried to flash cwm and it pushed it fine. But when I rebooted it would bootloop, I could get into cwm but not mount anything.
So I tried some instructions here to odin back a stock image, I had a charge, so I am comfortable with odin, it wrote everything, but failed. Now I get the screen described above and can't get to any other screen no matter what I press.
Click to expand...
Click to collapse
Your original boot loop was probably due to not clearing the cache?

CanaganD said:
Your original boot loop was probably due to not clearing the cache?
Click to expand...
Click to collapse
I wish, each step everything was cleared and then tried clearing multiple times after the loops started.
the odd thing was when i tried to mount usb through cwm, it couldn't find some sort of files. I was trying to install via zip the su.zip, but the only folder that was showing up on cwm was the clockworkmod folder, no other choices,

Okay, well I am back to the boot looping after successfully flashing odin, it didn't fix the original problem of bootlooping at the google screen.
I cannot mount anything to put anything on the sdcard. From what I can tell, I will have to push something using adb commands. but I am not sure what exactly.

so you used this below and it wont boot?
http://forum.xda-developers.com/showthread.php?t=1394051

no, the original bootloop happened when doing this:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
I attempted to use the Odin to fix it, which it did not.

ShotgunSam said:
no, the original bootloop happened when doing this:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
I attempted to use the Odin to fix it, which it did not.
Click to expand...
Click to collapse
Im asking what file did you use in odin?

I think I know what you did wrong. Did you use the correct cwm image.

321jurgen said:
I think I know what you did wrong. Did you use the correct cwm image.
Click to expand...
Click to collapse
I used the toro image. would it had put cwm on there if I used the gsm image?
I am currently working through http://forum.xda-developers.com/showthread.php?t=1399210
to try to fix it.

Sorry I see now you have verizon. That means you need to have the toro. I will do some research hopefully I can help you. I thought I had the same problem because I came in the same situation when I used the wrong cwm image.

droidstyle said:
so you used this below and it wont boot?
http://forum.xda-developers.com/showthread.php?t=1394051
Click to expand...
Click to collapse
yes, that is what I tried to flash through odin, it failed the first couple of times but when I changed computers, it flashed, but did not fix the boot loop.

Update, I flashed a stock image via adb through the instructions I mentioned above.....and..... SUCCESS!
I think my original problem was I freaked out when it cycled the colored thing longer than normal. After flashing the stock image today, it cycled the color things for a long time, then rebooted itself and cycled through a long time again. but eventually came up.
I appreciate everyone who took time to read this thread and chimed in.

clock work mod / root issues

So i am running the stock rom unlocked and rooted. Everything has been working fine until recently.
I wanted to flash a boot animation instead of just copy and paste with root explorer. So i booted into fastboot (volume hold then power). I then selected recovery and my phone shows the android thinking then he's flat on his back with an exclamation point above him. I followed the rootwiki for the gnex to the letter. Any ideas on whats wrong?
Thanks for helping a newb.

No solution from me.. but:
dalumberjack said:
So i am running the stock rom unlocked and rooted. Everything has been working fine until recently.
I wanted to flash a boot animation instead of just copy and paste with root explorer. So i booted into fastboot (volume hold then power). I then selected recovery and my phone shows the android thinking then he's flat on his back with an exclamation point above him. I followed the rootwiki for the gnex to the letter. Any ideas on whats wrong?
Thanks for helping a newb.
Click to expand...
Click to collapse
Afraid I can't help you but I had exactly the same issue. I used flashed the original recovery again and again but kept getting droid flat on it's back with the red exclamation mark. Finaly I decided that I found recovery imporatant enough and decided to flash CWM recovery. That gave me at least recovery back. I would prefer however getting stock recovery back. So if someone has a resolution I would be one happy camper.

Tried to flash it again and it gave me an error in adb saying faiked partition.
Any help is appreciated

Try flashing CWM with Rom Manager.

The android on his back with exclamation point is stock recovery. You have a few options: install ROM manager and flash clockworkmod through it (some people's phones need this done before each flash I think based on root process) or you can change the name of your recovery-from-boot.p file which is a file that causes ICS to revert back to stock recovery, and some have to use root explorer to change the read/write access to get clockwork to stick. I would just use ROM Manager for it. If you ever want stock recovery you can download the factory image file from Google and extract the recovery.img and use fastboot
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img

At least my problem is solved. The fact that droid with the red exclamation mark is stock left me searching how to get into recovery then. It appears that if you hit Volume up and power shortly when you see that image it loads stock recovery menu.
Two simple questions: I want my GN to be close to stock, haven't flashed custom rom's radio's etc. What I do want is Root and SetCPU (for power saving options during screen off), rootexplorer, Volume+ etcetera working. I've managed to put them all on, now:
If I reflash stock recovery and lock my bootloader: will they keep on working and:
If I get OTA updates: will they keep on working too?
Thanks in advance for any reply...

Diger36 said:
At least my problem is solved. The fact that droid with the red exclamation mark is stock left me searching how to get into recovery then. It appears that if you hit Volume up and power shortly when you see that image it loads stock recovery menu.
Two simple questions: I want my GN to be close to stock, haven't flashed custom rom's radio's etc. What I do want is Root and SetCPU (for power saving options during screen off), rootexplorer, Volume+ etcetera working. I've managed to put them all on, now:
If I reflash stock recovery and lock my bootloader: will they keep on working and:
If I get OTA updates: will they keep on working too?
Thanks in advance for any reply...
Click to expand...
Click to collapse
you can leave your phone unlocked and root with a method such as CF-Root and leave your factory recovery and OTA's will go through and install without issue. Having the bootloader unlocker doesn't effect OTA's at all. There are a some programs that claim they maintain root after OTA but even if they don't you can just re root with a program like CF-Root

joshnichols189 said:
Try flashing CWM with Rom Manager.
Click to expand...
Click to collapse
This. I had the exact same issue when trying to flash anything after I rooted. either flash CWM through rom manager or install CWM permanently if you haven't already. After I installed it I've had no issues.

updates failing on 4.0.1 yakju

I was on 4.0.1 yakjuxw before and I flashed yakju from this thread here:
http://forum.xda-developers.com/showthread.php?t=1464881
...and the actual flashing went perfectly and the phone works fine, and I was prompted to update my phone but during the process of updating at about 50 percent or so it failed and I got a red triangle with a big black exclamation mark which stopped the update. I was able to take the battery out and the phone booted up fine and the phone works still.
Does anybody know what caused the error? Is there a way to fix it so I can get updates working?

bump id still like some help with this.

You have cwm...can't do otas with clockwork. Either flash stock recovery or manually flash the image through fastboot
Sent from my Galaxy Nexus using xda premium

I just went to fastboot and then went into recovery from there and I got the android on his back with the red triangle with the "!" does that mean I have no recovery?

No, it means you have the stock recovery

jonnyg1097 said:
I just went to fastboot and then went into recovery from there and I got the android on his back with the red triangle with the "!" does that mean I have no recovery?
Click to expand...
Click to collapse
Just press Volume Up + Power button when you see that droid image and you should get the Stock recovery menu.

[Q] New Android user :)

Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA

KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
Yes that means its rooted, you should have a custom Recovery. If you power off and hold the volume keys and the power button then a green android will pop up use the volume keys and hit up twice to the "recovery mode" then hit the power button... then if you could tell me what you see? At the bottom it should say Clockworkmod 5.x.x.x or it will have TWRP which it will show TeamWin at first and a curtain will pull up. If you do have custom recovery you could just simply flash a custom ROM like AOKP for you device .

KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER on your ability to install updates OTA. It will happen if your recovery does not match your ROM.
You have a few options:
1) you can go to the "update" link in my signature, find the update for your build, and install it manually as per the instructions in that thread.
2) you can go to the "flash" link in my signature and flash stock (yakju) 4.0.4 as per the instructions.
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER or your ability to install updates OTA.
Click to expand...
Click to collapse
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.

ÜBER™ said:
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
Click to expand...
Click to collapse
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.

ÜBER™ said:
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
Click to expand...
Click to collapse
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha now that we are done bickering.. i hope the OP can find his way.

ycholish siempre
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
then if you could tell me what you see?
Click to expand...
Click to collapse
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .

KrizTM said:
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
Click to expand...
Click to collapse
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium

ÜBER™ said:
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?

Check my sig to get yourself on AOKP.

KrizTM said:
[snip]
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
Click to expand...
Click to collapse
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
KrizTM said:
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Click to expand...
Click to collapse
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
KrizTM said:
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Click to expand...
Click to collapse
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).

efrant said:
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
Click to expand...
Click to collapse
Awesome. That clears up a lot of things. Thanks a lot You're right. Gonna stick to stock 4.04 till I get better at this hehe.
Thanks

[Q] Cannot boot to recovery (on two completely separate phones).

I flashed CM10 onto my phone a couple weeks ago, everything went smoothly. Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update. Well I download the update, reboot phone into fastboot, attempt to go into recovery and I get the red triangle !. I know this is an issue with the phone apparently not finding a recovery boot but why didn't my reverting to stock reinstall the stock recovery? Does anyone have any guides they suggest to get stock recovery back? (I've found a few but thought I would ask).
Now, this is understandable that my phone can't boot into recovery since I flashed CM recovery onto it and whatnot, but I attempted to boot into recovery on my girlfriends phone (same phone, NEVER BEEN UNLOCKED OR FLASHED) and it can't boot into recovery either... Is something going on here or am I just missing a huge piece of the puzzle? I don't really want to have to flash anything on my girlfriends phone to fix it, she's not into the tinkering and would rather not have her data reset. Any help would be appreciated.
And for the record, I did a search to figure this out but at the very least I can only find solutions for people who have flashed CM or similar and nothing pertaining to the problem my girlfriend's phone has.

Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app

nktje said:
Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Used this method:
http://forum.xda-developers.com/showthread.php?t=1848566
It worked, I'm on stock ICS, but I didn't do ANYTHING after booting into ICS again and attempting to install JB and booting into recovery. Did I miss something? How do I "flash recovery"?

Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app

I think you are confusing a few things here. First off, the Android with the red triangle IS the stock recovery main screen. (If you want to flash the update manually, you need CWM -- go into fastboot mode and type: fastboot flash name-of-recovery.img, where name-of-recovery is the recovery that you downloaded and want to flash.) Second, you need the stock recovery for an update to install over-the-air, but you need a custom recovery if you want to flash it manually.

Muffinabus said:
Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update.
Click to expand...
Click to collapse
this happened. you installed stock recovery when you reverted, whats the surprise?
and you dont need to relock bootloader to successfully update through ota. seems to me know the op needs to refine his searching skills.
nktje said:
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Click to expand...
Click to collapse
just press vol up+power to bring up the stock recovery menu.
edit: damn efrant, i got this man
sent from my i9250

nktje said:
Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.

Muffinabus said:
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.
Click to expand...
Click to collapse
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250

bk201doesntexist said:
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250
Click to expand...
Click to collapse
Alright, I think I got it... so the android with the red ! triangle IS stock recovery? I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then? So what does the stock recovery DO other than sit there and reboot after a minute?

Muffinabus said:
Alright, I think I got it... so the android with the red ! triangle IS stock recovery?
Click to expand...
Click to collapse
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
Muffinabus said:
I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then?
Click to expand...
Click to collapse
No, that does not work on the GNex.
Muffinabus said:
So what does the stock recovery DO other than sit there and reboot after a minute?
Click to expand...
Click to collapse
Have a look at the menu, and you can see the options.

efrant said:
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
No, that does not work on the GNex.
Have a look at the menu, and you can see the options.
Click to expand...
Click to collapse
Thank you! I feel like an idiot now. I honestly thought it'd be the same as the Nexus S where you were able to do this...