yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] razandtim03:
now i have twrp 3.0.2.1... thanks for you man... but my phone is stucked on Patching system image... how can I fix it?

i have 10gb partition!:confused::(
[Galaxy S II Android Development] MigoMujahid:
It's because You didn't repartition your system to 1gb

Please read and follow the instructions in this guide by saber for pc instructions:

http://xdaforums.com/galaxy-s2/development-derivatives/mod-increase-partition-size-t3011162/

For non pc guide made by lanchon:

http://xdaforums.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036/
[Galaxy S II Android Development] Jamie_oppo:
i tried this and when it went to reboot. its wont pick up my device anymore in download mode and cant install recovery or boot into os help.

fixed it. this thing stuffed up the driver and reinstall worked
[Galaxy S II Android Development] PackElend:
Hallo,

I'm at very beginning to flash CM on the S2. The phone is still in the condition as it was sold.

The first step is to flash TWRP on it an I followed the instruction on this thread and on twrp what basically the same.

I use Heimdell on Linux openSUSE Tumbleweed VM on Win 10, there are some unofficial packages but they work well. I was able to follow and accomplish all steps as described (the pit file has exactly 4 KiB). I saw the progress bar going from 0 to 100 % and short moment a blue progress bar appearing on the phone. Afterwards in reboots as expected. But when I reboot it in recovery by pressing Vol. Up + Home + Power I see the stock recovery not TWRP, what I'm doing wrong here?
[Galaxy S II Android Development] MigoMujahid:
Try flashing twrp again, use odin if possible
[Galaxy S II Android Development] TriboDoP:
You need an isorec Kernel or isorec twrp will not show up (altough it is already installed on your device).

For updating to MM/N did you already read the noob friendly guides "want to update to cm 13...."

and "how to increase system partition"

both by Saber?
[Galaxy S II Android Development] PackElend:
thx for you quick replies.

Odin doesn't recognizes the phone in win 10 though the in this thread attached Samsung drivers are installed, so that why I'm using heimdall for openSuse .

I've read the thread want to update to cm 13... but it is postulated that some custom recovery is already installed on the phone what isn't in my case, I'm starting from scratch. Anything what I found is the same nothing how to start from scratch.

Therefor I assumed flashing TWRP would be the initiale step but it looks like it isn't. So what is the first step?

I skimmed the thread Increase system partition size and the related GitHub project Lanchon/REPIT, respectively. Both seem to be pretty much the same and can be applied on my i9100xxms3 but I haven't started to follow the there mentioned steps because I'm still struggling with TWRP.
[Galaxy S II Android Development] TriboDoP:
I posted this somewhere else:

You cannot install isorec twrp 3

on stock rom/recovery.

You have to root first and install a custom recovery.

Then using a kk compatible recovery install isorec kernel (or latest cm11 with isorec-kernel) together with isorec twrp3.zip from the.gangster.

In twrp 3 repit to 1gb system/4gb data by flashing lanchon repit tool (is a zip-file).

Now you can install any mm/nougat rom + gapps.
[Galaxy S II Android Development] PackElend:
thx again, can you put those in steps on the top of the thread, avoids that others asking the same again and you repost again.

Do you mind to putting the missing information in my description

the preceding steps would be as follows:

root device

install custom recovery, but which recovery???

Ice Cream Sandwich (4.0 - 4.0.4), compatible recovery, see xda

Jelly Bean (4.1-4.3.1) compatible recovery, see ibtimes.co.uk, can it be done with heimdall as well as described here and here

KitKat (4.4-4.4.4) compatible recovery, see xda, can it be done wiht heimdall as well?

[*]does this xda thread covers all?

install KiKat compatible recovery install isorec kernel (but what if I still run Jelly Bean?), you can get it from here or is is this one. Alternatively you can straight away flash CM (correct?)but what version?

This step isn't 100% clear nor newbie friendly some more details would be helpful

install TWRP 3 as described here in this thread

follow Increase system partition size or the related GitHub project Lanchon/REPIT and resize to 1gb system/4gb daat why not 1gb system/6gb data of even higher

update to CM13
[Galaxy S II Android Development] TriboDoP:
hi

we are now completely off topic.

To avoid spamming this thread i will qoute you and answer your questions in Sabers guide " want to update to cm13"

(a little bit later as i am right busy now...)
[Galaxy S II Android Development] RafaelRivero16:
How do I install and boot up to TWRP on galaxy S2 (my home button is broken)?

Hello guys, how do I install and boot up to TWRP on galaxy S2 (my home button is broken)?

Can anyone give me a guide? I'm new to this

I'll give a thanks for the one who can help me.

Thanks guys
[Galaxy S II Android Development] Namoi:
If your rom has advanced power menu you can reboot to recovery from there.

If not there are plenty apps on playstore that do this (search reboot recovery) but you must be rooted AFAIK.

Alternatively you can use adb.

For the install procedure read the first page of this thread and then read it again just in case.
[Galaxy S II Android Development] RafaelRivero16:
[/COLOR]

If i use ADB, can u give me a clear guide how to do it? or what's the best way to root my S2, then i'll try to use flashify? I'm very new to this and this is my first time going to install custom ROM, I don't want to mess up my phone. I'm still on stock TW JB. Please help me

Thank you very much
[Galaxy S II Android Development] PackElend:
in that case you should follow th thread [Guide/tutorial] Samsung Galaxy S2 i9100 Any version to Android 6/CM13 or 7/CM14 and ask how you can access recovery without a working home button
[Galaxy S II Android Development] RafaelRivero16:
Okay, thanks
[Galaxy S II Android Development] pponsil:
Good evening, i have a i9100 intl with twrp and cm12.1 installed. Yesterday I installed lineage os 14.1 nightly but when i rebooted the phone it remained on boot logo. I tried to reboot in recovery mode but it didn't work, only odin mode works. I installed twrp as per the guide but the phone is stuck on boot logo. Can someone help me?
[Galaxy S II Android Development] Namoi:
Did you repartitioned your phone ?

Did you install this isorec twrp without a compatible kernel ?

If not it is why you are in a boot loop and also why you can't boot recovery.

If so read this from the beginning

https://xdaforums.com/showthread.php?t=3313978
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=4296852]Namoi[/MENTION]

