Related
i flashed deodexed gb last night and wanted to go back to the odexed rom today. it aborted the install when i flashed the original and now i cant flash either and it is stuck in a bootloop....ive tried wiping data a dozen times...i downloaded the rsdlite and the 2.3.2 but rsd is not recognizing my device. HELP!!!!
Nevermind . I didn't have my 64 bit drivers installed. Highly stressful
you should access the recovery menu : power button + x(keypad) hit the magniflying glass key or if it doesnt work hit both volume rockers.
and then choose wipe data/factory reset and cache too.
Then reboot
I have the same issue as you except that no matter how many times i wipe cache/data in stock recovery i'm still stuck in a bootloop.
I did install gb prerooted and everything went smooth whereas when i installed the deodexed over it i'm now stuck forever in bootloop despite how many times i access and clear cache/ data in stock recovery. Any ideas?
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.
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.
Hello
I fear my defy is bricked :/
I installed Wakjiui stable (GB) to test it then wanted to go back to stock SBF so flashed it using RSD Lite and now my phone bootloops. Could it be that Wakjiui installed a custom kernel and it was not possible to revert to a Froyo kernel?
Do someone have an idea how I could get my defy to boot again?
Wipe data in stock recovery, power off the phone, and press power + voldown until you see a exclamation sign, then press volup + voldown, and select wipe data, wait until it finish, and reboot
That worked, thanks a lot
Hi,
I come with a maybe unusual problem. Every other rom works with me Defy (T-mobile) except the CMX by Quarx. I tried different versions (6-8), and all of them give this:
-Wipe factory, cache, dalvik
-Install CM10, Gapps
-Reboot
-Phone hangs with black screen with the red led (which is normal at 2nd boot right?)
After that, if I want to downgrade to CM9, or CM7.2 I can't wipe dalvik cache. When I click on the option in CWM, it does not give me the no no no no yes no no options. Nothing happens. The screen refreshes itself like I just entered the advanced menu in CWM. I have to restore Éclair, than go to Froyo, then to Gingerbread etc. with RSD lite, then reroot, all of the stuff to get my phone working after this. I've got tired of this, and i don't know why this bug happens. I followed the instructions well -as far as i know-. I tried to install it from CM7.2, and from CM9.
The strange thing is, if it means something: It looks like my phone is losing permission for system (?), because if i try to revert back from CM10 to CM9, and reboot, it gives: Error. Encryption unsuccessful for CM9, and CM7 does not even boot. If i reboot to CWM, I can't wipe dalvik cache again. What could cause the glitch in not being able to wipe dalvik cache?
My previous CM7.2 is Euroskank gigglebread, which is a pretty good ROM.
BAYER camera, MB525.
gyorgyszemok said:
Hi,
I come with a maybe unusual problem. Every other rom works with me Defy (T-mobile) except the CMX by Quarx. I tried different versions (6-8), and all of them give this:
-Wipe factory, cache, dalvik
-Install CM10, Gapps
-Reboot
-Phone hangs with black screen with the red led (which is normal at 2nd boot right?)
After that, if I want to downgrade to CM9, or CM7.2 I can't wipe dalvik cache. When I click on the option in CWM, it does not give me the no no no no yes no no options. Nothing happens. The screen refreshes itself like I just entered the advanced menu in CWM. I have to restore Éclair, than go to Froyo, then to Gingerbread etc. with RSD lite, then reroot, all of the stuff to get my phone working after this. I've got tired of this, and i don't know why this bug happens. I followed the instructions well -as far as i know-. I tried to install it from CM7.2, and from CM9.
The strange thing is, if it means something: It looks like my phone is losing permission for system (?), because if i try to revert back from CM10 to CM9, and reboot, it gives: Error. Encryption unsuccessful for CM9, and CM7 does not even boot. If i reboot to CWM, I can't wipe dalvik cache again. What could cause the glitch in not being able to wipe dalvik cache?
My previous CM7.2 is Euroskank gigglebread, which is a pretty good ROM.
BAYER camera, MB525.
Click to expand...
Click to collapse
Hi Buddy,
I had the same problem while trying CM10, The only solution worked for me is to flash back to Stock ROM. Once you have the stock ROM back.. You can root it again.. with CM7 or 9..
I should work.. as It worked for me.. I am on CM9 on my moto defy plus
Cheers
Smit
Because no one can count what you has done in the device I suggest to start from beginning and in correct order. (flash sbf., root, install 2ndinit....
gyorgyszemok said:
Hi,
I come with a maybe unusual problem. Every other rom works with me Defy (T-mobile) except the CMX by Quarx. I tried different versions (6-8), and all of them give this:
-Wipe factory, cache, dalvik
-Install CM10, Gapps
-Reboot
-Phone hangs with black screen with the red led (which is normal at 2nd boot right?)
After that, if I want to downgrade to CM9, or CM7.2 I can't wipe dalvik cache. When I click on the option in CWM, it does not give me the no no no no yes no no options. Nothing happens. The screen refreshes itself like I just entered the advanced menu in CWM. I have to restore Éclair, than go to Froyo, then to Gingerbread etc. with RSD lite, then reroot, all of the stuff to get my phone working after this. I've got tired of this, and i don't know why this bug happens. I followed the instructions well -as far as i know-. I tried to install it from CM7.2, and from CM9.
The strange thing is, if it means something: It looks like my phone is losing permission for system (?), because if i try to revert back from CM10 to CM9, and reboot, it gives: Error. Encryption unsuccessful for CM9, and CM7 does not even boot. If i reboot to CWM, I can't wipe dalvik cache again. What could cause the glitch in not being able to wipe dalvik cache?
My previous CM7.2 is Euroskank gigglebread, which is a pretty good ROM.
BAYER camera, MB525.
Click to expand...
Click to collapse
Why do u flash eclair?..start from froyo 2.2 deblur sbf...
nilesg19 said:
Why do u flash eclair?..start from froyo 2.2 deblur sbf...
Click to expand...
Click to collapse
I flash Éclair when all fails, because if I flash Froyo with RSDLite over any newer ROM then Gingerbread the device goes bootloop and the rsdlite can't repair it, but with Éclair I can.. I'm still waiting for some answer about why can't I just simply flash CM10 over CM7 or CM9? Why does it gives me bootloop and red led freeze? It also loses permission to wipe dalvik cache, which, imo is a very important information, and someone probably knows why, but I don't..
So, Questions are here:
-Is it connected to BL version? (The redled freeze/bootloop with 2nd-boot CM10 only)
-How do I check BL version? (Now i have CM9 Epsylon, if it matters)
-How come the phone freezes on red led (2nd-boot) and restarts, when I had no problem installing any other ROM?
-What can cause 2nd-boot not to work?
-How can I roll back to Éclair, but not Froyo/ICS (stock froyo flash with RSD Lite -> gives bootloop, CM7 won't start/CM9 Encryption unsuccesful)
Notes:
-After failed CM10 installation I can't wipe Dalvik cache, reinstalling ( without flashing Éclair -> Froyo -> GB -> root etc.and CM7/CM9.) CM9 gives the "Encryption unsuccesful" error, CM7 won't start (ever), I still can't wipe Dalvik!
-Every other GB, ICS ROM except CM10 (JB) works perfectly fine
-I can only repair it with starting all over again from Éclair (an issue with something about you can't rollback from GB to Froyo cancels other options)
---
edit: no ideas so far?