yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] TriboDoP:
The basic idea to get around the homebutton is to root with an app and Then use an app which enables you to enter recovery or download mode.

I can give specific details only for i9100, so you should look in s2 + forum.
[Galaxy S II Android Development] dinos3:
Are these still problems, or post is not updated?
[Galaxy S II Android Development] Saber:
The problem should still exist in the latest nightly build. I haven't updated the OP for a while, but may not need to do so until CM14.1 is official :)

Saber.
[Galaxy S II Android Development] Damna:
root glitch cm 13 again

I have cm 13 on i9100 and it works perfectly, with root. in the beginning i was unable to access root, flashed again the rom and got the root. now i flashed cm 13 on a i9105p and the same problem occurred. cannot access root, flashed again but this time it is not so easy. any suggestion?
[Galaxy S II Android Development] dinos3:
http://rootmygalaxy.net/enable-root-access-on-cm13/
[Galaxy S II Android Development] Damna:
yeah forgot to say that i unlocked the developer options and enabled root for apps and adb, but still no root

moreover.. cannot download files from any browser. :(
[Galaxy S II Android Development] blue whale:
How do I root my i9100 on cm13 ?

i used this

Root on Android Marshmallow

CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.

but rootchecker and titanium backup tell me that the phone is not rooted. I cannot use titatnium at all....

I tried to install supersu v2.78 in twrp, but it does not install anything....

In fact, now ''root access'' shows me only ''deactivate'' and ''only ADB''. i lost root for apps apparently.
[Galaxy S II Android Development] Saber:
Try reflashing CM13 again.

Don't install SuperSU because it doesn't work on stock CM13.

Saber :cowboy:
[Galaxy S II Android Development] arnab:
I will bring it soon. My mom was sick with low haemoglobin count and was hospitalized. So i was quite busy and will be throughout December.
[Galaxy S II Android Development] the.gangster:
In that case, you should forget about BLNWW and care for your mother first, no matter how long it takes for her to recover.

Wishing her all the best.
[Galaxy S II Android Development] blue whale:
this time it worked !
[Galaxy S II Android Development] RC.Conan:
Hello, after upgrading my s2 i9100 to cm13 the phone is usless now : when i try to apply a zip from sdcard0 it says installation aborted, i tried to flash the stock rom via Odin but the phone is not reconigzed by any PC and i tried more than 5 USB cables, i cannot install any apk file from other markets or from the ones that i have downloaded from the internet. please please please help me an thank you !!
[Galaxy S II Android Development] TriboDoP:
Hi

Did you update according to op?

Repitted and formatted properly and installed isorec twrp?

Can you use the recovery (which one is it)?
[Galaxy S II Android Development] RC.Conan:
Hi, when i updated the phone i was using cyanmo recovery and cm12.1 rom, i updated to the 1st build of cm13...About the recovery i can't flash any zip file i can only use it to format the phone...
[Galaxy S II Android Development] TriboDoP:
You have to flash another recovery with Odin.

Using odin anyway you should increase System partition with one flashing:

- in Odin Flash pitfile 1 GB system _4GB Data together with Gustavo Kernel KK with cwm Recovery.tar

(Do Not forget to tick on repartition).

- in cwm Recovery format: "mounts and storage/format sd0 (internal sd)/select default"

Then

- Format Data/Cache/System in mounts and storage

- Install Rom + gapps + recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip in one go !!

Do not reboot in between!!

- reboot system
[Galaxy S II Android Development] RC.Conan:
I tried to do that but the phone is not reconized by any pc ( many computers and usb cables )... i also tried by using adb but same thing... i connected to adb using wifi but i don't know how to use it...
[Galaxy S II Android Development] TriboDoP:
Maybe this works:

put latest cm 11 unofficial 20161119 by zjq985062714 on micro sd.

In cm recovery try "apply update" and choose the cm11 rom.

If it works we could continue repitting and all necessary steps.

Just try and tell me
[Galaxy S II Android Development] RC.Conan:
I can't apply anything. Everytime i try to do that ( over the intern stockage or a micro sd ) i get : installation aborted without even showing the files i formatted the phone but nothing ...
[Galaxy S II Android Development] TriboDoP:
Well, the only thing left is to get the connection pc to device working.

I know you already dried hard everything possible.

Remove usb drivers from pc and re-install them again. Use again different pc preferable windows 7. Try other odin versions.

try all usb ports available on all pc's. Again keep changing cables. If the usb connector on s2 is not broken, it should be able to get working.

I wish you the best.

(And adb with wifi has to be enabled in the first place on device)
[Galaxy S II Android Development] RC.Conan:
I will do my best... thank you for your time :)
[Galaxy S II Android Development] asia559571:
kernel
[Galaxy S II Android Development] Namoi:
The provided kernel which comes with cm13. Didn't tried cm14.

