yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] K9100ii:
Repaired my volume buttons (not a very good repair, but it works for all recovery, download (which doesn’t get detected by the computer because I still haven’t repaired micro USB, looks extremely small! Maybe just replace USB board with one from eBay at risk?) and volume controls, basically everything) and restored my nandroid backup for the second latest build from TWRP. Phone boots perfectly now. If I try to install the latest build, I always get the loop of bootloader, black screen, bootloader, black screen and repeating without stopping. Whatever I do, even with a clean install, it doesn’t boot. By the way, this is an actual issue! It shouldn’t really be bricking phones. I’m going to stay on the second latest build for now until a new build is released. For extra information, with the old boot.img on the new build, it gets to the LineageOS boot animation whereas the latest boot.img doesn’t do anything but that loop. I was restoring the nandroid backup where after restoring the older boot and recovery, the phone rebooted when I didn’t want it to and it got to the LineageOS boot animation, but I didn’t test beyond that. Rebooted back into TWRP, tried restoring the nandroid backup again, which completed without reboot this time, and it fully booted just as it used to be. Looks like the issue is somewhere in the kernel!
[Galaxy S II Android Development] rINanDO:
Thanks for your info. Restoring boot.img is a very interesting. Looks a kernel issue with a specific configuration unless everyone has issues with this one month old build. Are you using f2fs? I have 2 s2 running with ext4 and the repit configuration in OP.
[Galaxy S II Android Development] K9100ii:
Hi,

Yes, it really is very interesting. I am using F2FS on the cache and data partitions while I am using ext4 on the system partition, so yes. I will possibly try an install with ext4 on all partitions clean installed later.
[Galaxy S II Android Development] h3imdall:
Same issue here: clean install with 9.0 I get boot loop (galaxy logo, not even the lineage os one), clean install with the 8.1 image it works, except I'm not able to transfer files via MTP.

EDIT: I've installed microG 7.1 and it seems I have the same 8.1 MTP issue so ignore it.
[Galaxy S II Android Development] rINanDO:
I got a kernel log from someone who has f2fs on data-partition. F2fs is indeed broken since sdcardfs.
[Galaxy S II Android Development] K9100ii:
Looks like we have probably found the issue!
[Galaxy S II Android Development] a3956978:
Yeah, please tell me what you did differently to the steps in OP. Thanks
[Galaxy S II Android Development] philsilvers:
Coming from Stock 4.1.2

Apply - CWM-KitKatCompatible-i9100.tar using the mobile odin app.

When Samsung logo appears, remove battery for 5+ secs, then replace.

Go to recovery.

Apply - twrp-3.0.2.1-preload-compatible.zip (by the gangster).

Do not reboot recovery.

Apply - boot.zip (this is a flashable zip of los14.1 boot.img).

Apply - advanced/power off.

Go to recovery.

Apply - Wipe/Advanced Wipe, then wipe Dalvik ART Cache, Cache, System, Data, Preload, Internal-Storage.

Go back once and wipe sdcard0.

Apply - lanchon repit (system=1.5G data=max sdcard=min+wipe preload=min+wipe).

Apply lanchon repit again from tmp folder.

Apply - Wipe/Advanced Wipe, then wipe Dalvik ART Cache, cache, system, data, preload, sdcard0.

Apply latest los16.0 rom.

Apply - MindTheGapps 8.1.0-arm-20180808_153837.zip

Wipe/Swipe to Factory Reset.

Reboot System.

Done.

Edit: Coming from Stock 2.3+ or 4.0+

