Develop Bugs

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

How to Root Nexus 10 on Win/Mac/Linux! [Step-by-Step VIDEO Tutorials]

Here's a video tutorial on how to root your Nexus 10 for noobs!
Windows video tutorial:
Mac video tutorial:
Linux video tutorial:
All the files you need in one zip (adb+SuperSU+fastboot+Windows drivers):
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
Step-by-Step tutorial with photos here:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
Also, if you get stuck on bootloop after unlocking bootloader (This happened to me couple times), do a factory reset in stock recovery to fix:
Thanks to shimp208 for the sideload method and working CWM, ChainFire for awesome SuperSU and to all the developers who are worked on CWM recovery!

So the CWM that was just updated by Koushik on CWM does not work properly or does it work? Was asking based on this
While CWM Recovery is still being fixed
Click to expand...
Click to collapse
Edit: There's no driver issue if it were on a Mac right? Especially adb sideloading the CWM SuperSu zip?

How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..

johno86 said:
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
Click to expand...
Click to collapse
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!

I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. No red triangle. It boots into CWM and then after 20 seconds restarts itself and hits the bootanimation loop. Any clue what to do next? Trying to flash the stock image but having issues using cmds in windows cmd
*edit
I cleared cache through cmd and i got to the red triangle...thank ****ing the lord. DTWAZERE, I will remember tonight. Thank you for your help.

johno86 said:
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. Any clue what to do next? Trying to flash the stock image but having issues getting it into fastboot now...
Click to expand...
Click to collapse
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk

dtwazere said:
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
Click to expand...
Click to collapse
Yeah this is exactly what I did and it worked. I'll wait on flashing anything until there's a stable recovery. I was fairly confident in what I was doing until that happened. Not being able to input commands from cmd prompt made me sick so I'll wait for a dev to release something that works without having to quickly install the drivers again within a 15-20 second timeframe. Too much stress.

cant boot
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?

lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
Heh im having the same issue.

lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.

deevooneh said:
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
Click to expand...
Click to collapse
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.

i did everything, and it all went successfully after a few tried. Now i am stuck with the JB X load screen.
How do i get the stock google rom and how do i flash it?

lc684760 said:
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
Click to expand...
Click to collapse
Ok. Let me know if you figure something out. Hopefully we didnt brick it.

deevooneh said:
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
Click to expand...
Click to collapse
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!

lc684760 said:
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
Click to expand...
Click to collapse
How do we get back to stock? Might need to reattempt this.

If you are stuck on the boot animation (X) screen... power off your device and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely

dtwazere said:
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
Click to expand...
Click to collapse
deevooneh said:
How do we get back to stock? Might need to reattempt this.
Click to expand...
Click to collapse
Stock is here
https://developers.google.com/android/nexus/images#mantarayjop40c
Still need a way to get CWM stable, so we have time to copy to sd

craigacgomez said:
If you are stuck on the boot animation (X) screen... power off you devices and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
Click to expand...
Click to collapse
THIS WORKED!!
Youre a genius. thanks!

When I try to install the manta drivers manually and tell it to search the same area that it searched and found the android bootloader drivers for fastboot mode it says that the drivers couldn't be found and installed. Am I missing something? Also if i try to do fastboot flash recovery it gives me an error message stating that it cannot determine the image filename for the recovery image.

Well i guess i did it the long way around.
Went to https://developers.google.com/android/nexus/images#mantarayjop40c
and downloaded the Nexus 10 file. extracted, and the actual files in the Nexus10Root folder.
Opened the flash-all.sh and entered each command manually because it was erroring out running the script.
After the 3rd command it booted right into android!

[Q] How do I revert ODIN to custom bootloader and recovery?

