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

Search This thread

lebigmac

Senior Member
Jan 31, 2017
1,036
677
Hello, Lebigmac, and thank you for your work!
I ran the script in Android mode.
Please take a look at the resulting log file.
Is everything okay in there?
Can I try now to flash in fastboot?
Device: Realme GT Explorer Master Edition (rmx3366). Android - 11. Bootloader - unlock. Root - Magisk.

fastboot flash super super_fixed.bin
After that phone only boots in fastboot or fastbootd

fastboot flash super super_original.bin
All the same. Phone only boots in fastboot or fastbootd.

It won't boot into the system.
Which program can extract files from super_fixed.bin? To make sure all the partitions are there.
Device: Realme GT Explorer Master Edition (rmx3366). Android - 11. Bootloader - unlock. Root - Magisk.
Android mode.
Script runs without errors.
Does not boot into the system after
fastboot flash super super_fixed.bin
Does not boot into the system after
fastboot flash super super_original.bin
Hi @diogen78. Thanks for your extensive feedback including log files and screenshot! (y)
Something is wrong with your log. For some reason it's not removing shared_blocks read-only feature properly. Not sure why. Compare with other successful mylog.txt files from this thread and you will see what I mean.

To get out of bootloop in addition to restoring stock read-only super image you can try to re-enable dm-verity and verification using the included avbctl binary.

