yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] MaTSuNg:
Well thanks guys for pointing me in the right direction, indeed a lot of information would have been fun to know ahead of time. But here is MY take on the subject, after years of using CM in different versions and also updating through the "OTA" as you call it. I've rarely had an issue! That being said I'm not really a LATEST VERSION nerd/fanatic and when it comes to "If it ain't broke don't fix it" Age has brought me that through experience as well. But this morning I was a little fed up with the random reboots on the 12.1 and figured its been quite a while since I last updated so I decided to TRUST the incorporated UPDATE setup and this is what resulted. I'm familiar with updating roms, I'm familiar with using Recoveries and flashing Gapps been doing it for a while on different phones.

Now to find out that FIRST of all the actual memory card mounting feature is "broken", the issue seems to be a KNOWN FACT, why is the OTA still offering the update? Why haven't we suggested to temporarily turn off OTA On certain devices that we are aware of those tell tale situations that "so many users" seem to post about. It saddens me to find attitude saying something like : YOU SHOULDA DONE YUR HOMEWURK BEFORE YOU FLASHED.. I followed the procedures that worked for me 100% of the time in the past sometimes in life its not always a BAD thing to trust something you know works, and stop rechecking and making sure 50 times before you take action. Still am very greatful for forums like these to guide us I'm not trying to be a troll at all.

Now on to fixing the problem the GUIDE mentions what to do as if you were the smart guy who went and read the guide, what about those in my situation ? Is there a way to fix the problem AFTER you're stuck with it?

From my point of view, injecting a functional recovery through ADB, repartitioning my system, and reflashing CM13? Have i got the "Main idea" is there something I'm missing out on ?

I have a difficult time understanding in what order they SHOULD or HAVE to be done in "my situation", as of right now my CM13 works "fine" the only thing that's wrong with it is GOOGLE PLAY SERVICES HAS STOPPED WORKING "OK" every 10-20 minutes (4 times) before it stops. And of course the infamous recovery..

Edit : I also would like to point out that I manually went and got an APK for google services and used their "number charting" to figure out which one I would need with my phone (android 6, ARM, and "no DPI" or universal as we could say) the apk prompted an updated upon clicking on it and went on for like 5 minutes updating slowly and then claimed it was updated. Still get the crash issueo n the google services does that mean I need to upgrade the STORE also? Why wouldn't updating it manually work? Thanks

Thanks again! Really appreciated
[Galaxy S II Original Android Development] Lanchon:
man you are completely off topic here. and waaaaay off mark too... your previous lucky update-in-the-dark experiences are completely irrelevant: either read or dont update. or update without reading a single word and break your phone, and then see how much we care. yes, we know exactly what happens when you do what you did, thank you for telling us anyway. now please get back on topic, which is isorec, or please post elsewhere. btw, you posted here with evident complete ignorance of the thread's OP. on XDA you are required to read the OP before posting in a thread. please respect other people spaces and time, thank you.
[Galaxy S II Original Android Development] Lanchon:
guys i know you have the best intentions to help, but u r actually not helping the big picture. if someone starts an OT conversation -especially one discussed elsewhere already- you should just reply "this is OT". otherwise you do even more OT. and the user has to FAIL until he does things right. let them search! same thing when they ask for something that has already been answered 20 times in the same thread: "use search". dont spoon feed, their strategy has to fail for them to change. no to mention spoon feeding messes up the thread too. just saying. thanks!
[Galaxy S II Original Android Development] the.gangster:
[MENTION=4445692]MaTSuNg[/MENTION]

start with "3. Terminal method (Doesn't require PC)"

-> result: working IsoRec-Recovery

go on with "Lanchon's guide": http://xdaforums.com/gala...aring-t3311747 (who has actually moved his project to github)

-> result: 1GB System partition (all data preserved, except for preload partiton which is unused if you are not using DorimanX dualboot)

last step: get OpenGApps Pico Package as also explained in the OP of the linked help-thread.

Flash it in TWRP recovery. If it fails with #40, wipe system partition and flash CM13 + GApps in a row. You can look up the error codes here

-> result: you have GApps installed and all data preserved.

EDIT: Sorry, I also just realized what thread we are in. Maybe some mod can move that accordingly.
[Galaxy S II Original Android Development] Acid0057:
[MENTION=4141005]Lanchon[/MENTION] kinda starting to agree with you here. BTW thanks for IsoRec! Awesome work.
[Galaxy S II Original Android Development] MaTSuNg:
Thanks Gangster for being a much more human than what I've seen so far!!!

