Develop Bugs

Cyanogen Mod Boot Screen loop

I just used Unrevoked 3.2.1 and now installed Cyanogen 6.0.2. Now my phone just loops the Cyanogen boot screen over and over and over. Been doing this for about 15 minutes. What do?!?

install a different rom

kthx I already fixed it

How did you fix it, I am having the same issue and not sure what to do ..

i just had the same problem and fixed it by having to wipe all the data and cache, rebooted, at first it started blue looping but before i knew it, it went straight into the OS and worked.

derized said:
i just had the same problem and fixed it by having to wipe all the data and cache, rebooted, at first it started blue looping but before i knew it, it went straight into the OS and worked.
Click to expand...
Click to collapse
im having the same issue the only problem is when i went to clockwork restore back up i accidently clicked back up so it backed up the bad flash and now when i restore i get the splash screen loop over and over.... help

IamaNoobsickle said:
im having the same issue the only problem is when i went to clockwork restore back up i accidently clicked back up so it backed up the bad flash and now when i restore i get the splash screen loop over and over.... help
Click to expand...
Click to collapse
Boot back into recovery and use the old backup you intended on using initially. That should hopefully fix it.
Sent from my Droid Incredible running some random CM7 nightly.

Please Help! Able to flash roms in cwm but still getting a boot loop!

I use the gsm gnex and recently tried to change my boot animation so i put it in my data/local folder using root explorer. I then rebooted my phone to see it and it look really great. I wanted to try out another one so i copied another bootanimation.zip but then thought that the one i just tried was better so i didn't paste it. I then rebooted my phone to see it again but then i got stuck in a boot loop where it went halfway into the animation and then just rebooted. I was able to get into cwm so i formatted data, cache, system and wiped my dalvik cache, then I flashed my current rom (cm9 nightlies). I got the same problem when i booted back up again, so i tried restoring my nandroid. When i was restoring it stopped and said "Error when restoring data!". This happens every time i try to restore. I do not know how to use adb or fastboot and am wondering if there is a way to fix it with cwm. I have a locked boot loader but i have root and am able to flash roms through cwm. Please Help!

This happened to me recently, and the only way to fix it was to flash the factory images.

Sorry for being a noob but how do you do that?

Phone seems jacked, need help please..

I cannot get past the bootanimation screen. This just happened this morning out of the blue. It's been rooted since Dec, and been running fine since. I can get to recovery, but it just reboots and hangs from there on it's own. I'm using AOKP MS2, and FrancoKernel, which probably doesn't matter, but I just need to get this at least back to stock. What do you guys suggest? I have done a battery pull, entered recovery through fastboot, but it just won't boot up.

Since you can access recovery, just restore a nandroid backup. That will get your phone up and running again.

lonnyrs said:
I cannot get past the bootanimation screen. This just happened this morning out of the blue. It's been rooted since Dec, and been running fine since. I can get to recovery, but it just reboots and hangs from there on it's own. I'm using AOKP MS2, and FrancoKernel, which probably doesn't matter, but I just need to get this at least back to stock. What do you guys suggest? I have done a battery pull, entered recovery through fastboot, but it just won't boot up.
Click to expand...
Click to collapse
If you have a nandroid then flash that, if not you will have to wipe cache, system,dalvik and data and flash the rom again.
That should solve your problems.
Maybe try just wiping cache, dalvik and system and leave data alone and flash the rom again. That way all your apps etc will still be there.
If you get bootloops after that then full wipe and flash.

Can aokp m4 be flashed via fastboot? Not sure this is possible , anyone ever fastboot a custom rom? Or push it with fastboot and then flash it in cwm?
¢ £®0π π€XU$ |||

[Q] Help! flashed cyanogenmod, bootlooping

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

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!