Apply same as above + flash XXMS2 modem directly before flashing los16.0 rom.
[Galaxy S II Android Development] mirhl:
Phone going super bonkers (bootlooping with everything that isn't the bootloader) sounds so much a lot my problem with a corrupted partition (test case attached)

https://xdaforums.com/galaxy-s2/dev...ery-twrp-3-0-0-0-t3330457/page49#post69235161

I would guess whatever the **** crashes, may also be responsible for [MENTION=4095549]Rendering[/MENTION] problem.
[Galaxy S II Android Development] K9100ii:
No partitions are corrupt, SDCardFS is broken with F2FS

We have already found the issue, the F2FS filesystem is not working since the implementation of SDCardFS in the latest build. Nothing is corrupt, SDCardFS just broke F2FS. Many people use F2FS including myself and some still use EXT4, and it seems only EXT4 is working for now, and that’s why only certain people get the latest build working. The bootlooping with everything that isn’t the bootloader is simply the kernel unable to boot because of SDCardFS.
[Galaxy S II Android Development] Liquid Glass:
Also memory card formatted as exfat did not working. Showing unsupported file system. I forced to use vfat. Rom is working very well. All partitions formatted as ext4. Except memory card.
[Galaxy S II Android Development] rINanDO:
Good news! I fixed f2fs! Currently testing now before releasing a new build.
[Galaxy S II Android Development] mirhl:
It would be cool if somebody fixed the root issue that corrupted partitions make everything and the kitchen sink bootloop to be honest.
[Galaxy S II Android Development] calvinjung:
Now my i9100 can get Android pie.
[Galaxy S II Android Development] K9100ii:
Great! Hope to see a new build working soon!
[Galaxy S II Android Development] Iv4n99:
Good work rlNando!

Waiting the new release :D
[Galaxy S II Android Development] c0d3r!pp3r:
Eagerly waiting for this and so, i'll be updating to this build skipping the last build...

Thanks a ton [MENTION=2222292]rINanDO[/MENTION]
[Galaxy S II Android Development] rINanDO:
:) New build is up! :)

Build #11 2019-4-9

IMPORTANT: You need to migrate to emulated storage using TWRP 3.1.0-EMU-MIGRATION-M-20170318

See opening post for detailed installation instructions.

Overall state: Stable

Android build: 9.0.0-r34

Updated sources

Fixed F2FS for /system, /cache and /data partition

Fixed USB-modes via Settings->Connected devices

Enabled Selinux

Reverted /misc back to /preload (We have Lineage-recovery now)

Reverted low_ram-flag so we can multi-task/splitscreen (please check if performance is still acceptable)

Enabled multi-user, because we're on emulated storage

Enabled Call-recording (if allowed by your country)

Known issues:

Camera app "Snap" works buggy. Sometimes black screen

Wakelock on flashlight not working (Flashlight turns off after 10 secs)

Downloads:

TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip

lanchon-repit-20170115-system=1.5G-data=max-sdcard=min+wipe-preload=min+wipe-i9100.zip

lineage-16.0-20190409-UNOFFICIAL-i9100.zip
[Galaxy S II Android Development] Iv4n99:
rlNando the latest build boots on my phone without image :/

Black screen, only the hardware buttons are working
[Galaxy S II Android Development] Edhuin1:
Fresh install using twrp 3.2.3.0 (latest version), everything seems to be working just fine, thanks for the updated build!
[Galaxy S II Android Development] K9100ii:
After dirty flashing this build again and a cache partition and dalvik cache wipe, it works with F2FS perfectly. Only issue was because SELinux is now set to ‘enforcing’, ViPER4Android doesn’t work, but it works if I switch SELinux to ‘permissive’ and I understand why it needs to be this way (security and LineageOS build requirements). The low RAM flag disabled barely made a difference in performance for me, it works just as smooth. By the way, what do you mean by “We have Lineage-recovery now”?
[Galaxy S II Android Development] rINanDO:
Hi,

What is ViPER4Android? Nice to hear the low ram doesn't have much impact. That was my observation also. Lineage team has replaced the default recovery which works with los builds. No one uses this because we use twrp.
[Galaxy S II Android Development] s2l9100:
Hello guys,

I think I bricked my phone...

I tried to install the TWRP (from the 1st post) over an old one and now i can't even boot to the boot loader. The phone is looping on the very 1st screen "Samsung Galaxy SII".

I have rooted the phone with kitkat 4.4.4 when today i decided to give this built a try.

I would appreciate any help

Thank you!
[Galaxy S II Android Development] LeddaZ:
Try to restore stock 4.1.2 with Odin and start from scratch
[Galaxy S II Android Development] K9100ii:
ViPER4Android is an equalizer to improve audio. (that requires root access and needs SELinux to be set to ‘permissive’ to work, else driver status will be abnormal and it will show as unsupported) XDA Labs: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx XDA Thread: https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651 Yes, it is nice that it doesn’t have much impact. I tried setting the low RAM flag to false before the latest build, but it would always do the “Starting phone...” message every 15-30 seconds when the phone is locked, but now that its working with it set to false without that message, its still going smooth. I have heard of Lineage-recovery and how they replaced TWRP with it, but the recovery stayed as TWRP after an install/flash, so I was wondering. I had guessed no one uses lineage recovery, TWRP has much more features.
[Galaxy S II Android Development] s2l9100:
I'm not able to connect the phone over USB cause as soon as i turn it on it keeps looping... I have ADB and Odin installed but it is been a while since my last root done and maybe i'm missing something.
[Galaxy S II Android Development] Liquid Glass:
Are you tried ? Remove the battery and attach it again. Then hold volume down button + home button + power button then you will see a Warning screen when you see it press volume up. Connect the phone to computer. Configure the odin then start the stock rom installing.
[Galaxy S II Android Development] Catfish78:
Hello,

