I rooted my Galaxy tab 10.1, i tried to install CWM 5 and instead i got this twmr what ever that is... and i installed the rom after wiping the device.
then i installed Gapps and wiped cache and rebooted. now i have this blue circle that sais cyanogenmod and its circling its self for over half an hour... what do i do?!?!
ProGadgetReviews said:
I rooted my Galaxy tab 10.1, i tried to install CWM 5 and instead i got this twmr what ever that is... and i installed the rom after wiping the device.
then i installed Gapps and wiped cache and rebooted. now i have this blue circle that sais cyanogenmod and its circling its self for over half an hour... what do i do?!?!
Click to expand...
Click to collapse
Get CWM 6 flashed onto your device and wipe. If need be, then install CM10 again with gapps without rebooting. Also, are you using the right gapps? CWM 6 will be in the same place as the CM10 downloads called recovery, be sure to download from http://droidbasement.com/galaxy/roms/cm10/ and choose the right device.
Related
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
I rooted my phone and installed the cyan fox rom in December and it was working flawlessly, but yesterday it would randomly shut down and then get stuck in a boot loop or wouldn't boot up. So i installed a stock rom and there are no problems with that. Today I installed cyanogen mod on now the problem is coming up again. I have tried wiping dalvik cache, factory resting and that doesn't seem to do much.
Razorbrick said:
I rooted my phone and installed the cyan fox rom in December and it was working flawlessly, but yesterday it would randomly shut down and then get stuck in a boot loop or wouldn't boot up. So i installed a stock rom and there are no problems with that. Today I installed cyanogen mod on now the problem is coming up again. I have tried wiping dalvik cache, factory resting and that doesn't seem to do much.
Click to expand...
Click to collapse
Install Stock Rom again or ask in Cyanogenmod community
Recovery
What recovery are you using? Is it the latest version?
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!
Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!