yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] laptopu:
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.

I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.

I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.

So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?

Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?

I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
[Galaxy S II Android Development] Saber:
OP updated with recommendations from other users. Thanks for the suggestions! ;)

Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.

gsstudios
[Galaxy S II Android Development] rolves1899:
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
[Galaxy S II Android Development] fireburner-de:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
[Galaxy S II Android Development] Saber:
Already in the OP. It is the second link for the repartition section ;)

gsstudios
[Galaxy S II Android Development] UsualSuspectReaL:
AT LAST ! Now they will not spam the official thread of cm 13!
[Galaxy S II Android Development] fireburner-de:
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.

I fear, they still will :(
[Galaxy S II Android Development] Saber:
Yes, I forgot to change that. Updating now... ;) I read your post wrong :)

gsstudios

Edit: Done. Thanks!
[Galaxy S II Android Development] Saber:
Dorimanx kernel:

http://xdaforums.com/galaxy-s2/development-derivatives/kernel-dorimanx-jb-4-1-2-t3106241

It's isorec recovery compatible, but only CWM will fully work. Once you've flashed CM13 after flashing the kernel and rebooting to recovery, you can switch to TWRP.

gsstudios
[Galaxy S II Android Development] Arkan_:
Hello,

I've read all the topic and the first post, but, I'm still a bit confused for what I have to do in my case.

I'm running on CM 12.1 since november, so before the 20160119 build as mentionned in the first post. I have CM Recovery.

I've already done the repartion (did it when I flashed to CM 12.1 for not having problems with GApps install).

So I understood that I need to install IsoRec Recovery, but, I don't know what file to instal. There is a link to the topic, and several link into that following topic. I suppose it's that file : twrp-3.0.2-1-i9100.img (sorry, I'm not allowed to post a link since I'm a new user)

If I understand well, here are the steps for me :

1. Go to CM Recovery mod (since it's before the CM 12.1 20160119, the flash should works ?)

2. Wipe all data/cache as usual

3. Flash CM 13.1

2. Instal GApps

3. Flash IsoRec

4. Reboot

Do I absolutly need to flash and use one of IsoRec-compatible kernels ?
[Galaxy S II Android Development] TriboDoP:
I do not think you can flash img files with cm recovery.

some time ago i was on this cm 12.1 (before this very helpful thread and not having a working pc) and i found a solution for myself (there will be others of course).

But this worked for me perfectly:

To get a useful CWM-Recovery i clean installed in CM-Recovery (apply update) the latest cm 11 kitkat nightly (search for cm 11 nightly 20150614 by pikasonik for Galaxy S2).

Right away rebootet into CWM-Recovery and clean installed CM 13, Gapps and the isorec-recovery twrp 3.0.2.0-i9100.zip by [MENTION=414800]arnab[/MENTION] (NOT .img) in one go.

reboot system

later you can update in twrp recovery to twrp-3.0.2-1.img

---------- Post added at 11:09 AM ---------- Previous post was at 10:57 AM ----------

sorry i forgot to ask: did you flash the right pitfile with 1GB System and 4GB data.

if not this all will not work and you will have to flash this pitfile first and then do the other steps.
[Galaxy S II Android Development] Arkan_:
Thanks for you help !

Yes, I already extended my internal storage when I switched to CM 12.1 (Internal storage = 4go and "SD Card" = 9go) with pitfile via Odin.

The thing is, I cannot find the cm11 nightly 20150614 by pikasonik that you advised me. It's not anymore on cyanogenmod website (just cm11 snapchots from 2014, too old I guess), and I cannot find it via Google. Maybe you still have it ?
[Galaxy S II Android Development] TriboDoP:
my google search for this rom gives me the result:

cm-11-20150614-NIGHTLY-i9100.zip by Pikassonik for Galaxy S 2 - Android File Host.

So it is on androidfilehost for download.

Still i am not certain if you flashed the right pitfile, because it is very importent to have increased system to 1GB (not only increase data partition).

Just check if your system/total ram is 786 MB (if it is 512 MB then it is stock and you will not be able to install any 6.0.1 rom + gapps).

For checking you could use the free app "CPU-Z" from playstore.

in this app just go to device and to total ram.
[Galaxy S II Android Development] Arkan_:
Thanks again for your help. I was able to update my S2 with the right recovery. Yes, I had 786mb on my system/total RAM.

Just one more thing : I wasn't able to find twrp 3.0.2.0-i9100.zip, on every website where I checked, it was the .img availabled only. So I used recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab). It worked well, but now I want to flash twrp 3.0.2.0-i9100.img like what you said, but it ask me to select the partition where I want to flash it : Boot or Recovery. I guess I have to choose Recovery, but I want to be sure, by asking you, before I'm making a mistake :)
[Galaxy S II Android Development] Troubadour666:
Hi,

