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!

s5660M reflashing stock error

Hi guys, first of all there were similar posts, but couldn't find anything that looked like my problem
Im currently running CM 7.2-GIO-KANG [Update: February 13, 2012]...and CWM 5.2.0.7
Let me tell you how i ended up with this version
I bought my phone..flashed it with Darkshados rooted rom V2...then i used simply gio for a while..after which I upgrade to gio pro 1.3...and gio pro 1.4...after which i switched to CM 7.2.
Ive been told that this version shouldn't have any WiFi problems..but when my phone is screen locked for a while..the WiFi shuts off...and reactivate when I unlock it....this is pain..cause i use whats app...and if the WiFi isn't on when its locked...i don't get my messages.
SO i thought maybe...its because my model firmwear changed or something...and decided to flash back to stock...and install CM 7.2 form stock.
I had reason to believe this because...my phone also registered my netwrok provider as BELL...but im actualy with VIRGIN(Altho virgin uses bells network)...the previous roms didn't do this and showed virgin.
So i decided to go to downloading mode...and re flash to Stock V2 for the s5660M. And as expected I got a bootloop. Following the instruction for the bootloop fix..i went into stock recovery, installed CWM again...and wipe data..mounted partitions..and then installed arpegio..just to check..but i keep getting stuck on the boot screen every time. finally i used CWM to restore a CM 7.2 backup i made..and managed to get that working.
Anyone have any ideas to why i cant flash stock and another rom anymore
Please and Thank you^^

Flash stock rooted by darkshado with Odin. then go to stock recovery and wipe data, then r restart and wait for boot. Don't install cwm yet.
Sent from my GT-S5660 using XDA App

Ok Ill try that thnx

Thanks it worked XD

wasa67 said:
Thanks it worked XD
Click to expand...
Click to collapse
no problem. I have the exact phone and situation as you, so if you need help just let me know.

I think i did something stupid...

Well its been a while since I have modded this phone. I had turned it back to stock to wait for ics and I used the odin method and it worked fine. But then two days ago I wanted to try some of the new ICS roms out so I rerooted and installed the darkside ics rom and it was good but then today I see there is an update with some important patches so I decided to go ahead and update. So I pulled the odin file in the ICS thread to update but I did not wipe and go back to GB and now it installed and passed fine but the phone is not working at all. It powers on and gets to the start screen but when I press the android to get started it gives me a force close for the android services and framework. I have tried both of the odin files that I have one was the first update to 2.3.6 and the other is the newset update with the patches. But I know that the first one the original update is good because I used it a month ago to put the phone back to stock. So does anyone have any ideas? I am thinking of tring to reinstall CWM via odin then flashing the superwipe then installing a stock GB rom then tring the odin methode again. if not then maybe the keis recovery mode I dont know I will let you guys throw out some suggestions first.

mojorisin7178 said:
Well its been a while since I have modded this phone. I had turned it back to stock to wait for ics and I used the odin method and it worked fine. But then two days ago I wanted to try some of the new ICS roms out so I rerooted and installed the darkside ics rom and it was good but then today I see there is an update with some important patches so I decided to go ahead and update. So I pulled the odin file in the ICS thread to update but I did not wipe and go back to GB and now it installed and passed fine but the phone is not working at all. It powers on and gets to the start screen but when I press the android to get started it gives me a force close for the android services and framework. I have tried both of the odin files that I have one was the first update to 2.3.6 and the other is the newset update with the patches. But I know that the first one the original update is good because I used it a month ago to put the phone back to stock. So does anyone have any ideas? I am thinking of tring to reinstall CWM via odin then flashing the superwipe then installing a stock GB rom then tring the odin methode again. if not then maybe the keis recovery mode I dont know I will let you guys throw out some suggestions first.
Click to expand...
Click to collapse
After flashing through Odin did you factory reset the phone? I believe it is a must when flashing back to GB via Odin from ics.
Sent from my SGH-T989 using xda premium

okay update I sucsessfully installed cwm through odin then I was able to superwipe and install good ol juggs 5.0 phone works fine now so the next step is to figure out why those odin packages did not work I guess I will redownload them and try again. Will keep this thread updated for anyone else having problems

No I did not factory reset because I could not get into the phone to do so althought I guess I could have just used the key combo to do it but I didnt even think of that. Anyway I am now back on a gb rom and I am trying again thanks for the info though.

Okay that was the problem. I guess if you want to odin back to a gb stock from ics you should install a gb rom first then run the odin package. Or if you forget then try the key combo for the factory reset. I dont know if that will definitly work but it makes sence. but the first thing i said is what worked for me. So now all is well I am now stock gb.ULVDE 2.3.6 with kernel 2.6.35.11 and that is how I will stay until the ics update comes out. Thanks for trying to help out

[Q] Potentially bricked play. Error installing rom in CWM

Hi. I tried installing the latest CM9 nightly and when my phone rebooted it was stuck at the FreeXperia logo. I rebooted the phone and tried to get into CWM recovery but couldn't. So I booted into fastboot and installed the boot image from this (I can't like to the rom but it is called cm-9.1.0-zeus.zip) rom. Now I can get into CWM recovery. When ever I try to install the rom I get an error message Status 7. This happens after it says "assert failed: getprop("ro.product.device") == "R800i" etc.
It looks like either my device name on my phone is wrong or the device name for the rom is wrong. I'm pretty sure the rom I downloaded is the right one though. I've installed roms before but never ran into an issue like this so I'm lost. Seeing as I can get in to CWM recovery I reckon I should be able to get it back working again. Would really appreciate some help here.
Cheers.

re flash stock

CyberScopes said:
re flash stock
Click to expand...
Click to collapse
Downloading flashtool now. Will report back if it works or not. Hopefully it does.

I'm back on stock SE 2.3.3 rom now. Thanks a million, CyberScopes.

I guess I spoke too soon. It seemed like it was working fine with the stock rom. I went to put CM9 on it and everything worked fine apart from it not recognising the baseband. I put on the stock rom again and now it just keeps rebooting. *sigh*

AlmightyCushion said:
I guess I spoke too soon. It seemed like it was working fine with the stock rom. I went to put CM9 on it and everything worked fine apart from it not recognising the baseband. I put on the stock rom again and now it just keeps rebooting. *sigh*
Click to expand...
Click to collapse
Make sure you now have a compatible kernel and ROM.

Also make sure you have the recommended basebrand. I use .64
Sent from my Xperia Play using xda app-developers app

OK, I'm back on stock and the baseband is recognised. The guide I have been using for installing CM9 is this one (http://forum.xda-developers.com/showthread.php?t=1600833&highlight=cm9+guide). Is there something missing from that guide. I've never had to check if the kernel and rom were compatible. When using fastboot, I use the boot.img from the rom I download.

Flash kernel using flashtool.
Remember to do complete internal wipe and cache wipe.

I figured out why baseband wasn't working on CM the first time. It turns out that the stock rom I was using was an old one and the baseband for that wasn't working on CyanogenMod. I downloaded a newer one, installed that and then stuck CM9 on it and everything is working fine. Phew. Thanks again for the help. Really appreciate it.

Ure welcome. Im glad i helped u.
Sent from my R800i using xda app-developers app

[Q] Android 4.3 hanging on boot

I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.

danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.

captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?

danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers

danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).

I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app

I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???

Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).