Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Oh. I have that problem too. CM 13.1 not stable!
Jaccob25 said:
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Click to expand...
Click to collapse
Firstly look under settings -> about device and it will tell you the kernel version. If it says 3.0.101-CM------, you have the stock CM13 kernel. You said you have TWRP 2.8.x.x and not CM recovery?? This means you already have the isorec recovery enabled. All you need to do is flash the 3.0.2-1 .img from this recovery and you will have the newer one installed. And just do normal backup/wipes and install CM12.1 as you would any other rom. Just remember to use 5.1 gapps(arm;5.1;pico/nano)
Here is the last official CM12.1 I uploaded
Here is a more up to date unofficial CM12.1
noppy22 said:
Firstly look under settings -> about device and it will tell you the kernel version...
Click to expand...
Click to collapse
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Jaccob25 said:
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Click to expand...
Click to collapse
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
noppy22 said:
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
Click to expand...
Click to collapse
Ohh I thought that TWRP can't flash img file.
Thanks for advice. I try it today.
So I try that and almost everything works fine. Only GPS fixing seems like a little bit problematic. But I don't know my testing was short. I will see.
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
teraghik said:
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
Click to expand...
Click to collapse
You are correct. Isorec support was implemented before that last nightly iirc. No need to flash any kernels.
Note: Only use the official TWRP 3.1 from the TWRP website or the.gangster's one which is basically the same. They are compatible with the earlier android versions.
Hi Noppy,
Thanks very much for taking the time to reply and help - I am using "the gangsters" TWRP 3.1 from djibe's thread, appreciate the heads up. I can confirm that I flashed CM12.1, and it works fine!
Why don't you follow my tutorial to get the perfect smooth Android 7.1 for SGS2 ?
Here it is : https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
Related
Hi guys.
First sorry for my english.
I need your help solving the problem.
I must say that my knowledge is very basic.
Yesterday I downloaded the latest nightly build from cm site (cm-10.2-20130827-nightly-i9100)
After the download complete i tried to boot into recovery to wipe data/factory reset and cache and start flashing the rom But with no Success.
The device won't boot into recovery.
I read somewhere a post saying you should choose app and adb option under developer options\root access but still no success after changing this option.
One more question please
I downloaded the supersu app from the play store and each time it remind me the need to update the su binary each time i choose continue it faild to update.
find the kernel fixed by codeworkx in the cm thread or flash dorimanx kernel with odin ( there is one in .tar in the download list).
k2vmars said:
find the kernel fid by codeworkx in the cm thread or flash dorimanx kernel with odin ( there is one in .tar in the download list).
Click to expand...
Click to collapse
Can you post please a direct link and a guide ?
I forgot to mention that now I'm running cm-10.2-20130824 after flashing previous cm 10.2 builds with no problem.
Can u explain me what can go wrong ?
Link;OTA Problems
Rasra said:
Can you post please a direct link and a guide ?
I forgot to mention that now I'm running cm-10.2-20130824 after flashing previous cm 10.2 builds with no problem.
Can u explain me what can go wrong ?
Click to expand...
Click to collapse
Had the same problem yesterday: Auto-Update seems to be broken, if you apply an update downloaded OTA (even when coming from an older 10.2 Nightly), you can't get into recovery anymore:
Download the newest .tar (9.34) here:
http://dorimanx.shine.sk/
and flash it using ODIN
(insert .tar at PDA)
H3llwar said:
Had the same problem yesterday: Auto-Update seems to be broken, if you apply an update downloaded OTA (even when coming from an older 10.2 Nightly), you can't get into recovery anymore:
Download the newest .tar (9.34) here:
and flash it using ODIN
(insert .tar at PDA)
Click to expand...
Click to collapse
hi H3llwar.
1. Which update are you talking about? I did not do any update.
2. Is required to perform additional actions before flashing the kernel?
3. which odin ver should i use? 3.XX ? 1.85 ?
4. after flashing the kernel should i flash a custom rom again ?
thanks
Rasra said:
hi H3llwar.
1. Which update are you talking about? I did not do any update.
2. Is required to perform additional actions before flashing the kernel?
3. which odin ver should i use? 3.XX ? 1.85 ?
4. after flashing the kernel should i flash a custom rom again ?
thanks
Click to expand...
Click to collapse
1. There's an OTA update function which I used. Obviously, you didn't, it seems to be the nightly thats broken.
2. No, just flash it via ODIN
3. 3.XX worked just fine for me (changed to SlimBean yesterday as CM 10.2 seems too buggy for the moment)
4. You can flash just Dorimanx 9.34.tar, CM 10.2 & recovery should be acessible afterwards
Keep in mind that CM 10.2 and most other ROMs replace the kernel you currently have, if you want to flash another Custom ROM, flash 1. Rom.zip, 2. Gapps.zip & 3. Kernel.zip
H3llwar said:
1. There's an OTA update function which I used. Obviously, you didn't, it seems to be the nightly thats broken.
2. No, just flash it via ODIN
3. 3.XX worked just fine for me (changed to SlimBean yesterday as CM 10.2 seems too buggy for the moment)
4. You can flash just Dorimanx 9.34.tar, CM 10.2 & recovery should be acessible afterwards
Keep in mind that CM 10.2 and most other ROMs replace the kernel you currently have, if you want to flash another Custom ROM, flash 1. Rom.zip, 2. Gapps.zip & 3. Kernel.zip
Click to expand...
Click to collapse
Thank you very much for your help !
After flashing dorimanx kernel via odin was able to boot into recovery mode and flash the rom.
And yes the rom is very buggy maybe i will flash other rom meanwhile.
How is the slimbean rom ?
Rasra said:
Thank you very much for your help !
After flashing dorimanx kernel via odin was able to boot into recovery mode and flash the rom.
And yes the rom is very buggy maybe i will flash other rom meanwhile.
How is the slimbean rom ?
Click to expand...
Click to collapse
It's great!!!
Stable, fast, good battery life with shipped kernel, and just 81MB. I don't miss any feature that CM or AOKP have and it doesn't get bricked when installing Head Soccer like XenonHD does :victory:
Give it a try!
[Solved]
H3llwar said:
It's great!!!
Stable, fast, good battery life with shipped kernel, and just 81MB. I don't miss any feature that CM or AOKP have and it doesn't get bricked when installing Head Soccer like XenonHD does :victory:
Give it a try!
[Solved]
Click to expand...
Click to collapse
hi mate.
i really want to try the slimbean rom but for doing that i need your help (you r my private teacher )
The latest slimbean version appears on the official site is JB 4.22 built 8.
What actions it takes when you downgrade from cm 4.3 to slimbean 4.2.2 etc ?
Rasra said:
hi mate.
i really want to try the slimbean rom but for doing that i need your help (you r my private teacher )
The latest slimbean version appears on the official site is JB 4.22 built 8.
What actions it takes when you downgrade from cm 4.3 to slimbean 4.2.2 etc ?
Click to expand...
Click to collapse
It isn't different from any other ROM change because SlimBean ships with its own kernel and dorimanx supports both 4.3 and 4.2 ROMs:
In Recovery Mode:
1. Wipe data
2. Wipe cache
3. Flash Rom.zip
(Optional: 4. Flash Dorimanx 9.39.zip)
This recovery is more or less useless now. Files will still be hosted though.
ClockworkMod Recovery
Samsung Galaxy SII GT-I9100
All right guys im just going to keep this real nice and simple. Purpose of thread:
Latest CWM Recovery
Kit Kat 4.4 ROM Installation Compatible
Centralized Place to Put The Latest Recoveries
Just a heads up. This is NOT meant to be used as a kernel. I compiled these recoveries from source and only the recovery module is built therefore YOUR PHONE WILL NOT BOOT COMPLETELY AS THERE IS NO KERNEL. I made these recoveries so that users can flash
From ICS/JB to KK with ease
Flash This Over DorimanX Kernel So That You Can Update Your Kit Kat ROM
And Resolve Status 7 Errors When Flashing Kit Kat ROMs On A Out-Dated CWM Recovery
How To Use:
To Flash a Kit Kat ROM From a Out-Dated Recovery CWM Version Less Then 6.0.4.4:
Flash This CWM Recovery File (Does Not Matter Which Version You Pick Just Take The Latest) And Reboot Back Into Recovery Via The Option In The Advanced Menu
You Should Now Have A Grey Coloured Recovery With Version 6.0.4.X
Follow ROM Installation Guide From ROM Thread
Recovery Versions
Click The Numbers To Download e.g. 6.0.4.6
6.0.4.6 (Compiled From CM10.2 JB 4.3.1 Soruce)
6.0.4.7 (Compiled From CM11 KK 4.4.2 Source) (LATEST)
Thanks For Reading :good:
P.S. This is my first thread in the Galaxy SII forum
XDA:DevDB Information
ClockWorkMod Recovery For SGSII GT-I9100, Kernel for the Samsung Galaxy S II
Contributors
-Grift-, cyanogen
Kernel Special Features: Kit Kat Compatible CWM
Version Information
Status: Stable
Current Stable Version: 6.0.4.7
Stable Release Date: 2014-01-29
Created 2014-01-29
Last Updated 2014-08-16
good job! but i have to ask is Stweaks compatible?
Thanks for your efforts. Download link?
EDIT: Found it
edd89 said:
good job! but i have to ask is Stweaks compatible?
Click to expand...
Click to collapse
Its just the recovery module no use for stweaks :angel:
spectator123 said:
Thanks for your efforts. Download link?
Click to expand...
Click to collapse
Woa you guys are fast.. Just added
haha yes we are buddy keep up the good work
tried to flash this via CWM...does not work. am i doing anything wrong?
how do i install it normaly?
QuAn64m said:
tried to flash this via CWM...does not work. am i doing anything wrong?
how do i install it normaly?
Click to expand...
Click to collapse
Was there a error code?
Edit: Wait hold on you are using a GT-I9100G?????? This is only for the Exynos Galaxy SII GT-I9100/P/M/T
-Grift- said:
Was there a error code?
Click to expand...
Click to collapse
code 7 :-/
---------- Post added at 04:51 PM ---------- Previous post was at 04:29 PM ----------
QuAn64m said:
code 7 :-/
Click to expand...
Click to collapse
oops...my fault...i use a sgs2 G version. sorry !
can i flash this recovery on jb stock recovery??
scorpion.hbs said:
can i flash this recovery on jb stock recovery??
Click to expand...
Click to collapse
No you cannot but the fastest way to get from stock 4.1.2 to Kitkat 4.4 is to
1. Download this into external SDcard
2. Download my recovery and what ever ROM+Files you need into internal/external
3. Flash first file in stock recovery
4. Flash my recovery, reboot back into recovery
5. Wipe data+cache (factory reset)
6. Flash the ROM+Files
7. Reboot
:good:
@Grift, must say have been following your work/posts for sometime now and find/enjoy the way you can explain a lot of ( detail ) clearly without using many too English words. haha.
Thank you very much for this post & code CWM kk compatible.
foot note/tip. upgrade/flash Direct from ICS404 to KKat is possible But the user Must Format /system /data /cache within CWM Kkat as normal factory reset doesn't work for such a big version jump.(my thoughts/theory only).
Usual warning Nandroid backup First as all Rom data Lost doing it this way.
Copy of request below if possible. @Grift. If possible can you release a Temporary version of your (CWM kitkat with out kernel).
Similar to what Philz was releasing for GT i9100.
Reason for request. Is at moment Dorimanx kernel has older cwm. So when I flash permanent CWM kk compatible then re-flash Dori it can break 2nd ROM boot access/entry.
Therefore if possible a Temp version of what you are doing/releasing would be Perfect for my & others dualboot kitkat problems.
Thanks in advance bmad.
Barry Mad said:
@Grift, must say have been following your work/posts for sometime now and find/enjoy the way you can explain a lot of ( detail ) clearly without using many too English words. haha.
Thank you very much for this post & code CWM kk compatible.
foot note/tip. upgrade/flash Direct from ICS404 to KKat is possible But the user Must Format /system /data /cache within CWM Kkat as normal factory reset doesn't work for such a big version jump.(my thoughts/theory only).
Usual warning Nandroid backup First as all Rom data Lost doing it this way.
Copy of request below if possible. @Grift. If possible can you release a Temporary version of your (CWM kitkat with out kernel).
Similar to what Philz was releasing for GT i9100.
Reason for request. Is at moment Dorimanx kernel has older cwm. So when I flash permanent CWM kk compatible then re-flash Dori it can break 2nd ROM boot access/entry.
Therefore if possible a Temp version of what you are doing/releasing would be Perfect for my & others dualboot kitkat problems.
Thanks in advance bmad.
Click to expand...
Click to collapse
Will take a look into it:good:
@-Grift-
How much space is needed to compile a recovery in ubuntu? All, do I need trees used for building roms?
Aiko0923 said:
@-Grift-
How much space is needed to compile a recovery in ubuntu? All, do I need trees used for building roms?
Click to expand...
Click to collapse
I believe you do need the sources. From what I see you work on the Desire HD (Ace) ? Either you download the sources and compile from there or you can try Koush's CWM builder ( just search CWM builder on google ). As for source code Cm10.2 source can be upwards of 10GB easily. For the DHD im not sure if you guys have official CM11 source?
-Grift- said:
I believe you do need the sources. From what I see you work on the Desire HD (Ace) ? Either you download the sources and compile from there or you can try Koush's CWM builder ( just search CWM builder on google ). As for source code Cm10.2 source can be upwards of 10GB easily. For the DHD im not sure if you guys have official CM11 source?
Click to expand...
Click to collapse
We've got unofficial builds of cm11, and most devs have release pretty stable device and kernel trees. Thanks, 10GB isn't bad at all, but will it require me to setup my Build Environment differently?
Cwm
I'm running cwm version 5.8.1.5 and on stock rom 4.1.2. I am thinking of upgrading to 4.4.2. So can u just explain how to proceed with the recovery installation?
Okay can anyone help me? My odin 3.09 while flashing cwm 6.0.2.9 said reset instead of pass. Then phone turned off. After that I can only access download mode and it shows flash counter 2 times. Any help? Was running stock 4.1.2 rooted.
Sent from my Nexus 4
Sent from my Nexus 4
AndroidReborn said:
Okay can anyone help me? My odin 3.09 while flashing cwm 6.0.2.9 said reset instead of pass. Then phone turned off. After that I can only access download mode and it shows flash counter 2 times. Any help? Was running stock 4.1.2 rooted.
Sent from my Nexus 4
Sent from my Nexus 4
Click to expand...
Click to collapse
Flash this in odin
http://www.dorimanx.shine.sk/Androi...rimanx-V8.43-[12-21]-[24-10]-TAR-FOR-ODIN.tar
My rom is stock 4.1.2 and using cwm 6.0.1.5 but i can't flash anything include CWM 6.0.4.7 i back recovery and flash CWM 6.0.4.7 but it's error help please
Sent from my GT-i9100 by Tapatalk Pro ♠
6.0.4.8 is already out
Regards
I have a GS2 I9100XWLSW, suffering the EMMC brick bug. Still with stock kernel and recovery. Rooted with Framaroot.
First of all I'd want to flash a recovery, and a safe kernel - to avoid any possibile brick bug.
Later on I plan to flash Cyanogen or Omnirom, once a Lollipop stable versions is out.
Looking around I've found many ways to do this, but I'm unsure which one is safes (and possibly easier too):
- Installing Philz through Odin? Surely the kernel is safe, but CWM is and old version, not supporting KitKat ROM, right? Would I then need to flash an updated CWM + Kernel once I update to Lollipop? How?
- Using Clockwork mod install app to install a CWM? Can I install last CWM and still run on JB? But what about the unsafe, still not patched, stock kernel? Would still need to later update with a new Kernel for Lollipop? How?
- Others?
In particular, there's something concerning my GS2 that I didn't fully understand.. seems like differently from other phones, CWM needs to be installed together with a specific Kernel to work. Is this something true only for Philz's version, or is it so for CWM itself?
Malhavoc Blackdrake said:
I have a GS2 I9100XWLSW, suffering the EMMC brick bug. Still with stock kernel and recovery. Rooted with Framaroot.
First of all I'd want to flash a recovery, and a safe kernel - to avoid any possibile brick bug.
Later on I plan to flash Cyanogen or Omnirom, once a Lollipop stable versions is out.
Looking around I've found many ways to do this, but I'm unsure which one is safes (and possibly easier too):
- Installing Philz through Odin? Surely the kernel is safe, but CWM is and old version, not supporting KitKat ROM, right? Would I then need to flash an updated CWM + Kernel once I update to Lollipop? How?
- Using Clockwork mod install app to install a CWM? Can I install last CWM and still run on JB? But what about the unsafe, still not patched, stock kernel? Would still need to later update with a new Kernel for Lollipop? How?
- Others?
In particular, there's something concerning my GS2 that I didn't fully understand.. seems like differently from other phones, CWM needs to be installed together with a specific Kernel to work. Is this something true only for Philz's version, or is it so for CWM itself?
Click to expand...
Click to collapse
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
gsstudios said:
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
Click to expand...
Click to collapse
Thank you! Ok, let's see if I got everything right:
- First I need to flash Apolo, but I can't find the 4.14 version. Do I still use Odin? Instructions are unclear. The official thread seems this: http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756/post41742325
- By flashing Apolo 4.14 I should get a new kernel (EMMC safe) and TWRP (which version?)
- With the above, I can still run my stock JB 4.1.2, right?
Then, once I want to flash a Lollipo ROM:
- Do I need to update TWRP? Does this break my ability to run my current JB 4.1.2 ?
- Flashing the Lollipop ROM will overwrite the Apolo Kernel 4.14 with a suitable Lollipop kernel, right? Or am I forced to also flash a Lollipop kernel manually (either Apolo or anoter)?
Thank you in advance!
Malhavoc Blackdrake said:
Thank you! Ok, let's see if I got everything right:
- First I need to flash Apolo, but I can't find the 4.14 version. Do I still use Odin? Instructions are unclear. The official thread seems this: http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756/post41742325
- By flashing Apolo 4.14 I should get a new kernel (EMMC safe) and TWRP (which version?)
- With the above, I can still run my stock JB 4.1.2, right?
Then, once I want to flash a Lollipo ROM:
- Do I need to update TWRP? Does this break my ability to run my current JB 4.1.2 ?
- Flashing the Lollipop ROM will overwrite the Apolo Kernel 4.14 with a suitable Lollipop kernel, right? Or am I forced to also flash a Lollipop kernel manually (either Apolo or anoter)?
Thank you in advance!
Click to expand...
Click to collapse
What I said before about apolo requires the usage of CWM. If you can, flash philz kernel (through odin)first then you can flash apolo 4.14 (TWRP) using cwm. All kernels for the s2 are safe from the emmc brickbug (just make sure you read the first post of the kernel threads). TWRP version should be 2.7.0.0, but it should work fine with all zip files.
When you flash a lollipop rom, you most likely will not have to update TWRP (unlikely as the source code for lollipop isn't going to change). You can still flash back stock JB from a backup with no problems. Yes, flashing lollipop will replace apolo with a compatible kernel.
gsstudios said:
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
Click to expand...
Click to collapse
gsstudios said:
What I said before about apolo requires the usage of CWM. If you can, flash philz kernel (through odin)first then you can flash apolo 4.14 (TWRP) using cwm. All kernels for the s2 are safe from the emmc brickbug (just make sure you read the first post of the kernel threads). TWRP version should be 2.7.0.0, but it should work fine with all zip files.
When you flash a lollipop rom, you most likely will not have to update TWRP (unlikely as the source code for lollipop isn't going to change). You can still flash back stock JB from a backup with no problems. Yes, flashing lollipop will replace apolo with a compatible kernel.
Click to expand...
Click to collapse
All right, so, to recap, is this right?
- Flash Philz (of course the version for my kernel and JB) with Odin. This will also install CWM (an old version, not supporting KitKat and Lollipop)
- With the above, I can do a nandroid backup, which also includes Philz's kernel. Does it also include the recovery itself?
- Flash Apolo 4.14 through CWM. This will change both the Philz Kernel and the CWM recovery with Apolo Kernel and TWRP. Jelly Bean will still run, right?
- From this TWRP, I can flash and run both the current JB and future Lollipop without changing recovery, right?
Malhavoc Blackdrake said:
All right, so, to recap, is this right?
- Flash Philz (of course the version for my kernel and JB) with Odin. This will also install CWM (an old version, not supporting KitKat and Lollipop)
- With the above, I can do a nandroid backup, which also includes Philz's kernel. Does it also include the recovery itself?
- Flash Apolo 4.14 through CWM. This will change both the Philz Kernel and the CWM recovery with Apolo Kernel and TWRP. Jelly Bean will still run, right?
- From this TWRP, I can flash and run both the current JB and future Lollipop without changing recovery, right?
Click to expand...
Click to collapse
You are 100% correct with all of your questions. Happy flashing!
gsstudios said:
You are 100% correct with all of your questions. Happy flashing!
Click to expand...
Click to collapse
Thank you very much! Also found the Apolo version you were talking about. BTW, the reason I have to pass through Philz to flash Apolo is just because that Apolo version is available in .zip format only, right? Because if there was a .tar, I could just flash the stock rom with Apolo through Odin, without going through Philz first, right?
Malhavoc Blackdrake said:
Thank you very much! Also found the Apolo version you were talking about. BTW, the reason I have to pass through Philz to flash Apolo is just because that Apolo version is available in .zip format only, right? Because if there was a .tar, I could just flash the stock rom with Apolo through Odin, without going through Philz first, right?
Click to expand...
Click to collapse
Wow, you sound like you have flashed custom roms before. You are correct again.
gsstudios said:
Wow, you sound like you have flashed custom roms before. You are correct again.
Click to expand...
Click to collapse
Never before, but being a software developer I get these things not too hardly. Also, I'm really reading a LOT of guides everywhere to avoid doing a mess! :laugh:
Thank you again for your help.
gsstudios said:
Wow, you sound like you have flashed custom roms before. You are correct again.
Click to expand...
Click to collapse
I finally did all of the above, and I can confirm that everything worked perfectly. I just skipped during the Apolo flashing the clean script suggested, and just did Clean Cache + Dalvik Cache.
Now I have TWRP and Apolo v4.15.
Noticed however that TWRP is v2.6.3 , while you said that I would probably need 2.7.1.0+ to later flash Omnirom or CM12
Is it okay anyway, or do I need to flash a new one? Can I risk breaking something if I try to flash a new TWRP? I mean: may I end up flashing a TWRP not supported with my kernel / JB and get bootloops or something bad?
Malhavoc Blackdrake said:
I finally did all of the above, and I can confirm that everything worked perfectly. I just skipped during the Apolo flashing the clean script suggested, and just did Clean Cache + Dalvik Cache.
Now I have TWRP and Apolo v4.15.
Noticed however that TWRP is v2.6.3 , while you said that I would probably need 2.7.1.0+ to later flash Omnirom or CM12
Is it okay anyway, or do I need to flash a new one? Can I risk breaking something if I try to flash a new TWRP? I mean: may I end up flashing a TWRP not supported with my kernel / JB and get bootloops or something bad?
Click to expand...
Click to collapse
You will need to flash a newer recovery. If you use philz recovery, you can install all lollipop roms and kikat roms without a problem
Link to download latest philz recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip
Flash it with TWRP. Cheers.
gsstudios said:
You will need to flash a newer recovery. If you use philz recovery, you can install all lollipop roms and kikat roms without a problem
Link to download latest philz recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip
Flash it with TWRP. Cheers.
Click to expand...
Click to collapse
That link is indeed philz's latest version for i9100 (also from size it seems with just the recover, and no kernel, right?), but does it still run on JB with Apolo kernel? On Philz's thread I read something about latest versions supporting only kitkat / lollipop. Does it mean I have to flash this Philz's update just before flashing Lollipop, or I can flash it already and running my JB + Apolo, without problems?
Also, I heard that Philz is no longer updating his recover (is it?), so if possible I would prefer to stick with TWRP.. if there is a TWRP version which suits my needs with my device, of course!
Hello,
I have a Samsung Galaxy S2 GT-I9100p with CM12.1-20151023-NIGHTLY-i9100
I was recently on CM11 with CWM 6.0.4.3 recovery and everything worked as it should but since upgrading to CM12.1 I have been unable to boot in CWM recovery, it just takes me into the stock recovery. I've tried reflashing the CWM img but it has no effect.
Is this version of CWM not compatible with Lollipop? Can anyone tell me a version that will work?
I would also like to try TWRP but unsure which image to use, can anyone recommend one?
Thanks
Steven
caned_monkey said:
Hello,
I have a Samsung Galaxy S2 GT-I9100p with CM12.1-20151023-NIGHTLY-i9100
I was recently on CM11 with CWM 6.0.4.3 recovery and everything worked as it should but since upgrading to CM12.1 I have been unable to boot in CWM recovery, it just takes me into the stock recovery. I've tried reflashing the CWM img but it has no effect.
Is this version of CWM not compatible with Lollipop? Can anyone tell me a version that will work?
I would also like to try TWRP but unsure which image to use, can anyone recommend one?
Thanks
Steven
Click to expand...
Click to collapse
The recovery is bundled with the kernel in the S2. CM12.1 has CM recovery by default. The only way you can have a different recovery is to flash a compatible custom kernel. You could try the TWRP kernel from at the beginning of the CM12.1 thread or Dorimanx kernel that gsstudios builds
Thanks, where is the CM12.1 thread, I'm not sure which one you're referring to?
caned_monkey said:
Thanks, where is the CM12.1 thread, I'm not sure which one you're referring to?
Click to expand...
Click to collapse
This one. Under "Important information" in the first post there is a link
Thank you! Problem solved, very quick and easy to install
Hey guys,
My SGS2 just got soft-bricked, stuck on samsung logo. I didn't do nothing actually, just restarted my phone.
I have rooted phone with stock OS (latest one) on it a long time ago.
I can enter into recovery mode. Tried to wipe data with no luck.
BUT I want to make a backup. I read that if I install CWM recovery I will be able to mount USB storage to make backups. Is it possible to backup contacts using USB?
I also read that on SGS2 devices CWM will update OS's kernel so I will have to install new OS. Is it true?
Anyway, is it possible to make a full backup in this case?
GrigoryS said:
Hey guys,
I also read that on SGS2 devices CWM will update OS's kernel so I will have to install new OS. Is it true?
Click to expand...
Click to collapse
"A recovery is a kernel and a kernel is a recovery"
If your current OS supports the new kernel then there won't be a need to install a new OS.
Kevin3014 said:
"A recovery is a kernel and a kernel is a recovery"
If your current OS supports the new kernel then there won't be a need to install a new OS.
Click to expand...
Click to collapse
How to check if my OS supports new kernel?
What is more important is that if I install CWM breaking my current ROM and make a full backup will I be able to restore this backup on new ROM?
I ask this because I found the following warning:
"Warning: For GT-i9100 and SGH-i777, installing CWM or TWRP recovery also installs kernel. This is only recommended to install when installing a new custom ROM. Installing CWM/TWRP recovery will most likely break the ROM you are running currently as it overwrites the ROM’s kernel."
GrigoryS said:
How to check if my OS supports new kernel?
Click to expand...
Click to collapse
Simple. Just read the information provided by the threads. If you are on official jelly bean, use Apolo Kernel 4.15b or Siyah Kernel (Although this is outdated now). For Lollipop, you can either use DorimanX kernel 11.0 or CM12.1 kernel with TWRP by Lysergic acid (If you want to use CM12.1). For kitkat, you can use DorimanX kernel 10.45 by Me or 10.44 by Cybernetus, Gustavo kernel (make sure you install KK version) or Apolo Kernel 7.3.
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
GrigoryS said:
I ask this because I found the following warning:
"Warning: For GT-i9100 and SGH-i777, installing CWM or TWRP recovery also installs kernel. This is only recommended to install when installing a new custom ROM. Installing CWM/TWRP recovery will most likely break the ROM you are running currently as it overwrites the ROM’s kernel."
Click to expand...
Click to collapse
It depends on what ROM you are using. If you install the correct kernel, the ROM will not break at all.
gsstudios said:
It depends on what ROM you are using. If you install the correct kernel, the ROM will not break at all.
Click to expand...
Click to collapse
Hi! Is there any way to check the version of ROM I use on this phone? Maybe from recovery mode?
P.S.: I used latest OS which came through official update on SGS2 in Europe. It was something like 4.2.3 or 4.3.3.
If it was the last/latest/final official update, it would have been 4.1.2 Jellybean.....
http://i.imgur.com/rVnFwJM.jpg
Hm... That's strange... I was pretty sure I had 4.3.3 .
OK, let's imagine I install CWM with newer kernel breaking my ROM... what if I install older version after that? Will my ROM be back to work?
It *might* well be ok.....but having never intentionally installed the wrong kernel, I'm not going to stake my life on that as I have ZERO experience of that scenario....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
It *might* well be ok.....but having never intentionally installed the wrong kernel, I'm not going to stake my life on that as I have ZERO experience of that scenario....
Click to expand...
Click to collapse
OK I'll wait for someone who can confirm that. Thanks, anyway!
GrigoryS said:
OK I'll wait for someone who can confirm that. Thanks, anyway!
Click to expand...
Click to collapse
GrigoryS said:
Hm... That's strange... I was pretty sure I had 4.3.3 .
OK, let's imagine I install CWM with newer kernel breaking my ROM... what if I install older version after that? Will my ROM be back to work?
Click to expand...
Click to collapse
Stock 4.3.3 doesn't exist
Samsung only provided android version 4.1.2 as the last version.
If you install a older kernel after flashing the wrong kernel, your ROM should work again. Once again, the "older" kernel needs to be the correct version for the ROM.
If you do install the wrong kernel, your ROM will not boot and will either give you black screen or bootloop or phone constantly rebooting. So you need to quickly get to the recovery using the button combinations.