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

[lebigmac]

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!
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!

fastboot --enable-verity --enable-verification flash vbmeta vbmeta.img
fastboot flash super super.img

 

[diogen78]

Hi @diogen78. Thanks for your extensive feedback including log files and screenshot!
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!

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.

 

[psi.singh03]

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.

 

[diogen78]

There is no custom recovery for Realme GT Explorer Master Edition.
I tried to use the recovery from another phone model GT Neo 2.
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..
I had no luck with this phone.

 

[Md652]

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

 

[Md652]

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]

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]

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]

There is no custom recovery for Realme GT Explorer Master Edition.
I tried to use the recovery from another phone model GT Neo 2.
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..
I had no luck with this phone.

This also happened for me!

 

[gammarayXda]

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.

 

[RMX3370]

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

Spoiler

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 .

 

[lebigmac]

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

Spoiler

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
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!

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
Any talented developers want to contribute PM me!

 

[jis251]

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
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!

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
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]

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
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!

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
Any talented developers want to contribute PM me!

Thanks for reply ,
Output is attached

 

[tids2k]

be nice to have a solution finally.

 

[Tickbaby]

Worked for me. Pinephone64 running GloDroid Android 12.

 

[潇xiao]

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.

 

[zachariahpope]

@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.

 

[潇xiao]

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]

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