I think he flashed that official lineage 14.1 nightly that bricked quite a number of phones according to the thread where it had been warned to not install it.

If I am right he has to recover via flashing in odin.

Anyway he should find the solution in linageOS 14.1 thread.

Regards

---------- Post added at 10:01 PM ---------- Previous post was at 09:37 PM ----------

And of course he has to check all the important issues you mentioned!
[Galaxy S II Android Development] pponsil:
Thanks a lot. I asked for help in lineageos thread and I'm waiting for answers. I think that i have to flash kernel image via Heimdall ;)
[Galaxy S II Android Development] TriboDoP:
Hi

And if not yet done do not forget to repit/increase system and data and the need of an isorec kernel to continue as [MENTION=4296852]Namoi[/MENTION] told you already.
[Galaxy S II Android Development] desvariando:
Same problem in here.

I cannot install anything anymore.

How did you fix it?
[Galaxy S II Android Development] pponsil:
I solved installing this kernel https://pa1.androidfilehost.com/dl/...IM-IsoRec-20160207-cm-13.0-i9100-for-ODIN.tar with Heimdall and then I installed from recovery the patch from the lineage os thread.
[Galaxy S II Android Development] arnab:
If you guys want to switch permanently to emulated SD ....let be know...il make changes in the official twrp that way... btw Il be back soon.
[Galaxy S II Android Development] OllieW:
Good to know that emulated-SD is also supported by you. There is already a test version of TWRP 3.0.3 with emulated SD support by rINanDO and a lot of discussion how to realize conversion from non-emulated to emulated internal SD.
[Galaxy S II Android Development] xNombre:
I thing almost everybody now uses emulated SD, why not to create second, emulated twrp version!
[Galaxy S II Android Development] laptopu:
Yes I'd love to see emulated please [MENTION=414800]arnab[/MENTION] :)
[Galaxy S II Android Development] arnab:
K il go ahead and make some changes for that...But I need a full consent of everyone. Anyways will work on DU from feb end. and BLN too.
[Galaxy S II Android Development] laptopu:
[MENTION=414800]arnab[/MENTION] might be a good idea then if you want to get a broader view to ask for opinions in the lineage 14 official thread? For me the two biggest names are [MENTION=2222292]rINanDO[/MENTION] and [MENTION=6159291]Lysergic Acid[/MENTION] as they are key rom devs who certainly influence me a lot.
[Galaxy S II Android Development] Namoi:
+1 for emulated storage (and wipe option for preload just in case :D )
[Galaxy S II Android Development] arnab:
Lol iam a noob then aint I :D and dont knw ROM development :p
[Galaxy S II Android Development] laptopu:
Doh didn't mean that to sound the way it did :p :D
[Galaxy S II Android Development] darkkham:
/boot partition wipe option. :D
[Galaxy S II Android Development] Lanchon:
besides, you would need to resize to 200mb at least. because i think that f2fs has around 100mb overhead, which means that 105mb would only give you and effective 5mb cache partition. but tools that use cache expect 100mb there.

