Could someone provide me with an easy guide to rooting, installing recovery and installing a custom rom on my S2? I1900 version.
I'm wanting to put a KK rom on it but I'm confused about which recovery to use and the best method for rooting.
WastedJoker said:
Could someone provide me with an easy guide to rooting, installing recovery and installing a custom rom on my S2? I1900 version.
I'm wanting to put a KK rom on it but I'm confused about which recovery to use and the best method for rooting.
Click to expand...
Click to collapse
I read your post on another thread you said you have flashed siyah kernel, so you are already rooted. You just need to use a "kitkat compatible" recovery such as CWM 6.0.4.5+ or TWRP 2.7+ to flash kitkat roms
Just a quick google search for "kitkat compatible recovery" gave me this one. Just download the CWM .zip, flash it from siyah recovery, then reboot to recovery(not system), then do your wipes/backups and flash the rom and gapps you want and reboot to system. Done
will give this a go!
Related
I have trued to read and search the forums, but I haven't been able to figure a definitive answer to this...
When I flash CWM on my S2 using Odin, does it root the phone ?
I usually Root (with framaroot), Flash CWM, Flash CM 11 nightly, Re-root using framaroot.
But Can I just do : Flash CWM and Flash the CM 11 nightly ? does it auto root ?
What do you mean, 'usually'? Why is it that you can't just flash each new build of Cm11 from the previous one? Why do you need to re-root in the first place?
When I rooted my phone, rather than using a one-click such as framaroot, I flashed a kernel (siyah in my case) using Odin. That gave me CWM and root. That cuts out the step you're trying to to eliminate, if I've understood your question correctly?
I'm not sure in answer to your direct question, try it and see. Hopefully the alternative method I just gave you makes it a little quicker though
Edit : you could, if flashing CWM only doesn't give you root, just flash SuperSU from there and then continue.
Sent from a galaxy far, far away
Well mate your question is tricky to understand :cyclops:
1. NO installing CWM wont root your device requires another process (such a framaroot)
2. Aftrer installing CM 11 you dont have to re-root the mobile because CM comes prerooted with superuser !!
3. if you had already managed to install CM 11 think that you have already rooted your mobile
just for typing the 3 points my head spins in short no need for rooting after cm 11 ....and NO cwm wont root your device
thuva06 said:
Well mate your question is tricky to understand :cyclops:
1. NO installing CWM wont root your device requires another process (such a framaroot)
2. Aftrer installing CM 11 you dont have to re-root the mobile because CM comes prerooted with superuser !!
3. if you had already managed to install CM 11 think that you have already rooted your mobile
just for typing the 3 points my head spins in short no need for rooting after cm 11 ....and NO cwm wont root your device
Click to expand...
Click to collapse
Thanks for taking the time to reply.
Why do I have to install CWM if I'm already rooted ? Can't I just framaroot then install CM 11 ?
Can I do a CWM, Cyanogen install without rooting ? Since CM already comes rooted. So jut CWM using odin, then CM install ROM. ?
Other question, Let's say I root, flash CWM, flash a ROM (any rom), can I be unrooted after that and have to reroot again ? Or do ALL roms come pre rooted ?
Gregory48 said:
Thanks for taking the time to reply.
Why do I have to install CWM if I'm already rooted ? Can't I just framaroot then install CM 11 ?
Can I do a CWM, Cyanogen install without rooting ? Since CM already comes rooted. So jut CWM using odin, then CM install ROM. ?
Other question, Let's say I root, flash CWM, flash a ROM (any rom), can I be unrooted after that and have to reroot again ? Or do ALL roms come pre rooted ?
Click to expand...
Click to collapse
CyanogenMod comes rooted. Also, the default recovery on CyanogenMod is CWM as well, so you can boot into recovery with volume up + home + power and flash a new build from there. You don't even need to use framaroot or flash CWM using Odin...
And yes, most (almost all) custom ROMs should come rooted unless you're flashing stock Samsung ROM through Odin. Besides, if you're flashing something in recovery, I don't think you need to be rooted.
Gregory48 said:
Thanks for taking the time to reply.
Why do I have to install CWM if I'm already rooted ? Can't I just framaroot then install CM 11 ?
Can I do a CWM, Cyanogen install without rooting ? Since CM already comes rooted. So jut CWM using odin, then CM install ROM. ?
Other question, Let's say I root, flash CWM, flash a ROM (any rom), can I be unrooted after that and have to reroot again ? Or do ALL roms come pre rooted ?
Click to expand...
Click to collapse
Just to make sure that you understand everything i'm segregating your questions
1.Why do i install CWM when i'm already rooted?
Rooting is a process which just gives your overall control to your device, but just rooting wont make you eligible to flash any ROMS. Now when your install CWM (Clock Work Mod) its a unique type of recovery which enables your to flash Custom Roms. Your ordinary stock rom (your samsung firmware) also does have a recovery (stock recovery) which cannot penetrate into system files. So CWM is a must to flash roms !
Can i do a CWM and flash Cyanogenmod?
Absolutely NO!! Just because CM comes prerooted doesn't mean that you can flash CM without rooting.. CWM requires root to flash and change system files. For instance your are in Stock Samsung Firmware not rooted you just install CWM flash Cyanogenmod and you'll end up in a bootloop or softbrick. Since your system didnt allow files inside coz no ROOT!!..In the other hand if your already running Cyanogenmod (any version) you dont have to root nor flash CWM because they come prerooted and preinstalled with CWM.so you can flash on the go
Let's say I root, flash CWM, flash a ROM (any rom), can I be unrooted after that and have to reroot again ? Or do ALL roms come pre rooted ?
Well cyanogenmod has an inbuilt function to disable root and most of the Roms comes with it now it can be found in settings >developer options> and root access...but not all roms im assuming. on the other hand yes some roms never come prerooted such as (omni rom 4.4.2) where you have to flash superuser to get root. But as i said incase of all prerooted roms there is an option to disable root
hope this helps you understand about rooting and cwm :good:
Thank you both for your answers, I understand much more now.
BUT
Last two answers are in conflict. They say the opposite.
which one to choose ?
So I'm running Cwm version 5.8.1.5 and on stock rom. Now I want to put a custom kitkat rom . so for that, do I need to upgrade my cwm to 6.0.4.5?If so then how do I do it( wanna confirm)?
And just so that the process is streamlined, can anyone tell me the exact procedure before and after flashing the rom via CWM?
AndroidReborn said:
So I'm running Cwm version 5.8.1.5 and on stock rom. Now I want to put a custom kitkat rom . so for that, do I need to upgrade my cwm to 6.0.4.5?If so then how do I do it( wanna confirm)?
And just so that the process is streamlined, can anyone tell me the exact procedure before and after flashing the rom via CWM?
Click to expand...
Click to collapse
If you want back-up apps and data with titanium back-up.
Put all the files you need on your phone (CWM kitkat compatible, rom, gapps) reboot into recovery, nandroid back-up, flash the kitkat compatible CWM, reboot into recovery and follow the steps in the op of the rom you want to install.
I rooted my Galaxy S4 using: http://forum.xda-developers.com/showthread.php?t=2290798
Rootchecker shows root access. However, I cannot get TWRP or CWM to flash. I tried CWM through ROM Manager and TWR through GooManager. ROM Manager reports a good install but when I reboot to recovery it is stock recovery.
Any help would be appreciated.
Please tell me you're already read the (many) threads about basebands and build numbers and custom recoveries.
steven8515 said:
I rooted my Galaxy S4 using: http://forum.xda-developers.com/showthread.php?t=2290798
Rootchecker shows root access. However, I cannot get TWRP or CWM to flash. I tried CWM through ROM Manager and TWR through GooManager. ROM Manager reports a good install but when I reboot to recovery it is stock recovery.
Any help would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56030788&postcount=2281
this may assist U
Plenty of threads about this but let me help you out here.
What build number are you on? Any build number other than MDK have no known way to flash a custom recovery due to a locked bootloader. However if you read into some of the safestrap threads you can install a select few modified roms built for SS. Look here for some help http://forum.xda-developers.com/showthread.php?t=2441441 or use the search tool
i searched forum but i am unable to find way to install recovery to install Cm12.1 from official link official site have recovery *.img and ROM zip but i find no solution on how to install recovery
In my other phone(htc,xiaomi) i can just reboot to bootloader and fastboot flash recovery but this method is not working on samsung phone
kindly update me or show xda link showing how to install CM12.1 recovery on my SII 9100 T model phone i already downloaded ROM and Recoveyr.img from
https://download.cyanogenmod.org/?device=i9100
Does my i9100 T model support 12.1 ?
KiranP23 said:
i searched forum but i am unable to find way to install recovery to install Cm12.1 from official link official site have recovery *.img and ROM zip but i find no solution on how to install recovery
In my other phone(htc,xiaomi) i can just reboot to bootloader and fastboot flash recovery but this method is not working on samsung phone
kindly update me or show xda link showing how to install CM12.1 recovery on my SII 9100 T model phone i already downloaded ROM and Recoveyr.img from
https://download.cyanogenmod.org/?device=i9100
Does my i9100 T model support 12.1 ?
Click to expand...
Click to collapse
Forget about the recovery.img. I don't know why it is there. On the i9100(and i9100T), there is no seperate recovery partition. It is bundled with the kernel. So if you have a custom recovery that is capable of flashing a lollipop rom, just use that. Once you have flashed CM12.1, the CM recovery(kernel) will overwrite the recovery(kernel) you had anyway. Which is not a good thing(not that you have a choice). Currently the CM recovery is not very functional compared to CWM or TWRP
noppy22 said:
Forget about the recovery.img. I don't know why it is there. On the i9100(and i9100T), there is no seperate recovery partition. It is bundled with the kernel. So if you have a custom recovery that is capable of flashing a lollipop rom, just use that. Once you have flashed CM12.1, the CM recovery(kernel) will overwrite the recovery(kernel) you had anyway. Which is not a good thing(not that you have a choice). Currently the CM recovery is not very functional compared to CWM or TWRP
Click to expand...
Click to collapse
Thank you that answers many things , now can u kindly provide a LINK to recovery which is supported by my S2 I9100 T and flashing method so i can install CM12.1 nighties
KiranP23 said:
Thank you that answers many things , now can u kindly provide a LINK to recovery which is supported by my S2 I9100 T and flashing method so i can install CM12.1 nighties
Click to expand...
Click to collapse
I'm assuming you have stock unrooted firmware? The easiest way is to install philz kernel from stock(3e) recovery, then reboot to recovery and flash a newer recovery that is capable of flashing the newer versions of android. If you just want to install CM12.1 straight away just back up your efs then:
1. Download the DVLSH kernel .zip from HERE
2. Download the philz 6.48.4 from HERE
3. Reboot into stock recovery, flash the DVLSH kernel(if your firmware build is DVL**, you could probably reboot into system no problem)
4. Reboot to recovery(not system), flash the philz 6.48.4
5. Reboot to recovery(not system), follow the steps for installing in the CM12.1 thread after backing up etc
Keep the DVLSH kernel. Once you install CM, you will have CM recovery, which only allows you to flash signed .zips(which this one is)
EDIT - The philz 6.48.4 is also signed and is probably the more useful one to keep, being compatible with the newer roms
noppy22 said:
I'm assuming you have stock unrooted firmware? The easiest way is to install philz kernel from stock(3e) recovery, then reboot to recovery and flash a newer recovery that is capable of flashing the newer versions of android. If you just want to install CM12.1 straight away just back up your efs then:
1. Download the DVLSH kernel .zip from HERE
2. Download the philz 6.48.4 from HERE
3. Reboot into stock recovery, flash the DVLSH kernel(if your firmware build is DVL**, you could probably reboot into system no problem)
4. Reboot to recovery(not system), flash the philz 6.48.4
5. Reboot to recovery(not system), follow the steps for installing in the CM12.1 thread after backing up etc
Keep the DVLSH kernel. Once you install CM, you will have CM recovery, which only allows you to flash signed .zips(which this one is)
EDIT - The philz 6.48.4 is also signed and is probably the more useful one to keep, being compatible with the newer roms
Click to expand...
Click to collapse
thankyou i will backup efs with efs backup application form playstore then follow the procedure
thankyou , like you installed flashed recovery i installed from official LInk , flashed nano gapps = boots ,keyboard FC , after sometime frequent random reboots heavily
installed again after full formating ,wipe,dav cache etc flash only cm12.1 nighties =still FC keyboard and random reboots
help me pls
kbxdauser2011 said:
Kiran, i'm in the same stage as you for installing cm 12.1.1 on my SGS2 (GT-I9100) Stock 4.1.2 Rom (Non rooted). Can you please share the steps (step by step) you took to took to install the same . Also how good or Bad is it to be used as a daily regular rom compared to the Samsung Stock rom for the SGS2 (GT-I9100)?
Click to expand...
Click to collapse
noppy22 said:
I'm assuming you have stock unrooted firmware? The easiest way is to install philz kernel from stock(3e) recovery, then reboot to recovery and flash a newer recovery that is capable of flashing the newer versions of android. If you just want to install CM12.1 straight away just back up your efs then:
1. Download the DVLSH kernel .zip from HERE
2. Download the philz 6.48.4 from HERE
3. Reboot into stock recovery, flash the DVLSH kernel(if your firmware build is DVL**, you could probably reboot into system no problem)
4. Reboot to recovery(not system), flash the philz 6.48.4
5. Reboot to recovery(not system), follow the steps for installing in the CM12.1 thread after backing up etc
Keep the DVLSH kernel. Once you install CM, you will have CM recovery, which only allows you to flash signed .zips(which this one is)
EDIT - The philz 6.48.4 is also signed and is probably the more useful one to keep, being compatible with the newer roms
Click to expand...
Click to collapse
please look at above steps
Hi i want just install cwm on my s3, and be with stock firmware , i dont wanna install Custom Roms or same like that, just be with CWM and stock rom. so still root required when CWM INSTALLED FROM ODIN? SORRY FOR DUMP QUESTION
No need to root before installing a custom recovery with Odin.
I recommend TWRP over CWM as CWM has not been updated for a very long time.
audit13 said:
No need to root before installing a custom recovery with Odin.
I recommend TWRP over CWM as CWM has not been updated for a very long time.
Click to expand...
Click to collapse
Neither has the s3 and twrp is known for borking your nand, so much so that they have a section on it on twrp website.
My opinion, use the last official cwmr for your device.
@shivadow, I didn't know that twrp affected the s3. The last version I recall using on the last few sgh-i747m phones I had was 2.87.
Do you have a link to the twrp section regarding this issue? Might be good to have it stickied?
Thank you.
Twrp buggers all devices in the end, not just the s3. It's like there's a bug that can't be solved.
Quick Google found this https://github.com/TeamWin/Team-Win-Recovery-Project/issues/773