What problem do you have?

Of course you need root for it to work.
[Galaxy S II Android Development] Damna:
Does anyone know an "easy" thread about changing the boot screen logo [the zone before the boot animation] on the s2 with cm13? I see a lot of threads with tools to pack/unpack the boot.img but since it is an easy-to-brick procedure id like to follow a safe step-by-step guide. Thanx.
[Galaxy S II Android Development] TriboDoP:
[MENTION=5117944]PackElend[/MENTION]

Hi

Was just going to write to you as i saw there is a guide/tutorial for this.

https://xdaforums.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
[Galaxy S II Android Development] PackElend:
I followed the tutorial and now running RR 5.8.0 :good::):D
[Galaxy S II Android Development] ringen00:
boot logo again!

Hi guys!

Was on 12.1 with isorec and trimming via tasker once a day.

The reason why i flashed CM 13 was that the phone, out

of nothing, was stuck on the boot logo.

I'm using the phone as a server sort of thing so it was

laying on my table when it got stuck on the boot animation.

I didn't do anything and this way it ran for quite some month now!

To get CM13 I reset to factory, flashed CM 13, flashed gapps and booted. Next I flashed the newest TWRP recovery.

I didn't care about the kernel.

Using kernel auditor to improve for speed and SD Maid to

clean up some temp files every now and then.

This morning again the boot logo! The phone was stuck!

Tried to wipe dalvik and cache from TWRP but it said

it couldn't get mounted or so - didn't find the partition.

I was able to repair the file system of system and data.

Later, I had the battery, sd-card and SIM removed, I suddenly

was able to wipe dalvik and cache and after that the phone

booted normally.

- Is it ok that the phone, when booting, stays quite some time

(minutes) on the boot animation?

I recognised with CM13 a new window after the boot animation. Appeared quite often the first reboots.

Looks like dalvik gets written...

Just started the phone again and this time it was really

quick! Boot logo very short, no optimizations!

- Will it with CM 13 still be making sense to use trimming

with Tasker every day?
[Galaxy S II Android Development] the.gangster:
[MENTION=5811506]gsstudios[/MENTION]

Cool that you brought the information together here. I've seen your links to this one and now a had a look at it the first time.

Really suitable for linking to the top 90% of requests in CM13 thread.

Yet, I would have a suggestion to enrich your part "If you are one of those users who forgot to flash Isorec Recovery when upgrading, this is what you need to do:"

As there is a really smart way to flash the IsoRec TWRP from running CM13, using dd command in terminal to write the image to recovery partition mmcblk0p6.

Again it was Lanchon who described what to do. You could link to that post.

Doing that, one could even flash it after ending up in the dead end of CM13 with CM-Recovery and even with broken USB-port, when unable to use ODIN.

That way is mentioned far too rarely so far but can safe a lot of work.
[Galaxy S II Android Development] Saber:
OP updated again with more suggested information. Thanks [MENTION=6560258]the.gangster[/MENTION]

gsstudios
[Galaxy S II Android Development] Acid0057:
Sorry if you want Google Apps you have to change system partition. If you follow directions exactly the risk is minimal. Look in the Op just after the install directions. I used Lanchons Method on three S2 so far and worked fine on all three.
[Galaxy S II Android Development] slax81:
Hi all, i have a problem after following this guide.

I did everything in the guide, used the 1/4gb pitfile, flashed the cm13 and isorec recovery.

But after everything went successful, i noticed that the sdcard0 is reported as damaged? I tried formating it, but it wont work.

Ext sdcard1 is good.

Maybe i can use Lanchon's flashable repartition zip to fix it?

Thanks for any help
[Galaxy S II Android Development] slax81:
I solved the problem with lanchon's script http://xdaforums.com/galaxy-s2/orig-development/tool-lanchon-repit-data-sparing-t3311747

First it failed with repartitioning sdcard partition with vfat sistem, so i've changed to ext4 fs and now sdcard0 is working.