my S II didn't have and problem after dirty reflashing the newest build. Great work, Rinando! I'm very interested how long the battery power will last now. By the way, i am forgetting that i use the broken S II, and not the good one. Time to reflash it, too :) .

Regards
[Galaxy S II Android Development] bersem:
Dirty flashed. No isusses for now.. Works fine without bootloops.

EDIT: Soft reset again :confused::confused::confused:

Regards
[Galaxy S II Android Development] Renda16:
Hi guys, noob question. How can i use f2fs? Thank you for the reply.
[Galaxy S II Android Development] [Oxydeme]:
Maybe my fails could help somebody;

I realised that i always failed flashing recoveries on my sII,

Why? Cause I completely -even visible at startup- forger about this yellowish triangle when passing back to stock..

So guys if you encoutered the recovery bug while flashing and needed to re upgrade your recovery and so on.. Don't do as I did,

As soon as yellow triangle appears without regarding your os, root it and use chainfires work,

I feel really stupid to miss this before as it has been a while since I had such recovery loss.

For the record,

Before I understood my mistake, it took me exactly -Odin/Heimdall/Recovery- 86 flashes...

And now enjoying final Rinando's build from 04/09. I had to use Computer webview to see the DL, strangely wasn't showing in Smartphone webview, using it since yesterday,

And have noticed once bug that makes me bang head, Android finalisation of Configuration with the disabled Button to continue the processus.

Instead of that, I could sucessly verify that app i'm developing could run on latest Rinando's buid

Part from that build is stable, fast, but takes som time such as producing freezes or lags, but once booted correclty let's say 15-30 minutes, works like a charme with approximately 16Go Storage, what a breath :)
[Galaxy S II Android Development] rINanDO:
That doesn't sound good.... What happened? You use F2FS and dirty flashed? or just EXT4 and dirty flashed? I need to know this to troubleshoot. My F2FS dev phone still runs fine... And my daily EXT4 also (always dirty flashed)
[Galaxy S II Android Development] [Oxydeme]:
What happend if you quickly pull off your battery connect your phone to computer, push battery while pressing vol down?

Doing so I could entre DL mode and send recovery to concerned partition using Heimdall,

Or, completely from scratch, push old md5.tard 4.0.4 firmware with Odin and then redo steps from beginning to avoid mistakes,

Franckly, I used both as explained in my previous post.

I finished with ni bootable 4.1.2, 7.1.2, even 4.0.4 with different expérimentations,

In your case I would go through Odin
[Galaxy S II Android Development] rINanDO:
Thanks for the explanation of Viper4Android. I tried the app and saw it is a simple Selinux denial which can be resolved.

You are right about low_ram=false caused crashes due to missing framework-hack. The crash happens at ColorFade-out. But if low_ram=true, this fadeout-effect is disabled. In Oreo this settings wasn't related to ColorFade. And TWRP has indeed much more features.
[Galaxy S II Android Development] s2l9100:
Hi [MENTION=2222292]rINanDO[/MENTION] ,

I didn't use F2FS, just Ext4 - but my TWRP was 2-3 years old.

Now I have installed stock(4.12) and when i try to install TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip i got this... see the photo:

Thank you!
[Galaxy S II Android Development] s2l9100:
Hello again,

Now I'm back at the staring point CM11 KitKat 4.4.4 but with a bit updated TWRP from this post:

https://xdaforums.com/showpost.php?p=73559662&postcount=2

and again the same problem with looping on "Samsung Galaxy SII".

I hope this extra info will help.

Thank you!
[Galaxy S II Android Development] K9100ii:
You're welcome. How would you resolve the SELinux denial? The crashes seem like what probably had happened and yes.
[Galaxy S II Android Development] kingwangeve@gmail.com:
Is it recommended to use f2fs now? is it stable?

Thanks for reply.
[Galaxy S II Android Development] rINanDO:
I don't know. I don't use f2fs on my dialy drive phone.
[Galaxy S II Android Development] K9100ii:
F2FS is working perfectly for me, I’d say it’s stable.
[Galaxy S II Android Development] Catfish78:
Hello,

