yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] ze7zez:
Official_TWRP_App-Premium-1.15.apk	md5: 89f3088a068ca4986b8cca1d3708be0a

Are you sure apk comes from a legitimate source?

In my opinion, this is a mod.

Can you give the origin of the file?
[Galaxy S II Android Development] toy_story:
I'm sure of this file, but if you are not sure, then here's the original for you - Official TWRP App

But for me, this official application does not work and I get stock recovery of los, without twrp. The mod works fine and many times helped many, but want an official application, please.
[Galaxy S II Android Development] ze7zez:
If you need a special version of apk, download from apkmirrors.

You can have more confidence in apkmirrors than in warez.
[Galaxy S II Android Development] toy_story:
Do you not trust https://play.google.com ?

I only trust myself, XDA and 4PDA

I must know very well where, when and what applications and files I should take. Do not have to offer me something, better help the members of the forum more often.
[Galaxy S II Android Development] ze7zez:
Surely you do not help when you propose illegal versions of files that may (but need not) be more harmful than helpful. EOT.
[Galaxy S II Android Development] toy_story:
I wrote that you, better-helped forum users, and not only engaged in criticism and enough to write harmful posts.
[Galaxy S II Android Development] AdnanShah:
problem in installation of Recovery

am not able to install TWRP recovery 3.1.0.0 on my phone Samsung Galaxy S-II (GT-I9100) through Odin 3.12.3 but it shows the message at the end "complete (write) operation failed" (Failed 1).

I also try CWM and one another recovery to install it through Odin but it shows the failed message. What to do?
[Galaxy S II Android Development] Nobby1960:
You can't flash TWRP 3.1.0-0 as a .tar file via Odin on the S2. Try to flash the attached kernel with a built-in older TWRP. Now you can flash the newest TWRP as zip file from [MENTION=6560258]the.gangster[/MENTION], see here.

If all fails flash the stock ROM through Odin, go into download mode an flash the attached kernel.
[Galaxy S II Android Development] popekabu:
heimdall frontend wont open

Requires some .dll files. I have gotten them and now it says application was unable to start correctly. Please i need help asap. Thank you

---------- Post added at 09:56 AM ---------- Previous post was at 08:59 AM ----------

I used odin and it worked ! with the isorec
[Galaxy S II Android Development] yurais:
Hello

any chance to get the Zip file for install over recovery?

Am using CWM Recovery and need to upgrade to TWRP, the link on the downbload section is not working

anyone may upload pls ?
[Galaxy S II Android Development] yurais:
I tried this...

no erros so far, but, after rebooting recovery, I still have the same old TWRP version, the one flashed with the kernel...
[Galaxy S II Android Development] the.gangster:
If things haven't changed during the last 4 years the most likely reason is:

Your current kernel doesn't support IsoRec.
[Galaxy S II Android Development] yurais:
OK, this is what I did.

flashed stock touchwiz 4.1.2 via odin

Flashed this file: stock_kernel_twrp_1120-signed-for_Odin.tar via odin

then tried your .zip file...

if thats wrong,, then Am having a bad time finding the appropiate IsoRec, can you please point me in the right direction? as of what to write ?

Should I extract the boot.img file from lineage 14 Rom, and write it to boot partition ?

as far as I know the lineage 14 boot is IsoRec compliant, and my purpose is towrite lineage os 14 to the phone.
[Galaxy S II Android Development] the.gangster:
Yes. That should work then.

Patch for IsoRec got merged when 12.1/13 was current build.

You could also find kernels Here

More information and links in the respective thread.
[Galaxy S II Android Development] arnab:
Yes ur right...its a raw image. what i meant by rm -rf was just metaphorical for expressing delete...I was thinking of running this

dd if=/dev/zero of=/dev/block/mmcblk0p6 bs=4k
[Galaxy S II Android Development] the.gangster:
I was not at all fingerpointing or questioning who's fault this would be.

I just wanted to report, that there is a severe issue on CM12.1 (and obviously CM11), and to warn others, not to end up with an unusable phone.

Also, as [MENTION=4141005]Lanchon[/MENTION] already explained, it is absolutely possible to switch between IsoRec-recoveries directly.

And as I tested the most likely case, which is imho, that someone who is interested in TWRP3 already runs TWRP2.8.7, I don't see, what would be wrong in what I did. And on top, I tested this twice, not to post some rubbish nonsense here. In all the years of flashing and testing, these two revivals were increasing my flashcounter to "3", so I guess I know quite well how to handle recoveries and how to keep my device alive without using odin.