From the log i saw the size of the sdcard partition is too big for the vfat fs.

Hope this helps someone
[Galaxy S II Android Development] fireburner-de:
Nope, FAT32/vFAT filesystem can have partitions larger than 4GB! The 4GB is the file size limit, not the partition size limit, which is at:

according to Wikipedia

So we are far from reaching the partition size limit, on our S2!
[Galaxy S II Android Development] s2ing:
.

hello,

is it possible to install xposed on CM-13 ?

found this but not sure about it.

http://xdaforums.com/showthread.php?t=3034811
[Galaxy S II Android Development] Ham1do:
Install Xposed v80 sdk 23
[Galaxy S II Android Development] erotavlas:
Hi,

I have a i9100 smartphone. Up to yesterday I had installed the latest version of CM 12.1 and it worked perfectly. Today I updated the system and now I have CM 13. It is very strange that the system automatically upgraded to CM 13 without any warning. However, unfortunately the google service does not work any more and I have to reflash it. I copied the latest opengapp file.zip via adb or via copy and paste into the internal memory and SD card, but I cannot install them from recovery. I read in the first page that probably the CM recovery is unable to detect the SD card.

So how can I install file.zip? Only via ISORec? I downloaded ISORec, how to flash it without data loss?

Thank you
[Galaxy S II Android Development] Dobber_S:
Hey [MENTION=5811506]gsstudios[/MENTION],

nice and informative guide!

The only info I'm still missing though is info on root and specificly SuperSU. I remember reading in the main topic a while ago that there was no working SuperSU version? Has this changed? if not: might be interesting to mention also, and that they need to stick to CM root for the moment (and as you mentioned: not "fix" root). Alot of users are used to just flash SuperSU and be done with it, so this is also something that can cause problems.

thanks for the great guide!
[Galaxy S II Android Development] Saber:
[MENTION=4995592]Dobber_S[/MENTION]

I've heard about SuperSU issues. Will add some info about it sometime soon.

gsstudios
[Galaxy S II Android Development] fubo73:
Hi [MENTION=5811506]gsstudios[/MENTION], I do not see any info when a dumb user decides to update to CM13 using faulty CM12.1 updater (that should not let updating to CM13:)) and then they get errors with gapps.

Just to be precise, I think user is dumb because when moving from one SDK to another a full wipe should be always done. But also, CM12.1 updater should not offer CM13 update :).
[Galaxy S II Android Development] nikunj87:
Guys, I am stuck with a CM 13 nightly and can't get past. Please help.

