• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread
Jul 31, 2021
9
4
ОК на Xiaomi Redmi Note 10 Pro.
Итоговая папка systemrw_1.32_BUNDLE_proper \ systemrw_1.32_flashable \ systemrw_1.32 была помещена по пути:
данные / локальные / tmp / systemrw_1.32
Я вручную сделал папку img : data / local / tmp / systemrw_1.32 / img
Затем в Termux выполняются команды:
вс
cd /data/local/tmp/systemrw_1.32
./systemrw.sh размер = 500
После завершения скрипта в папке img находим файл super_fixed.bin
Копируем в основную память телефона super_fixed.bin и переименовываем в super_fixed.img, и вшиваем в TWRP как супер раздел.
Извините за мой плохой английский.
 

Attachments

  • mylog.txt
    6.9 KB · Views: 17
Last edited:
  • Like
Reactions: lebigmac

NisseGurra

Senior Member
Nov 22, 2005
1,167
461
Xiaomi Mi Pad 4
OnePlus 8T
Hello. I don't know but the probability is pretty high that it will just work straight out of the box. Give it a try and let us know your results! Good luck!


Hi. I don't think error 73 and cow files are related. Could you please send me your log files so I can double check?
Log files can be found in /data/local/tmp/systemrw_1.32/log/
Thanks!
Did you try yet the included troubleshooting repair script (Linux only)? That usually fixes error 73.
Another possible way to fix error 73 is the @harpreet.s slot switching method described in first post troubleshooting section. Good luck!
Here are the logs, did not try the repair script yet
 

Attachments

  • mylog.txt
    7.1 KB · Views: 5
  • lpdump.txt
    2.3 KB · Views: 4
  • myargs.txt
    812 bytes · Views: 4
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
940
557
OK on Xiaomi Redmi Note 10 Pro.
The final folder systemrw_1.32_BUNDLE_proper \ systemrw_1.32_flashable \ systemrw_1.32 was put along the path:
data / local / tmp / systemrw_1.32
I manually made the img folder: data / local / tmp / systemrw_1.32 / img
Then in Termux the commands are executed:
su
cd /data/local/tmp/systemrw_1.32
./systemrw.sh size = 500
After the script finishes, in the img folder we find the super_fixed.bin file
We copy it to the main memory of the phone super_fixed.bin and rename it super_fixed.img, and sew it into TWRP as the super section.
Sorry for my bad english.

Hi @sarychev.rescue thanks for your interest in this project and for your feedback!
Congratulations! I am happy for you that my script worked successfully on your Xiaomi device!
Please feel free to post some screenshots if you want!

If you look closely at line #453 of script file (systemrw.sh) you can see that mkdir -p command argument is used to create /img directory if not exist. No need to create /img directory manually.
size=500 is a little bit crazy! I don't recommend going above 100. The lower this value the higher the chance that script will actually work ;)


Here are the logs, did not try the repair script yet
Hi @NisseGurra thanks for your log files!
Holy cow! I just checked your log and you do have a system_b-cow partition!
It looks like cow error 70 is in fact fixed simply by omitting all cow related files when calling lpmake. This is great news!

Error 73 is easy to fix using the included troubleshooting repair script (Linux only).
Simply boot into any random Linux distro's live installation disk and run troubleshooting repair script from there.
Or you could try to run it from a virtual linux machine. Simply enable your USB 2.0 and 3.0 ports in virtual machine settings.
Good luck!
 
Last edited:
  • Like
Reactions: sarychev.rescue

NisseGurra

Senior Member
Nov 22, 2005
1,167
461
Xiaomi Mi Pad 4
OnePlus 8T
Hi @sarychev.rescue thanks for your interest in this project and for your feedback!
Congratulations! I am happy for you that my script worked successfully on your Xiaomi device!
Please feel free to post some screenshots if you want!

If you look closely at line #453 of script file (systemrw.sh) you can see that mkdir -p command argument is used to create /img directory if not exist. No need to create /img directory manually.
size=500 is a little bit crazy! I don't recommend going above 100. The lower this value the higher the chance that script will actually work ;)