http://xdaforums.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457

[MENTION=414800]arnab[/MENTION] post#1 said :

Update via Recovery

thanks
[Galaxy S II Android Development] Arkan_:
Oh, I forgot to look into that topic, I had so many open in my browser ^^ Merci beaucoup, all done !
[Galaxy S II Android Development] TriboDoP:
Nice to See that you have finally (with the help of [MENTION=4775725]Troubadour666[/MENTION]) cm 13 with latest twrp.

Cheers
[Galaxy S II Android Development] notknowntobeafcukgiver:
i am trying to update from CM9 4.0.4 (December 2012), with contemporaneous CWM recovery. Is there any extra step or I can just :

- flash KK compatible recovery (TWRP 2.8.4+ tar with Odin)

- flash CM12 kernel with Odin

- flash CM13 with Odin

- update recovery to TWRP 3

?

Thanks
[Galaxy S II Android Development] TriboDoP:
Have you allready increased you System partition ?

If yes: you do not need odin.

- in cwm install cwm KK compatible-i9100.zip

(For safety reason you could first flash the philz kernel using you cwm, then reboot in philz recovery and install the cwm KK compatible-i9100.zip)

- in this cwm then clean install cm 13.zip + gapps.zip + isorec recovery 3.0.2-0.zip by [MENTION=414800]arnab[/MENTION] IN ONE GO!

- reboot system

If you have not increased you system partition by flashing pitfile 1GB system_4GB data:

Please read the instruction in thread Guide Noobfriendly How to increase system partition size by [MENTION=5811506]gsstudios[/MENTION]

Post # 294 On Page 30 (and of course the entire thread)
[Galaxy S II Android Development] notknowntobeafcukgiver:
Thanks man, I really appreciate your advice. I think you have saved me from bricking the phone.

I wasnt sure what recovery to flash. you pointed at it http: //xdaforums.com/galaxy-s2/general/cwm-kit-kat-compatible-t2546597

philz kernels are here http: //xdaforums.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270 but they seem to be made for stock roms, not sure which one is good for cm9 so I may skip that step

Thank you
[Galaxy S II Android Development] Saber:
OP updated

I have removed redundant steps in the flashing guides and improved the overall flow by indenting the different sections of the guide.

gsstudios
[Galaxy S II Android Development] Saber:
Tuning guide has been updated

Guides have been separated for performance or battery life tweaks. I have added a few extra tweaks to the guide.

gsstudios
[Galaxy S II Android Development] Malantur2928:
Currently I am using CyanogenMod 12.1-20160115-NIGHTLY-i9100 which means I don't have isorec support.

I want to update to CyanogenMod 13 and I don't know how I should continue, how do I get isorec working on my phone?
[Galaxy S II Android Development] silvers01:
i'm little bit confused..in OP step 1, it is said: "back-up first, If you are using Cyanogen recovery from CM12.1, you should flash isorec recovery from this thread."

i'm currently on RR LP 5.1.1 r26 with your dorimanx kernel v12.0b001

do i need to flash isorec first? and then flash MM rom (i want to use RR MM rom), then gapps, then flash isorec again, reboot and done?

btw, MM roms do comes with isorec compatible kernel right? so i dont need to flash other isorec kernel?

another thing, what do i need for recovery, TWRP or CWM?

btw..im already done in repartitioning long time ago, i used 1gb3gb pit.
[Galaxy S II Android Development] :
Which recovery do you have now? If StanTRC/CWM, you just need to flash TWRP 3.0.2-0.zip from the TWRP thread or 2.8.7.0 from HERE then update(if you want the latest) with the 3.0.2-1.img