Gangster back to you

I went for the ODIN method "2. ODIN method (requires PC)" and flashed "kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100-for-ODIN" it was successful but the instructions state to boot back into recovery and start the CM13 guidelines without backup, which would make sense but it does NOT boot into TWRP I still get the broken CM Rec. so what step am I missing for TWRP to work?

Thanks
[Galaxy S II Original Android Development] wdevil12:
If you searched through the cm13 thread and couldn't find google services stopped posts, you better do your homework. Don't bother the dev who willingly publishes all this stuff for free.
[Galaxy S II Original Android Development] :
[MENTION=4445692]MaTSuNg[/MENTION]

Gangster back to you

I went for the ODIN method "2. ODIN method (requires PC)" and flashed "kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100-for-ODIN" it was successful but the instructions state to boot back into recovery and start the CM13 guidelines without backup, which would make sense but it does NOT boot into TWRP I still get the broken CM Rec. so what step am I missing for TWRP to work?

Thanks[/QUOTE]

Be Nice to people please, I know you are frustrated at the lack of help but aggressive posts like this are going to lead to a flame war

Cm problems should be reported in the cm thread this thread is for recovery only. If you are not finding much help try asking a question in the Q&A forum I think you will get more assistance there

Moderation Team
[Galaxy S II Original Android Development] Spyr0s:
In the last weeks there has been very serious breakthroughs in i9100. We have now have everything that we've dreamed for years. Seperate recovery from kernel, most reboots fixed, trim, features and instead of thanks we have users that refuse to do their homework and some users that want to use strange combinations of outdated OS like cm12.1 with new recovery like TWRP 3.0.

Lanchon and others should not answer at all in questions regarding CM12.1, TWRP3.0 and old IsoRec kernels. if users want support they should update to CM13 by following the guides, which is stable and fine. CM12.1 is dead, long live CM13.
[Galaxy S II Original Android Development] cherryb8844:
Hello [MENTION=4141005]Lanchon[/MENTION]

I didn't Read all of those post you all DAVs talking about how to reach custom recovery and kernel recovery I think that was already someone posted or not I don't know but I prefer when I need to go in twrp so I use reboot to recovery from power manu or when I want to reach cyanogen recovery so I want to do this turn off the phone hold power button+volume up+home button
[Galaxy S II Original Android Development] the.gangster:
yeah, go ahead and rewrite all the guides to reflect that.

And once doing so, also explain to all, why first all ROM maintainers are welcomed to merge the patches to support IsoRec recoveries and why shortly after you won't support them at all. LOL.
[Galaxy S II Original Android Development] Whiskey103:
Thread cleaned. Please stay on topic and answer your questions in the appropriate thread.

Whiskey

Forum Moderator
[Galaxy S II Original Android Development] Synvani:
Hey all,

Happy user of CM13 with IsoRec CWM for a long time now.

I've been thinking about moving to TWRP instead - question about that as I'm a little unsure about the procedure:

Do I need to flash the Disabler first, and then flash the TWRP IsoRec?

Or maybe I could just flash the TWRP IsoRec straight from my current recovery and all should go smooth?

Thanks in advance!
[Galaxy S II Original Android Development] Acid0057:
[MENTION=7334963]Synvani[/MENTION] just flash the twrp isorec. What Rom recovery are you currently on? You also need to make sure it's kernel supports isorec
[Galaxy S II Original Android Development] Synvani:
Hey [MENTION=5173535]Acid0057[/MENTION], thanks for the reply,

As I said I am on CM13 latest nightly so everything is compatible, and I've been using the CWM IsoRec with it so far.
[Galaxy S II Original Android Development] Acid0057:
Sorry missed that part. Then yes just flash the twrp isorec file directly from cwm recovery.
[Galaxy S II Original Android Development] Creativ3ady:
Don't know if I need isorec

I updated via OTA. Stuck with useless CM recovery. I had CWM before update. System says "storage: 413 MB total used of 1,97 GB". The only thing missing is CWM to install gapps. Anything I do...gets me to recovery. Any advice? Already on latest CM13 with wipe everything done :)

Forgot to say that I installed CWM and I tried to flash with it. Boots up, starts installing. Interrupts and reboots back to system. Loads CM13.
[Galaxy S II Original Android Development] LeBourrin:
CM recovery is useless. You have to install an ISOREC recovery in order to have CWM or TWRP

Everythings is here : [GUIDE][NOOB-FRIENDLY]Want to update to CM13? Read this first!