The only thing I was interested in from the very beginning is, that the name of the TWRP upon download is named in a way, to better reflect, that it is an IsoRec-recovery, and now, to also reflect, for which platfoms it is. As these files are shared all around the world without everyone knowing where to read first.

That's all I wanted to make aware of.
[Galaxy S II Android Development] good8life:
cache f2fs wipe error 255
[Galaxy S II Android Development] arnab:
IsoRec is mentioned. I can't help people who blindly downloads stuff. Also in the download page its mentioned. There are two places where its mentioned amply clear. And also coming to the platforms...I am myself finding out cm-12.1 has problems. Its not even been 24hrs yet. I think you imagine me as a robot.
[Galaxy S II Android Development] dwarf_hero:
I've updated/flashed from "recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)" - to new 3.0 directly from recovery with no problems. After flashing zip I've reboot to recovery. New recovery works fine.
[Galaxy S II Android Development] hitman4u:
LA's CM13 build 03-07 ,

Lanchon isorec trim kernel for i9100

Arnabs isorec twrp 2.8.7,

Succefully flashed arnabs isorec twrp 3.0.0.

Love it, its Awesome :):thumbup:

Thanks for [MENTION=414800]arnab[/MENTION] for giving such a wonderful gift.

Thanks for [MENTION=4141005]Lanchon[/MENTION] , obviously for the isorec trim kernel and the assurance about flashing arnabs isorec twrp 3 with arnabs isorec twrp 2.8.7

Last but not least , thanks for [MENTION=6560258]the.gangster[/MENTION] for notifying the release of arnabs 3.0.0 and also for creating a doubt in my mind about flashing it with isorec twrp 2.8.7:D:thumbup:
[Galaxy S II Android Development] Troubadour666:
little report

Hi [MENTION=414800]arnab[/MENTION] ,

strange things appen to me

yesterday night, i try your new twrp over my slimlp 5.1 with dagon kernel and twrp 2.8.xx (or 2.7.0 , dont remember now !)

but at recovery, i never have it, always old recovery 2.8.xx.

15 days ago i tryied some cm13 based roms with isorec and stop tests of cm13 roms.

i restored at that moment my SlimLP and used it until now with dragon kernel and twrp 2.8.xx.

yesterday, when trying your new twrp 3.0 , i used too the lanchon disabler isorec and reflash your twrp 3.0, but i never have it !!!

so today, now, i restored an old AICP 6.0 , one of the 1rst one with isorec recovery i tryed when i have that session tests of CM13. And now, when i restored it, i rebooted in recovery and have your new twrp 3.0 !!!

its good for me to have it now, to make a little themefor U, but have you an explain of what i have badly done to have it today, i mean your twrp 3.0 without flashing it ?

thanks
[Galaxy S II Android Development] arnab:
[MENTION=6560258]the.gangster[/MENTION] Changes done according to what you wanted.
[Galaxy S II Android Development] arnab:
Cm-13 has default TRIM enabled. You dont need to seperately flash a new kernel anymore for TRIM.
[Galaxy S II Android Development] the.gangster:
[MENTION=4775725]Troubadour666[/MENTION]

you can flash IsoRec-Recoveries as often as you want to. As long as your kernel doesn't support IsoRec-Recoveries they will not be used at all and won't overwrite kernel-embedded recoveries either. So the kernel-embedded recovery will continue to be loaded.

But once you flash an IsoRec-supporting kernel (again), the recovery in the recovery-partition will be detected by it and get loaded.

That's what happened to you.
[Galaxy S II Android Development] wdevil12:
[MENTION=414800]arnab[/MENTION] it is not cm12.1 rom that causes a problem, it is only the kernel's issue included in the rom. With dorimanx kernel twrp3 runs well here
[Galaxy S II Android Development] Troubadour666:
i imagined that now, after deduction :)

thanks Man.

PS : i dirty flashed AICP 03072016 , without gapps (because my SAVE restored them and the DIRTY FLASH seems to keep them too) , my SAVE have some stuff from /system , like LatinIME.apk (and some other files you can see on SS ) on /data , coz i havent repit my system for now. The only things i have done after dirty flash was to move LatinIME.apk again and other little files from /system to /data again, scratching those restored with my SAVE.

During "AICP is upgrading....." , i saw Google Play services.... , about 57 apk to process. (Sure i used file manager from twrp 3.0 to move the files to keep place on system)

Sory for OT about AICP.

thanks
[Galaxy S II Android Development] hitman4u:
Yes [MENTION=414800]arnab[/MENTION] I know that. I flashed the trim kernel before the merge with cm13 nightlies. Just for the record I mentioned that. And thanks for the reply.:):thumbup:
[Galaxy S II Android Development] Lanchon:
hey arnab, could it be that TWRP 3 requires a marshmallow kernel? if you are in contact with dees_troy, maybe you could ask?

