yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] i9100cm:
I installed them in cyanogen recovery.

and then i tried to install

lanchon-repit-20160216-system=1.0-data=same-sdcard=max-preload=min+wipe-i9100

but this one failed
[Galaxy S II Original Android Development] Acid0057:
I'm not sure how you could flash any of that in Cyanogenmod Recovery to be honest. Did you sign the zip files? I think you'll need to use Odin and flash a tar based kernel to get the phone working again.
[Galaxy S II Original Android Development] Dr AM:
There's a rumor saying that Xperience ROM has TWRP 3

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

If it's true then hope we will get an isolated version of it :)

P.s can't try it now to check myself

Edit: confirmed , it has TWRP 3

Sent from my GT-I9100
[Galaxy S II Original Android Development] Lanchon:
what you did wrong is flashing cm13 kernel on cm12.1 rom.

try booting into recovery by key combo and flash the right system or kernel.

wrt REPIT: no log means i cant help you.

wrt odin: probably an unrelated issue. follow odin tutorials
[Galaxy S II Original Android Development] Acid0057:
Somewhere on this thread [MENTION=414800]arnab[/MENTION] confirmed that twrp 3 is coming to IsoRec. Be patient
[Galaxy S II Original Android Development] arnab:
TWRP 3.0 as of now doesnt work. Ethen yonker asked a kmsg log from me.
[Galaxy S II Original Android Development] Acid0057:
Glad to hear it's being worked on though
[Galaxy S II Original Android Development] JimboAccy:
Hi all

Ive done a search on this thread but found nothing. I repitted my phone so it had a 1gb system partition and 6gb data (originally had 8gb data but the isorec arnab version of TWRP doesnt seem to like that - just sticks in a bootloop with no CM13 boot logo), then flashed the isorec twrp arnab recovery, the latest CM13 nightly and Open Gapps mini and the nightlies now install seamlessly once downloaded but my battery life has gone through the floor - anyone else experienced this? Not using it any more than I was before I was using the 'non' isolated TWRP recovery.. Just asking. Gone into the battery screen in the setup and cant see anything obvious - top result is the screen as to be expected probably??

Jimbo
[Galaxy S II Original Android Development] Lanchon:
isorec has *absolutely zero* effect on battery life, if that is your question.
[Galaxy S II Original Android Development] JimboAccy:
Ok thanks a lot :good:

Jimbo
[Galaxy S II Original Android Development] SaZoN:
Hi, [MENTION=414800]arnab[/MENTION] ! Сan you tell us about the progress in twrp 3.0? In night build now supports f2fs, but in our recovery to format impossible =(
[Galaxy S II Original Android Development] the.gangster:
[MENTION=2750826]SaZoN[/MENTION]

don't be rude. It's done when it's done. Did you read at least #299? So be thankful that he is working on it at all, but please don't ask for ETAs. Feel free to develop a new recovery yourself. ;)
[Galaxy S II Original Android Development] makix13:
FYI [MENTION=2750826]SaZoN[/MENTION]

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

Do it yourself and share with us the experience please. [MENTION=414800]arnab[/MENTION] is not our developer so respect him and probably one day soon we have a brilliant twrp 3.0 with f2fs support from him or not who knows, it's his work, his time and his live don't ask for it more. [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] arnab:
I had a internal stotage bug.. I just fixed it for du as well as for i9100g cm13. Without that fixing first i cudnt get a lastksmg as mtp didnt work.. Plz have patience. Iam wotking on twrp now.
[Galaxy S II Original Android Development] McConnor:
Am I mistaken in thinking that the isolated TWRP recovery for the i9100 wont work for the i9100G? As CM13 is about to get rolling on the i9100G it might be fine to flash such a permanent recovery...
[Galaxy S II Original Android Development] good8life:
ROM now supports f2fs

( mkfs.f2fs) I took the information from here: http://xdaforums.com/xperia-s/s-development/tutorial-migrate-filesystem-to-f2fs-ext4-t3004755

I'm use recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100.

Data format f2fs good, cache format error

What can I do?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=6619837]good8life[/MENTION]