My S2 has CM 13 nightly from 5th Feb. This was the first time I installed CM 13. Now my phone boots up and all fine, but I cannot install gapps or any other nightlies or any other zip's. Booting into CM recovery doesn't give me an option to install any zip (just apply update, which doesn't work either). I am attaching a picture of the recovery, please help me recover from this.

Thanks,
[Galaxy S II Android Development] the.gangster:
This is a running gag.

Read post #1!
[Galaxy S II Android Development] erotavlas:
I have the same problem. The current CM 13 is not able to install update from file.zip. You need to flash ISORec in order to be able to install file.zip. You can download it here http://xdaforums.com/galaxy-s2/orig-development/isorec-isolated-recovery-galaxy-s2-t3291176 and flash via ODIN or manually via terminal http://xdaforums.com/showpost.php?p=65164875&postcount=1002
[Galaxy S II Android Development] nikunj87:
Tried the terminal editor way and I can now boot into TWRP. Many thanks. Can you help me how to (and the recommended partition parameters, size, etc) for installing gapps.
[Galaxy S II Android Development] erotavlas:
Have you tried without repartitioning to install gapp?
[Galaxy S II Android Development] nikunj87:
No, I haven't tried. Should I? I was just going by what everyone has written that it is advisable to partition.

Thanks
[Galaxy S II Android Development] TriboDoP:
a noob-way to get rid of the cm-recovery and beeing able to flash any zip file without using odin or terminal:

- copy latest cm11 nightly on sd-card

- in cm-recovery "apply update" and flash the cm11 nightly and DO NOT REBOOT!

- take the battery out and in again.

- reboot into recovery by 3-buttons combo an you will have now CWM-Recovery (from cm11)

- make full wipe and install cm13 AND isorec recovery AND the gapps IN ONE GO!

- reboot system

(worke fine for me beeing on cm12.1 an should work an cm13 aswell)

of course if you did not flash the repartion file 1GB4GB before all that it will not work.

That is what this thread is all about.

Many thanks [MENTION=5811506]gsstudios[/MENTION] for this wonderful guide!
[Galaxy S II Android Development] erotavlas:
Why not?
[Galaxy S II Android Development] the.gangster:
Nice that you wanted to contribute with your first post (welcome!), but you should have really read here before posting a solution that will not work.

CM13 CM-Recovery does not give you the chance to flash ANY ZIP AT ALL.

---------- Post added at 03:20 PM ---------- Previous post was at 03:13 PM ----------

Maybe: Because he doesn't want to waiste our time any longer and do it right, right away? Why trying something that won't succeed? To fill this thread?
[Galaxy S II Android Development] nikunj87:
Guys, I tried flashing gapps before partitioning with no success (file space error). Then after using Lanchon script to repartition system, I was able to install ARM gapps 6.0 pico version but it force closes constantly. With support from this thread, I am almost getting there... just the last bit to sort out. Any indications as to why gapps (setup wizard, itself is force closing). I have tried reinstalling the rom and gapps multiple times, clearing cache, etc.

Thanks,
[Galaxy S II Android Development] laserkater:
Has anybody tried to intentionally dirty flash cm13 and gapps (after repartitioning, of course)? What were the results?
[Galaxy S II Android Development] erotavlas:
Thank you for your reply. So cannot I flash gapps without repartioning and so reinstall and reconfiguring all apps? Can I only use aptoide? However, it is not my fault if the OTA upgrading system manager automatically decides to install CM 13 without asking user permission. I would not upgrade to CM 13 because I know it is not stable, but I would only update to latest CM 12 since I reported some bugs and I would like to see if they will be fixed.

Why has been chosen to add CM 13 on the OTA, even if CM 13 is not stable?
[Galaxy S II Android Development] fireburner-de:
Every time a major version change was made, new nightlies were in the same update channel. So one should have known that already.

Official CM12.1 won't be updated anymore. Version from 3rd February is the very last official CM12.1 nightly.
[Galaxy S II Android Development] the.gangster:
[MENTION=5832907]erotavlas[/MENTION]

start reading, please.

If you are on stock size of system-partition (512MB), even the smallest OpenGapps-PICO package will fail.

For the rest of your questions, read Post 1 twice. There are ways to preserve everything you have....

And don't blame the update manager. It was your decision to activate it! So live with the results.

Anyway: everthing is described here already. It's not that hard. But reading is the minimum prerequisite for saving your day.

---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------

In TWRP: Try wipeing your system partition and reinstall ROM and GApps once more (all in a row)
[Galaxy S II Android Development] erotavlas:
Thank you again. If know in advance, I would not update to CM 13. I updated as usually. Maybe could be add a confirm check. Do you confirm to install CM 13? Now I have to waste my time to read the thread and follow all the procedure.
[Galaxy S II Android Development] nikunj87:
I have finally managed to get MM with gapps working. The only step I was missing (mentioned in one of the post somewhere) is to install the CM Rom and gapps in one go (i.e. without a reboot in between). If the device is booted in between the rom and gapps installation, the device will be plagued with force close errors. This is something to do with permissions required by gapps in MM.

Hope this helps someone.
[Galaxy S II Android Development] Ham1do:
Backup your apps with Titanium Backup ( choose ext SD direction ) ,follow instructions from 1st post especially the 5th one ( 1GB system required) , then restore
[Galaxy S II Android Development] Klitoni:
Great info right there bro !
[Galaxy S II Android Development] speedbirdengineer:
Hi Mate. It seems on my phone file explorer, root explorer both can see & explore my sd card. But when I connect phone to PC my GT-I900 on PC opens with I think internal card only (cannot see the internal card & sd card separately) & I cant paste anything in it either as it gives an error. Can someone pls tell me what am I doing wrong?? Read somewhere before I need to give permissions to sd card, but if that was so it wouldn't show up and I wouldn't be able to explore my sd card. I have the isorec recovery and all the works needed, but this PC issue is the only one I am having problem with. Some guidance will be appreciated. Cheers.
[Galaxy S II Android Development] Saber:
OP updated with some suggestions from a few users.

A few of my own additions were added to the guide as well.

Thanks, gsstudios

Update: The FAQ section is out! More to be added in the future.
[Galaxy S II Android Development] pacmanman:
Hi man, can you add link to JOdin for Linux users? I have used it to partition and install kernels, works great.

link: https://jodin3.casual-dev.com/

latest versions: https://builds.casual-dev.com/index.php?dir=JOdin3/

Greeting
[Galaxy S II Android Development] Saama:
can someone help me a little? I've read a lot of posts, and although I’ve encountered info on the matter, I find it very confuse. So if a good soul could help me by providing both links for files and info on how to proceed, that would be great.

i've read and done everything right with a 1gb sys/6gb data/7gb sdcard0 media. Now i want to go further. I really wanted to use a pit that can be 1gb sys 12gb data and emulated sdcard0 from something like /data/media. Problem is, although I have read the OP from which this new tread comes from, and search the topic, I cant get it right.

I got a pit from a different tread which is 1gb sys/12gb data. I’m using Gustavo cm12.1-kernel-22-06-for-ODIN at the same time I pit it. Then I’m flashing CM13 OFFICIAL nightly from 2 days ago, 02/14, Open Gapps pico for ARM 6.0.

I format sdcard0 in the CWM default (not ext4 or any other option) successfully, then mount it successfully, and after that, I do the same with data, cache and system in this order successfully. And after, I use Gustavo cm12.1-kernel-22-06-for-ODIN again because the CM recovery that comes with the CM13 is too restrict.

Problem is: sdcard0 is corrupted. I get that maybe its because it is a 0gb partition, but I was expecting that in CM13 it would be emulated by default (I don’t remember from where I got this idea, but it was based in xda during work reading.) and appear as it was not corrupted.

Well, I wanted to use it to store media. I wanted the 12gb partition to work sharing space between data end emulated good-to-save-in-media. can it be due to CM13? An unofficial would do the trick?

Someone? Thx for the patience of reading it all.
[Galaxy S II Android Development] feriber:
I think there is another THIRD way to flash isorec recovery, at least is the way i used, as the "terminal" way did not worked for me.

I did a sideload flash of recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip.

I my case I needed to update my Windows drivers, and my adb.exe files from HERE.

Once installed, in Cyanogen stock recovery, I selected sideload install

In a Windows command line window, in a folder containing adb.exe (and associated files), and the zip file with the recovery, just need to run:

adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip.

This is the way i flashed this recovery.

Afterwards, I could run into this recovery and UPGRADE my tk_gapps-modular-mini-5.1.1 with the new open_gapps-arm-6.0-mini, (I already had my phone repartitioned, and the script is able to delete old versions and install new ones. The only old app it has not deleted/updated is Street View, but it runs OK), and finally the phone started running perfectly with CM13.

I hope this will help as is a very simple way to update recovery.

Of course thank you very much for your work making this thread (if it would exist when I updated form CM12, to CM13, I would not learn a bit more about our phone ;) )
[Galaxy S II Android Development] Saber:
[MENTION=657872]feriber[/MENTION]