your mistake for converting to f2fs without reading!

isn't dori a marshmallow kernel?
[Galaxy S II Android Development] arnab:
Ya i will do that.
[Galaxy S II Android Development] good8life:
I'm not converting to f2fs, just wipe cache with f2fs , after I have error 255.

I'm converting long time cache and data to f2fs.

Problem wipe cache
[Galaxy S II Android Development] arnab:
Though twrp is set to permissive by default from here. [MENTION=4141005]Lanchon[/MENTION] Do u think it might be any sepolicy issue that is incompatible with L. Dori runs in permissive.

PS: Added IsoRec patch to my kernel.
[Galaxy S II Android Development] Troubadour666:
theming twrp : simple as 'bonjour'

little tries on theming our new recovery (thanks again [MENTION=414800]arnab[/MENTION] )

following this post from ( [MENTION=1019789]manbat[/MENTION] )

http://xdaforums.com/showpost.php?p=65641992&postcount=101

i took the LtBLUE_BACKGROUND_ui.zip and made 10 changes on it only (some colors in ui.xml and 2 files in images folder background.png and main_button.png)

not so bad to begin theming.

thanks.
[Galaxy S II Android Development] wdevil12:
more correctly said, dori sets selinux to disabled status.
[MENTION=4141005]Lanchon[/MENTION] no, dori v11 branch is for cm12.1
[Galaxy S II Android Development] Lanchon:
i'm completely ignorant of everything selinux, so i can't really help. but from here...

http://seandroid.bitbucket.org/Policy.html

"SELinux kernel policy is presently compiled as part of the Android build and added to the ramdisk image so that it can be loaded by init very early in boot, before mounting the system partition."

correct me if i'm wrong: isn't selinux a kernel extension that is configured from early userspace (sets policies, enables, etc.)? if this is true, then...

isorec switches to TWRP's init extremely early in the boot sequence. nothing worth noting is done before the switch, in particular nothing selinuxy: there should be nothing of selinux configured before TWRP's init runs, no matter if the kernel is CM12.1 or CM13.

in fact, initramfs_data.cpio (the one real ramfs bundled with the kernel, find it in your $OUT dir) that carries isorec doesn't even have a sepolicy file. sepolicy files are in the other two .cpio files (android and recovery) nested inside initramfs_data.cpio (in its stage1 dir). those .cpio files aren't even expanded, so their sepolicy files are never accessible by the kernel during isorec boot.

so this should rule out any sepolicy issue coming from the kernel: all of selinux config -if any- during isorec boot comes from your TWRP 3 .cpio file and is loaded by your init script.

but i think you should know that there's one big issue in isorec that comes from:

1) my limited understanding of boot sequence at the time i wrote isorec.

and 2) an ugly requirement of the standard CM recovery ramdrives.

and the issue is this:

when the isorec ramdrive is expanded prior to its init being called, it is not expanded over a clean file system: several folders already exist, such as /dev/block, and also the nodes of the emmc and its partitions. this is required for the standard CM recovery ramdrives to boot. (to see what the recovery gets preloaded on the file system, see initramfs_data.cpio: the preloaded folders and nodes all come from that archive.)

in retrospect, i should have coded isorec to hand out a clean slate to recovery, and i should have touched the CM recovery ramdrives to build whatever folder and nodes they need. the present solution is messy.

on the other hand, note that isorec on dorimax DOES hand out a clean slate. and my prediction is that the CM recoveries won't boot there if anybody ever test them.

if i had time i would rewrite CM's isorec to hand out a clean slate too, and i would update all the CM isorec recovery files that i publish to boot from clean slate. this way, wherever you boot from, the isorec recovery would always receive a consistent state: always a clean slate.

that said, AFAIK the state of the inherited file system is exactly the same using CM 12.1 and CM13 kernels, so this is probably not the problem.

it looks like maybe TWRP 3 requires some marshmallow kernel feature?
[Galaxy S II Android Development] chhapil:
Working fine on JB Neastock with my Dorimanx JB Isorec build.

I'm the only ancient troll here :D
[Galaxy S II Android Development] good8life:
flash nightly

wipe cache
[Galaxy S II Android Development] arnab:
PLz file it under bugs section.
[Galaxy S II Android Development] wdevil12:
As far as I guess from my poorly user knowledge, there has to be something that [MENTION=5811506]gsstudios[/MENTION] merged in dori beta28, as the changelog says

"DorimanX 11.0 b028 (STABLE)