You only need to flash the isorec recovery you want once. It will stay in the recovery partition and will survive any new rom flashes and clean wipes(system, data, cache etc)

Correct. TWRP is up to date. CWM stopped being updated a while ago. You may find issues flashing certain .zips with CWM(like open gapps), but CWM is less buggy when it comes to things like formatting and reading certain filesystems. CWM will still flash current roms AFAIK
[Galaxy S II Android Development] silvers01:
i've downloaded this one: recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip ..so i need to >flash that zip

>after flashing, reboot to recovery

>flash img to update twrp

>reboot to updated recovery

>flash rom, gapps

and then no need to flash twrp isorec again right? coz it will survive any flashing, as what you've said.

thanks :)

edit: yep, my current recovery is cwm/stanTRC

edit 2: i've just read somewhere, some people are still in stock recovery after flashing rom(rremix M) while they are using isorec twrp

so..to be sure..i need to flash again isorec after flashing rom? ..soo confused xD
[Galaxy S II Android Development] :
Yes, this is correct. The flashing rom and gapps step can be done from any compatible recovery(all those you mentioned are compatible). But yes, what you have written will work and no need to flash isorec recovery again ever unless you want to disable it or change it.

The isorec recovery will boot if the kernel is isorec compatible. No, you won't need to flash isorec again, but if the kernel is not compatible, it will ignore the isorec recovery and boot the bundled recovery that is built in the kernel. The isorec recovery will still be there, but will not be used
[Galaxy S II Android Development] silvers01:
thanks.. i'm now on RR M rom, got no problem at flashing. recovery is still twrp3 :)
[Galaxy S II Android Development] GreekDragon:
delete
[Galaxy S II Android Development] Delnjaye:
PAINED

please help.. i cant access root already set it on the dev opt nothing happens, no SD card found, Tried to restore factory gets error, cyanogenmod recovery mount / system does not work, cannot download from the browser, and busted usb port. Ive tried Adb over network still no use to push file like in the post Lanchon did nothing happen twrp didt flash though its been pushed. is still there a way to change recovery via wifi?

:crying::crying::crying::crying:
[Galaxy S II Android Development] Saber:
1. Root might not be working because you may have selected yes for 'fix root?' in the recovery. You need to select no.

2. You need to get your USB port fixed ASAP (if possible). Situations like this will be much easier to solve if you have working USB port, otherwise the risk of bricking your device is higher.

3. Recovery can only be changed through the described methods.

gsstudios
[Galaxy S II Android Development] the.gangster:
Hi [MENTION=5811506]gsstudios[/MENTION]

as you are constantly updating this guide :good: I have a look on the OP from time to time.

So here are some thoughts on what from my point of view could still be added/corrected/improved.

Just to keep efforts as small as possible if one day a snapshot version should be released. (LOL, I don't want to make a bet on how many posts per day would be dropped here then again).

So maybe you have a look @

Instead of linking "Recommended GApps" to the wiki (where nano is linked) and tell users to select pico on OpenGApps page it might be better to link directly using following URL:

http://opengapps.org/?download=false&arch=arm&api=6.0&variant=pico as this would choose the correct architecture, Androidversion and variant, no matter if the user already visited the page for other platforms, so it's even more noob-safe. (As the wiki can't link to it in such a way as it has to be valid for all CM-supported devices)

That's still linked to the old closed developer thread. Better use links to Lanchon's GitHub or the new discussion thread here on XDA (or even both).

In 99 percent this error occurs, when people used ODIN/PIT method to repartition and did not format emmc afterwards.

yet another option should be to "flash" the Repit.zip without providing partition configuration (as it would default to same and keep, performing just filesystem checks and trim)

But that just for info. Maybe we shouldn't add that to a noob-guide, as the zip would have be properly named for that, not to accidently kill data.

... and you better have a working USB subboard then.

;)

BLN is d i s a b l e d by default.

I assume the effects of preventing device from deep sleep are even bigger here than just the current for the LEDs. Once a notification occurs the device is kept awake (as it is not a BLNWW implementation).​
[Galaxy S II Android Development] Saber:
Done.