I have a toro/i515/Verizon Samsung Galaxy Nexus (the CDMA/LTE one) running a mostly stock (but rooted and with busybox) Jelly Bean JRO03O (Android 4.1.1).
I screwed up my build.prop (and can't boot normally), so I attempted to boot into CWMR 6. To my surprise, cold booting holding the Vol + button started to proceed with a normal boot. So I cold booted with the Vol - button held.
And that shocked me even more. I'm staring at ODIN Mode. WTF? When did ODIN get on my phone? What happened to the bootloader where I could select booting into recovery, or the bootloader, or normal booting?
I've been scouring Google and this forum, and many other forums, and I cannot for the life of me figure out how to boot this thing into a custom recovery so I can fix my build.prop through adb.
I'm at a loss. I suck at using ODIN (I only started using it recently when I bought my GTab2 10.1 GT-P5113).
How am I supposed to hack my phone when I can't use ADB, fastboot, or a custom recovery (booting normally hangs also)?
The only thing I don't want to do for a repair is a full wipe. I don't have a way of backing up my data without ADB.
I've tried enclosing various boot, bootloader, and recovery images (img files) into tar files (archives) and sending them to the phone via ODIN using the PDA and/or the BOOTLOADER button(s). I've tried to see if Wug's Toolkit would talk to my phone via ODIN.
Nothing seems to change.
Help!!! Please!!!
Any of the following will do:
1. Tell me how to get adb working.
2. Tell me how to revert ODIN back to the normal boot/bootloader (that works with fastboot) - this would be best. ODIN sucks.
3. Tell me how to get to my files via ODIN.
Please help. This sucks.

*sheepish grin* - I forgot about holding BOTH Vol + and Vol - at the same time while cold booting.
(I can at least get into fastboot mode now)...

From fastboot, boot to custom recovery (use vol keys to highlight, power to select), reflash rom.
Or
From fastboot, flash stock but dont flash userdata.img.
Sent from my i9250

The very same thing happened to me today.
I was on 4.2 JB (custom stock rom, only rooted) and I received a software update....it failed at doing it and then said something about not losing root. I checked YES and boom....wont boot. Stuck at ODIN...
Odin recognizes it but fails at flashing.
Fastboot works and boots into cwm recovery....but it wont boot into android...
What should I do...?
Sorry if I am rude by asking here.

dragoncius said:
The very same thing happened to me today.
I was on 4.2 JB (custom stock rom, only rooted) and I received a software update....it failed at doing it and then said something about not losing root. I checked YES and boom....wont boot. Stuck at ODIN...
Odin recognizes it but fails at flashing.
Fastboot works and boots into cwm recovery....but it wont boot into android...
What should I do...?
Sorry if I am rude by asking here.
Click to expand...
Click to collapse
From fastboot, boot to custom recovery (use vol keys to highlight, power to select), reflash rom.
i said this on the post before yours.

bk201doesntexist said:
From fastboot, boot to custom recovery (use vol keys to highlight, power to select), reflash rom.
i said this on the post before yours.
Click to expand...
Click to collapse
But there is nothing in my phone....
Internal is empty.
How can I flash something on the phone...
Sent from my GT-N7100 using xda premium

dragoncius said:
But there is nothing in my phone....
Internal is empty.
How can I flash something on the phone...
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
dont hijack other people's threads;
read the stickies
http://forum.xda-developers.com/showthread.php?t=1812959

bk201doesntexist said:
dont hijack other people's threads;
read the stickies
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Sorry. Didnt mean to hijack...just thought it is the same problem. Already read threads.
Sent from my GT-N7100 using xda premium

dragoncius said:
Sorry. Didnt mean to hijack...just thought it is the same problem. Already read threads.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
use adb to push a rom while on a custom recovery. it seems you need to read them again, and pay attention to it.
http://forum.xda-developers.com/showthread.php?t=1812959

SOLVED
chriv said:
*sheepish grin* - I forgot about holding BOTH Vol + and Vol - at the same time while cold booting.
(I can at least get into fastboot mode now)...
Click to expand...
Click to collapse
After posting the above, I meant to indicate that this thread could be closed. I knew exactly what to do now that I could finally get into fastboot.
Maybe ODIN was on my phone all along, but I could almost swear that I used to get into fastboot by holding Vol - while cold booting, and that I could get into recovery by Holding Vol + while cold booting. I don't remember ODIN being there at all.
Anyway, the bottom line:
Fastboot loads with Vol + AND Vol - held down while cold booting.
I was able to reflash boot, bootloader, and custom recovery with fastboot.
I was able to boot into custom recovery from fastboot.
Once CWMR 6 was running on my phone in recovery mode, I was able to mount /system from the recovery menu, to use adb to pull /system/build.prop, to edit it, to use adb to push build.prop back to /system, and finally to use adb to change permissions on build.prop back to 644.
Am I crazy? Was ODIN always on my VzW GNex?
Was it always loaded when holding Vol - down during a cold boot?
Or were the Vol - and Vol + buttons (individually) originally used for booting fastboot mode and recovery mode?
If I had forgotten that, then I haven't be hacking my phone enough, as I haven't been in fastboot in a long time.

chriv said:
After posting the above, I meant to indicate that this thread could be closed. I knew exactly what to do now that I could finally get into fastboot.
Maybe ODIN was on my phone all along, but I could almost swear that I used to get into fastboot by holding Vol - while cold booting, and that I could get into recovery by Holding Vol + while cold booting. I don't remember ODIN being there at all.
Anyway, the bottom line:
Fastboot loads with Vol + AND Vol - held down while cold booting.
I was able to reflash boot, bootloader, and custom recovery with fastboot.
I was able to boot into custom recovery from fastboot.
Once CWMR 6 was running on my phone in recovery mode, I was able to mount /system from the recovery menu, to use adb to pull /system/build.prop, to edit it, to use adb to push build.prop back to /system, and finally to use adb to change permissions on build.prop back to 644.
Am I crazy? Was ODIN always on my VzW GNex?
Was it always loaded when holding Vol - down during a cold boot?
Or were the Vol - and Vol + buttons (individually) originally used for booting fastboot mode and recovery mode?
If I had forgotten that, then I haven't be hacking my phone enough, as I haven't been in fastboot in a long time.
Click to expand...
Click to collapse
Odin is on every Samsung phone I believe
Sent from my Galaxy Nexus using Tapatalk 2

question/comment to old post
This is an old post I'm responding to but my A500 has been bricked for over a year. I just read, click the lock button and when I did, on the screen is "Bootloader v0.03.12 ICS:: Starting Fastboot USB download protocol and found a related post referencing "Odin". I, too, want to know how that got onto my tablet. Perhaps from the update.zip? Now I can't find any relevant information nor files to download which aren't corrupt or tampered with. Can someone perhaps take a moment to outline a plan of action for me and the significant files? I will gladly "donate" to whomever and by "time". Thx (little grey haired old lady) Smiles4Miles, VMD
chriv said:
I have a toro/i515/Verizon Samsung Galaxy Nexus (the CDMA/LTE one) running a mostly stock (but rooted and with busybox) Jelly Bean JRO03O (Android 4.1.1).
I screwed up my build.prop (and can't boot normally), so I attempted to boot into CWMR 6. To my surprise, cold booting holding the Vol + button started to proceed with a normal boot. So I cold booted with the Vol - button held.
And that shocked me even more. I'm staring at ODIN Mode. WTF? When did ODIN get on my phone? What happened to the bootloader where I could select booting into recovery, or the bootloader, or normal booting?
I've been scouring Google and this forum, and many other forums, and I cannot for the life of me figure out how to boot this thing into a custom recovery so I can fix my build.prop through adb.
I'm at a loss. I suck at using ODIN (I only started using it recently when I bought my GTab2 10.1 GT-P5113).
How am I supposed to hack my phone when I can't use ADB, fastboot, or a custom recovery (booting normally hangs also)?
The only thing I don't want to do for a repair is a full wipe. I don't have a way of backing up my data without ADB.
I've tried enclosing various boot, bootloader, and recovery images (img files) into tar files (archives) and sending them to the phone via ODIN using the PDA and/or the BOOTLOADER button(s). I've tried to see if Wug's Toolkit would talk to my phone via ODIN.
Nothing seems to change.
Help!!! Please!!!
Any of the following will do:
1. Tell me how to get adb working.
2. Tell me how to revert ODIN back to the normal boot/bootloader (that works with fastboot) - this would be best. ODIN sucks.
3. Tell me how to get to my files via ODIN.
Please help. This sucks.
Click to expand...
Click to collapse

[Q] Recovery mode red exclamation problem

Hi,
I just flashed my GNex to the stock yakju ROM using the link since, i wished to receive OTA updates. Everything is working properly except when i am trying to install Titanium Backup from recovery mode. When i get into recovery mode, i see the android logo with the red exclamation mark. Now, there are options available to install a stock recovery but i am uncertain that the OTA updates might stop if i install one !
Is there a way to rectify the recovery so that i can install titanium backup and restore my apps without losing OTA updates ?
Please point me to a link which explain the steps in details if possible as i have never done this before

24adithya said:
Hi,
I just flashed my GNex to the stock yakju ROM using the link since, i wished to receive OTA updates. Everything is working properly except when i am trying to install Titanium Backup from recovery mode. When i get into recovery mode, i see the android logo with the red exclamation mark. Now, there are options available to install a stock recovery but i am uncertain that the OTA updates might stop if i install one !
Is there a way to rectify the recovery so that i can install titanium backup and restore my apps without losing OTA updates ?
Please point me to a link which explain the steps in details if possible as i have never done this before
Click to expand...
Click to collapse
AFAIK, The red exclamation mark is not recovery mode.
You need to press Vol button up + down + lock. Then phone will reboot into bootloader.
Choose recovery mode by pressing vol down. then press power button.

Recovery mode red exclamation problem
neerajvd said:
AFAIK, The red exclamation mark is not recovery mode.
You need to press Vol button up + down + lock. Then phone will reboot into bootloader.
Choose recovery mode by pressing vol down. then press power button.
Click to expand...
Click to collapse
Yes, i did that. I pressed vol up + vol down + power button. I got restart bootloader option. I navigated to recovery mode using the volume buttons and selected it by pressing power button. After that i am seeing the logo with the red exclamation mark.

24adithya said:
Yes, i did that. I pressed vol up + vol down + power button. I got restart bootloader option. I navigated to recovery mode using the volume buttons and selected it by pressing power button. After that i am seeing the logo with the red exclamation mark.
Click to expand...
Click to collapse
Ok, i understood that pressing vol up + power button takes you to the actual menu . I want to install titanium backup from the zip i have made. Can anyone tell me how it is to be done?
I see options like
a)apply update from adb
b)apply update from sd card
c)wipe cache/data partition
d)factory reset
Where exactly should i keep my .zip file in the storage ? Inside android folder so that i can use option (b) ? Is there any other way to install the zip ?

