Develop Bugs

Jelly Bean animation locked

Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.

coachv said:
Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.
Click to expand...
Click to collapse
The animation is locked? I don't understand what you mean. Are you stuck at the boot logo (Google screen) or the boot animation (flashing X)? Either way, you can just go into your custom recovery, wipe data, and try flashing again if you are waiting on it to boot for that long. Some users have experienced waiting 5 minutes before it actually started up.

Agreed.
Initial boot on my Toro took 5-6 minutes.
It was butter ever since, however.
Give it a minute.
And make sure you're properly installing a rom (post 2 from the link in my signature).
Edit:
Anton&Juba.
Tag-teaming 'ze noobs until it goes out of style.

It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks

coachv said:
It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks
Click to expand...
Click to collapse
I see. So you're in a bootloop. What do you mean fastboot mode? Because I know some users get confused with the terms... I'm assuming you're able to enter the Bootloader (screen with android belly open, where you are able to move through some menu options with your up and down volume keys)? Note, this is not the screen with the Android and red exclamation point. If you are able to boot into bootloader, you should be able to enter your custom recovery (Clockworkmod Recovery?) and wipe data and either flash a rom (same one or new one) and try again, or restore a backup you made. If you're set on using fastboot commands, you can always flash Nexus Factory Images, although this will wipe your SD card. I recommend getting into your custom recovery and wiping and flashing or restoring. If you don't have a custom recovery, you can always flash a custom recovery (fastboot flash recovery recoveryname.img) and flash a custom rom or restore from there. Here is CWM recovery incase you don't have a custom recovery, or you have reverted back to stock (Android with red exclamation point).

yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.

coachv said:
yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.
Click to expand...
Click to collapse
Can you scroll through the menu options with your volume keys? And one of the options should be "reboot recovery." Do that one.

Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off

coachv said:
Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off
Click to expand...
Click to collapse
Okay dude.
1.) Move your volume keys to select recovery mode
2.) press the power button to actually select that option
3.) You will boot into your custom recovery
4.) EITHER Wipe Data, wipe cache, wipe dalvik, and then flash a new rom (or try re-flashing this jellybean rom you're having problems with) OR restore from a backup you have previously made (which I hope you did just incase something worse happens in the future).
You do know how to navigate through your custom recovery, right?

[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

AOKP to STOCK BIG PROBLEMS

i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess. i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery. i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys. just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out

jamesquags said:
i need some help here guys. i was running AOKP for the longest time and loving it. then today i tried to update to the latest version. i downloaded the rom and went to flash the .zip in CWM. i've done this dozens of times. this time things were completely different. i kept getting FCs over and over. so i booted into recovery again to reflash. for whatever reason, it seemed like my file system was corrupted. folders i had never seen were all over the place. it was a big mess.
i decided to flash back to stock. i booted into DL mode and did this with odin successfully. then upon reboot, the phone was stuck at the Samsung logo. looking into this i saw that i needed to boot into recovery, wipe data/factory reset, wipe cache, and wipe dalvik cache. i tried doing this but no matter what, my phone will not boot into recovery.
i have even used odin to flash CF-SGS3-CWM-v5.5-v1.0.tar. when i press volume up+home+power i get the first samsung logo with the tiny blue text up at the top saying "recovery booting" but then nothing happens and the phone just goes to a normal boot attempt, which stalls at the samsung logo. please help guys.
just for a quick overview. was on [ROM] AOKP(Jellybean 4.2.1 )Task & Ktoonsez (12/23) (AT&T/Rogers), potential file system corruption during a routine upgrade, flashed back to stock with odin (meaning i can still boot into DL mode), but CANNOT boot into RECOVERY mode. i'm freaking out
Click to expand...
Click to collapse
First of all, good job on searching before posting! :good:
Second, if you want help, try using capital letters at the start of a sentence and using paragraphs. It makes it sooo much easier to read that way.
Third, just keep trying. But from what you're saying about a file-system issue, that could be bad? It's not familiar to me anyways. Hope it didn't damage the internal SD.
If nothing else works, then try the USB-JIG to access Recovery mode. They're like $5 on eBay.
Okay, try these things.
1) Odin a non-rooted, stock ROM that comes with a 3E recovery and try to access that recovery.
If that doesn't work, move onto this step:
2) Odin a different recovery. I attached one to this post. Just unzip it and then odin it. :CWM-Recovery-LTE-SGS3-v5.tar:
Try to get recovery again after a battery pull.

If that doesn't do it, then try this next:
1) Odin a rooted ROM onto the phone.
2) Download the attached "openrecovery-twrp-2.3.1.0-d2att" and unzip it.
3) Download this ADB & Fastboot tool and extract it to your C:/ drive with subfolders using this path: "C:/Android/platform-tools/".
Here is the file to download:
http://www.androidfilehost.com/?fid=9390135922294523275
4) Rename the openrecovery-twrp-2.3.1.0-d2att to "recovery" and place it into the Platform-tools folder.
5) Open the JPEG and follow the EXACT same commands in the pic. This will install TWRP recovery for you.
Then try once again to get into recovery.
If it still doesn't work, then buy a USB Jig.

REPLY
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim

jamesquags said:
"Failed to Open Serial [COM] Port".
Click to expand...
Click to collapse
Have you installed the phone drivers? They're linked from the Odin thread.

smelenchuk said:
Have you installed the phone drivers? They're linked from the Odin thread.
Click to expand...
Click to collapse
Yes i have installed the drivers. I have flashed multiple .tar files today.