Jump to section "If you forgot to flash Isorec Recovery when upgrading"
[Galaxy S II Original Android Development] Creativ3ady:
Thank you !

Thanks for the quick reply.
[Galaxy S II Original Android Development] MaTSuNg:
Make sure to use the right ISOREC Recovery/Kernel versions I did an OTA flash too this week and after flashing a TWRP recovery phone booted once, tried to optimize apps for a while and then wouldn't boot anymore. Maybe its an isolated CASE but I would suggest you start over completely (Are you repartitioned already for the Gapps problem?)

If you are repartitioned, flash TWRP ISOREC 2.8.7, wipe data/cache/dalvik, flash CM13, Gapps 6.0 and you would have a clean setup. Unless you are more lucky than I was and just flashing a new recovery solves the problem!

Good luck have a good day.
[Galaxy S II Original Android Development] AlennGK:
What should I do with

ERROR: Failed to access device. libusb error: -12

error?

i.imgur.com/2JzD6CB.png?1
[Galaxy S II Original Android Development] yupo72:
Hi all,

this morning I've updated the CM13 and then, don't ask me why, I rebooted into Recovery and re-installed kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100.zip....well, now the phone is in loop and after updating apps it restart with CM blue face and again.

Not much a problem as I had a backup, btw, what could have been happened?

Thanks
[Galaxy S II Original Android Development] DevisG79:
Boot into recovery.

Wipe System,cache and dalvik.

Flash latest nightly but not 20160323, then gapps arm 6.0 and to go sure isorec recovery (not kernel)
[Galaxy S II Original Android Development] :
The kernel(Lanchons) is no longer compatible to the latest nightlies is my guess(changes in ramdisk etc). Btw, there is no reason to flash that kernel anyway, as the stock kernel has trim and isorec support anyway. Even if it was compatible, you would be flashing the stock kernel over the stock kernel.....
[Galaxy S II Original Android Development] the.divergent:
I had same issue. The trim is already merged so you don't have to install trim anymore. From some reason installing trim causes bootloop. Just wipe /data, /cache and /system, then install CM 13.

Edit : Just to add that if TWRP asks you to fix root, refuse it.
[Galaxy S II Original Android Development] yaseenarafath:
hello guys,

can you provide me link of Isolated Recovery for sgh-t989 (hercules), because currently im facing lot of issue with GAPPs on cm13 rom
[Galaxy S II Original Android Development] makix13:
[MENTION=349465]ringen00[/MENTION] be careful, if you are on CM12.1 you'll need to flash kernel-Lanchon-TRIM-IsoRec-20160112-cm-12.1-i9100.zip, you put in your message "kernel-Lanchon-TRIM-IsoRec-20160112-cm-11-i9100.zip", it's for KK not for LP rom. [emoji6]

The order if I'm not wrong, first the isorec kernel, then the isorec recovery.

Don't know about cyandelta sorry

S2 Cyanogenmod 5.1.1 [official nightly] - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] Lanchon:
do not flash disabler!

order is unimportant.

flash the TWRP manually just once.

then give my CM12.1 kernel to cyandelta to flash after every rom update.
[Galaxy S II Original Android Development] pilgrim011:
So, I have tried to use this: downloaded kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip and recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip, flashed first kernel, then recovery zip, rebooted to recovery, but I still have dreadful CM 12.1 recovery. What am I doing wrong?
[Galaxy S II Original Android Development] franticfreddy:
Hi,

its sure that the flashing was ok?

Because, in stock CM-recovery, you only can flash signed zips..

Maybe you didnt sign the zip files from Lanchon, as he wrote in

instructions..

Try take out battery for 10secs, then put back in, and reboot into CM-recovery,

then flash signed zip files from Lanchon, after that take out battery again, wait 10 secs, put back in and power on into recovery..then twrp should appear..
[Galaxy S II Original Android Development] pilgrim011:
Thanks, but Lanchon zips are already signed, me thinks.
[Galaxy S II Original Android Development] svbarbosa:
Now I am running latest kernel and IsoRec revovery:

- kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100

- recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)

Unfortunately the "android secure 0 bytes" problem is still there.

[MENTION=414800]arnab[/MENTION], will it be possible to fix this?
[Galaxy S II Original Android Development] arnab:
The recovery tht i gave u lanchon is made with M sepolicies branch... And there is a denial of .android_secure of selinux frm mmcblk0p11 ie the emmc part... Either u have to switch to permissive or get the policy defined if ur using it in enforcing.. It will show up in last_kmsg... Alternatively if u dnt wanna fix sepolicies u can either switch to permissive or

