yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] franticfreddy:
Sorry guys, i didnt want to start discuss about trim in generally, just because one of my phones

is dead now after use trim kernel and manually invoked trim.

Maybe [MENTION=4141005]Lanchon[/MENTION] is right, it could be possible for me that i had randomly bad luck because its

a real old device.

I dont want to complain about trim kernel in general, as for many other

users it works good and without errors or bad behavior. :)

--

So lets go back to topic and lets go on error / bug reporting if you found something.

--

Sorry for offtopic!

Best regards :)
[Galaxy S II Original Android Development] Lanchon:
no, you are wrong. AOSP 4.3 and later and its derivatives (CM) trim on schedule, typically daily. and AOSP 4.0 recoveries and later trim on partition wipe. and any older android or recovery might mount partitions with the DISCARD option, trimming online with file system use.

this is not bollocks. in fact official CM 10.1 (JB 4.2) has discard enabled on /data:

https://github.com/CyanogenMod/andr...ommon/blob/cm-10.1/rootdir/fstab.smdk4210#L10

and CM 10.2 (JB 4.3) doesn't have it:

https://github.com/CyanogenMod/andr...ommon/blob/cm-10.2/rootdir/fstab.smdk4210#L10

only because of my commit to remove it:

https://github.com/CyanogenMod/andr...mmit/6567216cfe307526967b1a6e8a879348f8c10471

no idea if stock 4.1.2 uses discard mount option.
[Galaxy S II Original Android Development] cherryb8844:
Hay [MENTION=4141005]Lanchon[/MENTION] thanks for this isorec there is some one guided to how to flash this recovery but I need more guidance about this

How to do with latest nightly I need to stick with trim+stock kernel that you provided on trim thread should I need to just flash latest nightly then flash this recovery

Because I like to use official nightly and [MENTION=1597520]Markox89[/MENTION] build that have linaro toolchan when I flash other kernel so I lost linaro that compiled in kernel by markox89 or I don't need to flash any other kernel after flash this isorec kernel on official nightly

Sorry for my noob question

[
[Galaxy S II Original Android Development] Lanchon:
you need ANY isorec-compatible kernel PLUS ANY isorec recovery.

my latest TRIM kernels support isorec. official CM now support isorec too (so flashing official CM + isorec TWRP will work).

if Markox89 kernel is isorec, then that will work too. if not, ask your kernel maintainer to merge isorec.
[Galaxy S II Original Android Development] g3lux:
Hi, [MENTION=4141005]Lanchon[/MENTION]. Thanks for your efforts to keep galaxy s2 rolling. isorec is awesome, so that we can have recoveries separated from the kernel.

As it is with i think all other android devices. Also for trim, i've been used and pretty good. Running Fine, with CM11 and gustavo_s trim kernel.

Now i see that the official cm 12.1 merged isorec patch. Now my question, is can i flash a non-isorec patched kernel?

Such as dorimanX LP UNOFFICIAL, which seems to not merging this patch.

What recovery would be active? the recovery on CM12.1(cyanogenmod recovery) or the dorimanX recovery(which is CWM)

I would like to use dorimanX kernel, because of BLN function, overclock, and such.
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=5428399]g3lux[/MENTION], if Dorminax has Isorec support yet, you could use it.

If it hasn't you will loose Isorec functionality. This means all would be like it was before Isorec, which means, the last flashed kernel will define the recovery.
[Galaxy S II Original Android Development] g3lux:
Thanks for the fast response, [MENTION=7183558]fireburner-de[/MENTION].

I thought since isorec, create's an isolation for recovery, that flashing non-isorec kernel, would like corrupt recovery, brick or weird stuff.

Awesome that it falls back to recovery within the kernel, if kernel is not isorec patched.

I will try CM12.1 or Euphoria in couple of days. Seems to be already pretty good for daily use.
[Galaxy S II Original Android Development] Lanchon:
yes, exactly right. thanks for responding.

there is no weird issue like the one you are describing.
[Galaxy S II Original Android Development] Lanchon:
better yet, point the developer to isorec, they'll probably be interested. merging this is zero effort.

if your kernel is unmaintained, maybe you should move to another one.
[Galaxy S II Original Android Development] WaLshy11:
Since isorec is now merged in CM 12.1, what's the process of getting TWRP and TRIM with this kernel?