it would be interesting to know the overall performance of F2FS on our S II. If it would be slightly faster in overall-performance, this opensource filesystem from Samsung could be a good possibility to speed up our phone a little bit.

Regards
[Galaxy S II Android Development] [Oxydeme]:
What about the yellow triangle at startup, if visible boot your rom and use chainfire triangle away

Else try to flash an syah kernel 6.05b smthg like that in order to boot your rom

And after that verify for that triangle otherwise it won't boot any twrp version after 3.1.0.0 ( such as TheGangster flashable isorec)

Before flashing this rom make sure to be on Rinando M Twrp specific prior to flash rom
[Galaxy S II Android Development] s2l9100:
ohh I understand now... That's why it doesn't boot with TWRP 3.1.+.+ cause of the yellow triangle.

Thank you!
[Galaxy S II Android Development] pocketrule:
Are you trying to flash a TWRP zip file from stock recovery? That won't work. First you have to flash TWRP (.img file) with Odin or heimdall, see here

https://twrp.me/samsung/samsunggalaxys2i9100.html

After that, you can flash another TWRP with TWRP (zip file). Good luck ?

Edit: you'll get the yellow triangle, but it'll work anyway this way.
[Galaxy S II Android Development] Renda16:
Hi guys, is it normale that the phone don't go in Deep Sleep? I see with Kernel Adiutor. I tried with wifi off and data connection off, but it doesn't go in Deep Sleep.
[Galaxy S II Android Development] fargh123:
Hi

Which superuser zip work with latest build I flashed 2.46 but I got bootloop
[Galaxy S II Android Development] speedjoe24:
Thanks Magical rINanDO!

This Rom works wonders :D, a little slow to boot, and slow to insert the pin of the sim (sometimes with error on the first try) :crying:.

Thanks for all your effort to revive the old and faithful S2 i9100 :good: :victory::highfive:
[Galaxy S II Android Development] a3956978:
Hey thanks for this build! Works like a charm now. No bootloops :good:
[Galaxy S II Android Development] c0d3r!pp3r:
Thanks rINanDO..

I'm on the last build and would like to update to the latest build from this post, Just wanted to confirm that do I need to repit if I have already gone through this process?
[Galaxy S II Android Development] pocketrule:
No, if you're already on emulated storage, you can just flash the update. Don't forget to make a nandroid backup - just in case something weird is happening :cyclops:
[Galaxy S II Android Development] MaddogIT:
Just wondering, should this rom switch to OFFICIAL as Pixel Experience one already did?
[Galaxy S II Android Development] ripee:
The criteria for official support are different for each rom. Furthermore, the big question is if it will be accepted for official support with emulated storage enabled.
[Galaxy S II Android Development] mithic:
Great work [MENTION=2222292]rINanDO[/MENTION]!!!

I follow your instructions in first post and flashed yesterday this rom (i was on latest 14.1 official...).Till now everything works amazing smooth.

My partition is as in the photo.

it's ok?

That's should be?

Thanks in advance.
[Galaxy S II Android Development] K9100ii:
Are you sure you had your repit configured to have the data partition at “max” so it’s as big as possible and sdcard partiton to “min” so it’s as small as possible, as we don’t use the sdcard partition on emulated storage? My /data partition on my phone is 12.99GB with 16GB storage, while you only have a 6GB /data partition.
[Galaxy S II Android Development] mithic:
That's why i ask.

Something doesn't like me...:)

I'm gonna look for...

edit1 :eek:H!! what a stupid i am!!

I pass through the point 5 of the process!!!

ok...now re-install...

edit2 : ok!!!now i have 13.46gb free space.
[Galaxy S II Android Development] Sebastian323:
switch to OFFICIAL

Hello,

that would be a great idea, to switch this Rom to official!

I think for the user aspecially to have the ota Update. It is not so comfortable, to do a full reset and flash every month.

Best regards

Sebastian
[Galaxy S II Android Development] Catfish78:
Hello Sebastian,

you don't have to reset your phone every time. Instead you can do a "dirty" flash. In most cases this is enough.

Regards
[Galaxy S II Android Development] K9100ii:
Alright, nice, that’s more like what I was expecting.

A full reset would not be necessary in almost all cases, and a dirty flash would be good. I’ve been dirty flashing the same data from LineageOS 14.1 from a few years ago to this ROM. We still need the bugs fixed before making it official.
[Galaxy S II Android Development] SethGeckoXDA:
Bugreport: Splitwise

