Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Al-Dazzlez said:
Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Click to expand...
Click to collapse
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
warrior1208 said:
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
Click to expand...
Click to collapse
Well that clears up a lot othings so thanks for the reply
Related
Hello,
I am really a beginner with flashing roms and I just flashed my first CWM and CM 10.1 rom.
But the version I chose has a few bugs, so I want to flash a different CM version. should I do it the same way as I changed from the stock ROM to CM 10.1, by moving it to root path and then via recovery choose install zip from sd card? What I also don't know is what will happen with the GAPPS. I flashed it right away the first CM flashing. but will I need to flash GAPPS again?
Also, If I want to change from non-touch CWM to touch-CWM, I do it via Odin in the same way I first flashed the non-touch CWM? Will that over-write the existing CWM?
Sorry I am really a beginner, but at least I flashed the first rom
Thanks to everyone who helps :good:
verynoob said:
Hello,
I am really a beginner with flashing roms and I just flashed my first CWM and CM 10.1 rom.
But the version I chose has a few bugs, so I want to flash a different CM version. should I do it the same way as I changed from the stock ROM to CM 10.1, by moving it to root path and then via recovery choose install zip from sd card? What I also don't know is what will happen with the GAPPS. I flashed it right away the first CM flashing. but will I need to flash GAPPS again?
Also, If I want to change from non-touch CWM to touch-CWM, I do it via Odin in the same way I first flashed the non-touch CWM? Will that over-write the existing CWM?
Sorry I am really a beginner, but at least I flashed the first rom
Thanks to everyone who helps :good:
Click to expand...
Click to collapse
Yes, all you said is the correct way. Its that way itself.
To sum it up, if you want to flash a different CM, reboot into CWM recovery, Wipe Data/Cache/Dalvik cache and flash the zip package and flash the gapps and do a wipe data/cache/dalvik cache again. Yes you need to flash GAPPS each time when you install CM.
For changing recovery, if you have another version installable via Odin, then you can go on with it, and it will replace your existing recovery.
Be sure to check this Table to know which GAPPS should be installed for which CM version.
Happy Flashing!
Trying to make a nandroid backup using CW 6.0.3.3, however I continue running into an error during the backup of /cache, I wiped cache and dalvik, any suggestions?
is this the recovery that comes with official cm10.1? i know that it has issues (the Warning: No file_contexts thing on startup is an example)
if it is, and you're running cm10.1 (or another 4.2.2 ROM) try this: http://d-h.st/xkk
cm kernel, comes with an older but most likely bug-free version of CWM 6.0.3.0
let me know if this helped
skepticmisfit said:
cm kernel, comes with an older but most likely bug-free version of CWM 6.0.3.0
let me know if this helped
Click to expand...
Click to collapse
Will this kernel also allow me to install cm-11-20131123-UNOFFICIAL-fascinatemtd? I have tried to install but recieved a message stating it will change my /data? I proceeded and it failed.
And won't CM10.1 just overwrite the new kernel every time I flash a nightly?
philosoweed said:
Will this kernel also allow me to install cm-11-20131123-UNOFFICIAL-fascinatemtd? I have tried to install but recieved a message stating it will change my /data? I proceeded and it failed.
And won't CM10.1 just overwrite the new kernel every time I flash a nightly?
Click to expand...
Click to collapse
You should be able to flash cm11, but flash hhp's kernel first, which will replace clockwork with twrp. Follow the guide in the cm11 thread if you're still confused
And yes, but there hasn't been a new nightly in months, so unless you're building your own nightlies, chances are there won't be a new build and you can flash whatever kernel you want and be fine.
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..
I installed CWM v5.5.0.4, CF-v.15 then install Hyper rom v8 on my friend's S3, everything just fine until yesterday he tried to reroot it himself due to wifi problem (as he said).
Now the phone cannot boot and cannot enter download mode with the volume down + home + power combo, or any other combos (it stucks on S3 logo for a while then reboot to cwm), in cwm I can't use volume keys to navigate, it still reboot when I press power button ("reboot system now" selected by default)
Please help, thanks
Flash TWRP and not CWM as CWM is very outdated. Then flash a custom ROM and Gapps from TWRP.
audit13 said:
Flash TWRP and not CWM as CWM is very outdated. Then flash a custom ROM and Gapps from TWRP.
Click to expand...
Click to collapse
Not true. Cwmr is not built for the roms that the phone was never designed to run. Cwmr is still the most stable recovery for the s3 provided that you don't go higher than 4.3, which is where the stock updates ended.
Beamed in by telepathy.
Neither CWM or TWRP, as far as I know, depend on the stock ROM installed on the phone, they both depend on the model of the phone. I stopped using CWM a long time ago and have not run into any issues. I like TWRP because it has many more options.
If you only want to flash stock-based custom ROMs, CWM should be fine but, from what I have seen in custom ROM threads, most newer (KK and higher) custom ROMs need TWRP.
The OP referenced Hyper rom v8 (https://forum.xda-developers.com/galaxy-s3/development/rom-hyper-rom-t3329988) in the original post and this ROM's installation video used TWRP rather than CWM.
My post was not meant to be disrespectful to CWM in any way as the CWM team has performed great work over the years.
audit13 said:
Neither CWM or TWRP, as far as I know, depend on the stock ROM installed on the phone, they both depend on the model of the phone. I stopped using CWM a long time ago and have not run into any issues. I like TWRP because it has many more options.
If you only want to flash stock-based custom ROMs, CWM should be fine but, from what I have seen in custom ROM threads, most newer (KK and higher) custom ROMs need TWRP.
The OP referenced Hyper rom v8 (https://forum.xda-developers.com/galaxy-s3/development/rom-hyper-rom-t3329988) in the original post and this ROM's installation video used TWRP rather than CWM.
My post was not meant to be disrespectful to CWM in any way as the CWM team has performed great work over the years.
Click to expand...
Click to collapse
No offence taken. I'm just being as factual as possible. Twrp is definitely needed for higher than 4.3.
Beamed in by telepathy.
shivadow said:
No offence taken. I'm just being as factual as possible. Twrp is definitely needed for higher than 4.3.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you. Now, back to the problem at hand:good:
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Swarion said:
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Click to expand...
Click to collapse
Please follow one of the guides available, like this one, or the one in my signature.
You have to be aware that twrp 3 requires kernel isorec support, so you must have a kernel that supports isorec, and also you must have a 1GB system partition to be able to install any nogut or mm rom.
thank you so much managed to find this guide before you answered.
anyway thanks so much my s2 is running lineage smoothly and now we saved some piece of electronics of garbage to early the planet and me are thanking you so much for every one having the same problem as me go with philz touch recovery and then flash the twrp you want from there
all the best