Just update to the latest nightly then flash a isorec TWRP recovery (via the link on the 1st page), do I need to flash TRIM at all or is that now built into the the official 12.1 as well?
[Galaxy S II Original Android Development] Saber:
Have a look at this post: http://xdaforums.com/showpost.php?p=64827143&postcount=598

If I find a way to make the patch work, I will add isorec into kernel. But for now, no isorec on DorimanX.

If someone wants to work on gustavo kernel, isorec will merge with no problems.

gsstudios
[Galaxy S II Original Android Development] Lanchon:
if you want TWRP just flash isorec twrp ONCE and forget.

if you want TRIM flash my kernel on top of CM every time you upgrade CM.
[Galaxy S II Original Android Development] Lanchon:
i looked at your github, i think it wouldn't be too much of a problem to implement when i have the time. i asked for more info on the github thread you opened.
[Galaxy S II Original Android Development] ssanjy:
I'm looking forward for your support to merge the patch in the dorimanx kernel.... I did try out the Iso rec kernel in rr but it did not succeed... May be I need to give another try some time later... Thank you very much for your contribution
[Galaxy S II Original Android Development] the.gangster:
And I am courious how all the dorimanx special features will look like in a TWRP isorec recovery. Lol
[Galaxy S II Original Android Development] Lanchon:
UPDATE: we got a version of IsoRec working on gsstudios' DorimanX and it is already merged.

future builds will be IsoRec-compatible.

thank you so much gsstudios!!!
[Galaxy S II Original Android Development] Saber:
[MENTION=4141005]Lanchon[/MENTION]

Credits list all updated with your latest contribution :)

Gsstudios
[Galaxy S II Original Android Development] ssanjy:
What an amazing new.....Absolutely impatient to flash the latest build.... You guys are great.... Thanks a ton.... :good:

Edit: Already downloading....
[Galaxy S II Original Android Development] Noctis Lucis Caelum:
Yeah running the latest DorimanX release with CM IsoRec all is good.

Just checking here, is it possible to have an IsoRec with Phill Touch recovery?
[Galaxy S II Original Android Development] Spyr0s:
Why someone would bother with something that is obsolete and worked only with stock firmware?
[Galaxy S II Original Android Development] Noctis Lucis Caelum:
I wouldn't say its obsolete, it better than Cwm in term of options,

And TWRP can't even function properly on the I9100, USB mass Storage issues or can't flash from ext sd.

Phill touch would be an option, you are wrong about it only working with stock firmware, the last Slimsaber 5.1.1 uses it although it's a couple of months old.
[Galaxy S II Original Android Development] cherryb8844:
You are wrong I'm always flash every zip from ext card it just called sdcard in TWRP recovery

When you are on flash just tap on up lavel top on the list when you then scroll down and see sdcard :)
[Galaxy S II Original Android Development] ssanjy:
Philz recovery option will be awesome as well... It's well presented form of cwm.... Between TWRP is also great recovery.. I've not found serious issues with it so far.....

Dorimanx with the IsoRec patches is running great... Am on TWRP... Just tried rom backup and it went good...
[Galaxy S II Original Android Development] Lanchon:
anybody can publish recoveries now. that said, phill's has been unmaintained for a long time now. but if someone has a good build you can ask them to do an isorec release.

alternatively, get these things from your kernel provider:

-the recovery cpio ramdisk from your kernel provider (it is either an intermediate file that is produced when building the kernel, or a pre-built recovery manually added to the kernel build).

-credit/authorship info

-permission

and i'll bundle it as an isorec recovery.
[Galaxy S II Original Android Development] cherryb8844:
I'm another fan of philz recovery that have more options then normal CWM recovery but philz are based on CWM and CWM is slower then TWRP recovery i notice the time flashing and backing up TWRP faster then philz Or CWM
[Galaxy S II Original Android Development] cdrivex4:
Created a backup mobile A trying to restore it to mobile B both are same in i9100 but can't restore backup A on B won't reconise there is a Backup present.

Any advice?
[Galaxy S II Original Android Development] the.gangster:
On SD? With which recovery?

Then create a backup of some small partition on mobile B.

You'll probably see a new device folder created under the backup path. Then move the backup of mobile A into folder of mobile B.

Now you should see it as backup to restore also on mobile B.
[Galaxy S II Original Android Development] cdrivex4:
Yup..externalsd card using twrp..

Sheesh if only had known sooner.that works.

Thanks :)
[Galaxy S II Original Android Development] ruicc:
Hi,

I'm using Euphoria rom on my S2 (I9100)

All i have to do is flash:

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

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

and that's all?