Hi @NisseGurra thanks for your log files!
Holy cow! I just checked your log and you do have a system_b-cow partition!
It looks like cow error 70 is in fact fixed simply by omitting all cow related files when calling lpmake. This is great news!

Error 73 is easy to fix using the included troubleshooting repair script (Linux only).
Simply boot into any random Linux distro's live installation disk and run troubleshooting repair script from there.
Or you could try to run it from a virtual linux machine. Simply enable your USB 2.0 and 3.0 ports in virtual machine settings.
Good luck!
Tested the repair script in linux, cant not get it to run at all.
I don't find any clear install instructions but even with proper abd install it can not get the script to run:

adb shell
su
chmod +x /data/local/tmp/sysrw_repair_v1.32/sysrw_repair.sh
cd /data/local/tmp/sysrw_repair_v1.32
./sysrw_repair.sh

Gives "inaccessible or not found"
 
Last edited:

lebigmac

Senior Member
Jan 31, 2017
940
557
Bash:
adb shell
su
chmod +x /data/local/tmp/sysrw_repair_v1.32/sysrw_repair.sh
cd /data/local/tmp/sysrw_repair_v1.32
./sysrw_repair.sh
Tested the repair script in linux, cant not get it to run at all.
I don't find any clear install instructions but even with proper abd install it can not get the script to run:

adb shell
su
chmod +x /data/local/tmp/sysrw_repair_v1.32/sysrw_repair.sh
cd /data/local/tmp/sysrw_repair_v1.32
./sysrw_repair.sh

Gives "no file accessible"
Your paths are wrong. Please double check again your paths. You are running this on a Linux machine right? Good luck!

Bash:
sudo su
cd /PATH_TO_WHERE_YOU_EXTRACTED_/sysrw_repair_v1.32/
chmod +x ./sysrw_repair.sh
./sysrw_repair.sh
 

NisseGurra

Senior Member
Nov 22, 2005
1,167
461
Xiaomi Mi Pad 4
OnePlus 8T
Your paths are wrong. Please double check again your paths. You are running this on a Linux machine right? Good luck!

Bash:
sudo su
cd /PATH_TO_WHERE_YOU_EXTRACTED_/sysrw_repair_v1.32/
chmod +x ./sysrw_repair.sh
./sysrw_repair.sh
Paths seems ok, can change permissions of the file.
Yes, running in ubuntu
 

Attachments

  • Screenshot_20210803-023413633.jpg
    Screenshot_20210803-023413633.jpg
    118.3 KB · Views: 522

lebigmac

Senior Member
Jan 31, 2017
940
557
screenshot_20210803-023413633-jpg.5376637


Paths seems ok, can change permissions of the file.
Yes, running in ubuntu
Are you sure? Looking at your screenshot it looks like you're trying to run this troubleshooting repair script on your phone from within root explorer, right? Please keep in mind the troubleshooting repair script is Linux only and is not designed to be run on the phone itself, unlike the systemRW script

Tested the repair script in linux, cant not get it to run at all.
I don't find any clear install instructions but even with proper abd install it can not get the script to run:
Click here for error 73 troubleshooting repair script instructions
 
Last edited:

bseosbseos

Member
Aug 3, 2021
16
6
I don't have a custom recovery for my Pixel 4 XL running latest android 11, will this still work for me?
 

asuhoops8628

Senior Member
Nov 9, 2011
367
64
hello, having an issue... Oneplus Nord N10 5g. Latest flashable zip appears to fail at the last step in Updating Partition Details:

Failed to mount '/system-root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Failed to mount '/product' (invalid argument)
 

lebigmac

Senior Member
Jan 31, 2017
940
557
hello, having an issue... Oneplus Nord N10 5g. Latest flashable zip appears to fail at the last step in Updating Partition Details:

Failed to mount '/system-root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Failed to mount '/product' (invalid argument)
Hi @asuhoops8628 that's not related to script or update-binary. Those are TWRP related errors.
Can you successfully boot into system after flashing super_fixed.bin?
Please send me your log files from /data/local/tmp/systemrw_1.32/log/
Thanks!