The app Splitwise does not work in the current version (09-04). It crashes right after opening, see the attached log file.
[Galaxy S II Android Development] js-xda:
Hi [MENTION=2222292]rINanDO[/MENTION], thank for your hard work! Two questions:

How do you judge the chances that your builds will move official? [MENTION=6005084]ripee[/MENTION] mentioned that the emulated storage could pose an issue.

If moving official, will it be possible to move (via dirty flash) from unofficial to official?

Background of my question: I am wondering how much to "invest" now if requiring soon after another move. I would prefer to go for the official ones rather sooner than later because of the OTA updates.
[Galaxy S II Android Development] SethGeckoXDA:
Error 1 on Repit

I clean flashed coming from Lineage 14.1. In step 5, Lanchon's repit script failed with Error 1. I finally figured out this was due to my /data partition being formatted as F2FS (this was recommended in djibe89's guide).

[MENTION=2222292]rINanDO[/MENTION] Maybe add ext4 formatted partitions as required precondition to your guide in the opening post (alternatively, one could alter the suggested repit filename to fit f2fs). This could spare other users some time.
[Galaxy S II Android Development] linusdan:
Someone with excessive battery consumption in standby mode?
[Galaxy S II Android Development] SethGeckoXDA:
RILD crashes (multiple SIM PIN entries neccessary)

Build: #11 2019-4-9 (clean flash)

Issues: every time I boot my S2, I have to enter my SIM PIN several times before it is accepted.

Things I have noticed:

- the screen where you have to enter the SIM PIN is laggy no matter how long you wait

- if I wait for a couple of minutes (~5 min) after turning my S2 on, the screen is still laggy but my PIN is accepted on first try

- this is not the case in the first 1-3 minutes (something needs to start up a long time, I guess?)

- the rild process keeps crashing (F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 2161 (rild), pid 2034 (rild))

To further investigate, I have switched my phone into aeroplane mode, turned it off, and back on again. See attached logs. The timetable of me doing actions is as follows:

16:48: turned the phone on

16:51: switched aeroplane mode off

16:52: first SIM PIN entry (not successful)

16:53: second SIM PIN entry (successful)

rild starts crashing with SIGSEV as soon as the aeroplane mode is turned off.

Furthermore I noticed, no tombstones are created for the rild crashes. Is this because of some binary vendor files?

It's a minor issue of course, but maybe this helps. ;)

Edit: Also, this might be related to occasional soft reboots.
[Galaxy S II Android Development] D...:
The phone with this rom gets very hot, is this normal?
[Galaxy S II Android Development] rINanDO:
No not normal, but this could be because of the current lmk profile and activity manager profile. I had a similar issue. Background apps starts and does some stuff and gets killed and a minute later it starts again and again. I update this profile in the next build.
[Galaxy S II Android Development] rINanDO:
No not normal, but this could be because of the current lmk profile and activity manager profile. I had a similar issue. Background apps starts, does some stuff and gets killed and a minute later it starts again and again. I update this profile in the next build.
[Galaxy S II Android Development] michelrs:
Bootloop when migrating to emulated storage.

[MENTION=2222292]rINanDO[/MENTION] Thank you for keeping this old device alive.

I’ve tried to follow the instructions to change to emulated storage but, I keep getting stuck on a boot loop.

I never get beyond step 3

Here is a little context: I had this device running android P for a while, one of the first alphas released and with the traditional file system, but one day I tried to update TWRP and instead of updating it, the recovery went back to the stock, not sure what went wrong but that is not the issue.

I followed this instructions to get TWRP back on my device https://xdaforums.com/galaxy-s2/help/preparing-clean-loss-data-installation-t3712409 and everything worked fine.

Now when I flash TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip and reboot the device it never makes it to recovery. It loops between the Samsung screen and a black screen. I’ve tried doing full wipes in-between TWRP installations, repairing the partitions, pitting it again from TWRP and nothing works. Not sure if I need a working Android 8.X installation working before I flash TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip or what I’m doing wrong, any advice will be highly appreciated

Regards,

Michael
[Galaxy S II Android Development] SethGeckoXDA:
How do you reboot your device after flashing TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip?

After flashing TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip, does it show any errors (red messages) on the screen?

Maybe try to re-download TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip and flash again from a working TWRP installation to rule out a broken download.
[Galaxy S II Android Development] michelrs:
I get no error message during the installation of TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip.

As for how I reboot the device, in TWRP I go to home then reboot and I select recovery. When that fails I do the volume up+home+power and it does not work either.

I'll try redownloading one more.