[SCRIPT][Android 10+] Universal Mount SystemRW / SuperRW featuring MakeRW (read/write)

Search This thread
fastboot'd not fastboot btw but so far its working on 13/15 yall are st8 G im sooo greartful
Screenshot_20220519-040301023.jpg
:cool::cool::cool:
quick and painless im thinking i may want to give more than what is here now tho can i do this one more time on general purpose???
 

ronaldocoyle

Member
Oct 28, 2021
13
3
Ok I'm now confused. Everything done exactly even was able to mount but can't copy file to system_ext.

Device: Redmi Note 11

[Note: I didn't run the script. The super_fixed.bin was from previous session. I just replaced super.img with super_fixed.bin of the same rom & flashed. Seems to be still able to mount but no idea why I can't copy. I can still delete stuff though]

PS C:\Users\Ryan> adb devices
List of devices attached
ac9353f device

PS C:\Users\Ryan> adb shell
spes:/ $ su
spes:/ # su mount -o remount, rw /
su: invalid option -- o

MagiskSU

Usage: su [options] [-] [user [argument...]]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment preserve the entire environment
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit
-mm, -M,
--mount-master force run in the global mount namespace

2|spes:/ # su mount -o remount, rw /system_ext
su: invalid option -- o

MagiskSU

Usage: su [options] [-] [user [argument...]]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment preserve the entire environment
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit
-mm, -M,
--mount-master force run in the global mount namespace


2|spes:/ # mount -o remount,rw /system
mount: '/system' not in /proc/mounts
1|spes:/ # mount -o remount,rw /system_ext
spes:/ # mount -o remount,rw /product
spes:/ # mount -o remount,rw /vendor
spes:/ # mount | grep dm-
/dev/block/dm-3 on / type ext4 (ro,seclabel,relatime,discard)
/dev/block/dm-0 on /system_ext type ext4 (rw,seclabel,relatime,discard)
/dev/block/dm-2 on /vendor type ext4 (rw,seclabel,relatime,discard)
/dev/block/dm-1 on /product type ext4 (rw,seclabel,relatime,discard)
/dev/block/dm-4 on /data type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data/user/0 type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/data_ce/null type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/data_ce/null/0 type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/data_de/null type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/cur_profiles type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
spes:/ #
Ok I figured it out. Turns out I just needed to flash with bigger partition size. Works fine on redmi note 11 android 11.


I have a suggestion. Since it modifies the rom & no modification to phone is needed maybe you could build a simple mobile app that let's people to just edit & restitch super.img with system rw. That way everyone can easily share custom roms easily without worrying about rw protection.
 
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
1,072
706
Ok I'm now confused. Everything done exactly even was able to mount but can't copy file to system_ext.

Device: Redmi Note 11

[Note: I didn't run the script. The super_fixed.bin was from previous session. I just replaced super.img with super_fixed.bin of the same rom & flashed. Seems to be still able to mount but no idea why I can't copy. I can still delete stuff though]

PS C:\Users\Ryan> adb devices
List of devices attached
ac9353f device

PS C:\Users\Ryan> adb shell
spes:/ $ su
spes:/ # su mount -o remount, rw /
su: invalid option -- o

MagiskSU

Usage: su [options] [-] [user [argument...]]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment preserve the entire environment
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit
-mm, -M,
--mount-master force run in the global mount namespace

2|spes:/ # su mount -o remount, rw /system_ext
su: invalid option -- o

MagiskSU

Usage: su [options] [-] [user [argument...]]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment preserve the entire environment
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit
-mm, -M,
--mount-master force run in the global mount namespace


2|spes:/ # mount -o remount,rw /system
mount: '/system' not in /proc/mounts
1|spes:/ # mount -o remount,rw /system_ext
spes:/ # mount -o remount,rw /product
spes:/ # mount -o remount,rw /vendor
spes:/ # mount | grep dm-
/dev/block/dm-3 on / type ext4 (ro,seclabel,relatime,discard)
/dev/block/dm-0 on /system_ext type ext4 (rw,seclabel,relatime,discard)
/dev/block/dm-2 on /vendor type ext4 (rw,seclabel,relatime,discard)
/dev/block/dm-1 on /product type ext4 (rw,seclabel,relatime,discard)
/dev/block/dm-4 on /data type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data/user/0 type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/data_ce/null type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/data_ce/null/0 type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/data_de/null type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
/dev/block/dm-4 on /data_mirror/cur_profiles type f2fs (rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,gc_merge,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,reserve_root=21484,resuid=0,resgid=1065,inlinecrypt,alloc_mode=default,checkpoint_merge,fsync_mode=nobarrier)
spes:/ #
Congratulations! It looks like it worked for you :D(y)
This mount -o remount,rw /system should be changed to this mount -o remount,rw /
What used to be /system in Android 9 and earlier is now / in Android 10+

