Droid 2 Cyanogenmod stuck at M logo - Droid 2 General

Not sure if this should be in general, so apoligies if I'm in the worng place... Anyway, I was running the first Cyanogenmod nightly and tried to update to the latest. After updating, the phone stuck at the M logo. I can't get into clockwork but can get into stock recovery.
I can sbf, reroot, reinstall gingerbread, and it works fine. whenever I apply the latest cyanogenmod nightly I get stuck on the M logo.
Each time, after sbf I'm doing factory rest and wiping cache at each step. Works right up to the CM part. I also tried sbf, then OTA update, then the CM nightly, same result.
Looking for suggestions on other things to try... I really want to get CM working on this phone again, because I can't stand the stock!!

If you install CM and it boots back up and gets stuck, try going to stock recovery and doing a wipe data and cache and it should boot into CM.

When you install the CM7, make sure the FIRST TIME you are about to boot into CM7 you do a full data/factory reset (with bootloader) not stock, because it will bootloot every time if it tries to boot with the gingerbread settings, and after the first try, i couldnt get factory resets to work from the stock recovery.

droid2master said:
When you install the CM7, make sure the FIRST TIME you are about to boot into CM7 you do a full data/factory reset (with bootloader) not stock, because it will bootloot every time if it tries to boot with the gingerbread settings, and after the first try, i couldnt get factory resets to work from the stock recovery.
Click to expand...
Click to collapse
This happened to me. I'm trying to do this for a friends phone and I am a little unfamiliar with Motorola because I have an EVO. Could you describe the steps for doing a full/data factory reset with bootloader?

The nightlies must be screwed up or something cause I'm having the exact same problem. I can SBF, flash the pre-rooted Gingerbread, and install the bootstrap Clockwork Recovery, but as soon as I flash one of the later nightlies, it's stuck at the Motorola logo with no where to go. Data wipe using stock recovery after words doesn't help at all.
Will be SBF'ing, and re-flashing, then will wipe data and cache while still in Clockwork Recovery and I will report back if this works.

my does the same, I flash back to stock 2.2, OTA to Gingerbread, root using droid 3, install the clockmod recovery, wipe, format, clear cache, install CM7, again wipe, format and clear cache, now it is stuck on M logo. factory recovery won't even give me the option of wipe and clear cache option. Looks like I am going back to stock again without CM7.
My mistake, I've downloaded the wrong kernel, you must get GB CM7 or it will loop.

sangweb said:
my does the same, I flash back to stock 2.2, OTA to Gingerbread, root using droid 3, install the clockmod recovery, wipe, format, clear cache, install CM7, again wipe, format and clear cache, now it is stuck on M logo. factory recovery won't even give me the option of wipe and clear cache option. Looks like I am going back to stock again without CM7. Avoid cm7 at all cost unless someone has a solution to fix this.
Click to expand...
Click to collapse
I'm assuming you guys are installing CM7 version for OTA GB. Simple mistake but I know it happens.

0vermind said:
The nightlies must be screwed up or something cause I'm having the exact same problem. I can SBF, flash the pre-rooted Gingerbread, and install the bootstrap Clockwork Recovery, but as soon as I flash one of the later nightlies, it's stuck at the Motorola logo with no where to go. Data wipe using stock recovery after words doesn't help at all.
Will be SBF'ing, and re-flashing, then will wipe data and cache while still in Clockwork Recovery and I will report back if this works.
Click to expand...
Click to collapse
This is true, dunno why CM Team is not updating the nightlies, I've tried everything, already SBFed to 2.2, updated to 2.3, rooted 2.3, wiped everything, flashed, no go, but boot loop.
I have managed to get earlier nightlies working b4 but it seems the latest nightlies are broken, can someone test them out???
Trust me, I've rooted enough phones to know what to do here (look at my sigs), these CM7.1 D2 nightlies DO NOT WORK!
The worst part about D2 is that you have to start from scratch once you end up in a boot loop, meaning you have to unroot back to 2.2 SBF, update to 2.3, then try flashing, a process that takes about 30 minutes. I've done it all day long yesterday and today, now trying to get some of the older nightlies to work.

i'm helping my co-worker put on CM for the first time and i got this same thing. i dont want to buy her a new phone. how do i fix this? im a long time htc user and so this is all new to me.

I used stock recovery, rebooted, still stuck. I'm having to sbf and I'm even having issues with that. Definitely gonna stick with Liberty until this gets sorted out now.

I Am Marino said:
I used stock recovery, rebooted, still stuck. I'm having to sbf and I'm even having issues with that. Definitely gonna stick with Liberty until this gets sorted out now.
Click to expand...
Click to collapse
I was having alot of issues from not reading and thinking that I had to be on the GB OTA.
I read somewhere that you are supposed to be on Verizon 2.3.20 with sbf then do a factory wipe. Afterwards you root with ADB. Then you use droid bootstrab 1.0.0.5 to install the nightly after factory wiping once more.
I kept thinking I had to be on the latest OTA and I would get stuck on the M every time. Then I ran into the cyanogenmod wiki for the droid2.. Now I am just stuck wondering about overclocking, but at least I have a working cm now