again, there is less and less reason to convert cache from ext4, except OCD.

people are OCD'ing on this converting system also, which is read only, and again makes zero sense. even for daily flashers the ext4 system partition is better: because the partition is formatted during every flash, the data is written sequentially anyway, so there is again no reason to use f2fs. in fact there is a fair chance that flashing on f2fs /system is slower, maybe significantly so.

IN THE END:

people should convert only /data if they so choose, and that's it.

not system, not preload, not cache.

just data. and maybe the sdcards.

---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------

ok i don't really know the booting seq. i'm just point out potential dangers; there's a lot that i don't know.
[Galaxy S II Android Development] arnab:
lol system is ro...not needed for f2fs.I get ur point about cache...but still if u can come with a repit soln which u blv is safe..then only Il give a go ahead. Until then this is not a bug anymore..Thanks alot [MENTION=4141005]Lanchon[/MENTION].
[Galaxy S II Android Development] Lanchon:
the autotrim is only enabled for f2fs partitions. nothing changed for ext4 which trims by vold fstrim dotrim as always.

the response you are looking for: benchmark and tell us :)
[Galaxy S II Android Development] the.gangster:
[MENTION=6022607]Ojdanic[/MENTION]

I haven't read at all, that /system would be already supported being on F2FS. Only /cache and /data is mentioned, also in the latest commit that is going to be included in next nightly build.

So I would strongly recommend, not to convert /system at all.

Just for me to understand it:

What's the purpose of disabling a 100mb limitation, if 98mb of it would already be needed for its own filesystem management?
[Galaxy S II Android Development] arnab:
It doesnt take 98mb k..it takes around 44mb in f2fs.
[Galaxy S II Android Development] the.gangster:
[MENTION=414800]arnab[/MENTION]

You were the one pointing to that post where they wrote:

But anyway. No need to go into deep any further (from my side).

While I was writing the last post, there were already new posts by you and Lanchon, so it was already kind of outdated when I sent it.

It seems, we currently all agree, that F2FS only makes sense on /data.

And btw: thanx alot for the IsoRec-TWRP 3.0.0. I'll give it ago upon next flashing.
[Galaxy S II Android Development] the.gangster:
Damn,

starting from CM12.1 with [MENTION=4141005]Lanchon[/MENTION] 's kernel-Lanchon-TRIM-IsoRec-20160206-cm-12.1-i9100 with IsoRec-TWRP-2.8.7.0-Recovery I flashed this TWRP-3.0.0.0 a couple of minutes ago.

Had checked hash before flashing. I felt safe as I thought, either I could start into the TWRP-recovery or (on a fail) I would have CM-recovery.

But: Now I am on Boot loop (right after Samsung logo)

So it looks like the compressed recovery is detected in mmcblk0p6 but cannot be loaded.

Anyone tested this already with CM12.1?

Also read in the bug-reports, that also [MENTION=5276891]ultravy[/MENTION] had the same problem with CM11 on Trim-IsoRec-Kernel.

There [MENTION=414800]arnab[/MENTION] responded isorec would only be present Lollipop upwards. But imho you can't put it this way, as Lanchon also published a kernel for CM11.

So please: be warned.

EDIT: as written in separate post: even a second try from scratch again led to boot looping device.
[Galaxy S II Android Development] Skyline:
I tried it with cm12.1 but with dorimanx and its working fine here don't know about stock kernel
[Galaxy S II Android Development] the.gangster:
UPDATE:

Meanwhile, after recovering to non-isorec-kernel with odin and reflashing from there to IsoRec-kernel and IsoRec-TWRP-2.8.7.0-recovery I gave it yet another try and:

same result -> bootloop

So I have to doubt, that it is compatible with kernel-Lanchon-TRIM-IsoRec-20160206-cm-12.1-i9100.

Maybe [MENTION=4141005]Lanchon[/MENTION] and [MENTION=414800]arnab[/MENTION] can look into that once more.

From my point of view at least it would be dangerous to distribute IsoRec-Recoveries that are not compatible with every IsoRec-Kernel without showing that in their name.

[MENTION=5798657]Skyline[/MENTION]

thank you for reporting. So maybe it's really just a difference in the kernel.

Update: Bad news: Just got yet another acknowledgement from yet another user, who suffered the same on CM12.1
[Galaxy S II Android Development] Dr AM:
I tried it on Minimal OS which runs on 5.1.1 and face same issue