I have updated the guide as per your suggestions.

I don't know why I didn't spot these a while ago ;)

gsstudios
[Galaxy S II Android Development] AzPerfect:
Hello friends, i want to resize the partitions of the internal sdcard of my s2 i9100.. but i don't have access to a computer.. so i wonder if is there any way to resize these partitions only via recovery ??! ?
[Galaxy S II Android Development] the.gangster:
Congrats for your first post!

Yes there is.

I wonder if you read the Opening Post of this thread before you decided to post in here. There are some repartition guides in there. One explicitly telling you, that no PC is needed for that, so choose wise. ;)
[Galaxy S II Android Development] anorakophobia:
Hi,

sorry I am new to the forum, but installed already some 12.1 nightlies ago, so thanks for your all great work!

But I do not manage it to update to cm13.

I tried now for several days to follow exactly the steps, flashing different kernels (isorec kernels as mentioned in the guide) and recoveries (up to TWRP 3.0.2-1) in all different combinations and orders, downgraded successfully back to my last cm12.1 version from febrary 20160203 and started several times from there (also with the cm recovery), and still have no luck.:(

I also tried the last nightlies of cm13 from 20160719 to 21 (newers are bugged), and verified their checksum.

I always formatted data/system/cache before and tried the isorec disabler before.

I was able to flash the cm12.1 from 20160203 successfully in any situation, so I think there is no hardware error.

The problem is in all cases, that if I flash a cm13 nightly, the recovery gets stucked in "Patching system image unconditionally" while installing. I waited also sometimes several hours.

The main question now:

Does anyone has an idea, what I possibly have done wrong or what can be wrong?

If something is wrong with isorec stuff, I thought it would not even boot to recovery or something. Or is this problem known if I have something done wrong with isorec?

The system partition is only 500mb, but the data partition is increased to 4,5gb. Is system partition too small?

I thought I would have problems then with gapps, but it not even flashes cm13

Thanks! :)

---------- Post added at 10:31 PM ---------- Previous post was at 09:49 PM ----------

ok, directly answering the question to myself ;)

After writing my question and with the system-partition size I then thought ok lets increase the system partition size ....

Good idea, because it worked ;)

Now flashed successfully and booting cm13, let's see how it runs.

Sorry to bother you ....
[Galaxy S II Android Development] the.gangster:
Meanwhile you managed to get it running, but want to answer/comment some of your questions nevertheless:

I guess you must have mixed up something here. The flashscript will only mount partitions mmcblk0p9 (system) and mmcblk0p10 (data) but not mmcblk0p8 (modem) before "Patching system image unconditionally".

No need to flash the IsoRec disabler unless you want to disable an already flashed IsoRec-Recovery on an IsoRec-supporting kernel.
[Galaxy S II Android Development] Saber:
Tuning guide for CM13 has been updated

See the post for details.

gsstudios ;)
[Galaxy S II Android Development] i91004ever:
OTA

I tried to update cm13 over OTA and it didn't boot and I also couldn't boot into recovery mode, so I had to start from scratch. One question, should I enable "Update Cyanogen Recovery" in the developer options? I'm asking because I had enabled it before I started the update. Back in cm12 I had it on and didn't experience any issues.

Edit 3. Can I just flash the newer ROM from recovery and that would count as an update?
[Galaxy S II Android Development] Saber:
You should leave this option disabled as Cyanogen recovery should always be avoided. Isorec recovery TWRP is the only recovery we should use nowadays.

You should flash CM13 again manually in recovery. If it still doesn't boot, you may need to wipe cache and/or data.

gsstudios
[Galaxy S II Android Development] i91004ever:
Thanks for the quick reply! However, I wasn't clear enough. My phone was soft bricked and I re-sized my partition and flashed twrp via Odin. Then I flashed CM13 and gapps via recovery. I wiped all my data. But that's no problem as I keep all my data on Google Drive. That's all good. But do I need to flash TWRP recovery again after I have installed CM13 (because the TWRP recovery was overwritten with Cyanogen Recovery after I flashed CM 13) before I proceed with OTA updates?
[Galaxy S II Android Development] Saber:
When you flash CM13 manually via recovery, TWRP is not overwritten (making sure you had proper isorec TWRP beforehand). If currently you have cyanogen recovery, I highly recommend flashing TWRP to avoid any further issues that you might encounter. After that, you may try OTA updates. IMO, it's better to flash a newer nightly manually in recovery vs OTA.