If you can mount / as rw and delete stuff but you cannot create files inside / that means you must run script again with larger custom size. Then script will give you some extra space to work with :D Don't worry next version of script which will be released in the next 2 weeks already has fully working auto-resize feature ;)(y)
Enjoy fully debloating and customizing your fully read/write-able device! :love:(y)

:cool::cool::cool:
quick and painless im thinking i may want to give more than what is here now tho can i do this one more time on general purpose???
Sure you can run script multiple times ;)(y)

Hi, I have a problom, my device is xperia 5 ii, android 12.
I use this 'sysrw_repair.sh' on linux, and it can works R/W on system_ext, product and vendor.
Then, sony 'thermal-engine.conf' is in /oem folder, but /oem folder has oem_a and oem_b, so I can't edit this text.
Someone can solve this problom?
/oem folder position is on picture.
View attachment 5615453
Hello. Open systemrw.sh script file with text editor and replace line # 238 with this one:
makeRW $fName
Now save file and try again. Good luck! (y)
 
Last edited:

Prince.Paul.K

Senior Member
Jan 2, 2013
138
48
Bangalore
Don't worry next version of script which will be released in the next 2 weeks already has fully working auto-resize feature ;)(y)

Hope it will support sdkversion=31. As of now script is failing sdkCheck().
Else will it work if I modify to add version 31 in the script?

Hatsoff for the contribution..!!(y)(y)
 

lebigmac

Senior Member
Jan 31, 2017
1,072
706
Hope it will support sdkversion=31. As of now script is failing sdkCheck().
Else will it work if I modify to add version 31 in the script?

Hatsoff for the contribution..!!(y)(y)
Hi @Prince.Paul.K thanks for your interest in this SystemRW / SuperRW feat. MakeRW by lebigmac project and for your kind words :D(y)

I hope THIS will answer your question regarding the sdkCheck() function ;)(y)
Good luck! (y)



Help. I do not have TWRP on Mi 11 pro, how to flash the received FIX without TWRP via fastboot?
Hello @llcrs2015 Did you run script in Android as root? Then you should have the super_fixed.bin file in /img subfolder of script path.
Just reboot device to bootloader and flash it and make sure you've got an original stock super.img at hand in case anything goes wrong. Good luck! (y)
 
Last edited:

jroki

Member
Mar 29, 2016
19
4
Huawei P30 Pro
Xiaomi Mi 10
Hi @lebigmac ,

Your script is badass!
Follow attached logs for Samsung S22+ (SM-G906B).

I've only question, how can i flash the output (super_fixed.bin)? I've tried with Odin... but couldn't flash. (yes, i've put the super_fixed.bin inside a tar like: super.tar)

Can you anyone give any advice?
For Samsung users without TWRP rename the super_fixed.bin to >>> super. Img then use 7zip to compress it to Tar
Then flash through odin
 
  • Love
Reactions: lebigmac

Shun_5377

Member
Apr 30, 2022
8
1
A few days ago, my device (ROG Phone 5) (running Android 12, and previously successfully gained write and read permissions to the System folder) was stuck in a boot loop. Then, I flashed the original bin file generated by the script, but to no avail, and ended up in booting my device into EDL mode and restoring stock firmware.

Is there any img file I need to flash in addition to the original img?

Thanks.
 

Prince.Paul.K

Senior Member
Jan 2, 2013
138
48
Bangalore
@lebigmac

I have successfully done it on Redmi Note 10 pro (sweet/sweetin) Android 12. Modified /vendor to fix the green tint issue while flashing sweet MIUI rom by EU on sweetin. I badly needed this because banking apps were detecting root and were not working. Flashed super_fixed.bin and unrooted.

Will it be possible to make it back readonly (tune2fs -O read-only vendor.img) ?