The red exclamation mark is the default recovery..................
Flash the latest copy of CWM/TWRP, Google for it, it's not hard..
If you do not have your bootloader unlocked, click on the bootloader link on my signature..

You can boot with a custom recovery without flash it. You should use this command in fastboot mode:
fastboot boot my_recovery.img
If you want flash recovery you should use:
(You will lose OTA updates)
fastboot flash my_recovery.img

Thanks for all your answers. I was able to access the menu by holding the vol up and power button simultaneously.

lkeops said:
You can boot with a custom recovery without flash it. You should use this command in fastboot mode:
fastboot boot my_recovery.img
If you want flash recovery you should use:
(You will lose OTA updates)
fastboot flash my_recovery.img
Click to expand...
Click to collapse
You don't lose ota updates if you flash a recovery.
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
You don't lose ota updates if you flash a recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You don't "lose" OTA but you can't install it.

lkeops said:
You don't "lose" OTA but you can't install it.
Click to expand...
Click to collapse
yes you can. ive been doing it for awhile.

Zepius said:
yes you can. ive been doing it for awhile.
Click to expand...
Click to collapse
Please, tell me which recovery you use and how you do.

lkeops said:
Please, tell me which recovery you use and how you do.
Click to expand...
Click to collapse
you can use either, but i use twrp.
when the OTA boots you into recovery, you just select the OTA file and flash it.
if you modified any other system files, it will fail and will tell you why it failed.

Zepius said:
you can use either, but i use twrp.
when the OTA boots you into recovery, you just select the OTA file and flash it.
if you modified any other system files, it will fail and will tell you why it failed.
Click to expand...
Click to collapse
Thanks! Too many people have reported several issues using this method. I don't know what determines the success.

lkeops said:
Thanks! Too many people have reported several issues using this method. I don't know what determines the success.
Click to expand...
Click to collapse
thats because those people modify system files and think they're still stock.
literally, if you just change the recovery and root your phone, you can still flash the OTAs. if you change anything else, install something that changes system files (such as busybox), you will not be able to install the OTA. it really is that simple.