Sent from my GT-I9100
[Galaxy S II Android Development] arnab:
There is nothing wrong with the recovery... Its compiled with DU source... If it was recovery... It would never had worked... Maybe its a problem with the recovery injector... Anyways use disable isorec which rm - rf the /recovery partition.. Then flash the new one.
[Galaxy S II Android Development] wdevil12:
flashed on top of dorimanx kernel, everything is working.
[Galaxy S II Android Development] arnab:
And btw why are u flashing an isorec recovery from another isorec recovery...u must flash an isorec recovery frm a normal recovery of twrp or cm... Bcoz the isorec recovery ur flashing from.. Ie 2.8.7.0 mounts /dev/block/mmcblk0p6 partition and remains in use... Then u try to flash the new 3.0 twrp which tries to replace files that are currently in use... So plzzz flash any isorec recovery from a non-isorec one.
[Galaxy S II Android Development] cherryb8844:
What you said buddy I tested your last DU 9.8 and I have your isore installed on official cm build when I was switch back to [MENTION=1597520]Markox89[/MENTION] build I have the recovery lanchon twrp that you provided 2.8.7.0
[Galaxy S II Android Development] Lanchon:
obviously this recovery is not compatible with the cm-12.1 kernel, for unknown reasons. it's not arnab's fault, he can't be expected to test it under all possible kernels.

---------- Post added at 02:36 AM ---------- Previous post was at 02:28 AM ----------

don't worry the world as we know it is not collapsing lol, he was mixed up with some other idea or partition as he wrote that. relax, you *can* flash any isorec recovery from any other recovery, be it isorec or not. TWRP 2.7 doesn't mount the recovery partition; no recovery can ever mount that partition because it doesn't contain a file system at all.
[Galaxy S II Android Development] arnab:
What I meant by mount was ..the isorec recovery resides on mmcblk0p6 and it remains in use when u boot to a isorec recovery...Now by the injector script...the kernel loads the raw ramdisk into memory from there...and then you are trying to replace that very same ramdisk whose contetnts are currently in use...Its like booting into windows and try formatting the windows partition itself where format fails. Granted it doesnt have a file system..and its emmc...even though its always best if u try to install any isorec recovery from /boot ie p5 partition.
[Galaxy S II Android Development] arnab:
Can anyone test the twrp on official cm-12.1 and report here.
[Galaxy S II Android Development] Lanchon:
no, it doesn't work that way. the partition is read once and copied to memory; it doesn't remain in use.

the exact same happens to the kernel partition during standard recovery boot: it is read once and doesn't remain in use. that's why it was always the case that you could safely flash kernels from any recovery, even though you were overwriting the partition were the kernel and recovery was stored. in the exact same way, now you can safely flash any isorec recovery from any recovery (standard or isorec).

recoveries always run from ram only. that's why from recovery you can do extreme stuff to the emmc, like repartitioning it (look for lanchon repit). (recoveries could in theory be run from disk of course, but no setup ever does that.)

---------- Post added at 04:29 AM ---------- Previous post was at 04:26 AM ----------

for followup on a generic fix for non-working isorec recoveries, see here:

http://xdaforums.com/galaxy-s2/orig...ated-recovery-galaxy-s2-t3291176/post65715289
[Galaxy S II Android Development] arnab:
I think I mentioned already that it boots from ram. anyways you are right...that it doesnt remain in use. In future I might add a rm -rf mmcblk0p6 in the updater script b4 executing package_extract_dir or b4 the write_raw_image.
[Galaxy S II Android Development] Lanchon:
i don't know what you mean by "rm -rf mmcblk0p6". keep in mind that that partition is never mounted and has no file system nor files to delete. maybe you are thinking that the partition has the recovery ramdrive files dumped in a file system, when in fact it just has the raw image of a tarball of the files. check out this code, it will clear all doubts:

https://github.com/CyanogenMod/andr...mmit/9bfbaf337207359ef6aefe0a329a3b760054a6b7

btw, that's the only time mmcblk0p6 is ever read, way before the recovery's 'init' is invoked. the recovery can do what it likes to mmcblk0p6 at any time without affecting itself: it is never read again.
[Galaxy S II Android Development] the.gangster:
[MENTION=414800]arnab[/MENTION]

don't know if you got a notification. I tried to get your attention on this thead .

As there is already some development and brainstorming and testing ongoing that we tried to take separate from the CM14-thread...

