I've been trying to upgrade from CM 7.2 to CM 10.{0,1,2}, but my phone keeps getting stuck with the red LED after the Motorola. My understanding is that this means that there is not a viable OS installed. When I flash the appropriate zip the recovery is updated (e.g., TWRP 2.5.0 is installed with CM 10.1). I've tried wiping cache, data, Dalvik cache before and after install, but it doesn't help.
Can anyone suggest what might be happening?
Here's the full story:
I've been running CM 7.2 for a long time and it's been great and stable. But, I saw that CM 10.2 was available a while ago and wanted to give it a try. I originally tried flashing straight to CM 10.2 from CM 7.2 but the installation aborted (status(0)). I posted on the CM 10.2 thread and _mak_V_ suggested that I needed to install TWRP or go through 10.1 first.
I installed Defy TWRP version 2.1.1 from the TeamWin webpage, but was still unable to install CM 10.2. Same problem, and I'm guessing that the recovery is still too old.
So, I decided to go through CM 10.1. I flashed this using TWRP 2.1.1 along with gapps-jb-20130812-signed.zip and the installation seemed to go smoothly. However, I was stuck at the red LED.
I reverted my TWRP backup to CM7.2 and then tried CM 10 with gapps-jb-20121011-signed.zip -- same thing.
To make sure I wasn't completely losing it I installed CM 9 which I tried before. This worked perfectly, but I still can't upgrade to CM10 or above.
Apologies if this question has been answered already. I'm sure that I'm missing something simple, but I've combed the Bravo and Defy threads and can't find anything to help. Can anyone suggest anything?
Thanks for your help!
still no answer?
sjbonner said:
I've been trying to upgrade from CM 7.2 to CM 10.{0,1,2}, but my phone keeps getting stuck with the red LED after the Motorola. My understanding is that this means that there is not a viable OS installed. When I flash the appropriate zip the recovery is updated (e.g., TWRP 2.5.0 is installed with CM 10.1). I've tried wiping cache, data, Dalvik cache before and after install, but it doesn't help.
Can anyone suggest what might be happening?
Here's the full story:
I've been running CM 7.2 for a long time and it's been great and stable. But, I saw that CM 10.2 was available a while ago and wanted to give it a try. I originally tried flashing straight to CM 10.2 from CM 7.2 but the installation aborted (status(0)). I posted on the CM 10.2 thread and _mak_V_ suggested that I needed to install TWRP or go through 10.1 first.
I installed Defy TWRP version 2.1.1 from the TeamWin webpage, but was still unable to install CM 10.2. Same problem, and I'm guessing that the recovery is still too old.
So, I decided to go through CM 10.1. I flashed this using TWRP 2.1.1 along with gapps-jb-20130812-signed.zip and the installation seemed to go smoothly. However, I was stuck at the red LED.
I reverted my TWRP backup to CM7.2 and then tried CM 10 with gapps-jb-20121011-signed.zip -- same thing.
To make sure I wasn't completely losing it I installed CM 9 which I tried before. This worked perfectly, but I still can't upgrade to CM10 or above.
Apologies if this question has been answered already. I'm sure that I'm missing something simple, but I've combed the Bravo and Defy threads and can't find anything to help. Can anyone suggest anything?
Thanks for your help!
Click to expand...
Click to collapse
Oc someone's going to tell you to use search or Google it but I'm not that person shortly I'm going to install cm10 on mine so I'll go through the steps and let you know what to do or might have happened I'll keep you posted.
just made the same mistake
Try updating the recovery and when you wipe you have to do it in ext3 if you want to revert to gingerbread and ext4 for jb as far as I know
Related
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...
Verizon VS980, TWRP 2.6.3.3
Finally, upgraded to the above TWRP, and was able to flash a CM 11 nightly. and Gapps for 4.3.0, 20130813 and to have that finally flash successfully is great! BUT it's not, when I boot into it I get an android system error and the keyboard AOSP error every time, I can't make it past the screen where I enter in my account.
I have wiped and tried again, and again, I have installed the ROM and gapps and then wiped dalvik and cache and same result...
It seems so close.
I have installed ROM Manager as well and it says that CWM is installed yet I cannot seem to boot into it, I have flashed it from the ROM Manager many times and no love. I was able to flash a zip of twrp, is there a zip of CWM that is flashable from twrp, I have heard that cwm works better with CM 11
Please help, I have no idea why going to CM 11 should be such a pain in the..
Thanks!!!
SO i figured it out
I was following/using rootz wiki for my reference of which gapps to use and it is not updated right now
got the right gapps here, and all is good now
http://d-h.st/mDt
Hey guys,
As I wrote in the title I ran into a problem when installing the new CM11 nightly build from Quarx on my Defy. Here's what I did:
1) Downloaded the recovery update: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
2) Downloaded this CM11 nightly build: http://quarx2k.ru/roms/defy-cm11.0/cm-11-20140501-NIGHTLY-mb526.zip
3) Rebooted into recovery and installed the recovery update. The install seems to have finished without problems, although after another reboot my recovery still read as "JB Recovery v5.7.0-jordan".
4) Did a data and cache wipe.
5) Tried installing CM11, but the installation was aborted by a "status 0" error right after the "installing update..." part.
What am I doing wrong? I assume this has something to do with the recovery update, but since as far as I can tell it was successfully installed I don't know what could I do to fix it.
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
MaicolS said:
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
Click to expand...
Click to collapse
I did restart my phone after installing the recovery update, I just forgot to mention it.
Since my last post I realized that the problem was that the CM10 nightly build I used before still came with the CWM recovery, not with TWRP. The reason is that some of Quarx's old builds didn't play nice with TWRP at the time. Since Quarx didn't explicitly say in his thread that the recovery update was for TWRP I just assumed that it was for his old builds that came with CWM. That doesn't seem to be the case however.
Chawitsch said:
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
Click to expand...
Click to collapse
Easier method: just flash defy_twrp_recovery_2.6.3.0.zip, as explained in the installation guide.
Thanks for the link Proverbs, I'll do that the next time I'll need to update TWRP. Like I said, I didn't realize that Quarx's recovery update was for TWRP. If I did, I would have flashed TWRP separately and then CM11. What matters is that everything turned out OK in the end.
I got bored today and decided to pull out the old N7, 2012 version. I update recovery to TWRP 2.8.7.0, installed CM 12.1, realized this tablet crawls with any version of Android other than shipped version, so I went and got CM 10 and GApps for JB, wiped and flashed them back on. I didn't see any errors when flashing them, but when rebooting after, it just boot loops. I see the Google logo with the unlocked icon at bottom, then reboot and back to Google/unlocked again. So I wipe and reflash cm12.1 and it's GApps and all boots and works fine, other than being slow. I'm assuming the recovery is the problem as I've run into something similar before on another device, but in that case, the recovery was too old and needed updated, but it makes sense that a recovery could be too new as well.
Am I correct that the recovery is the problem? If so, what should I run for CM 10 to flash and work?
Try cwm recovery
iwjosi said:
Try cwm recovery
Click to expand...
Click to collapse
I don't' know if it was using CWM or that I also tried CM 10.2 at the same time, but it's working now. On CyanogenMod's own page, there was no MD5 for CM10, but there was for CM10.2, so it's possible my copy of CM10 was a bad download. Either way, it's working now, so thank you good sir, or madam, or person on no specific gender.
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
matthewclso said:
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
Click to expand...
Click to collapse
you can...try this!
@halfdevil said:
you can...try this!
Click to expand...
Click to collapse
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
FIXED
Turns out that I just had to flash the boot image through fastboot, works great now! Thanks
matthewclso said:
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
Click to expand...
Click to collapse
well you can try AOSP too, just remember all these projects are discontinued, so any support in case you break anything support won't be there..so always backup.
for AOSP!