Thanks a trillion for your script and other devs for their tools..!!
 
Last edited:

akrox

Member
Mar 23, 2022
7
2
For Samsung users without TWRP rename the super_fixed.bin to >>> super. Img then use 7zip to compress it to Tar
Then flash through odin
Thanks for your attention. I did tried this... and indeed i was able to flash it with odin. But it did nothing as lebigmac said it doesn't work for samsung yet!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Oh **** it's June 1st already. You know what that means.
    That means meteorological summer time starts now. I guess I'll have to merge both the happy spring time version and the happy summertime edition into one single happy summertime edition then. 😃
    Don't worry I'll hurry up with the release ;)
    If you've waited this long for the new version then you are a true loyal customer. Thanks for your support! ;)(y)
    A couple more days and it should be ready... 🕗 ⌛
    4
    Will this work on any device that has super? I have an s22 ultra international version and i need my system to be R/O to delete files. Thanks.
    Hi. Current version v1.32 does not work properly with some modern Samsung / Realme devices.
    I am currently working on a fix behind the scenes for all Samsung / Realme users out there ;)(y)
    2
    Is it possible to use this on custom roms that use EROFS?
    2
    Did you need to rename the super fixed to super_origin for Oneplus ?
    I did not have to rename.
    2
    Outstanding! I have a OnePlus Nord n200 5g, and thanks to this script r/w is working great!

    I had to run the script from adb shell in system mode. Running this script in fastboot mode, or recovery did not work due to the encryption system. Decrypting with TWRP does not work on this phone no matter how many times you set a pin, or password for the phone. This phone does have a super partition.

    The steps I used to get it working are:

    unzip the flashable zip.

    adb push systemrw_1.32 /data/local/tmp/
    adb shell
    su
    cd /data/local/tmp/systemrw_1.32/
    chmod +x systemrw.sh
    ./systemrw.sh size=100

    ##### WAIT UNTIL YOU SEE: Please reboot into bootloader and flash the file(s) manually

    adb pull /data/local/tmp/systemrw_1.32/img/super_fixed.bin
    adb reboot fastboot
    fastboot flash super super_fixed.bin

    reboot into system, then tested with:

    adb shell
    su
    mount -o remount,rw /
    cd /system
    touch test
    ls -als test <- you should see the "test" file size, permissions, creatd date etc
    rm -rf test


    I hope this helps somebody else having issues with encrypted phones.

    Thank you for your hard work!
  • 146
    If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeni


    logo_large.jpg

    SystemRW / SuperRW (feat. MakeRW) v1.32 by lebigmac
    NEW VERSION COMING SOON! STAY TUNED!;)(y)
    ANY TALENTED DEVELOPERS WANT TO CONTRIBUTE TO NEXT VERSION? PLEASE CONTACT ME NOW! THANKS! :love:(y)

    Creation date: February 2021
    Updated: August 2021

    Requirements:
    • rooted STOCK Android 10 or newer (custom ROM should already be R/W!)
    • at least 10+ GB free space on phone for dumping data
    Description:
    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 OR your system / product / vendor partitions depending on whether or not you've got super partition
    • extracts embedded read-only partitions (system, vendor, product...) from super if applicable
    • makes these partitions read/write-able
    • joins everything back together to new super.img OR NOT depending on whether or not you've got super partition
    • flashes read/write-able images back to device using the super fast Kolibass technique (only in recovery mode)

    NOTE:
    • Before running this experimental software on your device it is recommended to make a full backup of your device (just in case you are unlucky enough to end up in an irreversible bootloop)
    • Extract BUNDLE.zip (the included sysrw_repair.zip is only for fixing error 73!)
    • 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 you've got a super partition on your device you can run this command: adb shell "ls -l /dev/block/by-name/super"
    • To check whether or not your device has the notorious 'shared_blocks' read-only feature you can run this code:
      Bash:
      adb shell
      su
      for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done
    • To check whether or not the script worked correctly you can run this code:
      Bash:
      adb shell
      su
      for a in /dev/block/dm-*; do mount -o remount,rw $a; done
    Manual installation:
    • Extract flashable.zip and copy systemrw_*VERSION* folder into /data/local/tmp/
    • run this command to make the script executable:
      chmod +x /data/local/tmp/systemrw_*VERSION*/systemrw.sh
    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 installer binary will auto-detect whether or not your device has a super partition and launch the script accordingly with the proper command line arguments.

    Flashable zip custom usage:
    You can set these custom installation arguments in the included config.ini file.
    Simply extract the flashable.zip and modify the included config.ini file and then save the file. Then compress the systemrw_*VERSION* and META-INF folders again as a new .zip and install it in recovery.
    First line of config.ini contains the script arguments for those WITHOUT super partition.
    By default this line is completely empty (no space).
    Second line of config.ini contains the script arguments for those WITH super partition.
    For example if you already dumped your super_original.bin and want to skip that process next time you install the .zip then put this in line #2 of config.ini :
    in=`realpath /dev/block/by-name/super` size=15
    Remember if you decide to use custom arguments in config.ini then the first character should always be an empty space. If no arguments are used such as by default in line #1 (no super) then the line should be completely empty, no space, nothing.

    Script usage:
    If you've got no super partition then simply call the script with no arguments from the shell (see examples below).
    If you've got a super partition I would recommend using the optional size=15 parameter as well to give some extra free space (in MB) to each partition.
    Optional script arguments:
    Replace x with your custom value
    • in=x *THIS IS IGNORED IF YOU'VE GOT NO SUPER PARTITION*
      With this flag you can specify an existing super image as input and skip the entire dumping of the super image process. Here you can use the super_original.bin which you dumped earlier with systemrw or the official unsparsed super.img from your downloaded firmware. (unsparse with simg2img). It's also possible to use your super partition block device as input.
      If omitted, systemrw will dump super image from phone to ./img/super_original.bin
      (path is relative to the script)
    • out=x *THIS IS IGNORED IF YOU'VE GOT NO SUPER PARTITION*
      With this argument you can specify the output path of the new patched super file.
      If omitted, default output value is ./img/super_fixed.bin
    • size=x *ONLY RECOMMENDED IF YOU'VE GOT SUPER PARTITION*
      With this parameter you can specify the extra free space (in megabytes) that will be added to each partition. There is a limit as to how much extra free space you can add per partition. Check your lpdump.txt to find out the exact maximum extra size.
      If omitted, default extra size is 0 (shrink to minimum)

    Examples:
    Bash:
    adb shell
    su
    cd /data/local/tmp/systemrw_1.32
    chmod +x ./systemrw.sh
    
    # Run this command *IF YOU'VE GOT NO SUPER PARTITION*
    ./systemrw.sh
    
    # Run this command if you're first time user *AND YOU'VE GOT SUPER PARTITION*
    # Specify the extra free space in megabytes for each partition:
    ./systemrw.sh size=15
    
    # Plug an existing super image into the script like this *ONLY IF YOU'VE GOT SUPER PARTITION*
    ./systemrw.sh in=./img/super_original.bin size=15
    
    # Specify both the input file as well as the output destination *ONLY IF YOU'VE GOT SUPER PARTITION*
    ./systemrw.sh in=./img/super_original.bin out=./custom/path/super_fixed.bin size=15
    
    # EXPERT EXAMPLE:
    ./systemrw.sh in=`realpath /dev/block/by-name/super` out=./img/super_fixed.bin size=50

    Uninstallation:
    • To free up space and keep script as well as r/w capability you can simply delete /img subfolder at /data/local/tmp/systemrw_1.32/img
    • To delete script and keep r/w capability you can simply delete whole script folder at /data/local/tmp/systemrw_1.32
    • 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 (inside /tools/ subfolder - also available in recovery).

    Troubleshooting:
    If you get error 255 in custom recovery when trying to install flashable zip then try to install it manually. If you encounter this error please send me this file /tmp/recovery.log
    Make sure the script folder was correctly extracted to:
    /data/local/tmp/systemrw_*VERSION*
    If you can't run the script try making the file executable like this: chmod +x ./systemrw.sh
    If you still can't get it to work run which sh in 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 have full read write access to the /data/local/tmp directory and that the containing files are not encrypted in custom recovery!
    If you get bootloop after successfully flashing super_fixed.bin then you can undo bootloop simply by re-flashing original stock super image and re-enabling dm-verity and verification with the included avbctl binary (inside /tools/ subfolder - also available in recovery). Those are the only changes performed by the script.
    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 enthousiasts (links can be found in the credits section below). Therefore I take absolutely no credit for the underlying core mechanisms of the script. 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 this annoying 'shared_blocks feature' was 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! This genius also showed me how to flash a 5GB file to my partition in just under 30 seconds! Much faster than fastboot! I still can't believe it!
    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.
    More thanks @gabrielfrias for his helpful comment
    Thanks @YOisuPU and of course @topjohnwu for discovering the 'shared_blocks feature'
    Thanks @HemanthJabalpuri for assisting me in optimizing the underlying algorithm!
    Thanks @aIecxs for helping me fix some shell scripting errors (y)

    Disclaimer:
    #Disclaimer v2.0​
    This 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 ensue from the (inappropriate) use of this software.
    • All responsibility, liability and risk lies with the end-user. You hereby agree not to abuse this software for illegal purposes.
    • Under no circumstances shall the comments & title section of the script (lines #1 - #100) as well as the included update-binary be modified or removed by the end-user without the original author's explicit consent.
    • Under no circumstances shall the end-user steal and / or abuse my entire SystemRW project or parts thereof (including but not limited to my update-binary, my script, my program logo, my program name or the names of my functions and/or my variables and more...) only to rename and republish my SystemRW / SuperRW feat. MakeRW project (or parts thereof) as his/her own creation without even mentioning original source!!! (yes this actually happened :( perpetrated by at least 2 fellow forum members...)
    • Unverified, unauthorized re-uploads of any files contained within this project to 3rd party websites are not permitted without the original author's prior knowledge and consent!
      If you want to share this software with your friends please just send them the link to this website. Thanks.
    • The end-user is allowed to improve the underlying algorithm (as long as no malicious code is added) and post his/her improvements, results and feedback right here in the official SystemRW / SuperRW feat. MakeRW project thread @ xda-developers.com
    • If the end-user wishes to re-use my SystemRW / SuperRW featuring MakeRW project (or any parts thereof) inside his/her own project then he/she shall first contact me! Thanks!
      If you want to make a video tutorial about this project please contact me first!
      Thank you! I can give you high resolution project logo and more!

    Please make sure to post your feedback and suggestions in the official thread right here.
    Enjoy customizing your fully read/write-able Android device! And feel free to share your Android system mods with other users in this thread! Thanks!


    v1-31d_01-jpg.5309953
    v1-31d_03-jpg.5309957


    1-jpg.5235933


    working-jpg.5525671


    Confirmed working on these devices:

    Download v1.32 mirror #1
    Download v1.32 mirror #2
    more official download mirrors coming soon!
    current status: experimental


    If you like this project and want to support further development of SystemRW / SuperRW feat. MakeRW & the creation of more amazing projects like this then please feel free to donate to the original developer by clicking the button below. Thanks! Your support is very much appreciated!
    Donate
    15
    If 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!(y)
    8
    Is 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! (y)

    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 :D(y) which has Android 12+ support out of the box, auto-resize feature and more ;)(y)
    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 (y)
    8
    Okay 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 ;)(y)
    The one and only, the original
    SystemRW / SuperRW featuring MakeRW by lebigmac
    This month new version should be ready :D(y)
    I'm working on it hard 🛠️⚙️⛏️🔧✂️🔨
    Hopefully we can start beta testing in 2nd half of April May and then it should be ready for final release :love:
    I'm so excited!


    This is awesome! Unfortunately, it doesn't support Android 12 yet : ( .

    The new version has support for Android 12 and beyond! :ROFLMAO:

    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
    }
    6
    New version 1.20 is ready! DOWNLOAD HERE
    Good news for those that don't have TWRP or couldn't get it to work in their TWRP. Now the script can also be run directly inside Android. Keep in mind that you will have to flash the patched images manually in this case using fastboot flash.

    The zip can still be flashed in TWRP (make sure zip signature verification isn't checked). This time I bundled my device's stock sh binary (which I used to develop the script) with the archive. Hopefully this will prevent avoidable sh-related syntax errors for some folks. The flashable zip installer update-binary automatically launches the script with the proper arguments using this bundled sh program (it's inside the tools subfolder).

    To those that were having difficulties running the previous version due to empty partitions or multiple partition groups inside their super : this has finally been fixed :D

    Please give this new version a try and let me know if it works for you or not and I will add it to the first post. Thanks for your feedback!