nadcicle said:
I was having alot of issues from not reading and thinking that I had to be on the GB OTA.
I read somewhere that you are supposed to be on Verizon 2.3.20 with sbf then do a factory wipe. Afterwards you root with ADB. Then you use droid bootstrab 1.0.0.5 to install the nightly after factory wiping once more.
I kept thinking I had to be on the latest OTA and I would get stuck on the M every time. Then I ran into the cyanogenmod wiki for the droid2.. Now I am just stuck wondering about overclocking, but at least I have a working cm now
Click to expand...
Click to collapse
After going with sbf nightmare after nightmare and having to buy a new battery, I finally got restored to stock and then rerooted, sticking with Liberty until I can easily flash CM like anything else without all the added steps.

Related

Bootloop with any custom ROM

I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
cdjadex said:
I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
Click to expand...
Click to collapse
Did you ever create a nand backup? If so, go back to it first and verify you don't have a hardware issue.
If you don't have a backup, search this forum for the Eris RUU and I'd go back to that and root using the newest method...basically start over from a working phone.
I do have a nand backup, I have been restoring when i leave work because my phone has to be working. It works fine with the OTA 2.1 that i had just rooted...
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Sjflowerhorn said:
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Click to expand...
Click to collapse
I had this same issue last night, though I kept repeating the Nexus-style boot screen (the "X" thing) over and over. I did a full data/dalvik wipe and everything came up just fine. I had this experience with two different CyanogenMod ports.

[Q] Bricked Phone, SBF, and Gingerbread

I bricked my phone while installing Jakebites Mod and was wondering what do I do next?? I was running the lastest CM7 GB nightly (112) and installed v12 jakebites mod and then my phone got stuck in a bootloop. I'm still not sure why my phone got stuck in a bootloop.
My phone settings said I was on Android 2.3.7. Which version do I SBF back to??
Also, the last nightly I was on was CM7 nightly 78, which was froyo. I wiped cache/dalvik and directly flashed 112 without any problems. I never did any OTA GB update or anything when I was on 2.3.340. Did I skip a crucial step??
deviations said:
I bricked my phone while installing Jakebites Mod and was wondering what do I do next?? I was running the lastest CM7 GB nightly (112) and installed v12 jakebites mod and then my phone got stuck in a bootloop. I'm still not sure why my phone got stuck in a bootloop.
My phone settings said I was on Android 2.3.7. Which version do I SBF back to??
Also, the last nightly I was on was CM7 nightly 78, which was froyo. I wiped cache/dalvik and directly flashed 112 without any problems. I never did any OTA GB update or anything when I was on 2.3.340. Did I skip a crucial step??
Click to expand...
Click to collapse
Did you wipe data/factory reset? If not do that first then wipe cache data partition, then dalvik.
Also sometimes you can go into a bootloop if you have your phone connected to a charger while installing a new rom and then unplug it. If you didn't do this then just try the above step.

[Q] question: infinite boot image with custom rom

I know it has been asked before, and I have searched the threads. reverting to stock is not a problem.
nexus 7 grouper when installing a custom rom (liquid smooth v2.9 specifically) I get stuck on the liquid boot image.
I have successfully installed v2.7 and am able to revert back to stock or custom.
after a data format, factory reset, and wiping all caches, installing the zip file from abd sideload, or directly from the device the new rom that has flashed will not get past the boot image. am I doing something wrong, or could I do something differently so that the new v2.9 boots up correctly?
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
thank you.
aircooledbusses said:
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
Click to expand...
Click to collapse
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
ameinild said:
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
Click to expand...
Click to collapse
I will keep trying. getting liquid to run on the fascinate was curious as well, but after a few flashes it took. I'll keep trying on the nexus.
Update: yes, persistence is the key. thanks
What I did was from v2.8 a factory reset, wipe cache and dalvik and flash from sideload
as expected it boot looped. manually booted into fastboot and flashed v2.9 again with only a cache and dalvik wipe.
this time it booted and I flashed gapps.
at the reboot I set up the rom to my liking and it seems to boot normally now.
aircooledbusses said:
at the reboot I set up the rom to my liking and it seems to boot normally now.
Click to expand...
Click to collapse
Yes, after it boots through the first time, I've only seen it boot normal from that point on.

[Q] Tried upgrading, now can't get to the home screen, I ruined the recovery.

I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Also relevant:
http://forum.xda-developers.com/showthread.php?p=48088388#post48088388
Achiron said:
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Click to expand...
Click to collapse
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
leandrolutz said:
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
Click to expand...
Click to collapse
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Achiron said:
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Click to expand...
Click to collapse
The defy doesn't really brick, because the bootloader is locked.
It may be no charge in the battery...
You need to use an external charger, or McGyver method, because the defy won't charge by the usb or wall charger...
After you make it, try RSD again, and choose the right SBF, from your carrier.
Hope it helps... gogogo defy :victory:

Nexus 4 Stuck at starting app when not on Stock

Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
wasa67 said:
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
Click to expand...
Click to collapse
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
blusydays said:
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
Click to expand...
Click to collapse
I did all that before, and it still didn't work.
I think your problems are related to flashing the recovery, did you try to revert back the the old one ?

Categories

Resources