jamesquags said:
Thanks so much for the advice.
Regarding the TWRP installation, is the phone connected to the computer in DL mode for this?
I am currently downloading a rooted stock ROM. This might help shed light on what is going on here.... I unzipped the .tar you attached to your first post and stuck it in the PDA slot with the phone connected and in DL mode. ODIN did nothing and the returned a FAIL message saying that it "Failed to Open Serial [COM] Port". Hmmmm. Anyways I am going to try to install the TWRP recovery. If not I will buy the USB jig. Thanks again for you help. -jim
Click to expand...
Click to collapse
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.

CZ Eddie said:
The TWRP doesn't use Odin. You have to use ADB/FastBoot like I show in the picture attached with it.
I have yet to find an Odin flashable TWRP.
Click to expand...
Click to collapse
After flashing the ROOTED STOCK ROM, I tried about 7 times to boot into recovery. It finally did!!! I then was able to do a wipe data and cache and I'm all set.
Thanks so much for helping me out. -jim

To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go if the power button but still press the home + volume up
Sent from my SGH-I747 using Tapatalk 2

jerrycoffman45 said:
To get into recovery hold the power+volume up+ home key when you see the blue text at the top of the screen let go of the power button but still press the home + volume up
Click to expand...
Click to collapse
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.

CZ Eddie said:
Why do you continue to hold the home + volume up? I release all three as soon as I see the blue text and it goes into Recovery just fine for me.
Click to expand...
Click to collapse
i dont know i have always done it that way well learned something new just tried it your way thanks

[Q] Installing custom recovery? New to Samsung phones...

Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks

ovimunt said:
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
Click to expand...
Click to collapse
May I ask what variant you are using? GT-i9195?
Then please boot your phone into download mode, this can be done by first switching of your phone completely then holding the power button, home button and volume down button until the download screen appears where you press continue. Once you have done that connect your phone using the usb cable and make sure all drivers have been installed! Once the drivers are installed start up Odin uncheck the f.rest time box and click the AP section and then select the recovery file provided by Sir Arco in the root thread.
If you need more help please ask, If it worked then still reply

Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.

Whosat said:
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Click to expand...
Click to collapse
Thanks for the response. Yeah, I kind of realized that's what's happening. I've managed to boot into the custom recovery right after the flash and did what I had to do in there, but then after I reboot the phone again, the custom recovery is gone. Is there a way to stop stock recovery being reflashed automatically?
Also, if I want to install a custom kernel, how can I backup the current one so that I can restore it at a later date if I need to? I know how to do this on HTC phones but it all seems to be a bit different on Samsung and I don't want to mess up anything.

How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.

Whosat said:
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Click to expand...
Click to collapse
Umm... yeah, I think it did ask but I just accidentally pressed no before reading what it said... So I guess I'll just have to flash the recovery again and then answer yes to that question.
Thanks

Yes that would be the correct way to do it.
Hope all goes well!

Stock recovery "vanished"

Hi all, after some modding it seems that my nexus 7 2013 lte custom recovery is vanished. I've tried to flash it via adb, I've flashed the new 5.1 official image, but nothing happen. Every time I try to boot into recovery mode, via adb or power+volume up, all I get is a dead android robot logo with no options.
And, btw, my N7 works perfectly
What can I do?
Thanks

When you flash a new android version you lose root and custom recovery, you need to root and flash custom recovery again as your currently on stock, when that robot is on his back you also have hold down a button combo to access the fastboot / bootloader or recovery, unless you send it the command via adb.
My advice is re-root using cfautoroot and flash custom recovery with flashify.

Ok, thanks! I've flashed twrp (I'm still no-root) and it works fine. Now is there any possibility to come back on stock recovery?

Flashify premium allows you to download and flash stock recovery or bootloader,
if you can't afford it or there not available for dl yet you can alternatively extract the .img files
from the factory image and flash them instead.

Q8-V08 said:
Flashify premium allows you to download and flash stock recovery or bootloader,
if you can't afford it or there not available for dl yet you can alternatively extract the .img files
from the factory image and flash them instead.
Click to expand...
Click to collapse
Nothing to do. I've extracted the img file from the factory image and flashed it via fastboot but, when I restart the device in recovery mode, it still shows the green half dead androidbot

^Thats normal. When you get to that screen you have to press volume up, down and power all at the same time, all three buttons. Just keep pressing them all at once a few times and it'll let you into stock recovery. It took me about 10 minutes to get in the first time. Don't hold the buttons, a quick press.

yosmokinman said:
^Thats normal. When you get to that screen you have to press volume up, down and power all at the same time, all three buttons. Just keep pressing them all at once a few times and it'll let you into stock recovery. It took me about 10 minutes to get in the first time. Don't hold the buttons, a quick press.
Click to expand...
Click to collapse
So you're saying that normally, on a Nexus 7 with no root and with stock recovery, the combination key to enter in the recovery isn't power+volume up ? Sorry for repeating, but I'm new at modding

I'm saying when you boot into recovery and it gives you the dead android (on it's back I think?) do what I said above.

yosmokinman said:
I'm saying when you boot into recovery and it gives you the dead android (on it's back I think?) do what I said above.
Click to expand...
Click to collapse
Done Thank you all!

Yeah it's pita to press, it's why I prefer to launch recovery from flashify or quick boot it's so much easier.
Android seems to love doing things arsed about faced / over complicated it should just be an option in settings, power off like
custom roms along with wireless adb.