as a first step: you could stop cross-posting this.
[Galaxy S II Original Android Development] ajislav:
Use the adb shell command provided by Lysergic Acid in the Dev thread

http://xdaforums.com/showthread.php?p=65495055
[Galaxy S II Original Android Development] kosmasgr:
Hello.

I'm on cm 12.1 with cm recovery.

Can I flash isorec twrp directly from cyaongen recovery ?
[Galaxy S II Original Android Development] gadiyari:
Yes, you can if your CM 12.1 version supports IsoRec.
[Galaxy S II Original Android Development] Alegom:
Hi. I'm on a stock-based ROM and I can't seem to flash this recovery from either CWM (philz's kernel) or TWRP (pedestre's kernel). I can flash between the two kernels I mentioned, but when I try to flash this recovery (either the CWM or the TWRP version) and reboot to recovery, everything stays the same. Any ideas?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=5141747]Alegom[/MENTION]

Sure.

I bet, you simply didn't understand how it works.

You flashed it successfully but it won't be used unless you have a supporting kernel.

Reread post #1. Depending on what you want to do next, flash an appropriate kernel or ROM.
[Galaxy S II Original Android Development] justagangsta:
How is the end-user supposed to use this?

Yes, I read the 1st post - many times.

No matter what, I end up with CM recovery, where you can't flash anything but "update.zip".

Of course, renaming any of the relevant files to "update.zip" doesn't work.

Would really appreciate a step-by-step guide on how to get this working.
[Galaxy S II Original Android Development] :
I'll try to simplify.

If you have flashed an isorec recovery, it is installed in the previously unused recovery partiton.

This recovery is then booted by the ramdrive, if the kernel is isorec enabled(such as cm13 and later cm12.1 kernels)

So you need 2 things. Flash an isorec recovery, and have an isorec enabled kernel.

Read this guide for options to get your preferred recovery.
[Galaxy S II Original Android Development] justagangsta:
Thanks for answering, and the link.

However, this is -exactly- what I've done. Over, and over, and over again.

Still, I'm stuck with the CM recovery that only allows "update.zip."

I flashed an isorec recovery both before and after flash everything else. Flashing in the beginning doesn't do anything. Flashing in the end makes the phone never load the OS.
[Galaxy S II Original Android Development] :
For the sake of accuracy, can you list the file names, the order you flashed, and which rom and recovery you flashed from? From your position, you should be able to get the recovery working if you use one of the methods in the guide I linked
[Galaxy S II Original Android Development] Lanchon:
thanks for posting.

it is almost unbelievable that flashing an isorec recovery "in the end makes the phone never load the OS". it looks like you are flashing an isorec kernel instead, and that would be the reason why it never worked. (my suspicion: you never flashed an isorec recovery yet.)

we are waiting for the list of files.
[Galaxy S II Original Android Development] himselfv:
It's the same for me! Here's what I do:

1. Odin-flash I91001GB_6GB.pit + gustavo-cm12.1-kernel-22-06-for-ODIN.tar => successfully boot into CWM recovery

2. Format data, sdcard0.

3. Sideload cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100.zip

4. Sideload recovery-Lanchon-IsoRec-CM-6.0.5.1-20160112-i9100.zip

5. Reboot => default CM 12.1 recovery.

Here's the only sequence that got me CM12.1 + CWM recovery:

3. Sideload cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100.zip

4. Sideload kernel-Lanchon-TRIM-IsoRec-20160206-cm-12.1-i9100.zip

5. Sideload recovery-Lanchon-IsoRec-CM-6.0.5.1-20160112-i9100.zip

I thought no IsoRec kernel is needed since IsoRec is now in CM 12.1, but this way it works.
[Galaxy S II Original Android Development] Lanchon:
you need an isorec kernel.

and who knows what u did with PITs... you might want to check out my repit.
[Galaxy S II Original Android Development] the.gangster:
No, it is simply the fact, that November snapshot didn't have Isorec-suppprt, yet.

The latter came with CM-12.1 nightlies as of January-19th.

That's why snapshot user still do need an additional IsoRec supporting kernel.