- Merged a few kernel updates from CM13"

I am guessing that's why cm13 default kernel and cm12.1 with dori kernel can run twrp3.
[Galaxy S II Android Development] arnab:
Added themes in 2nd Post.
[Galaxy S II Android Development] Troubadour666:
[MENTION=414800]arnab[/MENTION] , just share the 4 pngs for the transparency of buttons i sent you .

thanks
[Galaxy S II Android Development] arnab:
Plz add them in the main theme and name it as bonjour_transparent. And then mail me.
[Galaxy S II Android Development] good8life:
Sorry I don't have, I came back to recovery 13.01

I'm try recovery 08.03

A error I have from 07.03 recovery
[Galaxy S II Android Development] good8life:
08.03 recovery

Wipe cache error
[Galaxy S II Android Development] fireburner-de:
[MENTION=414800]arnab[/MENTION] I got just informed by a user on a german android board, that your TWRP3 is incompatiible with [MENTION=4141005]Lanchon[/MENTION]s repit script.

He got the following message:

It seems that some shell tools like parted are missing.
[Galaxy S II Android Development] arnab:
F2fs needs minimum 100mb partition.. Our cache is 98mb
[Galaxy S II Android Development] arnab:
U mean activelogs=2???
[Galaxy S II Android Development] Lanchon:
well that's a mount option. i just looked at mkfs.f2fs and it doesn't seem to have similar option, so i don't know.
[Galaxy S II Android Development] fireburner-de:
[MENTION=414800]arnab[/MENTION] [MENTION=4141005]Lanchon[/MENTION] did you guys see post #90?
[Galaxy S II Android Development] xn0live:
Hi,

where is the option mount & storage to format system, data, cache
[Galaxy S II Android Development] the.gangster:
I made a comparison of the two twrp recoveries yesterday already and can confirm: Twrp misses parted in its sbin folder.

In detail (just if someone depends on them) these are missing:

dosfsck

dosfslabel

fix_permissions.sh

fsck_msdos

libexfat.so

libgccdemangle.so

libjpeg.so

libstlport.so

libunwind-ptrace.so

load_policy

mkdosfs

mkfs.exfat

mkfs.vfat

modprobe

parted

r

This is just for information.
[Galaxy S II Android Development] Saber:
Nope, that's not why twrp3 works for dori kernel. Dori kernel handles isorec in a similar way to CM12.1 and CM13, but I think that the recovery flags are not removed making it able to boot into TWRP 3.0.

Then again, what I've just said could be wrong since I didn't create the isorec compatibility script for dori kernel (all credits to Lanchon)

gsstudios
[Galaxy S II Android Development] Lanchon:
no i havent seen that, thanks!

---------- Post added at 09:50 AM ---------- Previous post was at 09:48 AM ----------

dosfsck and nkdosfs are particularly noteworthy. i wonder if TWRP 3 can format in vfat...
[Galaxy S II Android Development] the.gangster:
[/COLOR]

in TWRP 3, there are the following new ones:

fatlabel

fsck.f2fs

fsck.fat

libbase.so

libc++.so

libexfat_twrp.so

libgpt_twrp.so

mkfs.f2fs

mkfs.fat

permissive.sh

sgdisk

simg2img

So I guess, mkfs.fat will do it instead.

I wonder, if it still could format exFAT. (only see an libexfat_twrp.so but no mkfs.exfat)
[Galaxy S II Android Development] :
adb sideload seems like doesn't work with twrp, i tried use it with cyanogen recovery and all went fine, but with twrp adb sideload doesn't work
[Galaxy S II Android Development] SAMDestroy:
sideload an update will instantly work but for full adb commands i have to wait a while til twrp is showing "failed" and then i can use all adb commands.
[Galaxy S II Android Development] arnab:
U need to have kernel exfat support.. Mine does.. Cm kernel doesnt have.
[Galaxy S II Android Development] Draky50110:
As it is not written on 1st post : I currently have IsoRec-TWRP by Arnb installed, alongside with CM13 nighlies.

Can I just flash this TWRP 3.0 directly ?

I don't want to "disable IsoRec" and lost ability to flash ZIP because of the buggy CyanoRecovery installed with CM13 nightlies.
[Galaxy S II Android Development] the.gangster:
[MENTION=3582785]Draky50110[/MENTION]

Yes you can
[Galaxy S II Android Development] arnab:
[MENTION=4141005]Lanchon[/MENTION]...i have a small test proposition for u...if u think it will succeed...what if I tell u we can flash the lzop directly on the recovery partition in download mode.
[Galaxy S II Android Development] Lanchon:
yes, it should work, i don't think RECOVERY is special in any way to prevent the bootloader from flashing it. but what will happen to the flash counter, i don't know. anyway, i won't do it because i don't use download mode. and if i do i use heimdall exclusively while most people use odin in windows. i rather have people unbrick using tested and documented methods to load philz touch or whatever and go from there.