[MENTION=4141005]Lanchon[/MENTION] Thanks for all your work, this is much appreciated
[Galaxy S II Original Android Development] Lanchon:
my kernel is for CM. find the right isorec kernel for your rom.
[Galaxy S II Original Android Development] Lanchon:
that is correct. the backup storage on twrp is broken up into subdirectories with names based on the serial number of the devices, etc, precisely to STOP you from doing what you want!

if you move the data from one dir to another you will be able to restore. and it very probably wont work! who told you you could do this?? you will probably even loose your IMEI. read on the subject or create a new thread for this.
[Galaxy S II Original Android Development] ruicc:
I don't think that euphoria has provided a isorec kernel, Lanchon..although euphria roms are CM based.

So, it's better to stand still, or where i can find a isorec kernel for this rom?

In alternative it's better flash CM12.1 rom?
[Galaxy S II Original Android Development] cherryb8844:
Euphoria os is based on cm12.1 so you can use [MENTION=4141005]Lanchon[/MENTION] isorec kernel (cm12.1) with caution and there is [MENTION=5811506]gsstudios[/MENTION] made dorimanx kernel with isorec see the few last post by lanchon
[Galaxy S II Original Android Development] cdrivex4:
As per this thread using the isorec twrp enabled. Some were discussing how twrp is broken in some senses or lacking features. Crucially EFS backup disabled, which I believe is where imei is? So.. If transfer data,dystem n boot loader from A to B. Should work.. Incidentally just checked imei on both, still original on both. Mobile B took the backup n working fine.
[Galaxy S II Original Android Development] ruicc:
Thanks...but no. I'll wait for more stable releases of MM roms. Then i'll see how it to goes when it comes to isorec. I think there's a lot to do and i hope all MM rom devs support this mod and include it on their roms.

For now, i'll stay still :)
[Galaxy S II Original Android Development] Lanchon:
i was not speaking of EFS partition, i assumed you would never restore that! many roms/devices have stuff in /data that matches your particular device (eg: data from the EFS) and will loose IMEI if /data in transplanted. ive personally seen this many times. (usually wipe /data restores IMEI.) thats why twrp is designed to prevent you from doing that. you were lucky that it worked in your case.
[Galaxy S II Original Android Development] DevisG79:
Sorry for the question. Do I have to Flash only the isorec recovery because the isorec kernel is just included in the Stock kernel of cm12.1? Or do i have to flash both isorec kernel and then isorec recovery? I am running official cm12.1 nightly from 26012016.
[Galaxy S II Original Android Development] jojobg:
Just flash isorec recovery and you are good to go.
[Galaxy S II Original Android Development] Acid0057:
Do we still have to flash this kernel with IsoRec if we want trim on official CM12.1?
[Galaxy S II Original Android Development] Lanchon:
yes, trim has not been merged.
[Galaxy S II Original Android Development] daniu:
Hi

I wonder: can we do anything to change that?

Regards

Sent from my x-phone using brain 2.0
[Galaxy S II Original Android Development] franticfreddy:
I think it depend on developer if he think its a good idea to merge trim for generally public release.

There exist brickbugged emmc chips and this *may* can cause problems then when use trim on such devices.

Also in dorimanx kernel thread there is written a warning about that.

My opinion is that it should not be merged for public, and when experienced user wants to have trim then should manally flash Lanchon kernel (or Dorimanx with trim, or any other..).

Best regards.
[Galaxy S II Original Android Development] Lanchon:
i am trying. you should discuss trim in the trim thread.

i will probably stop building these kernels.
[Galaxy S II Original Android Development] Naudiz:
What? Please NO! :crying:
[Galaxy S II Original Android Development] makix13:
What the fuc...., oh man, after read that, there isn't any reason to be alive [emoji23] [emoji23] [emoji23]

Hope trim will be included soon in official CM ...[emoji26] , I understand you Lanchon, great work without any recognition.

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] Lanchon:
it's not that. it's that the objective, restoring trim safely, was done ages ago. im tired of building the silly boring kernels.
[Galaxy S II Original Android Development] fireburner-de:
deleted

sorry
[Galaxy S II Original Android Development] kal4metal:
[MENTION=4141005]Lanchon[/MENTION] Is there any possibility for a CM13 kernel with TRIM and Isorec support, now that the nightlies will start rolling out? Thanks! :)
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=4141005]Lanchon[/MENTION] , are the Isorec revoveries from the Link in OP support CM13 already?
[Galaxy S II Original Android Development] Dr AM:
Tried TWRP and worked for me

