I currently have a an old GS3 I'm playing with and am curious can I load CyanogenMod 12.1 with CWM or do I have update my recovery and install TWRP. currently running Beanstalk 4.4
Thanks
Zb
You can try installing with the existing recovery. If it doesn't work, then change your recovery.
Related
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
tenpin416 said:
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
Click to expand...
Click to collapse
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
DMF1977 said:
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
Click to expand...
Click to collapse
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
tenpin416 said:
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
Click to expand...
Click to collapse
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
DMF1977 said:
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
Click to expand...
Click to collapse
After doing some reading I think the abort is caused by having the older ics bootlaoder.ive never had to update one before so im a bit hesitant. ..do you know if I update and try to switch back to my original restore or to a different rom (other than cm 10) Will I have to change the bootloader back again or will I run into a greater chance of problems in the future?
I have a boot loop problem when installing CM10.2, CM11, PAC ROMs on N7100.
I did every possible wipe and yet boot looping in animation.
The recovery is TWRP latest.
Is it a problem with the new bootloader with 4.3? I'm using it with Criskelo ROM and it works well.
Should I downgrade to the old bootloader? How?
Thanks
Hi folks.
I just installed the KitKat 4.4.2 (CyanogenMod 11.0) 20140116 from Novafusion on my GIO S5660.
Now I see "Cryanogenmod" in the lower display and a rotating arrow around a symbol for hours.
Is that normal or did something go wrong.
I had the mobile rooted and px-cwm-v2 installed, cleared cache and dalvik prior to ROM installation.
Installation was done via px-cwm-v2 in recovery mode.
Any suggestion appreciated.
You need to use the latest CWM for KitKat.
I use this http://forum.xda-developers.com/sho...dvanced Edition / PhilZ Touch Recovery 6.40.1
You will have to flash back to stock and root, because to install PhilZ you need to do it through Terminal Emulator. You could also try the latest MMB CWM which can be flashed through CWM (but I'm bit sure if it will flash KitKat properly).
Sent from my GT-5660 using XDA Free mobile app
For recent cm11 roms released in Aug 2014, you need to use CWM 6.0.5.3 to install them.
Read more if you what to know more.
Thanks guys!!!
Unfortunately the PhilZ Touch Recovery 6.40.1 didn't work for me as for some reason Odin got stuck setting up connection.
I assume that access to SD wasn't possible.
But the 6.0.5.3 was installable from SD in recovery.
With that "new" recovery I was able to install the Novafusion Kitkat and now everything is running fine.
Thanks for your valueable support!
working
i just trying install cm11 august releases with twrp 2.7.0.0, not work...then i install cwm 6.0.5.3 and latest cm11 august releases installs correctly...nice work at all
I want to flash the CM 12.1 to my T-Mobile Galaxy S III but I don't know where to download the gapps for the latest nightly here
i also dont know if T-Mobile is arm, arm64, or x86
so I cant download in this site from cynogenmod
another question- is it the Cyanogen Recovery from this link will be use to flash the ROM or it is the recovery that will be use after flashing the CM12.1?
Use the ARM gapps.
I recommend using either Philz Touch recovery or TWRP, both of which can be flashed using Odin.
I have never used Cyanogen's recovery but have had great success with Philz and TWRP.
audit13 said:
Use the ARM gapps.
I recommend using either Philz Touch recovery or TWRP, both of which can be flashed using Odin.
I have never used Cyanogen's recovery but have had great success with Philz and TWRP.
Click to expand...
Click to collapse
thanks on your reply but I already solve it using the recovery from ROM manager app that I downloaded in the Play store but there is still a problem on it when I update using CyanogenMod updates it will fail to flash automatically after clicking install, so I still need to flash it manually, that's why I still need to flash the recovery provided with CyanogenMod
I have never used the recovery from cyanogen so I don't know if it will automatically dirty flash the update. I also don't know if the cyanogen recovery can flash other zips such as supersu, different gapp versions, etc.
Automatic flashing is not something I like to do because a nightly can cause problems. By using twrp, I can easily make a nandroid backup before flashing a new nightly.
Just tried the Cyanogen recovery and, after downloading a nightly update, I click install and it reboots to recovery and dirty flashes the updated ROM; however, the Cyanogen recovery would not flash the LP Gapps while Philz and TWRP were able to flash the Gapps. Also, the Cyanogen recovery does not have an option to create a nandroid backup.
EDIT: So it turns out the latest version of Philz touch actually does work, at least after reflashing stock.
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
sorcererofdm said:
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
Click to expand...
Click to collapse
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
sorcererofdm said:
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
Click to expand...
Click to collapse
Actually, I got CM12 working after flashing CM12 on top of CM11 restored from philz touch after flashing stock. So this is probably more properly called an "upgrade" from CM11 to CM12