Samsung SII 19100T How to install recovery - Galaxy S II Q&A, Help & Troubleshooting

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

Related

Flashing new roms / New recoveries.

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!

[Q] CWM versions

Is it possible to upgrade CWM on my S2 or are the particular CWM versions matched to particular kernels, like Samsung stock or CM? I am running NeatROM with Philz kernel, which uses CWM 6.0.3.7. I see there is a newer versions of CWM that can be flashed which is KK compatible (thinking about giving Cyanfox a whirl in near future). Thanks.
Recovery is baked into the kernel on the S2, so any recovery you flash independently of it will only persist until the next reboot. If you want a particular CWM version permanently, you'll need to run a kernel which has it.
MistahBungle said:
Recovery is baked into the kernel on the S2, so any recovery you flash independently of it will only persist until the next reboot. If you want a particular CWM version permanently, you'll need to run a kernel which has it.
Click to expand...
Click to collapse
Thanks. That is very helpful to know. So if you "temporarily" flash the latest CWM for kitkat in order load Cyanfox, then does Cyanfox reinstall the CM11 kernel with the appropriate permanent CWM for kitkat?
corvus.corax said:
Thanks. That is very helpful to know. So if you "temporarily" flash the latest CWM for kitkat in order load Cyanfox, then does Cyanfox reinstall the CM11 kernel with the appropriate permanent CWM for kitkat?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2222843
downlaod the CM11 kernel, flash it via your current one, wipe data/factory reset from the new kernel, wipe system too just incase, and install cyanfox and its gapps.

Samsung SII i9100T CM12.1 error (keyboard FC and after sometimes OS full reboots

I was using stock ROM with root i followed the following procedure to install 12.1 nighties but after installing OS keyboard keep on FC's and OS reboots
i am using i9100T version of S2
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
Currenlty my phone is without OS , kindly provide a way to Fix this issue or kindly provide me link to goback to STABLE stock version
Phone i9100T
KiranP23 said:
I was using stock ROM with root i followed the following procedure to install 12.1 nighties but after installing OS keyboard keep on FC's and OS reboots
i am using i9100T version of S2
Currenlty my phone is without OS , kindly provide a way to Fix this issue or kindly provide me link to goback to STABLE stock version
Phone i9100T
Click to expand...
Click to collapse
You could try doing a full wipe and installing again. Try installing the rom, reboot to system, then let the system settle for a few minutes, then going back to recovery and install gapps.
Which gapps did you use? I would try the pico gapps from
The alternatives are:
1. You could download the stock rom for your region from sammobile.com or one of the other websites that provide stock roms, then install with odin
2. You could read up on some of the older custom kitkat or jellybean roms that are more stable and try those.
[url]http://forum.xda-developers.com/galaxy-s2/development-derivatives
A couple that come to mind are Slimsaber 4.4.4 by Fusionjack and the latest unofficial CM11 by Lanchon
FYI if your priority is stability, it's probably best to steer clear of lollipop roms atm. They all have their issues
noppy22 said:
You could try doing a full wipe and installing again. Try installing the rom, reboot to system, then let the system settle for a few minutes, then going back to recovery and install gapps.
Which gapps did you use? I would try the pico gapps from
The alternatives are:
1. You could download the stock rom for your region from sammobile.com or one of the other websites that provide stock roms, then install with odin
2. You could read up on some of the older custom kitkat or jellybean roms that are more stable and try those.
[url]http://forum.xda-developers.com/galaxy-s2/development-derivatives
A couple that come to mind are Slimsaber 4.4.4 by Fusionjack and the latest unofficial CM11 by Lanchon
FYI if your priority is stability, it's probably best to steer clear of lollipop roms atm. They all have their issues
Click to expand...
Click to collapse
Keyboard FC happened even when i didnt flash gapps , i did try clean flash multiple times , still same, ok downloading slimsaber Rom and kernel
to flash this slim rom
i first flash a recovery using ODIN then From CM recovery i flash slim kernel.zip ? then reboot then flash Slimsaber ROM ?
KiranP23 said:
Keyboard FC happened even when i didnt flash gapps , i did try clean flash multiple times , still same, ok downloading slimsaber Rom and kernel
to flash this slim rom
i first flash a recovery using ODIN then From CM recovery i flash slim kernel.zip ? then reboot then flash Slimsaber ROM ?
Click to expand...
Click to collapse
All you need to do is
1. Flash either of the philz kernels
2. Turn phone off and reboot to recovery
3. Full wipe, flash slimsaber(and 4.4.x gapps if you want)
4. Reboot to system
You don't need the slim kernel

Confused about rooting, recovery and custom roms

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!

Unable to mount system

Hi, i found my old gt 9100 galaxy s2 and i want to flash some roms on it or the original one back and working again, but twrp 2.3.2.3 is not letting me flash anything, it says unable to mount '/system, , if anyone could help me i ll appreciate it thanks?
KonC13 said:
Hi, i found my old gt 9100 galaxy s2 and i want to flash some roms on it or the original one back and working again, but twrp 2.3.2.3 is not letting me flash anything, it says unable to mount '/system, , if anyone could help me i ll appreciate it thanks[emoji16]
Click to expand...
Click to collapse
To flash roms like android 4.4.4 you need newer (kitkat compatible) twrp. Yours is outdated.
To flash latest roms you need also an isorec kernel and isorec twrp and you need to increase size of system- and data-partition (there are many threads how to do).
For stockrom you need odin to flash.
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
To flash roms like android 4.4.4 you need newer (kitkat compatible) twrp. Yours is outdated.
To flash latest roms you need also an isorec kernel and isorec twrp and you need to increase size of system- and data-partition (there are many threads how to do).
For stockrom you need odin to flash.
Click to expand...
Click to collapse
I tried to flash isorec kernel from odin but it fails, and also whatever im trying to flash from twrp is says unable to mount system, and in the mount tab the system is unchecked and i cant check it!
KonC13 said:
I tried to flash isorec kernel from odin but it fails, and also whatever im trying to flash from twrp is says unable to mount system, and in the mount tab the system is unchecked and i cant check it!
Click to expand...
Click to collapse
No idea on which rom you are and what exactly you tried to flash.
So what i would do: using your twrp i would flash a kitkat-compatible custom recovery (cwm or twrp). Then boot straight this kk recovery (do not boot system) and make a clean flash of latest unofficial lineage 11 android 4.4.4 by grzwolf together with isorec twrp 3.1.xxx.zip by the.gangster (this rom has already isorec-kernel).
After that you could carry on with repartioning system and data and flashing nougat roms etc. (Having made a backup before doing all sorts of thing is of course adviced)
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
No idea on which rom you are and what exactly you tried to flash.
So what i would do: using your twrp i would flash a kitkat-compatible custom recovery (cwm or twrp). Then boot straight this kk recovery (do not boot system) and make a clean flash of latest unofficial lineage 11 android 4.4.4 by grzwolf together with isorec twrp 3.1.xxx.zip by the.gangster (this rom has already isorec-kernel).
After that you could carry on with repartioning system and data and flashing nougat roms etc. (Having made a backup before doing all sorts of thing is of course adviced)
Click to expand...
Click to collapse
Thanks man you saved me!!!!!

Categories

Resources