That's all.
[Galaxy S II Original Android Development] jdog320:
lanchon, will this work with cm11-20150905? Plus if it does how do I install it? lik this:

1. flash 6.0.5.1 recovery

2. wipe all

3. flash cm11

4. flash kernel

5. flash gapps

6. profit$$$$$

btw i'm going to use philz touch
[Galaxy S II Original Android Development] himselfv:
Thanks. Then that is clear. Maybe make a clarifications in the post? Something like "new builds of Cyanogen 12.1, 13 are IsoRec compatible, but stable versions from the download page may still require the kernel patch".
[Galaxy S II Original Android Development] Acid0057:
What do you want to end up with for a recovery in the end? Because after flashing the kernel in this thread you also need to flash the isorec recovery you'd like.
[Galaxy S II Original Android Development] the.gangster:
Not if [MENTION=6512940]jdog320[/MENTION] refers to "recovery-Lanchon-IsoRec-CM-6.0.5.1-20160112-i9100.zip" at his point
[Galaxy S II Original Android Development] Acid0057:
Very true. We'll have to wait for jdog320 reply
[Galaxy S II Original Android Development] jdog320:
SO:

1. flash 6.0.5.1 recovery

2. wipe all

3. flash cm11

4. flash kernel-Lanchon-TRIM-IsoRec-20160112-cm-11-i9100.zip

5. flash recovery-Lanchon-IsoRec-CM-6.0.5.1-20160112-i9100.zip

6. flash gapps

7. reboot

8. profit$$$$$

but where can i get the recovery img?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=6512940]jdog320[/MENTION]

where everybody should read before posting: on the opening post of a thread.

This is also true for this thread.

:)
[Galaxy S II Original Android Development] cherryb8844:
OK I'll clear here

When you have latest build of cm 12.1 or cm13 so just flash latest lanchon isorec by arnab then you don't need to flash any recovery anymore or when you need IMG so extract the zip

Here the processes

Flash cm12.1 ROM any [MENTION=1597520]Markox89[/MENTION] is a latest build I'm using it

Then flash recovery

Profit

Now when you will switch any newer build of cm you don't need to flash any recovery anymore

For more detail tell us about what you're installed on you'r device and did you expended your system partition download disc info app from app store and see cm13 need 1GB system

Sorry for OT guys :)
[Galaxy S II Original Android Development] jdog320:
So just flash isorec and that's it? No need to flash the recovery-Lanchon-IsoRec-CM-6.0.5.1-20160112-i9100.zip. I don't wanna use cm 12.1. wanna stick with 11.
[Galaxy S II Original Android Development] drdebian:
This is wonderful! Thanks to everyone involved for this easy to use solution!!
[Galaxy S II Original Android Development] cherryb8844:
So when you're using cm11 so first flash isorec kernel then flash isorec recovery

Cm11 don't merged isorec

And why you don't try cm12.1 that was superb then cm11 ?
[Galaxy S II Original Android Development] jdog320:
I could try it eventually. How's battery with 12.1? SoT and standby?
[Galaxy S II Original Android Development] Lanchon:
1 get any custom recovery working on the phone.

2 flash my cm13 isorec trim kernel.

3 flash my twrp by arnab.

4 reboot recovery.

now you can flash any rom.

5 flash my repit, set sys to 1gb, data to 6gb. wipe as many partitions as you can (system, data, preload for example); its faster that way.

6 better if you reboot recovery now.

7 flash cm 11 or 12 or 13. flash my cm11 build if you want cm11.

8 flash my corresponding trim kernel (unless you are on latest cm13 nightly; already has trim).

9 flash gapps. take a look at opengapps nano or mini.
[Galaxy S II Original Android Development] arnab:
[MENTION=4141005]Lanchon[/MENTION] How did u compress the existing recovery cpio archive...uncompressing it and then compressing it back to lzo ??? what tool did u use ???
[Galaxy S II Original Android Development] the.gangster:
[MENTION=414800]arnab[/MENTION]

if I remember right, [MENTION=4141005]Lanchon[/MENTION] mentioned using lzop once.

