Well I flashed CM9 RC2 on my T-Mobile S2, running ICS 4.0.3, after it finished installing, it booted up. It's been sitting on the boot animation for about ten minutes.
I flashed it via Rom Manager, downloaded the RC2 version of CM9 as well as the ics gapps, then it went into recovery mode and it did itself.
How long is it supposed to take on first boot? Or is my phone bricked.
arseny87 said:
Well I flashed CM9 RC2 on my T-Mobile S2, running ICS 4.0.3, after it finished installing, it booted up. It's been sitting on the boot animation for about ten minutes.
I flashed it via Rom Manager, downloaded the RC2 version of CM9 as well as the ics gapps, then it went into recovery mode and it did itself.
How long is it supposed to take on first boot? Or is my phone bricked.
Click to expand...
Click to collapse
if you can get to the boot animation, it's not bricked. try to reboot into recovery again, wipe data, cache, and dalvik cache, install CM9 again, and reboot.
He's right, but overall, post in the correct forum next time for better results and it's just good for everyone else lol. I clicked on this solely cause I saw Release Candidate, I was like no way!?!?! Haha
Related
I just flashed a fresh cm7 rc4, along with gapps, and zendroid kernel (avs i think i'm not sure which one).
Things were working great. I was using the phone, had just installed widget locker, and then tried to plug my phone into the computer.
Thats when the trouble started. For some reason, usb debugging worked, even the wireless tether worked, but I could not get the sd card to be on the computer, the option just never came up.
To fix the problem, I tried resetting the phone, but when I did so the phone became stufk on the cm7 boot animation for a few hours. What do I do?
I would just do a fresh install, but this is actually the third time that I have gotten stuck on the bootloading screen with cm7, so I just need to find a solution. Please help.
-AJ
Really need some help with this, guys...need my phone back
You're not alone. I installed GApps along with CM7. Stuck in Boot animation. My wife is pissed.
You posted in the wrong section. I will transfer this over to the EVO Q&A area.
I am assuming that you have your EVO rooted. If you are stuck in a bootloop, simply pull your battery, put it back in and press the power button while holding Vol Down. This will make you go into bootloader. From there, simply go into recovery, wipe everything, and reflash the rom. I have done CM7 and gapps and have no issue.
egzthunder1 said:
You posted in the wrong section. I will transfer this over to the EVO Q&A area.
I am assuming that you have your EVO rooted. If you are stuck in a bootloop, simply pull your battery, put it back in and press the power button while holding Vol Down. This will make you go into bootloader. From there, simply go into recovery, wipe everything, and reflash the rom. I have done CM7 and gapps and have no issue.
Click to expand...
Click to collapse
I did that, many times. One time, it just worked. Didn't do anything different as far as I know, but kind of makes me unsure about future flashes etc.
Pull your battery out, wipe data, cache, and dalvik cache in recovery. Flash ONLY CM7 and the google apps. I think the kernel might be the problem for the bootloop.
harryprk2x said:
Pull your battery out, wipe data, cache, and dalvik cache in recovery. Flash ONLY CM7 and the google apps. I think the kernel might be the problem for the bootloop.
Click to expand...
Click to collapse
I never wipe any of those things seperately, I just use calkulin's format all. That couldn't be the source of any problems right?? I mean, I always believed that that was the best way.
Thanks. I ended up doing that. All is better now.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
My problem was installing both at the same time.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
thenimboo said:
I never wipe any of those things seperately, I just use calkulin's format all. That couldn't be the source of any problems right?? I mean, I always believed that that was the best way.
Click to expand...
Click to collapse
I've used Caulkin's format all twice, and both times, I got stuck in the white screen boot loop and had to reflash Amon Ra, just to get back to recovery and flash one of my nandroids.
Wiping everything in recovery works perfectly fine for me.
I use Calk's format all at least a few times a week, sometimes a couple times a day. Always works fine.
Did you wipe?
Did you wipe the data/cache from the handset? if not do so through clockwork
So I must admit I am new to this. I am on a Samsung Galaxy Nexus (CDMA). I was running stock 4.0.2. Unlocked bootloader, rooted, and clockwork mod recovery.
I decided to flash my first custom ROM. I choose Android Open Kang Project - toro Milestone 3. I made a nandroid backup. I wiped data. First I did "wipe data/factory reset", then I did "wipe cache partition", and then finally I did "wipe dalvik cache". After that I pushed the aokp_toro_milestone-3.zip to the /sdcard/. After that I entered clockwork mod recovery and installed from zip. Installed successfully, then in recovery I was going to flash the aokp_gapps-ics-403-011312.zip and accidentally rebooted the system.
Well, it has been doing the team kang unicorn boot animation for about 40 minutes now. Is this normal? I read that it takes a long time for the first boot, but this seems excessive. Could it be because I accidentally skipped flashing the gapps? Should I reboot(adb reboot bootloader)? If I do that should I start from scratch(wipe data, re-flash ROM, flash gapps, flash kernel?, and then reboot device)? Or do I wait.
I would appreciate any advice/help!
I spoke with a friend, he said it was alright to reboot to the bootloader and start over. That is what I did. This time it booted up.
This thread can be deleted.
On past Androids I have owned I have seen dif ROMs that actually say you need to pull battery, flash twice, etc.. Not trying to say that's normal procedure, just saying it happens from time to time. You did good to wait and see though! First start can take a while sometimes, you don't want to do a premature bat pull. Glad you got it working.
I flashed the latest Axiom and everything was fine. Did a reboot and it just sat on the boot animation for a while. Like, 15 minutes. So I did a battery pull and tried to boot again. No go. Pulled the battery and went into CWM, wiped data/cache/dalvik and formatted /system then re-flashed the ROM. Stuck again. Went BACK into CWM, wiped/formatted, and installed Liquid (which worked before). STILL can't get past the boot animation. Tried to restore a Nandroid and got an error.
I'm in a bit of a panic mode here because I have no idea what to do.
Relax bootloops aint a major problem really, i suggest you go to cwm and wipe all, or try and testore a backup, if all else fails just go back to stock using a toolkit, re root and flash a rom
Sent from my Galaxy Nexus using xda premium
SomeGuyDude said:
I flashed the latest Axiom and everything was fine. Did a reboot and it just sat on the boot animation for a while. Like, 15 minutes. So I did a battery pull and tried to boot again. No go. Pulled the battery and went into CWM, wiped data/cache/dalvik and formatted /system then re-flashed the ROM. Stuck again. Went BACK into CWM, wiped/formatted, and installed Liquid (which worked before). STILL can't get past the boot animation. Tried to restore a Nandroid and got an error.
I'm in a bit of a panic mode here because I have no idea what to do.
Click to expand...
Click to collapse
Do this.
okay, i was trying to root and flash cyanogenmod9 on to my friends s2. i personally have a droid x, that has been flashed a billion times, so i had a good idea of what to do. i rooted his phone using odin to flash clockwork, then flashed superuser in clockwork. after confirming i had root i booted into clockwork, and wiped cache and data. then flashed the hercules.zip and gapps. here's where things get tricky. his power button is broken and everytime i tried to reboot it couldn't because the power button was constantly pressed. eventually he got it to boot, but it never booted up completely, it just stayed on the boot animation. my question is did i do something wrong? do you guys thinks its because of the button since it couldn't have a fresh boot up. should i try flashing another rom to see if that works? any ideas?
I ran across this problem when I was flashing a Jellybean version of Cyanogenmod. If you flashed it on a NON-TOUCH recovery it will most likely boot loop like mine did. I installed a touch recovery and flashed and BANG. I had had Cyanogenmod. Hope this helped
This was my fix...
dj923 said:
okay, i was trying to root and flash cyanogenmod9 on to my friends s2. i personally have a droid x, that has been flashed a billion times, so i had a good idea of what to do. i rooted his phone using odin to flash clockwork, then flashed superuser in clockwork. after confirming i had root i booted into clockwork, and wiped cache and data. then flashed the hercules.zip and gapps. here's where things get tricky. his power button is broken and everytime i tried to reboot it couldn't because the power button was constantly pressed. eventually he got it to boot, but it never booted up completely, it just stayed on the boot animation. my question is did i do something wrong? do you guys thinks its because of the button since it couldn't have a fresh boot up. should i try flashing another rom to see if that works? any ideas?
Click to expand...
Click to collapse
If it is the CM9 bootloop issue (where it hangs at the little blue dude) check out this page (sorry it won't let me insert a link because I'm a new user lol):
forum.cyanogenmod.com/topic/59357-cm9-boot-loop-issues-my-solution/
I couldn't get it to work until I followed this method, likely the use of Darkside Super Wipe and Darkside Cache Wipe was what fixed it. Hope this helps.
OOOhhh this happened to me when i first rooted my phone LOOOL......this is what u do....
if you are on cwm 5.0.2.7 or lower...u need to use darkside super wipe then flash the rom
i did the darkside wipe and it booted up fine. thanks a lot guys!
if cant be fixed flash stock. it happened to me once too. i think it was because i flashed the wrong radio
Greetings!
I've had my S2 for a few months now, and have been running PA 2.11 since the begging of September. So I've decided to upgrade to the latest and greatest, and everything I flash a new rom, I get stuck in a boot loop. I've tried the latest PA, PAC, LiquidSmooth, All-Star and slim bean. Each time, boot loop. I'm using the latest CMR. Current kernel is Cyanogen 3.0.42. My process is essentially factory wipe, system wipe, clear caches, flash rom, clear caches, reboot, wait 10-20min, reboot, wait an additional 10 min, reboot again. I go back and forth between factory wipe and Darkside Super Wipe, seeing if anything makes a difference, and so far, regardless of my process, I keep getting boot loops. I always follow the flashing instructions the first couple times, then try other options, but keep getting these damn boot loops. Thoughts? Your assistance is much appreciated..
dr_destructo said:
Greetings!
I've had my S2 for a few months now, and have been running PA 2.11 since the begging of September. So I've decided to upgrade to the latest and greatest, and everything I flash a new rom, I get stuck in a boot loop. I've tried the latest PA, PAC, LiquidSmooth, All-Star and slim bean. Each time, boot loop. I'm using the latest CMR. Current kernel is Cyanogen 3.0.42. My process is essentially factory wipe, system wipe, clear caches, flash rom, clear caches, reboot, wait 10-20min, reboot, wait an additional 10 min, reboot again. I go back and forth between factory wipe and Darkside Super Wipe, seeing if anything makes a difference, and so far, regardless of my process, I keep getting boot loops. I always follow the flashing instructions the first couple times, then try other options, but keep getting these damn boot loops. Thoughts? Your assistance is much appreciated..
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
suaverc118 said:
What recovery are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I was using 5.x, but after quite a few boot loop flashes, I upgraded to the latest and greatest with no effect on the outcome.
You're doing way too much. Here:
http://forum.xda-developers.com/showthread.php?p=32532260
That's my thread on how to properly wipe before ROM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
So, don't know what the initial issue was with flashing the new ROM, but I took CWR 6.X off and put on 5.0.26 and got All-Stars up and running in no time. Thank you for your help!