If you can find the time, it would be great you'd share your views in there.
[Galaxy S II Android Development] Meandi51:
Guys, I really read a lot the past days in different threads in xda in order to figure out for me

how it works to revive good old SII with a MM Rom (awarded DU 10.6).

I am not unfamiliar with flashing (just a user).

Did several devices and never failed in the end ;).

But for this one here, the more I read the more I confused I get.

My situation :

there is CM 11 and CWM 6.0.5.1 installed (years ago).

My planning:

flashing IsoRec_TWRP_3.0.0-0_i9100.zip in cwm,

then repit by lanchons zip,

then flash DU + pico gapps.

Voila.

But isorec twrp does not keep (I guess for incompatible kernel)

And at this point now I stuck.

May anyone pls just brief me how to succeed.

Any assistance is much appreciated.
[Galaxy S II Android Development] TriboDoP:
Flash this cm11 and continue as planned:

https://www.androidfilehost.com/?fid=673368273298924336

Latest twrp ist:

https://www.androidfilehost.com/?fid=24591000424954841
[Galaxy S II Android Development] Meandi51:
That was the trick - mission accomplished :)

Thanks a lot for your support
[Galaxy S II Android Development] TriboDoP:
You are welcome!

(Grüss Gott Bayern)
[Galaxy S II Android Development] Meandi51:
Vergelts Gott und Prost :svetius:
[Galaxy S II Android Development] Bhavesh_khatri:
Compatible Isorec TWRP 3.0.2 for i9100G ? any link? or thread? This failed to install. [MENTION=6560258]the.gangster[/MENTION]
[Galaxy S II Android Development] wihushae:
Hey!

I've TWRP 2.8.7.0 on my sgs2 (i9100) and want to update to the latest 3.0.2.0 version. Already tried to install the IMG in the TWRP recovery and also with the TWRP app, but the result is always the same: the Version remains at 2.8.7.0. what's wrong here? Btw. My current ROM is slimlp 5.1.1

Thanks!
[Galaxy S II Android Development] jojobg:
And you have isorec enabled ROM and you have followed the reboot instructions as part of the install procedure ?
[Galaxy S II Android Development] wihushae:
Actually I don't know if the ROM is isorec enabled...

Reboot instructions are rebooting again into recovery, right?
[Galaxy S II Android Development] jojobg:
Yes ensuring you have isorec enabled kernel/rom, install isorec via your favorite method and make sure you boot first into recovery or else no version change ;)
[Galaxy S II Android Development] the.gangster:
I don't know if i9100g has IsoRec-support. Due to different hardware most developement for it will be done separately. And I only wrapped arnab's TWRP into a flashable zip. So I only allowed it to install on the HW it is known to be build for. If you want to do experiments with this TWRP here on your device just install it using one of the plenty other methods. But I would recommend to simply ask in a thread for the i9100g.

Just from reading this I would tell you that your current ROM/kernel obviously does *not* support IsoRec Recovery loading.

And current official version is 3.0.2-1 by the way.
[Galaxy S II Android Development] wihushae:
Thanks for your reply! I switched to lineageos and afterwards I could install twrp without any problems. :)
[Galaxy S II Android Development] GreekDragon:
TWRP 3.0.3-0

Hey guys. :)

I made an updated version of TWRP for our device since the current one is really outdated.

For update. Just flash the zip on recovery.

Download
[Galaxy S II Android Development] laptopu:
Thanks, is there a changelog please?
[Galaxy S II Android Development] thearczoro:
Just tested and bootloop, thanks. No Isorec?

update:

My phone now, Bootloop and forget to enabled USB Debugging. Hhmm.. Any suggestions?
[Galaxy S II Android Development] 0670:
No problem and fully working, thanks.

Edit: On official lineage 08/02 build
[Galaxy S II Android Development] the.gangster:
[MENTION=5651185]GreekDragon[/MENTION]

as you've build it on 7.1.1 I assume it will show the same severe problems if run from a previous android build!

We had that already with the first 3.0.0 release that they would bootloop on devices with CM11 or CM12 due to incompatibilities in selinux stuff. That's why arnab invested time into fixing it back then.

EDIT: meanwhile confirmed by [MENTION=6616449]thearczoro[/MENTION] to affect CM13, too.

## A T T E N T I O N ####

## people be warned if combining this recovery with non-Nougat builds! ##
[Galaxy S II Android Development] thearczoro:
I'm on CM13 with Official TWRP by [MENTION=414800]arnab[/MENTION] before. Bootloop and my USB Debugging is disabled. Can you help me [MENTION=6560258]the.gangster[/MENTION].