Samsung SII i9100T CM12.1 error (keyboard FC and after sometimes OS full reboots - Galaxy S II Q&A, Help & Troubleshooting

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

Related

Will my phone bricked if I flash it from Speedmod to Cyanogenmod??

Im thinking about change my rom to Cyanogenmod, but Im afraid it will crash and brick my phone.
Can i just flash it directly? or should i wipe out all stuff first?
Speedmod is a kernel, Cyanogenmod is a ROM.
CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII Q&A.
No, ist very very unlikely to brick your phone just because you go from stock (or modded stock) or whatever to Cyanogen,
If something goues wrong, you can (nearly) always flash a stock Firmware via ODIN.
As far as I know its almost impossible to brick a modern Android Phone. Except you do do some really "deep" stuff.
But you should wipe your phone when you go from Stock (or modded Stock) to Cyanogen.
And you should flash the Cyanogenmod Rom twice because its using a new or modded version of clockworkmod.
There is a step by step discription in the Cyanogenmod Wiki.
I hope that Information helps a bit.
How to
normalife said:
Im thinking about change my rom to Cyanogenmod, but Im afraid it will crash and brick my phone.
Can i just flash it directly? or should i wipe out all stuff first?
Click to expand...
Click to collapse
1.just download latest nightly of cyanogemod and put it on SDcard...Link for latest nightly here: (http://download.cyanogenmod.com/get/cm_galaxys2_full-94.zip)
2.enter CWM recovery and do a wipe data/factory reset,,, wipe cache,, wipe dalvik cache(it is in Advanced option in CWM main menu)...so yes wipe out all stuff first
3. install nightly .zip file from sdcard
4. install nightly .zip file from sdcard AGAIN...REALLY DO IT OR IT WILL NOT BOOT
5. reboot phone from recovery and you will be in CyanogenMod 7 ROM
PS: do not be afraid about SpeedMod kernel....flashing cyanogenmod nightly .zip also flashes CM7 Stock kernel for you
PS: You can try Siyah kernel 2.1 beta 14 (http://www.gokhanmoral.com/public/files/siyahkernel/test/Siyah-v2.1b14-CWM.zip) info here: (http://forum.xda-developers.com/showthread.php?t=1263838)
I am using this kernel since beta 12 and no problems
PS: Speedmod is name of kernel = core of android system...Cyanogenmod is a ROM = phone firmware
You can ask me again if needed..or send me a PM
Should he not at least make a nandroid backup first
Dude, do some research.
If you managed to get Speedmod onto the phone, then you shouldn't have any other problems.

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 19100T How to install recovery

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

Flashing a different Custom Recovery without a charging port (Broken charging port)

So i wanted to install custom rom(cyanogenmod 14.1) on my S3 device I realized that my device has already CWM (v5.5.0.4 :: CF -v1.5 ). I can flash cyanogenmod 14.1 with no issues but I can't flash gapps. After installing gapps, I get a lot of errors when I boot(Setup wizard has stopped). I tried 2 different versions of gapps(aroma,nano) both of them didn't work. I started to think that my CWM version is the issue. I want to flash another Custom Recovery like newer version of CWM of TWRP but as I said my charging port is broken. I just want my device to have android nougat with google apps. I hope I can find a solution
Download the TWRP App from Google play and install. You could also search for a flashable TWRP recovery und Update within TWRP to latest version by flashing the .img file.
The problem wont be the recovery. Make sure gapps is the correct one for your device. Check the software versions and cross reference them against Apkmirror.com.
Beamed in by telepathy.
That's a problem of Cyanogenmod 13 / 14.
Wipe your Cache/System/Data Partitions and reflash Cyanogenmod 14.1. Then don't boot up, you've to install the gapps package directly after that.
Make sure that you have downloaded the ARM 7.1 gapps-package.
You can flash twrp or stock rom from 'mobile odin'. Or you can download flashable twrp.zip....but flashing stock ROM requires additional download
I solved the problem. The problem was recovery and i knew it. I downloaded the apk of TWRP App from their official website. It worked flawlessly. After that i Flashed Cyanogenmod 14.1 then gapps with the latest version of TWRP and perfect! Everything works without any problem. I hope this answer is helpful for the other people having the same issue.

Categories

Resources