• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

silent27

New member
Jul 30, 2021
4
1
yes, the super section has sections: system, vendor, system_ext, product, odm after flashing the script, everyone got permission, except for odm

the fingerprint fell off from here, since odm read-only, stock firmware realme 7pro
 
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
836
483
@silent27 Okay in next version of script I will make r/w all contents of super image and try to implement auto-resize feature.

In the meantime you can try replacing line #238 in script with this new line (not tested):
makeRW $fName;
Good luck!

The only issue i got on using this flashable fix was i cant mount vendor partition but system and product partition can be modified and are mountable im using poco m3 with super partition
@samsungics1200 why you can't mount /vendor as r/w ?

Same. I just finished de-bloating all the system apps but I'm stuck with "Title 3 months free trial" (yeah, that's the actual name of the app), linkedin, and some random "call of duty" that is already old. I'm crossing my finger this script might be modifiable to fix /oem, if not then I know that for the Xperia 1II the Russian firmware does not have the "/oem" partition and so if I scrap everything I've done, and flash that, I won't have to deal with it. I prefer not to use the Russian one though because I lose some functionality with my carrier in the US.

When I try mount -o remount,rw /oem I get '/dev/block/bootdevice/by-name/oem_a' is read-only
@DeathShot9 does this mean script actually works on modern Sony devices? That's great news! Where exactly is /oem partition located? Is it inside super image?

@lebigmac

Hey remember I messaged you a while back and posted on this thread that I did get it to work successfully. I also added a step by step on how I got it to work a few pages back. I believe @Keven11 got it to work as well

Hi @tha_mechanic yes I remember I was just revisiting some older interesting or unanswered comments ;)

I did indeed get it working. I just installed Linux Mint on my old laptop. My issue wasn't so much that I don't know how to use Linux. I was having a hard time navigating the windows file system using the Linux UI. Once I had a full Linux environment as opposed to a VM it wasn't a problem.
Hi @Keven11 congratulations on getting it to work on your device.
Honestly I didn't even change that much in the new version. Cleaned up the code a little bit and tried to fix that damn cow error. Apparently that did the trick :D

If you got the old version to work you don't need to run the new version again unless u feel adventurous and want to resize your partitions (or you want to unlock individual partitions...)
 
Last edited:

Suryashis

Senior Member
I can confirm that the flashable.zip worked for me flawlessly in 1st attempt. I am running Poco F3/ Mi 11x with Xiaomi.eu version 12.5.4.0 on android 11. Now my root is fully writable.
And fingerprint unlock is fully functioning...

But I just noticed that approx 9gb of my internal memory is consumed. Probably some backup being done as u mentioned in original thread.
Is there any way by which it can be regained?
 
Last edited:
  • Love
Reactions: lebigmac

X - root

Member
Mar 14, 2019
6
2
Tangerang
im finish to flash systemrw.sh from termux, then flash super_fixed.bin from fastboot. n then reboot.

but when i opened Root Exploler, then i push button Mount R/W it doesnt change.
and when im check remount to rw section from temux, its read only too.

how possible is that?
sorry if my bad english. @lebigmac

My Device : Redmi Note 9 [Merlin]
Miui Version : 12.0.6.0 [Global]
Android OS : 10
Have Magisk : Yes. 23.0

fyi: im tried flash flashable from twrp. but it said ERROR:255 even i reflashed new twrp it doesnt change too. stuck at ERROR: 255. So i chose termux way
 

Attachments

  • lpdump.txt
    1.1 KB · Views: 3
  • mylog.txt
    4.4 KB · Views: 5
  • Screenshot_2021-07-30-20-56-33-123_com.termux.jpg
    Screenshot_2021-07-30-20-56-33-123_com.termux.jpg
    361.5 KB · Views: 37
  • IMG_20210730_222113.jpg
    IMG_20210730_222113.jpg
    27.8 KB · Views: 34
Last edited:
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
836
483
I can confirm that the flashable.zip worked for me flawlessly in 1st attempt. I am running Poco F3/ Mi 11x with Xiaomi.eu version 12.5.4.0 on android 11. Now my root is fully writable.
And fingerprint unlock is fully functioning...

But I just noticed that approx 9gb of my internal memory is consumed. Probably some backup being done as u mentioned in original thread.
Is there any way by which it can be regained?