OK,Let me try,thanks
Hi @Gentisz new version of script apparently works for OnePlus devices too. Feel free to give it a try while you're at it! And please send me back your results. Thanks!
Also keep in mind you will have to restore original stock read-only super image before using each tool (SystemRW script by @lebigmac or Superrepack tool by @munjeni) as both tools pretty much do the same thing but in a different way (y)
 
Last edited:

asuhoops8628

Senior Member
Nov 9, 2011
367
64
Hi @asuhoops8628 that's not related to script or update-binary. Those are TWRP related errors.
Can you boot into system after flashing super_fixed.bin?
Please send me your log files from /data/local/tmp/systemrw_1.32/log/
Thanks


False alarm - I reflashed my rom, flashed your zip and it appears to be working!


EDIT: Confirmed working flawlessly, OnePlus Nord N10 5G
 
Last edited:
  • Love
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
940
557
False alarm - I reflashed my rom, flashed your zip and it appears to be working!


EDIT: Confirmed working flawlessly, OnePlus Nord N10 5G
That's wonderful news for OnePlus users! Could you please upload a screenshot here in this thread and send me your log files? Thanks! You can send me logs through PM if you want.

Then I can add your device to the list of successful devices on first page! (y)✅

Try remounting your partitions as r/w like this:
Bash:
adb shell
su
for x in / /product /vendor; do mount -o remount,rw $x; done

1-jpg.5235933
 
Last edited:

bseosbseos

Member
Aug 3, 2021
16
6
I have installed/flashed my custom kernel with "EX Kernel Manager"

Is it possible to flash this script with EX Kernel manager or is it advised to use TWRP only?
Ok, so i managed to find an test version of TWRP compatible with Android 11 for my phone (Pixel 4 XL).

However I'm getting this error when i try flashing the image.

WhatsApp Image 2021-08-04 at 4.44.30 PM.jpeg


EDIT:

Confirmed working! on Google Pixel 4 XL on stock Android 11, rooted with magisk and on Kirisakura kernel with the following argument
Code:
size=50
Using the default size=15 would result in error "write error: no space left on device in system" when editing system partition.
 
Last edited:

Danmann

Senior Member
Jan 11, 2015
487
125
pwoss.org
Hey

I just tried your script manually on Ulefone Armor X7 Pro phone.
The phone has only the possibility for root. TWRP might be possible but I haven't done it yet.
The script hasn't shown any major errors or at all. Check the logs.
So i flashed it:
Code:
fastboot flash super super_fixed.bin

But the system is still read only.


Any suggestions?
Thanks!
 

Attachments

  • lpdump.txt
    1.1 KB · Views: 4
  • mylog.txt
    4.4 KB · Views: 6

lebigmac

Senior Member
Jan 31, 2017
940
557
Ok, so i managed to find an test version of TWRP compatible with Android 11 for my phone (Pixel 4 XL).

However I'm getting this error when i try flashing the image.

View attachment 5377661
Hi @bseosbseos I can't find the error in your screenshot.
Please send me this file from your recovery /tmp/recovery.log

Hey

I just tried your script manually on Ulefone Armor X7 Pro phone.
The phone has only the possibility for root. TWRP might be possible but I haven't done it yet.
The script hasn't shown any major errors or at all. Check the logs.
So i flashed it:
Code:
fastboot flash super super_fixed.bin

But the system is still read only.


Any suggestions?
Thanks!
Hi @Danmann. First of all I'm happy the script didn't cause bootloop on your device.
Unfortunately your device have no shared_blocks (read-only) feature so script doesn't know what to do. Some other security feature is preventing your device from being mounted as r/w. If you figure out what's forcing your device to remain locked in read-only state please let us know! Thanks! Good luck!
 
Last edited:

bseosbseos

Member
Aug 3, 2021
16
6
Hi @bseosbseos I can't find the error in your screenshot.
Please send me this file from your recovery /tmp/recovery.log
Uploaded here: https://pastebin.com/pKycev6A

EDIT:

Confirmed working! on Google Pixel 4 XL on stock Android 11, rooted with magisk and on Kirisakura kernel with the following argument
Code:
size=50
Using the default size=15 would result in error "write error: no space left on device in system" when editing system partition.
 
Last edited:
  • Like
Reactions: lebigmac

Top Liked Posts

  • 1
    lebigmac Hello bro from Russia! Your script works without any problems on the POCO X3 PRO phone! There was a problem mounting partitions in TWRP from Nebrassy. Installed Orangefox and everything went smoothly! Thanks for your work!
    P.S. size=250
    1
    Hello @QuaZero. I'm very happy that my script works smoothly on your Xiaomi device! Congratulations! (y)
    Please send me your other log files from this folder /data/local/tmp/systemrw_1.32/log/
    Thanks! Your feedback is very useful for further script development (y)
    Enjoy debloating and customizing your fully read/write-able device! :love:(y)
    Here you go, there is only 2 files
  • 3
    i use poco m3 rom xtrv hellas....your script is rock..i remove permanently bloatware with root explorer...nice job
    Hi @masricky I'm happy you like the script. Please send me your log files from this folder. Thanks (y)
    /data/local/tmp/systemrw_1.32/log/

    Enjoy tinkering with your fully read/write-able device and make lots of backups before modding stuff! :love:(y)

    Yes it's true. I wrote this script but it wouldn't exist as such without
    Thank you to everyone who contributed positively to this project! :D(y)
    Also keep in mind script is not perfect for all devices out there yet. Rest assured I'm always working hard on next version ;)(y)
    2
    Hi @Flashfire5606 thanks for your log files.
    Hi @Rahamatulla thanks for your interest in this project.
    Please keep in mind that removing shared_blocks read-only feature will duplicate lots of blocks that used to be shared. This will increase size of each partition which is embedded inside your super partition by approximately 200 MB.
    Maybe that's why @Flashfire5606 gets error 70 (insufficient space) despite using size=0 (shrink to minimum).
    I'm sure this can easily be fixed somehow...
    2
    Thanks! It works flawlessly (although I had to do it manually, it's easy enough). My device is a Redmi Note 9S (curtana). If I update my device, do I need to remake the fixed super.img or should I flash the one made before the update?
    Hi @LanceLot9980. Congratulations for getting the script to work on your device! Enjoy a fully read/write-able device! :love:(y)
    If you upload your log files from script folder and a screenshot of your system mounted as r/w then I can add you to the list of successful devices on front page ;)(y)

    @LanceLot9980 yes I noticed your question but I was on the road.
    If you update OTA this will most likely restore the shared_blocks read-only feature on your super partition which means you will have to run script again if you want to go full r/w again ;)
    Thanks! It works flawlessly (although I had to do it manually, it's easy enough). My device is a Redmi Note 9S (curtana). If I update my device, do I need to remake the fixed super.img or should I flash the one made before the update?
    The flashable zip gave you error 255? Don't worry I already fixed this issue in next version ;) Hopefully I can release it soon!
    2
    hi and thank's for your work...
    I have an issue with your script, I flash it on twrp on my renoir on A11 LOS and the flash is correct but at the end got these errors messages
    failed to mount system/ext/product/vendor (invalid argument) here are the logs and the ss...

    when I try to copy a .xml on vendor partition got, no more space available and it copy a .xml but empty..
    Hello @rayman95. You're welcome. Thanks for your log files and the screenshot (y)
    Don't worry about this TWRP related error at the very end. This has nothing to do with the script. This only means you must reboot the device. That's all ;)(y)
    Failed to mount '/system_ext' (Invalid argument)
    Failed to mount '/product' (Invalid argument)
    Failed to mount '/vendor' (Invalid argument)

    According to your log it looks like everything worked as expected but I think you must run script again with larger custom size. Which custom size did you use? I can't see it in the log :(
    Hopefully I can release that new version soon. The included auto-resize feature should fix this kind of issue in next version ;)(y)



    it worked great on poco x3 pro, but vendor didn't, when I try to edit an XML located in "vendor/etc/device_features" it doesn't work, even so, thank you very much for the work.
    Hi @Revokke. You're welcome. Thanks for your feedback.
    Please feel free to send me your log files from this folder and I'll have a look at your specific issue. Thanks (y)
    /data/local/tmp/systemrw_1.32/log/

    Which MIUI version number are you using? Official stock MIUI or Xiaomi.eu ROM ?
    What do you mean it doesn't work? I just tried it on my device and it just works. I can create and delete files in this directory /vendor/etc/device_features
    Make sure you remount /vendor partition as rw before copying or deleting files.
    If you can only write empty files to /system, /product or /vendor that means you must run script again with larger custom size. Good luck! (y)
    1
    My tests with parted.

    Yeah, I'm a noob with android, most defo. But...

    I flashed your tool, and could not get enough space for add/delete apps, so tested and decided to use 1024 as my size, which worked for me, at least in being able to install busybox, because I wanted to prove SU works in 10_Q. I proved that to myself, in that it does NOT crash 10_Q.

    So I read of parted, and see the auto... and knowing if a command is available, it will run, (wether it does anything or not) I decide to reflash to stock, only this time, when using system_RW, instead of size=80 or whatever, I did use size=auto and set it in the config too, so there was no doubt.

    The script ran, and I could indeed flash super_fixed.img (my f'n uses .img, so for the noob, mb mention to check the file ends in bin or img, will save a lot of noobs saying they cant flash or find it... ) and even though it showed the space I'd have if I used size=1024 (i settled on this number, would'nt go higher, hint hint..) I got the not enough space. I do not get this with make2fs, using 1024, prob because the tools uses make2fs, so it cant instruct the parted I installed to system in order to use size=auto.

    In the end, I stopped using system_RW until make2fs is changed to parted, knowing it will happen eventually...

    The commands are pretty much the same.

    Then you need to spoof the system's rw ability to ro for the files expecting to 'see' ro, even if they are rw.

    Thanks for the priv msg :)
  • 110
    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© v1.32 by lebigmac

    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:
    • Extract BUNDLE.zip (the included sysrw_repair.zip is only for fixing error 73!)
    • Before launching script make sure you've got full read/write access to the /data partition by first decrypting and then mounting /data partition as R/W!
    • 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)
    • 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 these commands in Android:
      Bash:
      adb shell
      su
      touch /sdcard/my_tune2fs_output.txt
      for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i>>/sdcard/my_tune2fs_output.txt; 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=`ls -l /dev/block/by-name/super | awk '{print $NF}'` 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=`ls -l /dev/block/by-name/super | awk '{print $NF}'` 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 @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 to @Brepro1 for allowing me to basically copy his awesome tutorial and make it into a script. Without your tutorial guiding me I couldn't have created this script.
    Big thanks @munjeni for allowing me to use his 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!

    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 - #65) 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 my variables and more...) only to rename and republish my SystemRW project (or parts thereof) as his / her own without even mentioning original source or original credits!!! (yes this actually happened :( perpetrated by a fellow forum member...)
    • Unauthorized re-uploads of any files contained within this project to 3rd party websites are not permitted without the original author's prior consent!
    • 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 project thread @ xda-developers.com
    • If the end-user wants to integrate my SystemRW project into his/her own project then he/she shall first ask me (the original author) for permission.
      If you want to make a video tutorial about my script 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_02-jpg.5309955
    v1-31d_03-jpg.5309957


    1-jpg.5235933


    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 & the creation of more amazing projects like this then please feel free to donate to the developer by clicking the button below. Thanks! Your support is very much appreciated!
    Donate
    12
    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!
    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!
    5
    I try to redo the procedure, i want to change the size. but i get error, can't remove lock.

    Good news. New hotfix available HERE
    I got rid of that buggy get minimum size function and reworked the size querying algorithm a little bit. Should be more stable now.

    Next step will be to make the script compatible with those devices that have empty partitions embedded inside their super partition...
    Also ronnie was complaining about syntax error but I have yet to find the syntax error... If anyone finds it please let me know so I can fix it. Thank you!