i got a weird bootloop after installing cm7. I installed kernel then forgot to wipe user data and format. It got into bootloop. Then i reflashed kernel and re-installed rom wiping user data and full wipe. It boots to lockscreen, then shows bootanimation, then shows lockscreen, then again boot animation. I installed both kernel and rom again but problem still remains
I had the same thing with cm 7.1.0.2
Try 7.1.0.1, worked for me
Related
I just flashed the new CM7 ROM onto my Atrix. I was running the Dark Side ROM before the flash. I tried booting my phone up, it goes to the boot animation which runs for about 5 seconds, then reboots. Its cycled for 10 minutes. I pulled battery, reflashed, but the problem seems pretty persistent. Any Ideas?
it may be obvious but did you do the "3 wipes" before flashing CM7? also try "fastboot -w" if you've done wipes in recovery already before flashing
i am having a similar issue with the MOD 2 version of this rom, i was using my atrix with the hdmimirror.zip that i installed other than that the phone was just stock rooted, with an unlocked bootloader. now that i have flashed this rom ( doing all the necessary wipes and etc.) when i try to reboot i am stuck at the dual core screen. any thoughts?
Format the system partition, factory wipe/reset, wipe dalvik cache. Reboot into CWM and then go ahead and flash the ROM. That should hopefully make sure it's all clean before the install.
Hi,
I am starting from rooted stock with emmc CWM v5.0.2.8
As always before flashing any ROM I backup, wipe data/factory reset, and wipe dalvik cache.
I have tried flashing SlimBean, LiquidSmooth, CyanogenMod unofficial, and CyanogenMod nightly; all with the same result.
Cyanoboot comes up just fine, then it proceeds into the ROM boot animation, sometimes it displays the boot animation for a few seconds,freezes then loops, others it just loops.
I have tried flashing "flashable_fix_bootloop.zip"
I have also tried flashing from CWM 6.02.7 but that recovery for me is very laggy and cannot access sdcard
I am really confused I would love for my tablet to be on jellybean the stock B+N is terrible
Any help is much appreciatted,
thatsnailguy
You could always do what I describe in the topic that at this moment is right below yours. Not the most elegant, but almost fool proof! The CM10 I use is better than any 10.1 I have tried. Either way, it's better than stock.
thatsnailguy said:
Hi,
I am starting from rooted stock with emmc CWM v5.0.2.8
As always before flashing any ROM I backup, wipe data/factory reset, and wipe dalvik cache.
I have tried flashing SlimBean, LiquidSmooth, CyanogenMod unofficial, and CyanogenMod nightly; all with the same result.
Cyanoboot comes up just fine, then it proceeds into the ROM boot animation, sometimes it displays the boot animation for a few seconds,freezes then loops, others it just loops.
I have tried flashing "flashable_fix_bootloop.zip"
I have also tried flashing from CWM 6.02.7 but that recovery for me is very laggy and cannot access sdcard
...
Click to expand...
Click to collapse
To flash CM10 you need a newer version of CWM v6.x.y.z. See http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for more pointers.
If you still cannot boot past the boot-animation try flashing Succulent's fix flash_kernel_acclaim_30MAR2013_HD.zip at posted at http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/ (under the heading "Flash this if your NT doesn’t boot newer kernel").
Thank you apparently I downloaded a wrong version of a 6.x.x.x cwm its all working now.
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
hello,
have a problem with my galaxy s2:
just updated my s2 to the latest nightly of cyanogenmod "cm-10.2-20130921-NIGHTLY-i9100".
my old kernel was: dorimanx 9.34 + rootbox 4.2
after update it booted to cyanogenmod and worked for few minutes. then it showed some errors like "android.core.*" stopped working. after reboot it can´t even boot on recovery mode. download mode is still availabile, flashing to old kernel + firmware doesn´t help anything.
same probelm: no boot (stuck at bootscreen)
anyone has an idea what to do?
thanks in advice
Have you tried wiping data in recovery when it stuck in boot loop.
Also did you format system before you flashed cm 10.2
I got it to work fine on my S2. Played around on it for a few hours, got everything installed. Then bam, upon restart I get boot loop. Wiping cache/delvik didn't work. Various tutorials recommend repeating the install process and/or continuing to factory wipe until it works.
EDIT: I have repeated the process. Make sure that before you install CM/Gapps, you factory reset, wipe cache and delvik. Have reset the phone several times and it now works.
If you are installing a new ROM and it's stuck in a boot loop after rebooting in the custom ROM, when you do WIPE, tap FORMAT DATA before installing the new ROM. This has worked for me. Each time.