Hi @Suryashis. Thanks for your message. That's great news. Congratulations for getting it to work!
You can delete whole script folder from /data/local/tmp/
Or if you plan on running script again in the near future you can delete only img subfolder inside script folder. That's where all the data is dumped to.
Img subfolder should be recreated next time you launch script.

There was an update to the moto g 5g.
I tried v1.32 and got bootloop.
v1.31d worked fine.
Hi @PEACH-PIT thanks for your input.
The only thing that changed was the script version? Everything else is the same? Or did you update phone firmware since using v1.31d ? Thanks.
I remember you used to have error 73 on your motorola device. Did you get same error 73 in new version 1.32 ?
If I understand you right then overall the script went well , gave you error 73 as usual, then you used sysrw_repair_v1.32 to create super_fixed.bin and manually flashed it to your super partition but then it gave you bootloop? Is that it?

im finish to flash systemrw.sh from termux, then flash super_fixed.bin from fastboot. n then reboot.

but when i opened Root Exploler, then i push button Mount R/W it doesnt change.
and when im check remount to rw section from temux, its read only too.

how possible is that?
sorry if my bad english. @lebigmac

My Device : Redmi Note 9 [Merlin]
Miui Version : 12.0.6.0 [Global]
Android OS : 10
Have Magisk : Yes. 23.0

fyi: im tried flash flashable from twrp. but it said ERROR:255 even i reflashed new twrp it doesnt change too. stuck at ERROR: 255. So i chose termux way

Hi @X - root thanks for your log files.
Could you please send me this file from your custom recovery? /tmp/recovery.log
That way I can check what exactly is causing error 255 in recovery. I thought I had already fixed this error but apparently I only fixed error signal 6.

I checked your log file and you don't have shared_blocks feature so my script cannot do much other than maybe resizing your partitions... Did you check if your partitions were resized correctly? Do you have 30 MB of free space on each partition /, /product and /vendor ?

systemrw: / is read-only
systemrw: /product is read-only
systemrw: /vendor is read-only
systemrw: NO 'shared_blocks feature' detected @ system.img
systemrw: NO 'shared_blocks feature' detected @ product.img
systemrw: NO 'shared_blocks feature' detected @ vendor.img

Something else is preventing your device from mounting your partitions as r/w and I don't know what it is. You must figure this out if you want to be able to mount your partitions as r/w.
Usually it's shared_blocks feature that is the culprit of read-only lock but your device don't have this feature.
Hopefully you can figure it out. Good luck!

I'm happy that despite this, your device didn't experience bootloop! That's great. You did flash the super_fixed.bin manually right?
 
Last edited:

X - root

Member
Mar 14, 2019
6
2
Tangerang
Hi @PEACH-PIT thanks for your input.
The only thing that changed was the script version? Everything else is the same? Or did you update phone firmware since using v1.31d ? Thanks.
I remember you used to have error 73 on your motorola device. Did you get same error 73 in new version 1.32 ?
If I understand you right then overall the script went well , gave you error 73 as usual, then you used sysrw_repair_v1.32 to create super_fixed.bin and manually flashed it to your super partition but then it gave you bootloop? Is that it?



Hi @X - root thanks for your log files.
Could you please send me this file from your custom recovery? /tmp/recovery.log
That way I can check what exactly is causing error 255 in recovery. I thought I had already fixed this error but apparently I only fixed error signal 6.

I checked your log file and you don't have shared_blocks feature so my script cannot do much other than maybe resizing your partitions...



Something else is preventing your device from mounting your partitions as r/w and I don't know what it is. You must figure this out if you want to be able to mount your partitions as r/w.
Usually it's shared_blocks feature that is the culprit of read-only lock but your device don't have this feature.
Hopefully you can figure it out. Good luck!

I'm happy that despite this, your device didn't experience bootloop! So that's great. You did flash the super_fixed.bin manually right?

Did you check if your partitions were resized correctly? Do you have 30 MB of free space on each partition /, /product and /vendor ?
sorry, you mean i cant mout system r/o to r/w from your file ?

im flashed new rom [NusantaraProject] 23mnt ago, so im lost log from custom recovery you want.

now i will try to use your file to this rom.
Android 11.
Partition System R/O
 
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
836
483
sorry, you mean i cant mout system r/o to r/w from your file ?
I don't know what kind of 'read-only features' your manufacturer has added to your firmware.

You could try this command and at the same time call dmesg to find out more info about what exactly is forcing your partition to stay locked in read-only mode.

1-jpg.5235933