Edit: with -9 compression.
[Galaxy S II Original Android Development] arnab:
Ya got it..

lzop -9 ramdisk-recovery.cpio
[Galaxy S II Original Android Development] jdog320:
Thankyou!

So I have to flash the isorec trim kernel 2x? To flash the seperate recovery and after Install the os? btw i'm not going to use twrp for flashing cm11.
[Galaxy S II Original Android Development] Lanchon:
then do it your style! i just sent something that worked
[Galaxy S II Original Android Development] Lanchon:
yep! just compress the .cpio
[Galaxy S II Original Android Development] Lanchon:
hi

[MENTION=6159291]Lysergic Acid[/MENTION]

[MENTION=414800]arnab[/MENTION]

[MENTION=6560258]the.gangster[/MENTION]

[MENTION=5811506]gsstudios[/MENTION]

it finally happened -much earlier than i expected- that a kernel and a recovery are incompatible. please see here:

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

the problem is compounded by the fact that people use the "reboot recovery" option after flashing an isorec recovery: because the recovery doesn't boot, it can't clear the "reboot to recovery" flag. and thus the user can't boot android to solve the situation, the phone is soft bricked in case of incompatibilities, and the only solution is download mode and odin/heimdall.

this sucks big time, and we can do better. please see:

http://xdaforums.com/galaxy-s2/orig...ated-recovery-galaxy-s2-t3291176/post64770557

the idea is to be able to cancel IsoRec boot and force booting of the recovery bundled with the kernel by one of these methods:

A) recovery boot (and only recovery boot) would be delayed by 3 seconds during which you could press a button to abort isorec boot. the 3 second delay is unavoidable with my current knowledge.

B) you could cover the proximity sensor during recovery boot to abort isorec boot. no delay would be needed.

-in both cases, aborting isorec boot would result in standard recovery boot (bundled recovery).

-in both cases, some kind of user feedback would be implemented in addition to A) or B).

so here are my questions to you guys:

#1) would you favor the 3 second plus keypress implementation, or the proximity sensor implementation?

#2) and for LA: would you merge this into CM 12.1 and 13? because no reason to implement anything if you don't like it and it wouldn't get merged.

thanks!
[Galaxy S II Original Android Development] arnab:
proximity sensor is a bad idea as its dependent on hardware..a fail in that will render ur whole work useless...I would vote for time delay. Also for time delay plzzz map the home button if possible. but the vol keys are more rugged.
[Galaxy S II Original Android Development] Lanchon:
i agree about resiliency of the buttons. but some people might hate the delay.

if implemented, i will map ALL buttons: any button pressed during that time window will abort isorec. but it has to be actually pressed (buttons held down all throughout the time window don't count). this achieves 3 goals: 1) it works on the many devices that have some particular failing button. 2) it works on devices that have a stuck button (ie: pressed all the time; i've seen some). most importantly, 3) it makes the isorec code valid for all device variants, as some could have different button mappings.
[Galaxy S II Original Android Development] arnab:
Just skip the power button...it has a default 8 sec gap for simulating battery pull. It will be too close call.
[Galaxy S II Original Android Development] jdog320:
Can you have a seperate "reboot to kernel recovery" and "reboot to (isorec recovery)"
[Galaxy S II Original Android Development] Lysergic Acid:
I'm pretty sure the sensor doesn't work during early boot, but anyway, doesn't sound good. I'm open for the other implementation if you find it really needed, but I don't see why you can't just warn the users about the possible risk of bricking, or just don't release recoveries that can possibly brick the phone.
[Galaxy S II Original Android Development] Lanchon:
you mean the sensor doesn't work after kernel bootup when init is started and some userland config must be done? ok i didn't know that.

yes i agree that buttons are better. but i wanted to discuss options instead of imposing an implementation later on.

the problem is that:

-the recovery works fine, it just doesn't with some kernels. no recovery developer can be expected to try their recovery on every possible kernel there is out there. arnab did everything right, the problem here is the platform.

