Develop Bugs

Stuck on boot animation after flashing rom

Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!

Flash the stock ROM on the phone. You have access to recovery so use it then after you verify you can boot with the stock ROM then try flashing another ROM on again.
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
No idea what caused you from being able to boot to this issue but this is my advice.

by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
Click to expand...
Click to collapse
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it

polish_pat said:
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
Click to expand...
Click to collapse
Go into cwm, do a wipe and also go into advanced and wipe dalvik. You should then be able to reflash your custom rom to fix your boot loop. If thats successful then go back to cwm and make a NANDROID backup so they have a restore point if anything goes wrong in the future.
If you want to flash back to stock its quite simple and can all be done from my ToolKit. Its basically going to http://code.google.com/android/nexus/images.html and downloading the latest factory rom for your model, moving it to the correct folder in the ToolKit and then selecting option 8 from the ToolKit to extract the images and flash it.
Mark.

polish_pat said:
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Click to expand...
Click to collapse
I've run into the same issue tonight going back to Apex 1.0.2 from the 4.0.4 leak. I'm trying the suggestion below to wipe and re-flash the ROM. I'll report back when I'm finished.
Edit: Yep, it worked!

[Q] Help, won't boot any custom roms.

After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant

Did you wipe data and cache when you flashed the new rom?

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM

cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you

chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik

nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.

Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app

[Q] T-Mobile SGH-T989 won't Shutdown/restart

I have a T-Mobile Galaxy S2 That i have rooted and still running the stock rom vers. 4.0.4. Everything runs fine except the ability to restart or shutdown the phone.For some reason it gets stuck on the pink goodbye screen. Also i have tried to flash different roms only to get a boot loop. The only way i can get the phone to start is to restore a old backup. Sorry for being such a noob.thanks for any help!

you have to un-root and then upgrade to the latest firmware 4.1.2 then re-root/..... the 4.0.4 had some bug when you root it wont shut down and they never fixed it from what i can tell

krazierokz said:
you have to un-root and then upgrade to the latest firmware 4.1.2 then re-root/..... the 4.0.4 had some bug when you root it wont shut down and they never fixed it from what i can tell
Click to expand...
Click to collapse
Thanks man! I really appreciate the help!

no problem man and if kies fails on you might have to take the odin approach all these tmobile firmwares that came out for this phone have all been buggy or glitchy and off course they have done nothing about it so good luck

No...the problem is not from ICS 4.04..Something is corrupted around your system or data partition...That happened to me after I used dark side wipe and restored an old nandroid backup...I had to odin to stock and that fixed it...
In your case, Odin the JB stock UVMC6 , after you reboot, boot into recovery then do factory reset .

[Q] [SOLVED] T-Mobile Samsung Galaxy S4 (SGH-M919) Soft-bricked

Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!

I would suggest going all the way back stock on stock firmware via Odin. Then re-root, TWRP, and re-download the rom of your choice. Dont restore the backup. Just start fresh.
I Think My S4 Is Insane
SICK MADE DEVELOPMENT

alloycowboy said:
I would suggest going all the way back stock on stock firmware via Odin
Click to expand...
Click to collapse
Thanks for the reply.
And okay, I tried that.
I flashed stock using the T-Mobile ROM I found here: galaxys4root_(dot)_com/galaxy-s4-stock-firmware/
This is the same ROM file I used to completely restore the phone I had to return, and that worked fine.
But it still won't boot up or go into recovery mode (just shows the Samsung logo for a split second before shutting down).
One thing I did do on the other phone was flash a kernel which had set-MUID to off so I could WiFi tether, but I thought flashing the stock ROM would revert that back as well. Do you think that's the reason it messed up so badly? I restored the backup from the other phone with a different kernel? Right after I restored the backup to the new phone and everything was working, I remember checking the kernel info in the About Phone section of the settings, and it was in fact the kernel I'd installed on the other phone.
TLDR: Tried flashing stock ROM to no avail. Download mode still works but can't enter recovery mode or boot.

Are you doing a factory reset after flashing stock firmware?
I Think My S4 Is Insane
SICK MADE DEVELOPMENT

I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Sent from my SGH-M919 using xda app-developers app

alloycowboy said:
Are you doing a factory reset after flashing stock firmware?
Click to expand...
Click to collapse
Yeah, as soon as it finished installing I went into stock recovery and did a factory reset.
Karakoram2 said:
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Click to expand...
Click to collapse
Alright, I'll try that.
Is the konane tar an actual ROM? And what do you mean in the stickies?
Sorry, not very familiar with XDA forums.

Samsung GT-I9500 flashes n switches off!
BallisticallySimilar said:
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
Click to expand...
Click to collapse
The same thing has happened to me! Did you find any solustion for this?? Please help!! This was my first attempt and i have no idea wats going on!

Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Sent from my SGH-M919 using XDA Premium 4 mobile app

What I did to unbrick my T-Mobile S4 (SGH-M919)
killerwolf2121 said:
The same thing has happened to me!
Did you find any solutions for this? Please help if you can; this was my first attempt and I have to idea what's going on.
Click to expand...
Click to collapse
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Android_Monsters said:
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Click to expand...
Click to collapse
Thanks

BallisticallySimilar said:
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Thanks
Click to expand...
Click to collapse
I am on 4.3 and yes, flashing the stock rom worked for me too! relief thanks a ton!

Having trouble unbricking M919 T-Mobile
Hi, I'm trying to unbrick my M919 through Odin. I have all the updated software, but I keep getting a fail message. Any help would be appreciated.

[Q] URGENT - Recent 4.4 update boot-looped my phone

Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner

JaedenRuiner said:
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
Click to expand...
Click to collapse
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).

lvpre said:
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
Click to expand...
Click to collapse
I eventually found a 4.4.2 full stock ROM and was able to get that over. Of course this wasn't until after some sight suggested a wipe user data could help, so I'm re-building the phone from the base...*sigh* It happens. I'm about due for an upgrade anyway, so I can make due.
Thanks for the response,
J"SD"a'RR