yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] marqwe:
Thank you for info.

"Universal Mount SystemRW / SuperRW featuring MakeRW (read/write)" doesn't seem to know f2fs. I tried "superunpack" (superrepack.arm64_pie), which also doesn't know f2fs, but it gave me information about what partitions are in super.emmc.win and at what locations. I found that the conversion of ro partition system to rw makes it significantly larger. So I first made a reorganization of partitions under TWRP (via adb):

lptools remove system
lptools remove odm
lptools remove product
lptools remove vendor

lptools create system 8178892800
lptools unmap system
lptools map system
lptools create odm 21389312
lptools unmap odm
lptools map odm
lptools create product 1081081856
lptools unmap product
lptools map product
lptools create vendor 2705326080
lptools unmap vendor
lptools map vendor

dd if=super.emmc.win of=/dev/block/dm-0 bs=1M skip=1 count=5426
dd if=super.emmc.win skip=5557248 count=20888 of=/dev/block/dm-1 bs=1K
dd if=super.emmc.win skip=5448 count=1031 of=/dev/block/dm-2 bs=1M
dd if=vendor-from_dm-3.img of=/dev/block/dm-3 bs=1M

(I made the vendor a bit smaller than the original one in super.emmc.win and didn't take it from super.emmc.win)

The system modified above works. system is still ro, but the /dev/block/dm-0 partition has 7800MB and is ready to be enlarged.

Subsequently, I took inspiration from the /system/bin/multidisabler script and created the rw partition system as follows:

cd /sdcard/sunpack
mount /system_root
truncate -s 7800M system-rw.img
toybox blkid /dev/block/dm-0 | egrep '[0-9a-f]{8}-([0-9a-f]{4}-){3}[0-9a-f]{12}' -o
make_f2fs -g android -O project_quota,extra_attr,inode_checksum,sb_checksum,compression,flexible_inline_xattr,verity,inode_crtime -U 26d6704a-2659-478c-805f-ec7d567357d0 -f -l system system-rw.img
mkdir -p system-rw
mount system-rw.img system-rw
cp -rp /system_root/* system-rw
umount system-rw
fsck.f2fs -f system-rw.img
dd if=system-rw.img of=/dev/block/dm-0 bs=1M

The result is a rw system (which is a bit bigger than the original ro) that I can modify. However, for unknown reasons, the boot doesn't work. Do you know what the problem might be?
[Samsung Galaxy S22 Ultra] afaneh92:
I will answer the last part, if it boot I wouldn't mind share a script. I just cant test to fix it. This will take me multiple data wipe and end up with no main phone.
[Samsung Galaxy S22 Ultra] tids2k:
Have you tried to post in the original SuperRW thread ? Does TWRP has option to change the filesystem ( repair ) to a fat based filesystem. Have you tried changing the filesystem first and then try the script ? I think f2fs support can be added to the script but I am not the original handler. reach out to @lebigmac , he might be able to help you out.
[Samsung Galaxy S22 Ultra] tids2k:
This for steps in linux : https://xdaforums.com/t/tool-win-li...ake-partitions-rw-in-super-partition.4120963/

Maybe dead end here : https://xdaforums.com/t/tool-win-li...s-rw-in-super-partition.4120963/post-87273723

Have you tried to unpack with the Rom Kitchen ? https://xdaforums.com/t/tool-windows-kitchen-crb-v3-0-0-beta15.3947779/post-79886519
[Samsung Galaxy S22 Ultra] marqwe:
Thank you for the information.

I do everything in TWRP. The problem in desktop Linux (Debian 11 for me) was that the tools for f2fs there are evidently not compatible with images f2fs on S22 Ultra. It is also about a lot of data and copying partitions within S22 Ultra, where I have so far a lot of space is lightning (600MB/s).

"Rom Kitchen" is unfortunately only for Windows and I do not have it.

Finally I managed to create a working system image rw - I will mention it in the next post.
[Samsung Galaxy S22 Ultra] marqwe:
I was able to create a bootable rw system (from the original ro system). The problem was that the command "cp -rp /system_root/* system-rw" is insufficient and does not transfer everything needed.

For my progress from the post above, you need to change the last steps:

cd /sdcard/sunpack
mount /system_root
truncate -s 7800M system-rw-cpapa-mychcon.img
toybox blkid /dev/block/dm-0 | egrep '[0-9a-f]{8}-([0-9a-f]{4}-){3}[0-9a-f]{12}' -o
make_f2fs -g android -O project_quota,extra_attr,inode_checksum,sb_checksum,compression,flexible_inline_xattr,verity,inode_crtime -U 26d6704a-2659-478c-805f-ec7d567357d0 -f -l system system-rw-cpapa-mychcon.img
mkdir -p system-rw
mount system-rw-cpapa-mychcon.img system-rw
cp -a --preserve=a /system_root/* system-rw
chcon u:object_r:rootfs:s0 system-rw

I have also taken the following steps, but they do not seem to be necessary:

cd /system_root
chmod 700 /sdcard/sunpack/mychcon
find . -type d -exec /sdcard/sunpack/mychcon {} \;
cd /sdcard/sunpack

For the previous commands you need to create a script /sdcard/sunpack/mychcon, with the following content:

#!/system/bin/sh
FILE=$1
CON=`ls -adZ1 $FILE | cut -d' ' -f1`
#echo "chcon $CON '/sdcard/sunpack/system-rw/$FILE'"
#ls -adZ1 "/sdcard/sunpack/system-rw/$FILE"
chcon $CON "/sdcard/sunpack/system-rw/$FILE"

Final steps:

umount system-rw
umount /system_root
fsck.f2fs -f system-rw-cpapa-mychcon.img
dd if=system-rw-cpapa-mychcon.img of=/dev/block/dm-0 bs=1M

So far I have only successfully changed the build.prop file within Total Commander. I will see if there is any problem.
[Samsung Galaxy S22 Ultra] tids2k:
Try to use root explorer and post result.
[Samsung Galaxy S22 Ultra] lebigmac:
haha I know old v1.32 of my script has no idea that such a thing as f2fs even exists! :ROFLMAO:

Hopefully I can add proper f2fs support in next version of my script but without access to a next-gen Samsung device it's not very easy to debug (Xiaomi user here).

I definitely like where this is going so please everyone keep up the good work! :D(y)

Being locked to read-only mode sucks! It's time for some RW baby ;)(y)
[Samsung Galaxy S22 Ultra] starbucks2010:
Hi,

Have you done this procedure only for system.img or for all 4 partitions (system, vendor, odm and product)?

Have you tried to boot rooted on these rw images with latest magisk?

Thanks.
[Samsung Galaxy S22 Ultra] marqwe:
First I applied TWRP according to the procedure in this forum. Part of this procedure is running script "multidisabler" (2x), which converts "vendor" to rw. Part of the procedure is also application of modified kernel with selinux in "permissive" mode.

The script "multidisabler" was my main inspiration when converting "system" to rw. And I created the rw image "system" from it. Unfortunately, this image is much larger than the original ro "system" and it is not possible to apply it to the original /dev/block/dm-0. I was looking for a way to change the location and size of dm-X partitions - I was able to do that with the "lptools". I think that the rw image "system" doesn't do compressions unlike the ro image and that's why it's so big. It's quite lucky that after rearranging the partitions (inside "super") everything fits - there's not much extra space left.

Unfortunately, it turned out that with rw "system" the phone wouldn't start (boot loop). I did a little research on /proc/last_kmsg (see: https://android.stackexchange.com/questions/213722/how-to-debug-boot-loop) and concluded that the problem could be that rw "system" doesn't have everything well migrated compared to ro. Command:

cp -rp /system_root/* system-rw

is insufficient. That's why I replaced it:

cp -a --preserve=a /system_root/* system-rw

Subsequently, I found the listings:

ls -laZ /system_root
ls -laZ system-rw

that the security context data did not transfer well. Therefore, I manually applied the command to the root of the new rw "system":

chcon u:object_r:rootfs:s0 system-rw

and created the "mychcon" script with which I used "find" to correctly transfer the security context to all files.

With the resulting rw system, the phone was already starting. Later I tried to skip the "find" start with "mychcon" and even here the start took place, but I went back to the image where I used "find" because I believe it is more faithful to the original ro.

For a working boot all you need is only cp -a --preserve=a /system_root/* system-rw and chcon u:object_r:rootfs:s0 system-rw . I didn't try to see if everything would work after skipping chcon u:object_r:rootfs:s0 system-rw.

It might be a good idea to make changes to "multidisabler" when converting "vendor" to rw, but so far there doesn't seem to be any problem.

I haven't done the conversion of "odn" and "product" yet. So far I'm trying to get my bearings on a number of different partitions - for my planned modifications I'll hopefully make do with the rw "system". With the conversion of "product" to rw on the S22 Ultra there would be a problem with its magnification and it might be a problem to fit all the partitions into "super".

Already before the transfer I had a Magisk 25.2.

I'm not an expert - I'm trying to get my bearings so I can make some adjustments to the "system".
[Samsung Galaxy S22 Ultra] afaneh92:
Thanks for your efforts, I will decrease vendor size and make an external zip to convert all to rw, I already did but not released for some reasons.
[Samsung Galaxy S22 Ultra] dr.ketan:
Thank you @afaneh92 and @marqwe

Just made S908E system rw

I have abandon project just beacuse of couldn't figure out issue was causing by

cp -rp /system_root/* system-rw

Thanks you once again @marqwe for great sharing!

View attachment 5707833
[Samsung Galaxy S22 Ultra] tids2k:
Waiting on a + RW recovery .. :)
[Samsung Galaxy S22 Ultra] lebigmac:
Does anyone know how to mount an f2fs image on the fly on Android device? :unsure: Thanks! (y)

I tried like this but no luck :(

mkdir -p /mnt/dir
mount -o ro -t f2fs vendor.img /mnt/dir
# mount: '/dev/block/loop29'->'/mnt/dir': Structure needs cleaning
[Samsung Galaxy S22 Ultra] afaneh92:
Check my multidisabler script
[Samsung Galaxy S22 Ultra] tids2k:
Wondering if this can be implemented in recovery.

# ================================================== #
Force reading arguments.txt=false
# ================================================== #
Flash DFE= true
Disable AVB= true
Disable QUOTA= true
Hide not encrypted= true
# ================================================== #
Flash Magisk= false
# ================================================== #
Reflash Recovery for OTA= false
Reflash current Recovery for Recovery= false
# ================================================== #
Wipe DATA= false
Remove PIN= false
# ================================================== #
Skip warning= false

Actual thread :

[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"​
[Samsung Galaxy S22 Ultra] samH4Sung:
for step:

this wipes ALL DATA correct? I ask for clarity because i forgot to install twrp after i've rooted and been using my s908B daily for the few weeks now. Also i need to install the official tmobile firmware to get the 5g bands working on this phone. So i need to do a full image backup just before i do a firmware install.
[Samsung Galaxy S22 Ultra] Kuba1996:
Yes, this wipe all of Yours files etc. Take backup and send on PC
[Samsung Galaxy S22 Ultra] marqwe:
I switched back to the encrypted data partition (switching to the original /vendor/etc/fstab.s5e9925, Wipe metadata, Format Data, Reboot System). I don't have any unlocking configured on Android.

Is there any way to mount this encrypted data partition in TWRP?
[Samsung Galaxy S22 Ultra] JohnTheFarm3r:
No.
[Samsung Galaxy S22 Ultra] marqwe:
Why not? What's missing?
[Samsung Galaxy S22 Ultra] wilaq:
Does not seem to work with android 13: boot loops
[Samsung Galaxy S22 Ultra] afaneh92:
You are doing something wrong, flash latest kernel
[Samsung Galaxy S22 Ultra] wilaq:
I am not able to, MTP not working, making it impossible to transfer kernel to device to flash.

Not sure whether MTP not working is specific to my device or to my recent upgrade to android 13. (I use the correct cables and drivers on my winpc)

Trying to look whether something in terminal could fix this
[Samsung Galaxy S22 Ultra] lebigmac:
By doing chcon u:object_r:rootfs:s0 system-rw aren't you only changing the context of the temporary container folder called system-rw ? Wouldn't it make more sense to call the command like this? :unsure:

chcon -R u:object_r:rootfs:s0 system-rw
[Samsung Galaxy S22 Ultra] afaneh92:
use adb
[Samsung Galaxy S22 Ultra] marqwe:
It's not a change in the "temporary folder" but a change "security context" in the root of the new rw system (the rw system is mounted in that "temporary folder"). Yes, but it only changes the root. For the change in other files throughout the tree, I used my "mychcon" script in conjunction with "find". Replacing "mychcon+find" with "chcon -R" would not bring the "security context" setting as the original has, as the original has a different "security context" for different files.

I'm not an expert on the "security context" but my goal was to perform a transformation to rw to maintain as much fidelity as possible with the original system ro.
[Samsung Galaxy S22 Ultra] marqwe:
Try:

ls -laZ /system_root
ls -laZ system-rw

Do you have the same "security context" in both?

Currently for me it looks like this:

# ls -aZ
u:object_r:rootfs:s0 .
u:object_r:rootfs:s0 ..
u:object_r:cgroup:s0 acct
u:object_r:apex_mnt_dir:s0 apex
u:object_r:rootfs:s0 audit_filter_table
u:object_r:unlabeled:s0 bin
u:object_r:unlabeled:s0 bugreports
u:object_r:cache_file:s0 cache
u:object_r:carrier_file:s0 carrier
u:object_r:rootfs:s0 config
u:object_r:unlabeled:s0 d
u:object_r:system_data_root_file:s0 data
u:object_r:mirror_data_file:s0 data_mirror
u:object_r:tmpfs:s0 debug_ramdisk
u:object_r:device:s0 dev
u:object_r:rootfs:s0 dpolicy_system
u:object_r:efs_file:s0 efs
u:object_r:unlabeled:s0 etc
u:object_r:unlabeled:s0 init
u:object_r:rootfs:s0 init.container.rc
u:object_r:rootfs:s0 init.environ.rc
u:object_r:linkerconfig_file:s0 linkerconfig
u:object_r:metadata_file:s0 metadata
u:object_r:tmpfs:s0 mnt
u:object_r:vendor_file:s0 odm
u:object_r:vendor_file:s0 odm_dlkm
u:object_r:oemfs:s0 oem
u:object_r:omr_file:s0 omr
u:object_r:vendor_file:s0 optics
u:object_r:postinstall_mnt_dir:s0 postinstall
u:object_r:system_file:s0 prism
u:object_r:rootfs:s0 proc
u:object_r:system_file:s0 product
u:object_r:rootfs:s0 publiccert.pem
u:object_r:unlabeled:s0 sdcard
u:object_r:tmpfs:s0 second_stage_resources
u:object_r:rootfs:s0 sepolicy_version
u:object_r:spu_file:s0 spu
u:object_r:storage_file:s0 storage
u:object_r:sysfs:s0 sys
u:object_r:system_file:s0 system
u:object_r:unlabeled:s0 system_ext
u:object_r:vendor_file:s0 vendor
u:object_r:vendor_file:s0 vendor_dlkm
[Samsung Galaxy S22 Ultra] dr.ketan:
@marqwe @afaneh92

cp -a --preserve=a is seems working and device boots but still may not be perfect. Here context difference betwen stock and one made with system-rw using cp -a --preserve=a

Probably that's why we needs to use permissive kernel.

1st image is rw script 2nd image is stcok

View attachment 5747301 View attachment 5747303
[Samsung Galaxy S22 Ultra] marqwe:
The other file permissions (first image) are not for regular files, but only for symlinks. I don't like it, but maybe it's not a problem.

To properly migrate the security context, it is necessary to use my mychcon + find script (which is why they are wrong in the second image).

WARNING: cp -a --preserve=a /system_root/* system-rw does not resolve the permissions or the security context on the root folder (respectively, the root of the filesystem). Neither does mychcon + find. It needs to be set separately. Furthermore, this "cp" does not resolve dot files (".filename") that might be in the root directory (in the case of "system" it doesn't matter - there are no dot files in the root).

But what I think this "cp" command should solve is the security context for the files and directories inside - but it doesn't do well and therefore mychcon + find is necessary.
[Samsung Galaxy S22 Ultra] marqwe:
I'm looking at my post #34 here in the forum and my command for setting up the security context:

find . -type d -exec /sdcard/sunpack/mychcon {} \;

I confess I have no idea why I only deal with directories. It should be more correct:

find . -type d -or -type f -exec /sdcard/sunpack/mychcon {} \;
[Samsung Galaxy S22 Ultra] MrBlazeVR:
mine keeps rebooting and i cant get into the twrp :/ any idea what to do?
[Samsung Galaxy S22 Ultra] afaneh92:
Vol up and power while usb connected to pc
[Samsung Galaxy S22 Ultra] MrBlazeVR:
doesnt help, still reboots again :/ moment i plug it in it starts booting until after the first samsung logo, then i get my warn about my bootloader being unlocked, then it does it all over again i dont have control anymore :/
[Samsung Galaxy S22 Ultra] afaneh92:
Its about timing
[Samsung Galaxy S22 Ultra] MrBlazeVR:
ill try a few 100 times more xD
[Samsung Galaxy S22 Ultra] MrBlazeVR:
ill let u know if i get it up r not in a hour r 2
[Samsung Galaxy S22 Ultra] afaneh92:
When device reboot and you feel vibration and blank screen press vol up and power and release power on warning.

Also what is your device?
[Samsung Galaxy S22 Ultra] MrBlazeVR:
alright, and galaxy s22
[Samsung Galaxy S22 Ultra] afaneh92:
S22 doesn't help, post your model
[Samsung Galaxy S22 Ultra] MrBlazeVR:
no idea what the original was but when i rooted it for the first time it should be SM-908U
[Samsung Galaxy S22 Ultra] MrBlazeVR:
..., what happens if i download a SM version for 21 instead of 22 and downloaded that to my phone with odin ._.
[Samsung Galaxy S22 Ultra] MrBlazeVR:
i think i installed the SM-991U
[Samsung Galaxy S22 Ultra] MrBlazeVR:
still no luck here :/
[Samsung Galaxy S22 Ultra] afaneh92:
You don't need to think, you need to be sure

Otherwise dont spam the thread
[Samsung Galaxy S22 Ultra] MrBlazeVR:
according to my snapchat its either

SM-G980F

or

SM-G996B
[Samsung Galaxy S22 Ultra] dr.ketan:
None of these are S22

How you were able to root it?

Best thing with information you are providing, better to send to service station or try with smart switch
[Samsung Galaxy S22 Ultra] MrBlazeVR:
i rooted with odin, and how so smart switch? i have no idea what that is xD
[Samsung Galaxy S22 Ultra] MrBlazeVR:
i guess i installed a 21 then? ._.
[Samsung Galaxy S22 Ultra] afaneh92:
I suggest yo not spam the thread anymore and find someone more knowledgeable to do it for you.

Why people can't read, that why I have supported list in my OP
[Samsung Galaxy S22 Ultra] MfmeheyitsmeIam:
I have a m62 and when I flash any vbmeta disabled.tar it boots to download mide with custom vbmeta error. Verification disabled bit is set
[Samsung Galaxy S22 Ultra] afaneh92:
This is S22 thread
[Samsung Galaxy S22 Ultra] MrBlazeVR:
aye i got into download mode what do i do now lol
[Samsung Galaxy S22 Ultra] afaneh92:
Find your correct model and correct thread
[Samsung Galaxy S22 Ultra] tschertel:
Hi guys,

Do I need to repeat the installation process to upgrade it?

Or is there any easier way to do it, like just use the TWRP itself to run the upgrade?
[Samsung Galaxy S22 Ultra] DrewPoss:
Hi, it may be a very dumb question, but how can I flash the kernel if the device doesn't have sd card support, and adb sideload doesn't work? i followed all the steps but really couldn't flash the kernel. Maybe the solution is so easy but I cannot really figure out how to do it.

I also try adb push to internal storage, then installed twrp and tried to flash it from there, but the file obviously doesn't show up. Any help?

seems like usb otg is the only option, but is there another solution besides that?
[Samsung Galaxy S22 Ultra] afaneh92:
adb/mtp/usb-otg many options
[Samsung Galaxy S22 Ultra] DrewPoss:
Adb commands aren’t working on this recovery

adb and mtp aren’t working. I’ll get an otg cable and try out :)
[Samsung Galaxy S22 Ultra] afaneh92:
Use older 3.6 for now
[Samsung Galaxy S22 Ultra] insestito:
No updates yet with adb and fastbootB fixed?

Thanks mate
[Samsung Galaxy S22 Ultra] tschertel:
So... How can I upgrade TWRP?

Do I need to repeat the installation procedure?
[Samsung Galaxy S22 Ultra] afaneh92:
Just flash twrp
[Samsung Galaxy S22 Ultra] tschertel:
Using Odin?

So it works just like a regular installation?

I can't flash it using TWRP itself, right?
[Samsung Galaxy S22 Ultra] afaneh92:
Need to extract the tar file to img and flash with twrp to recovery partition
[Samsung Galaxy S22 Ultra] Terrorigel97:
works on oneui 5.1 a13?
[Samsung Galaxy S22 Ultra] afaneh92:
Yes
[Samsung Galaxy S22 Ultra] Terrorigel97:
another question why do we really use the kernel? or can you just flash via odin (a13) and do I have to do a factory reset? because my cell phone is already rooted & set up
[Samsung Galaxy S22 Ultra] afaneh92:
That was answered in the 3rd post, but people don't like to read
[Samsung Galaxy S22 Ultra] saeab:
i followed al the instructions but in the end its keep rebooting
[Samsung Galaxy S22 Ultra] afaneh92:
maybe wrong kernel or twrp
[Samsung Galaxy S22 Ultra] marqwe:
Flash twrp-3.7.0_12-2_afaneh92-b0s.tar and vbmeta_disabled_R.tar FAILD with this info on display:

SW REV. CHECK FAIL(VBMETA) DEVICE: 0x6, BINARY: 0x5

I am use ROM: S908BXXS6CWF6/S908BOXM6CWF6/S908BXXS6CWF6/S908BXXS6CWF6
[Samsung Galaxy S22 Ultra] marqwe:
The solution was to root through Magisk. Where Magisk would patch the AP image (which I understand also includes vbmeta). See:

Installation

The Magic Mask for Android

topjohnwu.github.io

I then installed a Magisk patched ROM through Odin. Subsequently, after rebooting and performing the "Factory data reset" (apparently in stock recovery), I installed via Download mode TWRP (without vbmeta_disabled_R.tar).
[General Questions and Answers] Pinguudroid:
Hi,

I have a oneplus with a unstable screen,

and I wanted to mine crypto with it since it’s fully functional but just not suitable as a normal phone.

So is there a way to completely nuke the gui on my phone, so when I boot up my phone it has a internet connection but just boots directly into a shell?

Regards
[General Questions and Answers] alecxs:
No, surfaceflinger.rc is essential for zygote. Why bother with display? Or do you mix up with unstable touchscreen (disturbing ghost touches)?
[General Questions and Answers] Pinguudroid:
So I can mine more. The lower amounts of irrelevant stuff the phone have to process the better
[General Questions and Answers] alecxs:
so just pm uninstall --user 0 <pkgname> irrelevant apps - surely display is not
[Samsung Galaxy S22 Ultra] afaneh92:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.

Supported Models:

Galaxy S22 Ultra S908E/S908N/S9080.

Download & Guide:

1. Unlock your bootloader.

2. Downloads for S22 Ultra: AFH: b0q twrp and kernel / Drive: b0q twrp and kernel

3. Reboot to download mode

4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.

5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).

6. Disable encryption:

- Go to Advanced > Terminal, type: multidisabler.​

If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​

- Type: multidisabler again. will see - Finished. when done.​

- Go back to Wipe > Format Data > type yes.​

- Reboot to recovery.​

7. Flash custom kernel and magisk apk in twrp.

8. Reboot to system, Enjoy.

Bugs:

- Encryption not fully working.

Thanks:

TWRP team

@ianmacd for multidisabler

@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite

Donators

Sources:

Kernel tree

Device tree
[Samsung Galaxy S22 Ultra] BajaBlast4Life:
Fantastic!
[Samsung Galaxy S22 Ultra] butchieboy:
Once again, Mohammad works his magic