-people use the "reboot to recovery" feature, that breaks if the recovery doesn't boot. because the recovery (and not the bootloader) resets the flag, so once the flag is set, android is unavailable forever until recovery successfully boots. PEOPLE SHOULD NEVER USE THIS OPTION after flashing a kernel or a recovery and should boot with buttons; but they will because it's there.

isorec should be safer because we can make it so. it could:

-clear the "reboot to recovery" flag.

-implement the isorec abort.

-or both.

any of those will prevent bricks. i'm going for isorec abort (at least at first) because it fits nicely into the scope of what isorec is already doing instead of going off a tangent. in fact i thought of abort in the very beginning, but mistakenly believed that boot-to-android would be enough of a safety net. i was wrong, it isn't.

so i'll try and find some time to implement abort. meanwhile if anyone knows where the "reboot to recovery" flag is stored and where it is handled in code, please post here. thanks!
[Galaxy S II Original Android Development] arnab:
Linked this thread from the Main OP installation instructions for people to find out what is IsoRec.
[Galaxy S II Original Android Development] the.gangster:
[MENTION=4141005]Lanchon[/MENTION]

as you asked: I would also prefer the press-button-method over the proximity-sensor-solution (even if it was possible at that early stage).

Also to read all button changes as an option to cancel the IsoRec-detection/launch if it makes it easier.

I was first wondering about the Vol-down key, as I remember from using DormianX kernel on CM11 and using Vol+Down (or Up) to switch between primary and secondary-ROM (stored in Preload). But as that key is used there on normal boot only and not on recovery boot, (and as if I got that right one shouldn't flash an IsoRec-Recovery anyway if one wants to use dual-boot on DorimanX) I wouldn't expect any interference with that.

btw: on my first try I was pretty sure, that I had picked the "reboot system" option in the recovery (while on the 2nd try I definitely chose reboot to recovery).
[Galaxy S II Original Android Development] MaTSuNg:
Hey guys,

Spent most of the afternoon reading and making logical sense of everything I've found. I must say I've had my i9100 for many years and we've been down on each other several times and I'm aware of most of its mechanics. Been running CM for a while, have used ODIN successfully on many S1's and 2-3 S2's (i9100 again) and have CM Recovery stamped on my forehead I know how it works.

After the CM 12.1 update I had issues with the partition size, was able to go around it with a set of PICO apps from a certain site I don't remember where, if there still is such a workaround I would enjoy it to say the least. I updated to CM 13 this morning from the Cyanogen updater ROM is faster than 12.1 in my opinion and I like some of the new changes. DOWNSIDE I keep getting the message that google services needs to be updated and that it has STOPPED. RECOVERY is not the same as it USED TO EVEN THOUGH I had selected in developer options that I didn't want the Recovery to be updated with future ROM updates. (BUMMER!) The error doesn't directly point to PARTITION SIZE even though it COULD be related but when I select "Apply update >>>>> SDCARD 0, it immediately says INSTALLATION FAILED, INSTALL ABORTED but I didn't even get to select anything yet... so how could he know if I wasn't gonna reflash CM or something else?

I feel sort of trapped right now in the sense that the phone works well, apart from the random GOOGLE PLAY HAS STOPPED.. but if I factory data reset I lose all my apps, and if I want to come back to an older version i can't since recovery isn't letting me do shiz.

Another concern i have : In my FILE MANAGER under /storage my SD CARD's folder name is 706D-0A0A and its creation date is 1969 - 12 - 31 drwxrwx-x

Could this have something to do with my inability to select anything in recovery? (Used to work fine before CM13 flash)

EDIT : I'm just a bit lost as to what the first steps should be, I thought of going straight to the repartition method, ISOREC but I can't flash anything and was wondering what the most efficient way to work with this would be?

Thanks a lot!

Mat
[Galaxy S II Original Android Development] Acid0057:
[MENTION=4445692]MaTSuNg[/MENTION] I'd start by reading the original post in this thread http://xdaforums.com/showthread.php?t=3313978
[Galaxy S II Original Android Development] the.gangster:
Looks like you did not read this Thread so far. It's all explained in there. Solutions as well.

Regards

EDIT: Acid was faster, but at least we recommend the same one. :) But do read at least also posts 2-3.