but if you want you can create a 'tarmd5' or whatever odin file with a recovery AND a kernel inside, so that bricked people can unbrick in one step.

another step you can take to ease unbrick via odin is to replace the outer .cpio of a kernel (the one that bundles the two .cpio's inside it and runs one of them, android boot and recovery boot) and replace it with only the recovery cpio. then you can flash this kernel via odin, and the device will never try to boot android and go directly to your recovery. your TWRP 2.8.7.0 with a standard stable kernel such as CM's and android boot disabled would make the best tool to unbrick via odin.
[Galaxy S II Android Development] arnab:
ur not getting me...I can use heimdall...manually select the pit ..select recovery.and then directly flash it on recovery partition...the lzop file...no kernel required.
[Galaxy S II Android Development] Lanchon:
lol yes i know! our usual flash script just does that :) i thought u wanted to publish your recovery in odin flashable format
[Galaxy S II Android Development] arnab:
I will put the simple lzop file with instructions...maybe this way we can get a official twrp
[Galaxy S II Android Development] laptopu:
Thanks for this [MENTION=414800]arnab[/MENTION] it's great work. Before I take the plunge, is there likely to be an update to address any of the points raised in this thread? Also the twrp website says i9100 will never be official so I guess they will not take up your work which is a shame, is that just the way things will be?
[Galaxy S II Android Development] arnab:
First dont quote OP...2nd that thing mentioned in twrp website...that thing no longer implies. We have changed the equation or more specifically [MENTION=4141005]Lanchon[/MENTION] did.
[Galaxy S II Android Development] laptopu:
Great (sorry about quoting op). So what happens next to get this official? And thank you :)
[Galaxy S II Android Development] TPXP:
Confusing partition naming in the "Wipe" menu

Hey!

Many thanks for this excellent port, it works like a charm with CM 13. I just wanted to let you know about a little issue I'm facing while using it :

If an SD card is put inside of the phone, some labeling is confusing. Indeed, when you go to the "Wipe" section, and touch "Advanced" to select the partitions to wipe, it will show two "SD Card", which makes it a bit confusing for the user to know which one is the real SD card (the other one is internal storage). I wiped my Internal Storage thanks to this, a quite enjoyable experience. :D

Maybe a small patch should be applied to make it clearer for everyone ?

Thanks in advance for your help ! Keep up the good work !

TPXP
[Galaxy S II Android Development] arnab:
Its not a port. Its source compiled. And your problem is already addressed in bugs section.
[Galaxy S II Android Development] arnab:
Added instructions and required files in the main OP about how to flash the recovery in download mode using heimdall which is odin's counterpart. Plz read the instructions very carefully before proceeding. Remember u must have [MENTION=4141005]Lanchon[/MENTION] isorec support in kernel tomake this work. I added this process since cyaogenmod recovery is broken, we need a direct flash method like odin. I didn't add linux version as its very complicated and requires advanced users.
[Galaxy S II Android Development] YbkcLtwv:
I moved from stock ROM to i9100 + CM13 + TWRP3 + GApps = Working using Heimdall 1.4.0 on Debian 8.3 ;)

See post #27 in Gapps + Cm12.1 + I9100 = Working in CyanogenMod Forum → Samsung → Samsung Galaxy S II - i9100, i777, hercules, sc02c → Samsung Galaxy S II Release and for Heimdall on Linux: [TUTORIAL] Flashing i9000, i9100 or i9300 with Heimdall in andmod.blogspot.de (sorry, I am not allowed to post external links).
[Galaxy S II Android Development] arnab:
Majority uses Windows. But for a change, I am more accustomed to linux.
[Galaxy S II Android Development] Galse de HSM:
when i press start i see this error:

Initialising connection...

Detecting device...

Claiming interface...

ERROR: Claiming interface failed!

what should i do
[Galaxy S II Android Development] arnab:
Power off and start the download mode again
[Galaxy S II Android Development] fireburner-de:
Looks like Mint. Is it the Ubuntu based version or LMDE?

sorry for OT, but I like to see people using Linux and I am on my way to replace as much Windows as possible, with Linux :)
[Galaxy S II Android Development] arnab:
Mint 17.3 kde ubuntu based.
[Galaxy S II Android Development] emilianoheyns:
Can you outline the steps you took? I'm on Linux, my S2 is on stock 4.1.2.