If you can only access fastboot then I would suggest downloading stock firmware (same version that's installed on device) from your phone manufacturer website and then flash the vbmeta partitions + stock super.img
(Script only modifies vbmeta* and super partitions)
Please report back your results. Good luck! (y)

Bash:
fastboot --enable-verity --enable-verification flash vbmeta vbmeta.img
fastboot flash super super.img
 
Last edited:
  • Like
Reactions: AdalisVaxeler

diogen78

Member
Feb 22, 2010
13
9
Hi @diogen78. Thanks for your extensive feedback including log files and screenshot! (y)
Something is wrong with your log. For some reason it's not removing shared_blocks read-only feature properly. Not sure why. Compare with other successful mylog.txt files from this thread and you will see what I mean.

To get out of bootloop in addition to restoring stock read-only super image you can try to re-enable dm-verity and verification using the included avbctl binary.

If you can only access fastboot then I would suggest downloading stock firmware (same version that's installed on device) from your phone manufacturer website and then flash the vbmeta partitions + stock super.img
(Script only modifies vbmeta* and super partitions)
Please report back your results. Good luck! (y)

Bash:
fastboot --enable-verity --enable-verification flash vbmeta vbmeta.img
fastboot flash super super.img
The only way to boot into the system is to flash the entire stock firmware through the fastboot.
Then I get root again through patching boot.img with magisk.
Then:
1. Backup super.img by Partitions Backup & Restore or Universal Mount SystemRW.
2. Flash stock super.img without any changes
fastboot flash super super.img
3. Device does not boot into the system. Stays in fastboot mode.

It turns out that the problem is not about the script, but the fact that it is impossible to make a valid backup of super.img.
 
  • Like
Reactions: AdalisVaxeler

psi.singh03

Member
Apr 25, 2017
10
4
Singrauli
Thanks and respect to sir Lebigmac for this awesome creation.

It works on Redmi 9 Power (India variant)

Over: MIUI 12.5.4 / 12.5.5 Android 11 (Xiaomi eu)
Rooted: Magisk Canary - f822ca5b (patched boot image)
Kernel: Stock
Recovery: TWRP (XTRV)
After flashing this script, I got my full super partitions as rw namely but not limited to /system; /system_ext; /product & /vendor respectively.
THANK YOU AGAIN SIR!
Feeling blessed.
 
Last edited:

diogen78

Member
Feb 22, 2010
13
9
There is no custom recovery for Realme GT Explorer Master Edition.
I tried to use the recovery from another phone model GT Neo 2.:LOL:
I did not flash this recovery, I just booted into it and ran the script.
The script worked correctly.
Successfully flashed /data/local/tmp/systemrw_1.32/img/super_fixed.bin to /dev/block/sda10
And I even booted into the system. What I was not able to do when flashing through the fastboot.
But the system partition is still in read-only mode.:cry:.
I had no luck with this phone.
 

Attachments

  • lpdump.txt
    5 KB · Views: 5
  • mylog.txt
    3.4 KB · Views: 11

Md652

Member
Dec 4, 2021
7
0
The script does not work for me because my device (King Kong Mini 2) is 32 bit I also tried superunpack but I still can not change the system it is really urgent for me to create a different system and download a lot of things I would be very happy you can help me with what tools from your amazing script I can Use avento to edit my system to rw
Huge thanks
 
  • Sad
Reactions: lebigmac

Md652

Member
Dec 4, 2021
7
0
Now I see that superunpack worked fine for me to download the blocks_shared Because I did the test you wrote in the first post and it went downbut I still do not have r / w and when I run mount this is the result "
KINGKONG_MINI2:/ # busybox mount -o remount,rw /system
mount: can't find /system in /proc/mounts"
can someone help me urgently
 

jis251

Senior Member
Aug 2, 2013
180
49
Now I see that superunpack worked fine for me to download the blocks_shared Because I did the test you wrote in the first post and it went downbut I still do not have r / w and when I run mount this is the result "
KINGKONG_MINI2:/ # busybox mount -o remount,rw /system
mount: can't find /system in /proc/mounts"
can someone help me urgently
Try to mount root first
mount -o remount,rw /
And then /system. Just a thought though
 

bear263

Member
Mar 22, 2009
44
13
I've tried searching for my problem but unable to find it. Hope someone can help me. I have a motorola edge 2021 bootloader unlocked. I've ran with success the systemrw.sh file. It created the .img's. But I get the error 73 when creating new image. I loaded up ubuntu on a thumb and tried executing the repair file as instructed. I get an error about adb not excutable 64-bit efl file error. I've tried setting chmod on adb but still same error. I'm able to shell into the phone, cd.....etc so I am connected to the phone.

Any advice?
 

sarbazg180

Member
Dec 12, 2021
9
2
There is no custom recovery for Realme GT Explorer Master Edition.
I tried to use the recovery from another phone model GT Neo 2.:LOL:
I did not flash this recovery, I just booted into it and ran the script.
The script worked correctly.
Successfully flashed /data/local/tmp/systemrw_1.32/img/super_fixed.bin to /dev/block/sda10
And I even booted into the system. What I was not able to do when flashing through the fastboot.
But the system partition is still in read-only mode.:cry:.
I had no luck with this phone.
This also happened for me!😭
 

gammarayXda

New member
Jan 25, 2022
1
1
Thank you soo much for making this tool. It took about 2 3 minutes to flash the zip.
My device is Xiaomi Redmi Note 10, Android 11 with super partition.
 

Attachments

  • log.zip
    2.5 KB · Views: 12
  • Love
Reactions: lebigmac

RMX3370

Senior Member
Device - Realme GT Neo 2 Android 11 rooted with magisk RUI 2.0 Stock ROM

No error reported system has rebooted without any problem . NO BootLoop



Can you check if Device shows requirement for flashing both partitions
Since I get this when I try to check slot
C:\adb>.\fastboot.exe getvar current-slot
current-slot:
finished. total time: 0.003s

Now I can see partitions in mixplorer but I still cant delete files , I removed Facebook App Manager it failed i thought on reboot it will go but after reboot also it stays there .

I have attached photo of partitions that reappeared but i cant seem to delete any apps or even change permissions .
 

Attachments

  • lpdump.txt
    5.1 KB · Views: 6
  • mylog.txt
    3.5 KB · Views: 6
  • IMG_20220125.jpg
    IMG_20220125.jpg
    267 KB · Views: 23
Last edited:
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
1,036
677
Device - Realme GT Neo 2 Android 11 rooted with magisk RUI 2.0 Stock ROM

No error reported system has rebooted without any problem . NO BootLoop



Can you check if Device shows requirement for flashing both partitions
Since I get this when I try to check slot
C:\adb>.\fastboot.exe getvar current-slot
current-slot:
finished. total time: 0.003s

Now I can see partitions in mixplorer but I still cant delete files , I removed Facebook App Manager it failed i thought on reboot it will go but after reboot also it stays there .

I have attached photo of partitions that reappeared but i cant seem to delete any apps or even change permissions .
Hi @Email44841 thanks for your interest in this project & for providing your log files. According to your log the script didn't do anything other than disable dm-verity and verification. I'm happy that your phone still boots :D
It looks like you've got the same problem as @diogen78 in this comment here
@Email44841 @diogen78 please run these commands and show me result thanks! (y)
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done

Don't worry new upcoming version (which is just around the corner) should work better on your device I think ;)(y)
Any talented developers want to contribute PM me!
 
Last edited:
  • Like
Reactions: RMX3370

jis251

Senior Member
Aug 2, 2013
180
49
Hi @Email44841 thanks for your interest in this project & for providing your log files. According to your log the script didn't do anything other than disable dm-verity and verification. I'm happy that your phone still boots :D
It looks like you've got the same problem as @diogen78 in this comment here
@Email44841 @diogen78 please run these commands and show me result thanks! (y)
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done

Don't worry new upcoming version (which is just around the corner) should work better on your device I think ;)(y)
Any talented developers want to contribute PM me!
HI, @lebigmac
I hope your next version comes soon, thank you for your great work (and thx for Beta Testers too).
When you published your next version, can you quarantine that restoring the original superpartition, from your saved partition or TWRP backup or Partition Backup, will work OK? Do we have safe return back to original? Is that tested?
I hope it is.
Thank you
 

RMX3370

Senior Member
Hi @Email44841 thanks for your interest in this project & for providing your log files. According to your log the script didn't do anything other than disable dm-verity and verification. I'm happy that your phone still boots :D
It looks like you've got the same problem as @diogen78 in this comment here
@Email44841 @diogen78 please run these commands and show me result thanks! (y)
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done

Don't worry new upcoming version (which is just around the corner) should work better on your device I think ;)(y)
Any talented developers want to contribute PM me!
Thanks for reply ,
Output is attached
 

Attachments

  • output.txt
    2 KB · Views: 16
Last edited:
  • Like
Reactions: lebigmac

潇xiao

New member
Jan 28, 2022
2
0
Unlocked, but not yet fully unlocked.

You can create a file, but you can't write to the original file. You can't copy files with non-0 bytes, and you can't delete files with non-0 bytes.
 
  • Sad
Reactions: lebigmac

zachariahpope

Senior Member
May 5, 2012
270
221
@lebigmac this worked flawlessly for me ... I'm on a LG V60 (Verizon Variant) on the latest January 5th firmware. Thank you so much for your hard work.
 

Attachments

  • mylog.txt
    8.1 KB · Views: 21
  • Haha
Reactions: lebigmac

潇xiao

New member
Jan 28, 2022
2
0
I completely cleared the data of my mobile phone and re swiped miui13 V13 0.5.1.5. Dev, I used your script again after twrp swiped into magick24001 (beta version) to get root. After startup, I modified the / system / etc / hosts file with MT manager and saved it successfully. This indicates that it has been successful. Thank you.
 

ANDARXapi

Member
Nov 30, 2021
23
3
Samsung a12 nacho (sm-a127)
Android 12
It works on this device on any firmware version, verified by me. logs attached
 

Attachments

  • log.zip
    1.8 KB · Views: 22
  • Love
Reactions: lebigmac

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    MOD ACTION:

    Thread cleaned,

    Guys please don't expect support round the clock in any thread. Given the different time zones users live in and given RL situations, it just will not be possible. And please don't act entitled. No developer is indebted to you for anything so please don't use language that hurts.

    Thank you.
    3
    @lebigmac, can you edit your script to make possible resizing of /product, /system, /vendor (and/or /system_ext) by different sizes?
    I tried to rewrite your script but stuck (I'm not linuxoid so have some troubles with that) - one bug after another...
    I tried to:
    1) write super image to a file just once and use it in my tries to avoid flash killing with big writes;
    2) resize different partitions with different numbers.
    Because my tries mostly stuck in "no more space" phase I tried to resize with slow raising numbers (but it leads to a lot of flash writes and killing cells). I try to find a numbers that will raise partitions to a max possible sizes and avoid "no memory" when converting apps to a system apps (and integrating app updates). I have Redmi 9T with TWRP 3.6.0_10-1 (brigudav) and there is the same option as I understand "convert ROM to RW", it shrinks partitions and adds 100Mb to /product, 100Mb to /system, 100Mb to /system_ext and 100Mb to /vendor... It's a joke...
    I flashed original ROM, brigudav TWRP, converted super to RW, tried to integrate updates, but "no space", ok, then I deleted some apps (Yellow pages, weather, quicksearchbox etc) and found that free space in TitaniumBackup raised just a little, because some of the apps was in /vendor, some in /product, some in /system_ext (/system). I run "convert ROM to RW" from TWRP again and... it shrinked then added 100Mb to each of them and now I have almost zero free space.
    So I with to use ALL of the available space in super, for example, add 512Mb to /product, 256Mb to /vendor (maybe I will flash OpenGapps later?), 512-768Mb to /system_ext and as much as possible to /system?
    My super image is 8Gb, but current shrinked sizes of product + system + system_ext + vendor is 5411Mb... 2781Mb is unused.
    Can you help me?
    My broken code in spoiler, I've failed.
    Hello. New version of script has fully working auto-resize feature. I wanted to release it long time ago but something is always causing the release to be delayed...
    I set myself a goal to release it this month. Hopefully I can do it. Just hang in there. (y)
    Yes I know every month I say this month but this time I really mean it :ROFLMAO:
    2
    Very Successful On Redmi Note 10, without Constraints And Problems. i tried On miui ID 12.5.6.0. I want to ask if flash Clean from miflash will restore everything to its original state. Thank you.

    Nubia redmagic 5g
    after many bootloop I also succeed :)[
    Congratulations! Enjoy fully debloating and customizing your fully read / write-able device! :love:(y)
    @mhddonip yes that is correct if you flash clean stock OTA then you will go back to original read-only stock state.
    @izsdeaman what do you mean you succeed? My SystemRW / SuperRW feat. MakeRW by lebigmac script actually works on Nubia devices? That's wonderful news! Can you please send me your log files from your Nubia device? Then I can add your device to front page to the list of officially supported devices. Thank you for your feedback! :D(y)
    2
    :oops: It looks like next version will be released in May 2022 then (y)
    ⌛Time goes by way too fast... ⏩
    The final release candidate version needs a little bit more debugging...

    trying out this on samsung device with android 12 but unfortunate for me the super_fixed image file does not contain the system image but rather only vender, product and odm

    Hi @jroki that's weird. Why would it not contain the system.img :unsure:

    Apologies.
    Wasn't sure if the above was enough.

    Attached the logs i could find inside systemrw_1.32/log
    Hi thanks for the logs. (y)
    Good news! Working on a Samsung and Realme fix as we speak 😃(y)

    Hi, i used your flashable script, which says it succeeded. I tried creating a file in system but it fails.
    Then ran the "mount -o remount,rw /" command.

    On Realme GT Neo2. Rooted etc..

    screenshot_2022-05-03-16-54-23-43_84d3000e3f4017145260f7618db1d683-jpg.5605077
    Hi. You forgot to type su ;)(y)

    Your Samsung Galaxy A6+ (2018) cannot mount as rw by default?
    Try this:
    1-jpg.5235933
    2
    is there another way?
    Nope. Eventually, try a different ROM for your phone and try doing it again with SystemRW.
  • 143
    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
    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!
    6
    MOD ACTION:

    Thread cleaned,

    Guys please don't expect support round the clock in any thread. Given the different time zones users live in and given RL situations, it just will not be possible. And please don't act entitled. No developer is indebted to you for anything so please don't use language that hurts.

    Thank you.