Sent from my GT-I9100
[Galaxy S II Original Android Development] Acid0057:
[MENTION=4141005]Lanchon[/MENTION] are you planning on making kernels with IsoRec and Trim for CM 13.0 for the i9100?
[Galaxy S II Original Android Development] fireburner-de:
CWM runs good with Cm12.1. The only question, that comes in mind is, that CWM every time asks me if it shall fix root. I always answered NO and nom root issues in Cm12.1. But why does it ask this and what would happen if I would answer with yes?
[Galaxy S II Original Android Development] kal4metal:
CWM used to install some root libraries in KitKat. CWM development stopped before Lollipop so it still asks you to install these libraries. You shouldn't choose yes anyway since it's some useless junk :)
[Galaxy S II Original Android Development] Lanchon:
isorec is merged. i've too much work to do kernels now, sorry, maybe later. running without trim for some time wont create any problems. i think we should focus on merging trim. the change is in gerrit.

it asks because thankfully it doesn't see kitkat root files installed in cm12.1. bad things.
[Galaxy S II Original Android Development] Lanchon:
no idea. i just made the mechanism to run separate recoveries, i expect other people to make recoveries now. for starters, none will understand adopted storage, and no idea which ones support encryption.
[Galaxy S II Original Android Development] Acid0057:
Okay thanks for all you're hard work on our device Lanchon. At least with you're IsoRec I can have cm 13 and twrp.
[Galaxy S II Original Android Development] Dr AM:
How does it's backup work !!!

I wipes system , data , and cache before clean installing cm13 nightly but TWRP is still there

I'm not complaining but happy that it's still there but want to know how it's still there even after wiping everything

Sent from my GT-I9100
[Galaxy S II Original Android Development] franticfreddy:
Because TWRP is installed on another separate recovery partition / block.

Best regards.
[Galaxy S II Original Android Development] Dr AM:
Oh sorry got it "now I feel stupid :D "

Edit: but doesn't flashing another kernel or ROM bring back its own recovery !!

Sent from my GT-I9100
[Galaxy S II Original Android Development] fireburner-de:
If the other ROM has Isorec support, you will still have TWRP.

If it's not Isorec compatible, you will see its Recovery.
[Galaxy S II Original Android Development] Draky50110:
Hello.

Maybe little bit noob but... how do I flash this ?

I'm currently on Gustavo Kernel + CWM Recovery (provided with Gustavo Kernel)

My ROM is Resurrection Remix (based on CM 12.1).

My goal is to flash CM13, but I read it would work flashing CM13 from IsoRec (better than TWRP ?) so...

Will this replace CMW ?

Will I need to flash TWRP after or just boot on IsoRec then flash ROM + Gapps ?

Thanks.

PS : my PIT is 1GB/4GB as I change it before flashing Gustavo+CWM.
[Galaxy S II Original Android Development] franticfreddy:
The CM13 supports isorec recovery. If you want have CWM or TWRP,

then you must first flash the isorec compatible CWM or TWRP recovery

from Lanchon now with Gustavo Kernel/Recovery. (Because recovery will be

written on a separate partition / block.)

After that you can flash CM13 and you will keep your choosen recovery,

because CM13 kernel support isorec.

Its strongly recommended that you first flash isorec recovery from Lanchon.

Otherwise you will have stock cm recovery only.

Best regards.
[Galaxy S II Original Android Development] Draky50110:
Thanks :)

I found IsoRecTWRP "by arnab" ZIP so I guess I can flash this "by arnab" to have TWRP AND IsoRec.

Then CM13.

Will replace Gustavo CWM recovery no ?
[Galaxy S II Original Android Development] giosu994:
I installed the CyanogenMod 13 and now I have the recovery cyanogen ... but does not make me install the .zip file ... how to solve the problem?
[Galaxy S II Original Android Development] chrisXL:
See here http://xdaforums.com/showthread.php?p=65164875
[Galaxy S II Original Android Development] Cintra2:
Have updated 12.1 to latest CM13 nightly OK having first installed Lanchon TWRP zip, and on first reboot to recovery there is an initial TWRP message "Keep system read only" or not, and I am not sure what to do. Advice would be appreciated :)

Decided not to tick Read only and went ahead to install Nano gapps for 6.0

Installed OK, but I had trouble with the Setup Wizard stopping. I found a fix on a Nexus 5 CM13 thread to go into Settings>Apps>Setup Wizard (not the CM one) and set permissions ON for Telephone and Contacts.