https://github.com/kularny/GeniSys.Kernel/tree/smdk4210/out/ramdisk get the latest last ramdisk available that was built with the old cm12.1 compatible sepolicies frm the link.... Or u can delete the . Android_secure manually in usb mass storage mode frm twrp by showing hidden items. But i think u have to fix sepolicies in both cases.. With the new one that i gave u or the old one. It will come frm u:object_r:vfat:s0 and it will be in like allow init vfat:file {read open}.. The avc denial will be of read open.. But i think it will be for both new one and the old ones.
[Galaxy S II Original Android Development] svbarbosa:
Thanks for the quick reply. :)

I am just a user and do not know how to proceed.

[MENTION=4141005]Lanchon[/MENTION], can you use these instructions to make the IsoRec TWRP handle android_secure under CM 12.1?
[Galaxy S II Original Android Development] arnab:
last_kmsg denial:

<5>[ 3.280191] c1 type=1400 audit(1452277167.830:9): avc: denied { read } for pid=1886 comm="recovery" name=".android_secure" dev=mmcblk0p11 ino=2 scontext=u:r:init:s0 tcontext=u:object_r:vfat:s0 tclass=dir permissive=1
<5>[ 3.280312] c1 type=1400 audit(1452277167.830:10): avc: denied { open } for pid=1886 comm="recovery" name=".android_secure" dev=mmcblk0p11 ino=2 scontext=u:r:init:s0 tcontext=u:object_r:vfat:s0 tclass=dir permissive=1

The fix:

file_contexts
/storage/sdcard0/.android_secure u:object_r:vfat:s0

init.te
allow init vfat:dir { read open };

I am building a new DU release which will incorporate these seploicies. Lets hope the new ramdisk that Il get, probably tomorrow Il build, will fix this issue...There were gazillions of denials that I postponed for the final release..I will do the fixing in 2 parts...One half part was done in 9.8 which had logcat and dmsg denials fixed...remaining part will be of frm a last_kmsg...the final one will have this denial fixed..and alot of others too. Ofcourse Iam a human being and not a machine..So i went thru 2 part policy. Maintaining both Kernel and ROM is a tad bit difficult.
[Galaxy S II Original Android Development] kal4metal:
For me it works like a charm! Thank you [MENTION=4141005]Lanchon[/MENTION]! I hope it gets merged alongside trim! One more obstacle thrown away! ;)
[Galaxy S II Original Android Development] Naudiz:
Just out of curiosity:

If I remember correctly, older versions of TWRP on the i9100 had the possibility to backup /efs.

The current one from OP seems to lack this. Is this intended?
[Galaxy S II Original Android Development] Lanchon:
instead of packing your last ramdrive with CM12.1 policies, i'll better wait for the ramdrive of your new Dirty Unicorns; i think it will create less confusion. thanks again for all your hard work and please excuse all the tagging of your name that happened here :)
[Galaxy S II Original Android Development] arnab:
Yes i purposely disabled efs partition backup...it contains sensitive info like imei data and all..if u begin to play with it and if in some case backup restore fails..u will loose ur imei data including wifi mac and all others like device serial no...many users had a bad experience on other threads of playing with efs..so i disabled it altogether..u shud never touch efs partition.

---------- Post added at 11:33 PM ---------- Previous post was at 11:32 PM ----------

Its cool..am happy to help :)
[Galaxy S II Original Android Development] Lanchon:
im very sorry about this, booting to a CM 12.1 recovery can be a pretty scary experience, yes...

did you solve it? i suppose maybe you got a bad TWRP download. you can get the MD5 hash of your downloaded files and compare them to the MD5 displayed on the file download page.

else something might be overwriting your partitions? you can pull your current partitions and check the contents. boot to recovery, connect via adb using sudo/administrator mode (adb kill-server; sudo adb devices), then pull the partitions:

adb pull /dev/block/mmcblk0p5 kernel.img
adb pull /dev/block/mmcblk0p6 recovery.img

your are correct.
[Galaxy S II Original Android Development] pilgrim011:
Sorry, forgot to post - everything is ok now, after I have flashed LA's twrp kernel first, and after that, from his twrp recovery flashed your kernel and recovery.
[Galaxy S II Original Android Development] arnab:
Update

A small update...Despite me fixing the policies I still got denials...then i saw that twrp is made to run in permissive even kernel is set to enforcing...Not going into much technical details...