gsstudios
[Galaxy S II Android Development] i91004ever:
Do I need to format anything prior to flashing or afterwards, or to wipe dalvik cache or something?
[Galaxy S II Android Development] the.gangster:
[MENTION=7681136]i91004ever[/MENTION] [MENTION=5811506]gsstudios[/MENTION]

just want to point out once more, that the developer settings option "update CM-Recovery" does not affect anything. Tested here.

[MENTION=7681136]i91004ever[/MENTION]

As you flashed a TWRP Recovery by ODIN you simply never flashed an IsoRec version. That's all. Otherwise, once flashed it remains there forever as it is not touched by any of the usual actions. That's one of the reasons why an IsoRec-disabler was published to "destroy" the IsoRec relevant header information in the Recovery-Partition.

Apart from that all information should already be given (or linked to) in the first posts of this thread.
[Galaxy S II Android Development] i91004ever:
Hey, that's quite interesting. I wonder why the option even exists.

Well, I must be doing something wrong then. I flashed the "kernel lanchon trim freezefix twrp" that was linked on the first page then via TWRP recovery I flashed CM13. After that when I went into recovery it said Cyanogen Recovery. Should I now flash an IsoRec version via Odin before doing anything else?
[Galaxy S II Android Development] the.gangster:
[MENTION=7681136]i91004ever[/MENTION]

the option exists as there are other devices that really make use of it.

And yes. That's what I said. You are doing something wrong there. But even that is covered in the OP. I'd use method 3 now to go on....
[Galaxy S II Android Development] i91004ever:
NEVER MIND, MATE. Thanks so much for your help. I figured it out. I just had to flash that recovery after flashing CM13 and bingo! Cheers :)

P.S. One HUMONGOUS advantage to having all your files on the cloud is that setting up my phone takes a couple of minutes and I can always start from scratch! :)
[Galaxy S II Android Development] Peterlymo:
Can i get philz recovery for Gt i9100? This phone running JB and it has dorimanx kernel?
[Galaxy S II Android Development] indiyet:
Hi to all!

First of all i wanna thanks to [MENTION=5811506]gsstudios[/MENTION] for the very simple and easy guide.

I flashed this CM13 on my S2 (reparticioned first) and all runs fine untill i tried to connect to my Wifi Network. I get the "Autentification Error" and does not connect it. Ive tried many times the password and still get the same error. The Wifi works fine (tried from another fhone). Also restart the modem many times without Success.

Can somebody help me?
[Galaxy S II Android Development] Saber:
Hi,

Can you provide more details about your network? e.g. Are you running 5ghz or 2.4ghz wifi (if you have 5ghz, try restricting to connect 2.4ghz Wifi)? Have you tried shortening your wifi password just to see it can authenticate? Did this happen before you upgraded to CM13? Make sure you are running WPA2-PSK and not any other authentication methods.

gsstudios
[Galaxy S II Android Development] EMONESSboy:
anyone tried the new oficial nightly build cm13. (build5/9/2016)...?

---------- Post added at 11:08 AM ---------- Previous post was at 10:48 AM ----------

reboots when recieving calls is seems a major issue hmmmmm will install it when it ill be fixed
[Galaxy S II Android Development] Saber:
This issue only happens to some people. I never experienced this issue in my testing.

gsstudios
[Galaxy S II Android Development] indiyet:
Hi, thanks for the answear. Im using 2.4ghz.. already tried wiht 5ghz but still get the same error. Sometimes i get this error before to update to CM13 but always connect after without problem.
[Galaxy S II Android Development] jojobg:
Was on 5th for less than a day and no reboots on calls.

On 6th since 12+ hours on primary corp. phone, no reboots all day long, I had enough calls also.

P.S. at all, sorry guys just realized that this is totally off topic for this thread.