A bit more info: I am unable to mount USB for backup purposes with the isoREC TWRP solution
[Galaxy S II Original Android Development] rickwind:
I flash from CM12.1 to CM 13 now I have Cyanogent Recover and there is no install from zip. What i should do in simply way to fix it and install google apps?
[Galaxy S II Original Android Development] daniu:
Most important: do not ask this question anywhere again!

Then: go to the official thread of cm13 for the s2 and find one of the many answers to this question between 1000 other people who were too stupid to read and asked instead even the answer is there already.

Sent from my x-phone using brain 2.0
[Galaxy S II Original Android Development] franticfreddy:
Its really been asked and answerd already too much in last 2 days!

You should search corresponding threads!

Even in OP of CM13 nightly thread is written you first

should flash isorec recovery twrp (arnab) by Lanchon!

Because stock cm recovery is bugged by se linux mode.

--

In stock cm13 recovery you only can install isorec recovery twrp or

cwm from Lanchon! Can be done with adb sideload!

Thats the solution!

So in cm stock recovery go to adb sideload mode,

install Lanchon's isorec recovery zip, and reboot to recovery.

Search and read the threads. :)

Best regards.
[Galaxy S II Original Android Development] the.gangster:
As he also wrote in the cm13 thread, his USB port is broken. But anyway, even alternatives are given there already...
[Galaxy S II Original Android Development] Fuerte11:
I asked in CM 13 thread, that can I install this isorec twrp (arnab) recovery normally via non-isorec twrp recovery (Cm 12.1), but they said that it should be asked here instead. So can I?

If not, then is this adb sideload mode the only solution? If it is, then do I need to install Android SDK or something for it?
[Galaxy S II Original Android Development] makix13:
Hi Fuerte,

I'm who recommend you read and ask in isorec thread to understand how it works.

Yes, you can flash isorec recovery with your current twrp,and if everything goes OK, you will have twrp isorec recovery.

But remember, with your current ROM you will flash CM 13 with your current twrp, isorec recovery only will appear when you have CM 12.1 or CM 13 isorec compliant (not need to said you will make a nandandroid backup [emoji6] ).

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] hebermc:
The issue is CM13 was made available as a nightly download for cm12.1 users, so a LOT of us accidentally updated without reading anything about CM13 and the whole recovery issue. CM13 should be removed from the CM12.1 nightlies.

CM13 Recovery (20160204/5) cant access SDCards, so it cant install anything. Anyone without access to a ODIN enabled PC is currently stuck with an unusable phone (like me).

The current solution seems to be (coming from 12.1):

1) Pit file

2) ?isorec? recovery

3) cm13

4) gapps

5) isorec recovery

No clue how to do it if you are already on 13.
[Galaxy S II Original Android Development] Fuerte11:
Thanks, I start to understand the whole picture now. So I can install isorec twrp with my current non-isorec twrp, but it would not be used, until I update CM 12.1 or CM 13 to isorec version. Then when I have CM 13, for example, it would be used, and then I would be able to install Google Apps also from SD card.

CM 13 requires full wipe though. I guess that it means, that I need to do full wipe first, then install isorec twrp, then install CM 13, and maybe then install Google Apps also before booting. Then everything should work.
[Galaxy S II Original Android Development] franticfreddy:
Well , I half-agree with you.

Beside your phone is not "not usable".

As i wrote several times now already,

if you want go back to CM12.1 , you are now able to boot into

cm stock recovery and can adb sideload isorec twrp by Lanchon (arnab).

Then in this twrp recovery you will have access to sd-card again.

And its possible to full-wipe and re-install CM12.1 from external sd-card.

Only bad thing is when didnt have backup of internal sd-card.

Best regards.
[Galaxy S II Original Android Development] makix13:
Hi,

First install isorec recovery with your current recovery, full wipe & format, install CM 13 zip, then gapps reboot and crossfingers [emoji6] , if CM don't boot (at least 15 or 20 minutes so battery 100%), in recovery mode you must access twrp isorec recovery.

Hope everything goes well.

In case of issues you will need Odin (download mode) and isorec kernel in tar format, gsstudios has a great thread about it

http://xdaforums.com/showthread.php?t=2994381

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] Fuerte11:
Yes. The only thing that is unclear: does full wipe remove isorec recovery as well? Or formatting the drive? My Android/Linux skills are lacking.