Connect emmc in usb mass storage mode from mounts...before that disable mtp...open .android_secure..put any file which is 1mb+ ..it will show the value...Earlier the size was in kb...thats why it didnt show up as twrps unit was in mb. every thing is good and works fine.

service set_permissive /sbin/toolbox setenforce 0
oneshot
seclabel u:r:recovery:s0

This code is here. See the setenforce 0. It means twrp will start in permissive mode on every boot.
[Galaxy S II Original Android Development] makix13:
Just flash isorec kernel plus isorec twrp recovery from arnab and all fine.

Big thanks [MENTION=4141005]Lanchon[/MENTION] and [MENTION=414800]arnab[/MENTION] from your amazing work [emoji122] [emoji122] [emoji106]

S2 Cyanogenmod 5.1.1 [official nightly] - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] TeutonJon78:
Thanks for doing this. I've been wanting to switch to CM from OmniROM on my i777 since CM is still being worked on, but I couldn't deal with that horrible recovery. This made the ability to switch painless.

You can also add this to another report of it working correctly. The only issue I've run across is that the MTP under TWRP has a file transfer limit, and it's too small to transfer a full GAPPS package. Not sure if that is a problem with TWRP in general, or this build.
[Galaxy S II Original Android Development] Lysergic Acid:
So, I see the patch on gerrit. Is this working fine, without anything else needed? The change seems so simple that I coudn't believe it. I'll merge it on official kernel if no one has complaints :)
[Galaxy S II Original Android Development] Lanchon:
cool! lol yes extremely simple :) and yes, it's working fine on devices affected by the change, i9100 and i777, both tested.

the change would also affect n7000 and d710, but only theoretically as those devices dont have cm12.1 branches. yet it should work fine on those devices too, they identical in this regard.

btw, i made cm11 isorec kernels for n7000 and d710 but received no feedback. i also made a cm11 kernel for i9100 and tested: isorec works fine on cm11 too.
[Galaxy S II Original Android Development] Lanchon:
the hercules is qualcomm, not exynos 4210, so currently no isorec support.

does it have the same stupid monolithic kernel/recovery issue?
[Galaxy S II Original Android Development] arnab:
[MENTION=4141005]Lanchon[/MENTION] Since your'e instructing to use adb in OP, add this ADB tools to your main OP. Drivers + Windows adb setup exe file.

ADB
[Galaxy S II Original Android Development] kvevand63:
Can now confirm that TWRP 2.8.7.0 for i9100 by arnab flashes and works great on SPH-D710. In updater script asserts change one of the device names to SPH-D710, flash and reboot recovery. Will update to 3.0.2-0 via adb later. Many thanks to arnab and Lanchon!
[Galaxy S II Original Android Development] Lanchon:
cool, later tell us if 302 works, thanks!
[Galaxy S II Original Android Development] yaseenarafath:
yes, it also have that issue with kernal,recovery....unable to use the cm13, gapps issue
[Galaxy S II Original Android Development] kvevand63:
Now confirming that 3.0.2-0 for i9100 flashed, working and tested on D710. Flashed the 3.0.2-0 img via 2.8.7.0, rebooted recovery, TWRP 3.0.2-0 now working great on my D710. All features tested and working. Thank you once again!

BTW, running CM11 041016 nightly. Also was able to repit my device. The D710 version did not work, however the i9100 one worked flawlessly.
[Galaxy S II Original Android Development] Mavrikmeercat:
I was able to flash Lanchon's twrp-2.8.7.0.zip to mmcblk0p6 by simply editing the updater-script to get.prop the d710. It boots just fine and will flash .zips. It will not mount my /external_sd at all. When I try to flash twrp-3.0.2-0-i9100.img to the recovery partition (from twrp-2.8.7.0 using the img install option) it clobbers mmcblk0p6 and reboot recovery brings me back to cwm recovery which is packed in the kernel/boot partition. I even tried to data dump the image from recovery terminal. Eg. dd if=twrp-3.0.2-0-i9100.img of=/dev/block/mmcblk0p6. Still same results.. Just boots to kernel recovery. :confused:

How did you get it to work? Details please?

Also I did notice that 2.8.7.0 won't flash d710.zips it will only flash i9100.zips. Might be why you had to repit with i9100 files
[Galaxy S II Original Android Development] Lanchon:
figures. i believe in the d710 the external sd is handled by a different peripheral.

probably a bad download of the .img. check the md5.

of course!!!!! lol this is the problem i wasn't remembering! this sucks...

yep, that's the reason.