File structer must be UFS then for the script to work. Stock firmware from A12 and up uses EROFS and the script doesn't work for that file structure!
- Status
All custom roms now are based on OOS12+ (EROFS) and i'm on A13, so yeah. The script extracts the partitions and rebuilds them as ext4 (and un-shares blocks), add a bit of space so it can switch the RO to RW.
It didn't work on LE2127 after multiple tries...unless I am doing something wrong!
i am also using it on custom roms but oos12.13 have erofs and custom doesn't that's the reason for working custom rom, ( CUSTOM ROM DONT HAVE EROFS ) ......
It worked
Thanks a lotPixel 6a, unlocked bootloader, Android 13.
Do I need to re-do the steps every time there is an android update?
Yeah, i think so.It worked
Pixel 6a, unlocked bootloader, Android 13.
Do I need to re-do the steps every time there is an android update?
Is there a chance to get this to work with F2FS A13 as well? (Samsung Galaxy Z Flip 4, SM721B)
Code:
systemrw: Please wait and ignore the invalid sparse warnings...
Not enough space on device for partition product with size 1089863680
systemrw: Error! failed to create super_fixed.img file. Error code: 70How to fix this error. Thank
remove anything from the .img system partitions before expanding the partition, and packing it into super. unfortunately the lebigmac script can't do that.
I don think so, I have done ota's on my pixels and it stays (its the super partition which does change with a/b) however I haven't done a/b and another a/b update so I dont know 100%. Dont worry though since its so easy to do it.It worked
Pixel 6a, unlocked bootloader, Android 13.
Do I need to re-do the steps every time there is an android update?
Not sure, but you may have -cow partitions taking up space in super (those are temp partitions created after ota) so before dumping your super from your device you need this:remove anything from the .img system partitions before expanding the partition, and packing it into super. unfortunately the lebigmac script can't do that.
In fastbootd you can see if it's present:
fastboot getvar-all
Anything ending in -cow is a temp file that can be deleted, like this:
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition system_ext_a-cow
fastboot delete-logical-partition system_b-cow
fastboot delete-logical-partition system_ext_b-cow
fastboot delete-logical-partition system-cow
fastboot delete-logical-partition system_ext-cow
See this post:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter) by lebigmac
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Thanks for you info.Not sure, but you may have -cow partitions taking up space in super (those are temp partitions created after ota) so before dumping your super from your device you need this:
In fastbootd you can see if it's present:
fastboot getvar-all
Anything ending in -cow is a temp file that can be deleted, like this:
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition system_ext_a-cow
fastboot delete-logical-partition system_b-cow
fastboot delete-logical-partition system_ext_b-cow
fastboot delete-logical-partition system-cow
fastboot delete-logical-partition system_ext-cow
See this post:
Also there's Enhanced Fastboot and Payload dumper which could show you the cow partitions and let you delete them[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter) by lebigmac
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
Hi everybody, perhaps someone will be able to help me...
My need is not the apply the script to a real phone but to an AVD (android virtual device) on Android Studio.
I applied the script on my AVD running on Android 11.
The script works well and I have now 5 files :
Now that I have those files, I would like to recreate a new AVD with the files above.
I've noticed that the AVD uses a Google "system.img" file located in C:\Users\<ID>\AppData\Local\Android\Sdk\system-images\android-30\google_apis\x86_64.
When I unzip this system.img there are 2 files in it : 0.vbmeta.img and 1.super.img.
If I unzip the "1.super.img" file I have 4 files in it : product.img, system.img, system_ext.img and vendor.img.
My first question is : why I have that scratch.img with the script and not in the img files of Google ?
Here are all my unsuccessfull tries :
First try :
I rename the "super_fixed.bin" file in "1.super.img", overwrite the Google 1.super.img and ZIP the Google 0.vbmeta.img + 1.super.img in a new file called system.img.
I overwrite the Google system.img in C:\Users\<ID>\AppData\Local\Android\Sdk\system-images\android-30\google_apis\x86_64 with my new system.img
I try to create a new AVD in Android Studio and launched it with : emulator.exe -avd Pixel_6 -writable-system -no-snapshot
Black screen...
Second Try :
I was thinking that it can be due to scratch.img that I have in super_fixed.bin and not in Google system.img.
Then I created a ZIP with only my new product.img, system.img, system_ext.img and vendor.img.
I rename the ZIP in "1.super.img".
I ZIP the Google 0.vbmeta.img + 1.super.img in a new file called system.img.
I overwrite the Google system.img in C:\Users\<ID>\AppData\Local\Android\Sdk\system-images\android-30\google_apis\x86_64 with my new system.img
I try to create a new AVD in Android Studio and launched it with : emulator.exe -avd Pixel_6 -writable-system -no-snapshot
Black screen...
Do you know If i have a chance to succeed or am I doing something wrong in my steps ?
Best Regards,
Guillaume
My need is not the apply the script to a real phone but to an AVD (android virtual device) on Android Studio.
I applied the script on my AVD running on Android 11.
The script works well and I have now 5 files :
- product.img
- scratch.img
- system.img
- system_ext.img
- vendor.img
- super_fixed.bin
Now that I have those files, I would like to recreate a new AVD with the files above.
I've noticed that the AVD uses a Google "system.img" file located in C:\Users\<ID>\AppData\Local\Android\Sdk\system-images\android-30\google_apis\x86_64.
When I unzip this system.img there are 2 files in it : 0.vbmeta.img and 1.super.img.
If I unzip the "1.super.img" file I have 4 files in it : product.img, system.img, system_ext.img and vendor.img.
My first question is : why I have that scratch.img with the script and not in the img files of Google ?
Here are all my unsuccessfull tries :
First try :
I rename the "super_fixed.bin" file in "1.super.img", overwrite the Google 1.super.img and ZIP the Google 0.vbmeta.img + 1.super.img in a new file called system.img.
I overwrite the Google system.img in C:\Users\<ID>\AppData\Local\Android\Sdk\system-images\android-30\google_apis\x86_64 with my new system.img
I try to create a new AVD in Android Studio and launched it with : emulator.exe -avd Pixel_6 -writable-system -no-snapshot
Black screen...
Second Try :
I was thinking that it can be due to scratch.img that I have in super_fixed.bin and not in Google system.img.
Then I created a ZIP with only my new product.img, system.img, system_ext.img and vendor.img.
I rename the ZIP in "1.super.img".
I ZIP the Google 0.vbmeta.img + 1.super.img in a new file called system.img.
I overwrite the Google system.img in C:\Users\<ID>\AppData\Local\Android\Sdk\system-images\android-30\google_apis\x86_64 with my new system.img
I try to create a new AVD in Android Studio and launched it with : emulator.exe -avd Pixel_6 -writable-system -no-snapshot
Black screen...
Do you know If i have a chance to succeed or am I doing something wrong in my steps ?
Best Regards,
Guillaume
I disagree, I have tried on STOCK, QPR1 so it works on most pixels. Custom ROMs don't require this script as they all have resized and RW partitions.
- Status
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
17┤Thread Closed├
Hello everyone
As helpful as @lebigmac may be, no one – not even us – is above XDA's Forum Rules. Our work as moderators usually remains in the background but it felt necessary to provide some transparency here. After consulting our team I have decided to ban the OP of this thread for three months and it will remain locked until OP requests to open it back up after the ban expires. For some of you this will come as a complete surprise and may seem unfair but I would like to stress that we have invested a massive amount of energy and a mountain of patience to come to a resolve with lebigmac. Several moderators were involved. Despite our many efforts, (s)he persisted to openly accuse people of plagiarism, inciting conflict, call out the people involved and communicated in a very condescending and demeaning way.
We of course regret this course of action. Developers and development is everything to us but boundaries must be respected. After several earlier time-outs we had no other option but to proceed this way. We're hoping this will bring back some peace in this feud as well. With so much going on in the world we really don't need opposing developer parties. Open source is about cooperation and improving existing code, not about bitter fights over protecting your own code, which is based on the work of others anyway. One questionable screenshot aside, there hasn't been any viable proof of plagiarism provided to us related to this project.
Thank you all for your understanding and as always we remain available to answer your questions and concerns via PM. Have an amazing day!
Kind regards
Timmy
Senior Moderator3New version 1.35 is live
I think this might be THE version lol. Fingers crossed.
You can find the Download button in bottom of first post of this thread!
I hope it works for y'all! Good luck!
Please report back your feedback right here. Thanks.
And most importantly have fun with it but please don't rip it apart and recycle the best parts for your own unauthorized copycat imitations without mentioning original source because that's not what open source is all about. Thank you
Enjoy!3
The new version v1.35 will run from anywhere and has no hard-coded project path like the old version v1.32. You can for example push the sysrw_1.35 folder into /data on an encrypted device and it should still work as long as there is sufficient free space to work with in /data drive.
Good news for the Realme users with lots of bogus my_heytap sub-partitions where the script failed at the final auto-resize step:
The new auto-debloat() function should soon be ready2
Whenever you'd create the patched super image, there will be 2 commands that use the "avbctl" binary. However, just to give myself time to prepare for a wipe of my data, I disabled those commands, with @lebigmac's help of course, and flashed the "vbmeta" image, with the following command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img.
Also, if you have either "vbmeta_vendor" or "vbmeta_system", within your stock firmware, replace "vbmeta.img", with what you need2I am happy to announce that thanks to the addition of the brand new Auto-Debloat feature (which I just created from scratch) to my integrated MakeRW / ro2rw component, my main SystemRW / SuperRW program has just reached stable status! This is a huge milestone in the development timeline of this unique and original RW project for Android.
I would like to use this opportunity to thank God and every single one of the users out there who contributed positively to the creation & evolution of this amazing and unique RW project for Android from scratch. Without your high quality feedback throughout the past 2 years this project would not exist as is (and neither would all the unauthorized copycat clones out there).
Thank you for your support! You are simply the best! I'd also like to thank the team at XDA for making all of this even possible in the first place by providing us with this wonderful forum that we all take for granted every day. XDA-developers.com is such an amazing place where great ideas can come together and materialize into even greater programs.
BRAND NEW STABLE RELEASE INCOMING IN THE NEXT 24-48H ! GET READY !
I think this really might be THE version. This time for real!
@LeeGarChat why you never told me that my unique and original RW Multi-Tool for Android is SOOOOO GOOOOD? I had absolutely no idea what this baby is capable of When exactly were you planning on telling me about that? If ever?
The RW party is just about to get started my friends! Finally. It was about time -
172Welcome to the one and only, the original, universal,
System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac
Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW, F2FS-2-RW, EROFS-2-EXT4-CONVERTER, F2FS-2-EXT4-CONVERTER, Super Resizer/Flasher, SYSTEM-RW / PRODUCT-RW / VENDOR-RW / ODM-RW, root enhancer, real root, FULL ROOT, RW MULTI TOOL and many more aliases!
(NOTE: Full F2FS-RW support coming in 1. quartal 2023 ! Get your Samsungs ready!)
The prophecy has finally been fulfilled.
Making Android ten years younger!
Inspiring a whole generation of talented developers and empowering the open source community.
The Pandora's Box has been fully unlocked at last!
The genie has been unleashed from within the bottle!
Sesame! Open up now!
Let the Olympic Android System Modding Games (OASMG) begin!
The power is now in YOUR hands! And don't forget:
With great power comes great responsibility!
Creation date: February 2021
Updated: January 2023
Requirements:
- rooted STOCK Android 10 or newer
- at least 10+ GB free space on phone for dumping data
A script for all Android power users that wish to make their read-only Android 10+ system read/write-able again to remove bloatware and make more thorough customizations to their device.Script only modifies super and vbmeta partitions. /data partition is not affected. It's only used for dumping data and for storing script files.In a nutshell this is what the script is doing:- dumps your existing super partition
- extracts embedded read-only sub-partitions (system, system_ext, odm, vendor, product...) from specified super image
- makes these sub-partitions read/write-able using the one and only original MakeRW/ro2rw algorithm
- joins everything back together to new super.img
- flashes read/write-able patched super image back to device using the super fast Kolibass technique (only available in recovery mode)
NOTE:
- The script can be run both inside custom recovery and inside Android operating system.
If you run script in Android mode you will need to fastboot flash the patched image(s) manually! - To check whether or not the script worked correctly you can run this code:
Bash:adb shell su mount -o remount,rw / mount -o remount,rw /odm mount -o remount,rw /product mount -o remount,rw /system_ext mount -o remount,rw /vendor mount | grep dm- | head -5
- Extract flashable.zip and copy sysrw_*VERSION* folder into /data/local/tmp/
- run this command to make the script executable:
chmod +x /data/local/tmp/sysrw_*VERSION*/sysrw
Automatic installation:
Installation of the script has never been this easy!Download the flashable.zip below, do NOT enable zip signature verification and simply install it in your custom recovery (works in TWRP, OrangeFox and PBRP!)The update binary will auto-detect the arguments in config.ini and launch the script accordingly
Flashable zip custom usage:
You can easily modify the custom script execution arguments in the included config.ini file. Simply extract the flashable.zip, edit the included config.ini file with notepad and then save the file. Next compress the sysrw_*VERSION* and META-INF folders again as a new flashable .zip and install it in recovery. Have fun playing around with your config.ini
Script usage:
Simply execute the program from the terminal shell with or without custom argumentsOptional script arguments:
Replace x with your custom value
- in=x
Specify existing super image as input [OPTIONAL]
Omitting this parameter is equivalent to using [email protected] which is equivalent to using your super block device as input - out=x
Specify patched super image output file path [OPTIONAL]
Omitting this parameter is equivalent to using [email protected] and the patched super image will be saved as ./img/super_patched.bin by default - size=x
Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL]
Omitting this parameter is equivalent to using [email protected] which will activate the auto-resize feature - -r
Specify whether or not the patched super image should be output in raw file format [OPTIONAL]
Omitting this parameter will create a sparse patched super image by default
Usage examples:
Bash:adb shell su cd /data/local/tmp/sysrw_1.33 chmod +x ./sysrw # Run program with default settings [RECOMMENDED] ./sysrw # Specify existing super image as input [OPTIONAL] ./sysrw in=./img/super_original.img # Specify patched super image output file path [OPTIONAL] ./sysrw out=./img/super_patched_new.img # Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL] ./sysrw size=15 # Specify whether or not the patched super image should be output in raw file format [OPTIONAL] ./sysrw -r # EXPERT EXAMPLE (Warning! This command could potentially corrupt your system. Only use at your own risk in recovery mode!) ./sysrw in=img/super_original.bin out=`realpath /dev/block/by-name/super` -r
Uninstallation:
- To free up space and keep script as well as r/w capability you can simply delete /img subfolder at
/data/local/tmp/sysrw_*VERSION*/img - To delete script and keep r/w capability you can simply delete whole script folder at
/data/local/tmp/sysrw_*VERSION* - To undo all changes performed by the script you can simply reflash original stock read-only super image and re-enable dm-verity and verification either through adb/fastboot or with the included avbctl binary.
Troubleshooting:
If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeniIf you get any errors from the update-binary in your custom recovery during installation of the flashable .zip then please send me this log file /tmp/recovery.logand a screenshot of your error. Thanks!Make sure the script folder was correctly extracted to:/data/local/tmp/sysrw_*VERSION*If you can't run the script try making the file executable like this:chmod +x ./sysrwIf you still can't get it to work runwhich shin your shell and replace the shebang in the first line of the script with the output of that command. Don't remove the first two#!symbols though. Then save the file and try again.Make sure you've got full read / write access to the/data/local/tmpdirectory and that the containing files are not encrypted in custom recovery!If you get a bootloop after successfully creating and flashing super_patched.bin then that's probably because you didn't properly disable your dm-verity and verification.To undo any bootloop simply re-flash original stock read-only super image and re-enable dm-verity and verification with the included avbctl binary or through adb/fastboot. Those are the only changes performed by the script. If you have any more questions just ask in this thread. Good luck!
About:
I did not come up with all this by myself. After searching for a solution for countless days without success, going even as far as learning hex editing - I accidentally came across a couple of very interesting threads burried deep inside the new forum interface where this method has been described by various rw enthousiasts (links can be found in the credits section below). Therefore most credit goes to these rw enthousiasts. I'm only the amateur who put it all together into a compact script so that everybody can enjoy an Android system that's read/write-able again. Just like it used to be in Android 9 or earlier. Before these annoying 'shared_blocks' and 'EROFS' read-only features were implemented.
Credits:
Huge thanks to @Brepro1 for allowing me to use his awesome tutorial and make it into a script. Without your tutorial guiding me I couldn't have created this script.Huge thanks to @Kolibass for allowing me to use his partition tools for Android. Without your tools this script would not work on the Android platform!Big thanks @munjeni for allowing me to use his amazing superunpack V1 tool in the initial version. It helped me to understand how these super images work.Thanks @AndyYan your great tutorial also helped me a lot for automating the script especially the lpdump part.Thanks @bynarie for making available his otatools package! A part of it was bundled with the initial version which helped me to create this universal version. It's still part of the troubleshooting repair script to fix error 73.Thanks @HemanthJabalpuri for assisting me in optimizing the underlying algorithm!
Disclaimer:
#Disclaimer v3.0This open source software is provided as is without any kind of warranty or support whatsoever.By using and viewing this software you agree to the following terms:- Under no circumstances shall the author be held responsible for any damages that may occur from the (inappropriate) use of this software (or parts thereof).
- All responsibility, liability and risk lies with the end-user. You hereby agree not to abuse this software for illegal purposes.
- Please don't steal, hack, crack, mod, hex-edit, decompile, rebrand and / or abuse this software or parts thereof. Thank you!
- This software can be re-uploaded to 3rd party websites indefinitely as long as the software itself (or any parts thereof) were not modified by unauthorized 3rd parties without the original author's prior knowledge and explicit written consent
- This software (or parts thereof) were provided for free only for non-commercial, educational, personal, legal purposes
- To use this software (or parts thereof) for commercial purposes, please rent a commercial usage license
Thank you very much for your support! Thanks to your amazing support I can continue working on this project and other interesting projects like this.
Enjoy debloating and customizing your fully read/write-able next-gen Android device!
Please post your feedback, suggestions and your Olympic Android System Mods (OASMG) @ the official SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac links below. Thanks
https://forum.xda-developers.com/t/...tition-converter-resizer-by-lebigmac.4247311/
https://forum.xda-developers.com/t/...n-converter-erofs-rw-ext4-rw-f2fs-rw.4536821/
Confirmed working on these devices:
Xiaomi Poco X3 NFC
Xiaomi Poco X3 Pro
Xiaomi Poco X2 - Android 10/11
Xiaomi Poco X2 - Android 11
Xiaomi Poco F2 Pro - Android 11
Xiaomi Mi 10 T Lite - Android 11
Xiaomi Mi 10 T lite - Android 11
Xiaomi Mi 10 - Android 11
Xiaomi Mi 10 Ultra - Android 11
Xiaomi Mi 10i 5G (gauguin) - Android 11
Xiaomi Mi Note 10 Lite - Android 11 - OrangeFox
Xiaomi Redmi Note 12 5G - Android 12 - latest MIUI 13.0.3
Xiaomi Redmi 9 - Android 10
Xiaomi Redmi 9 - Android 10
Xiaomi Redmi Note 9 Pro joyeuse - Android 10
Xiaomi Redmi Note 9 Pro gauguin (China) - Android 10
Xiaomi Redmi Note 9S - Android 11 - MIUI Global 12.5.3 Stable (RJWEUXM)
Xiaomi Redmi 9T - Android 11
Xiaomi Redmi K30 - Android 10
Xiaomi Redmi K30S Ultra(China), Android 11
Asus ROG Phone 3 - Android 10
Asus ROG Phone 5 - Android 11
OnePlus Nord - Android 11
OnePlus 8T - Android 11
Doogee S96Pro - Android 10
F150 model B2021 - Android 10
Realme C12 - Android 11
Realme GT 5G - Android 12
Pixel 4a (sunfish) - Android 11
Google Pixel 4 XL (coral) - Android 10
and many more!
NOTE: Please post your feedback in this thread (with screenshot as proof that you are RW) if you want your device to be included in this list
Download
current status: experimental
If you like this project and want to support further development of it & the creation of more amazing projects like this then please feel free to donate to the original developer lebigmac by clicking the button below. Thanks! Your support is very much appreciated!
Donate17┤Thread Closed├
Hello everyone
As helpful as @lebigmac may be, no one – not even us – is above XDA's Forum Rules. Our work as moderators usually remains in the background but it felt necessary to provide some transparency here. After consulting our team I have decided to ban the OP of this thread for three months and it will remain locked until OP requests to open it back up after the ban expires. For some of you this will come as a complete surprise and may seem unfair but I would like to stress that we have invested a massive amount of energy and a mountain of patience to come to a resolve with lebigmac. Several moderators were involved. Despite our many efforts, (s)he persisted to openly accuse people of plagiarism, inciting conflict, call out the people involved and communicated in a very condescending and demeaning way.
We of course regret this course of action. Developers and development is everything to us but boundaries must be respected. After several earlier time-outs we had no other option but to proceed this way. We're hoping this will bring back some peace in this feud as well. With so much going on in the world we really don't need opposing developer parties. Open source is about cooperation and improving existing code, not about bitter fights over protecting your own code, which is based on the work of others anyway. One questionable screenshot aside, there hasn't been any viable proof of plagiarism provided to us related to this project.
Thank you all for your understanding and as always we remain available to answer your questions and concerns via PM. Have an amazing day!
Kind regards
Timmy
Senior Moderator15If the script works on your device please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/
And please write your phone model - Android version - firmware version
Then I can add you to the list of successful devices and it will be helpful for further development. Thank you!10Okay I know you guys have been waiting a long time... Thanks for your patience, loyalty, support and your interest in this amazing project for the past year! Unfortunately there's lots of dubious copycats floating around by now. Remember you saw it here first
The one and only, the original
SystemRW / SuperRW featuring MakeRW by lebigmac
This month new version should be ready
I'm working on it hard
Hopefully we can start beta testing in 2nd half ofAprilMayJuneJuly August September October and then it should be ready for final release
I'm so excited!
The new version has support for Android 12 and beyond!
Bash:sdkCheck(){ sdkVersion=`getprop ro.build.version.sdk` if [ $sdkVersion -lt 29 ]; then printf "$app: Please install Android 10 or newer and try again\n\n" && exit 1 else android=$(($sdkVersion - 19)) fi printf "$app: Current Android version: %s\n" $android }9Is it summer holidays yet or what? So much interest in my thread right now it's crazy. I can't even keep up with every single comment there's just too many. I just want to say thank you to every single one of you for your enthousiastic interest in this amazing SystemRW / SuperRW feat. MakeRW by lebigmac project!
Guys please stop wasting your time trying to get that old version to work in Android 12 + as it was originally not designed for such a new Android version. Just be patient for a couple more days and I will officially release BRAND NEW VERSION which has Android 12+ support out of the box, auto-resize feature and more
I'm working on it hard as we speak...
If you're Samsung or Realme device user just send me a message and we can work on a fix! Thanks