Thanks for the suggestion, will add adb method soon. You didn't have to quote the OP :)

gsstudios
[Galaxy S II Android Development] TriboDoP:
Thanks [MENTION=6560258]the.gangster[/MENTION] for your reply!

I made 2 mistakes:

1.) Things that worked on cm recovery (on cm12.1) do not automatically work on cm recovery in cm13

I should have tried it myself (but all mm`s i am testing are of course on twrp)

2.) i did not read properly the op ("cm-recovery is not able to mount sd-card" an other info)

because i never use cm-recovery - so had never any troubles when testing all available mm roms.

I am very sorry for having spammed this thread!
[Galaxy S II Android Development] _followers_:
hello guys im in badly need your help, i know how to flash everything from kitkat until M rom but my problem is my wifi connect, no internet then connected after a second it say SAVE then CONNECTED again did i miss something...all of M's ROM same problem in me. is there anybody can help me how to fix this problem? thank you in advance ;)
[Galaxy S II Android Development] Dark1Angel:
Hi! how do I set selinux to permissive? I've searched kernel adiutor and haven't gound the setting
[Galaxy S II Android Development] Saber:
There should be a tab called plugins. Click on the download button then confirm to download the selinux changer. Install it like a normal app and it should appear in the plugins menu of kernel adiutor.

gsstudios
[Galaxy S II Android Development] Saber:
OP updated with ADB method of isorec install while in cyanogen recovery.

A few cosmetic changes were done to the guide as well.

gsstudios