Did you try different mount command yet? For example busybox mount or toybox mount?
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
./tools/toybox mount -o rw,remount /
dmesg > ./log_new.txt
 
Last edited:

X - root

Member
Mar 14, 2019
6
2
Tangerang
I don't know what kind of 'read-only features' your manufacturer has added to your firmware.

You could try this command and at the same time call dmesg to find out more info about what exactly is forcing your partition to stay locked in read-only mode.

1-jpg.5235933


Did you try different mount command yet? For example busybox mount or toybox mount?
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
./tools/toybox mount -o rw,remount /
dmesg > ./log_new.txt
for toybox comand :
it display [block/dm-2' is read-only]

for the ask :
yes, i flashed super_fixed.bin manualy.

the Question is :
is it possible to move service.jar (smali patcher) to system/framework with other way?
i mean, this manufactur system lock by read-only so i cant write or replace any file to system manually.
 
  • Sad
Reactions: lebigmac

PEACH-PIT

Senior Member
Jan 22, 2018
104
25
Hi @PEACH-PIT thanks for your input.
The only thing that changed was the script version? Everything else is the same? Or did you update phone firmware since using v1.31d ? Thanks.
I remember you used to have error 73 on your motorola device. Did you get same error 73 in new version 1.32 ?
If I understand you right then overall the script went well , gave you error 73 as usual, then you used sysrw_repair_v1.32 to create super_fixed.bin and manually flashed it to your super partition but then it gave you bootloop? Is that it?

That's right.
I updated moto g 5g to the latest FW.
Then I ran v1.32 on linux.
The systemrw stopped with error 73.
sysrw_repair seemed to have finished successfully.
However, a boot loop occurred.
I flashed the FW again and tried 1.31d in the same way.
The sysrw_repair finished normally and no boot loop occurred.
 
  • Wow
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
836
483
yes, the super section has sections: system, vendor, system_ext, product, odm after flashing the script, everyone got permission, except for odm

the fingerprint fell off from here, since odm read-only, stock firmware realme 7pro
with mounting all partitions helped, thanks

sorry the fingerprint didn't work

Hi @silent27
I tried to remove 'shared_blocks feature' from /odm partition on my Xiaomi device and the script can successfully remove it but then after booting into system, the /odm partition is still read-only and it still shows 'shared_blocks feature'.
What the hell!?
 

lebigmac

Senior Member
Jan 31, 2017
836
483
does it work on xiomi Redmi mi 10x 4g
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!

Tested 1.32 on stock zenfone 8. Still getting error 73, most likely to the pesky cow files
Hi. I don't think error 73 and cow files are related.
I believe error 73 is caused by stubborn selinux settings. Try to completely disable it.
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!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    why using yandex. I don't want create a account for downloading
    2
    For everyone using RN9 merlin and Lancelot it works. I am on Lancelot with custom rom A11 OSS. You have to put the script in /data/local/tmp and go to recovery and run the script manually using the command: systemrw.sh size=20. Afterwards wipe data and format.

    Then reboot back into recovery (don't boot rom) and flash your rom again. Once rom is flashed please go ahead and reboot to recovery again.

    Once back in recovery please go to mount and select (SYSTEM ONLY!!) Then go to your terminal in your recovery and type: "mount -o remount,rw /system_root" once done flash magisk and your gapps and flash disable encryption last and reboot.
    Screenshot_20210908-102731202 (1).jpg
    Screenshot_20210908-102916853.jpg
    2
    I really would like to try the script with Redmi Note 9 (miui 12.0.4.0) but the yandex link doesn't work.
    Could you please use some universal file hosting with less limitations, like gdrive, mega, ...

    why using yandex. I don't want create a account for downloading

    New download mirror available on front page ;)
    More official download mirrors coming soon!
    1
    Confirmed working on Moto G Power 2021 (borneo) using the repair script. Beautiful work! Thank you!
    1
    Successfully got RW in OnePlus Nord with android 11 rom. Only one thing compulsory to work script is current slot b need to be active.
    But system/reserve folder is RO.
    How to make this folder also RW because this folder also has bloatware.
  • 95
    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

    *NEW* SystemRW v1.32 *NEW*
    automated bash script by lebigmac for Android 10 and above

    Creation date: February 2021
    Updated: August 2021

    Requirements:
    • rooted STOCK Android 10 or newer (custom ROM should already be R/W!)
    • at least 20 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.

    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 have 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 have super partition
    • flashes read-write-able images back to device using the super fast Kolibass technique (only in recovery mode)
    User data is not affected.

    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.
    Before launching script make sure you've got full read/write access to the /data partition and that /data partition is not encrypted!

    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.
    The script can be run both inside custom recovery and inside Android operating system. If you run it in Android you will need to fastboot flash the patched image(s) manually!
    Optional arguments: (replace x with your custom value)
    • in=x : *THIS IS IGNORED IF YOU HAVE 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 HAVE 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 HAVE 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:
    Code:
    # Run this command *IF YOU HAVE NO SUPER PARTITION*
    ./systemrw.sh
    
    # Run this command if you're first time user *AND YOU HAVE 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 HAVE 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 HAVE 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

    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"

    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!

    NOTE:
    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). So 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.
    Thanks @AndyYan your great tutorial also helped me a lot for automating the script especially the lpdump part.
    Also big thanks @munjeni for allowing me to use his superunpack V1 tool in the previous version. It helped me to understand how these super images work.
    Thanks @bynarie for making available his otatools package! A part of it was bundled with the previous version which helped me to create this 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:
    This is open source software and 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 arrise 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.
    The end-user is free to improve the underlying algorithm (as long as no malicious code is added) as well as redistribute this script in his own project as long as the comment and title section of the script (lines #1 - #65) as well as the included update-binary are not modified or removed.

    Please make sure to post your feedback, suggestions and improvements in the official thread right here.
    Enjoy customizing your read-write-able Android device!


    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
    current status:
    experimental
    If you like this project and want to support the developer at finishing this project & creating more amazing projects like this then please feel free to donate to the developer by clicking the link below. Thanks! Your support is very much appreciated!

    Donate
    8
    If the script works on your device please write me your phone model, Android version, script version and if you have super partition or not. Also please send me your log files.

    I will add you to the list of success 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!
    4
    @lebigmac
    I am happy to say that, all the things went fine with my Realme C12.

    I have removed original super.img right after lpunpack finishes. This makes me use your tool with just 15GiB free space.

    A small thing is that, in your update-binary, please create a dir /data/local/tmp if it does not exist.
    If it does not exist, your tool will fail to install.
    It will be not present if a person clean flashes your tool(wipe data).

    Also system RW works fine, but vendor RW gives operation not permitted.
    Do I need use chattr with the block of vendor?


    Also, we can use like this sh makesysrw.sh. Advantage of this is that, we don't need to make it executable and shebang is ignored.

    Thanks

    Hello HemanthJabalpuri. Did you actually get my script to work on your device? This is wonderful news.

    Thanks for the suggestion about creating /data/local/tmp folder if it doesn't exist. I will do it in the next version.

    vendor RW gives operation not permitted.
    Do I need use chattr with the block of vendor?


    Operation not permitted? I never seen this error before. Do you get this error in the script or elsewhere?
    Sorry I don't know what is chattr.

    Also, we can use like this sh makesysrw.sh. Advantage of this is that, we don't need to make it executable and shebang is ignored.

    Thank you very much for this precious piece of advice. Some people have old sh version in their twrp that don't even support basic array functions. Do you think it's possible to bundle my own sh file (that I used for development) with the flashable zip and rule out any sh compatibility issues this way?

    In the next version of the script I would like to remove twrp completely from the requirement list so that everybody can enjoy a system that's read write-able, not only those with twrp. Some devices have no twrp or orange fox available.

    No Orangefox recovery too for Oneplus 7T , unfortunately. Oneplus really messed up 7T's decryption with android 10. I'm hoping for it to fixed with OOS 11 update which too, got delayed because they didn't care for its decryption issues in the first place. Its mind boggling that the 7T doesn't have a working TWRP even after 1 ½ years of being launched.

    Hi shady_soldier
    Yes that kind of sucks I agree. I wish I knew how to actually compile recovery. Too bad I'm only an amateur!
    I tried to compile Xiaomi stock recovery the other day but no luck so far...

    @lebigmac Any chance to uninstall It?
    Thx!!

    Hi Morello12. Did you actually run the script successfully or not?
    Sure simply delete the entire folder /data/local/tmp/makesysrw_1.15c

    But is it a new version or what?
    Does it work without disabling DM-verify?

    No. Disable dm verity and verification is always a good idea!
    @Ayoub$# You could also try flashing an empty vbmeta with fastboot if you can't disable dm verity manually.

    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img