[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)

[Pachacouti]

First post I see today deserves a response:

I place extracted systemrw_1.32 in my adb folder.

I right click on adb folder and select open cmd window here.

adb push systemrw_1.32 /data/local/tmp/systemrw_1.32

adb shell

su

chmod +x /data/local/tmp/systemrw_1.32/systemrw.sh

cd /data/local/tmp/systemrw_1.32

./systemrw.sh size=80

Let it do its thing. But at this point watch for where it stores your super_fixed.bin, because to save doing this again, you can

adb pull /data/local/tmp/systemrw_1.32/img/super_fixed.bin

Now reboot into fastboot, remember I'm on A-only, so I actually do this:

fastboot --disable-verity --disable-verification flash vbmeta vblankmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vblankmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vblankmeta.img
fastboot --disable-verity --disable-verification flash boot Magisk'd _Bootloader.img
fastboot --disable-verity --disable-verification flash recovery Magik'd_Recovery-TWRP.img

fastboot --disable-verity --disable-verification flash super super_fixed.bin

The vblankmeta is my own blanked vmeta, renamed to also wipe system and vendor...

Now, after doing this I can:

Rellash stock bootloader, load Twrp to recovery, flash a zipped magisk, reboot, and up until magisk FORCED update can in fact read and write to system, but cant SU in GUI because magisk wants the internet to GIVE su (why adb shell su freezes...) and the update put's magisk in charge, removing the rw access we have, to the super (allowing rw system/vendor) to begin with, and how does it do it?

John wu thinks system is ro.

I would stop concentrating on system/vendor partitions, that are ro, and concentrate on a new way to load linux... boot it from the beginning of SUPER.img.

To the SUPER directory!!! instead of SYSTEM!


(A only cannot SEE sytem, fastboot cannot WIPE system, but I can flash and wipe super...!)

ooops... running away here... but all you read I learnt using this script to see I can access the system rw, but only in twrp...

If twrp can su from recovery, all else can be wiped, and reflashed with whatever else.

 

[KimNatorz]

Thank u so much.. it's working on Redmi note 10.. I really wanted to install Dolby Atmos but failed because the file system is read only

 

[Pachacouti]

Thank u so much.. it's working on Redmi note 10.. I really wanted to install Dolby Atmos but failed because the file system is read only

To understand overlayfs is simple, you have an overlaid root. overlaid system symlinked to /

Root apps mostly fail just now, saying read only, because they look for /system, which is no longer the case, and so while you have root, since android 10_Q,

/system is actually conmtained WITHIN super, so dont expect fastboot to work, or root or twrp or... well, cheers magisk... nowt actually works in this a-only... rooted or not...

But hey, it feels good seeing that root in root checker... shame it means nowt with sysstem as root...

 

[lebigmac]

How can I use this, how do I connect the phone to the computer, and how do I put the script, I have lubuntu.
I try it from the zip with twrp, but it gives me the error 73. and it also does not work with the change of slot a and b.

Hi @Ricardo Cruz. Please send me your log files from this folder. Thanks.
/data/local/tmp/systemrw_1.32/log/

Here you can find official troubleshooting repair script instructions (Linux only).

 

[lebigmac]

Thank u so much.. it's working on Redmi note 10.. I really wanted to install Dolby Atmos but failed because the file system is read only

Hi @KimNatorz. Thanks for your feedback.
Please send me your log files from this folder and I will add you to list of successful devices on front page. Thanks.
/data/local/tmp/systemrw_1.32/log/

Enjoy a fully read/writeable device!

 

[Ricardo Cruz]

Hola, [USER = 11816235] @Ricardo Cruz [/ USER]. Envíeme sus archivos de registro desde esta carpeta. Gracias.
/data/local/tmp/systemrw_1.32/log / [/ ICODE] Simplemente conecte el teléfono a la computadora usando un cable usb-c a usb-a. [URL='https://xdaforums.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/page-23#post-84901531'][B]Aquí[/B][/URL] puede encontrar las instrucciones oficiales del script de reparación de resolución de problemas (solo Linux). [/QUOTE] Hello, sorry for the delay, I imagine that these are the files that you ask me [/QUOTE]

 

[Pablo_S]

Hola saludos! amigo soy nuevo por aqui tengo un Infinix hot 10 X682B quiero tener root eh visto demasiado tutorial en Youtube pero ninguno me da respuesta excepto un canal de una persona de la india que me dió a entrenar muy poco por su idioma obviamente hasta que me decidí a buscar en Google y encontré esta página donde me ví que era demasiado útil para mí problema quiero hacerlo por el método adb fastboot ya tengo algo de idea de cómo iniciar y conectar mi dispositivo pero no sé lo siguientes pasos de cómo instalarlo espero pueda ayudarme amigo se lo agradecería en el alma

 

[lebigmac]

Thanks @Ricardo Cruz your log looks good. Now run the included sysrw repair script in Linux while phone is connected through USB cable as described in the troubleshooting repair script instructions. Good luck!

Hola saludos! amigo soy nuevo por aqui tengo un Infinix hot 10 X682B quiero tener root eh visto demasiado tutorial en Youtube pero ninguno me da respuesta excepto un canal de una persona de la india que me dió a entrenar muy poco por su idioma obviamente hasta que me decidí a buscar en Google y encontré esta página donde me ví que era demasiado útil para mí problema quiero hacerlo por el método adb fastboot ya tengo algo de idea de cómo iniciar y conectar mi dispositivo pero no sé lo siguientes pasos de cómo instalarlo espero pueda ayudarme amigo se lo agradecería en el alma

Hello @Pablo_S please check first post in this forum thread for manual installation instructions. Good luck!

 

[Ricardo Cruz]

Thanks @Ricardo Cruz your log looks good. Now run the included sysrw repair script in Linux while phone is connected through USB cable as described in the troubleshooting repair script instructions. Good luck!


Hello @Pablo_S please check first post in this forum thread for manual installation instructions. Good luck!

Good morning, sorry I try to run sysrepair.sh, but nothing happens, the phone is off, in fastboot or I just connect it. I send you a screenshot of the script in lubuntu.

 

[krasevalex]

=== Moto G Power (2020) XT2041-4-SS FIRMWARE: Android 10 "SOFIA_RETAIL_QPMS30.80-109-5" ===
1)
systemrw_1.32 (./makesysrw.sh size=50) => error code 73 (either way auto or manual)
2)
sysrw_repair_v1.32 (USB stick Ubuntu Mate 21.4) => Successfully created patched super image at /media/ubuntu-mate/Drive-C/sysrw_repair/img/super_fixed.bin
3)
"fastboot flash super super_fixed.bin" (in FASTBOOTD) => was sent 8 sparses SUPER out of 8, no errors
4)
restarted phone => OK
5)
adb shell
su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor
6)
weird things started appear...
build.prop 0 Kb and copying saved earlier file build.prop to /system does not help it stays empty... I could change permissions in properties but it didn't help build.prop empty and nothing I could do... I repeated system rw remount but now I started getting bad returns like "mount: '/system' not in /proc/mounts" as I never flashed rw super image...
7)
flashed super image again in FASTBOOTD => same results: build.prop empty and nothing you can do with it
8)
flashed super image again now just in BOOTLOADER but weirdly in bootloader there were only 6 sparses SUPER out of 6 (in FASTBOOTD there were 8 sparses out of 8) => same results: build.prop empty and nothing you can do with it
9)
flashed and restored my FIRMWARE: SOFIA_RETAIL_QPMS30.80-109-5 (without erasing: boot, recovery, metadata and user data partitions) phone is fine but ROOT the same RO

-----------------------------------------
P.S. I was afraid to flash SUPER to slots A and B like:
fastboot flash super_a super_fixed.bin
fastboot flash super_b super_fixed.bin

and I didn't do it even though I remember some guy mentioned that it helped with two slots...

I didn't take a chance... I just got my phone back after being dead bricked from Motorola service... in the bricked phone i had perfect touch screen in TWRP (3.5.0_10) damn! in the phone of the same model they send me back TWRP touch screen does not work... (looks like the different drivers are set for the touch screen)

 

[Ricardo Cruz]

ready and the script is active, thank you very much for everything.

 

[lebigmac]

Good morning, sorry I try to run sysrepair.sh, but nothing happens, the phone is off, in fastboot or I just connect it. I send you a screenshot of the script in lubuntu.

Hi @Ricardo Cruz. Thanks for your feedback. It looks like your device is not recognized by adb?

ready and the script is active, thank you very much for everything.

Did you get the sysrw_repair script to work inside your Linux environment? What was the problem?

Was super_fixed.bin created successfully and did you fastboot flash it to your super partition yet?
What is the result? Can you do this now?

=== Moto G Power (2020) XT2041-4-SS FIRMWARE: Android 10 "SOFIA_RETAIL_QPMS30.80-109-5" ===
1)
systemrw_1.32 (./makesysrw.sh size=50) => error code 73 (either way auto or manual)
2)
sysrw_repair_v1.32 (USB stick Ubuntu Mate 21.4) => Successfully created patched super image at /media/ubuntu-mate/Drive-C/sysrw_repair/img/super_fixed.bin
3)
"fastboot flash super super_fixed.bin" (in FASTBOOTD) => was sent 8 sparses SUPER out of 8, no errors
4)
restarted phone => OK
5)
adb shell
su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor

Hi @krasevalex. Thanks for your feedback. Please send me your log files from this folder. Thanks.
/data/local/tmp/systemrw_1.32/log/

You can successfully boot device after flashing super_fixed.bin AND you can remount partitions as R/W? That sounds like a success to me. Congratulations!

6)
weird things started appear...
build.prop 0 Kb and copying saved earlier file build.prop to /system does not help it stays empty... I could change permissions in properties but it didn't help build.prop empty and nothing I could do... I repeated system rw remount but now I started getting bad returns like "mount: '/system' not in /proc/mounts" as I never flashed rw super image...
7)
flashed super image again in FASTBOOTD => same results: build.prop empty and nothing you can do with it
8)
flashed super image again now just in BOOTLOADER but weirdly in bootloader there were only 6 sparses SUPER out of 6 (in FASTBOOTD there were 8 sparses out of 8) => same results: build.prop empty and nothing you can do with it
9)
flashed and restored my FIRMWARE: SOFIA_RETAIL_QPMS30.80-109-5 (without erasing: boot, recovery, metadata and user data partitions) phone is fine but ROOT the same RO

-----------------------------------------
P.S. I was afraid to flash SUPER to slots A and B like:
fastboot flash super_a super_fixed.bin
fastboot flash super_b super_fixed.bin

and I didn't do it even though I remember some guy mentioned that it helped with two slots...

I didn't take a chance... I just got my phone back after being dead bricked from Motorola service... in the bricked phone i had perfect touch screen in TWRP (3.5.0_10) damn! in the phone of the same model they send me back TWRP touch screen does not work... (looks like the different drivers are set for the touch screen)

I think you need to run script again with larger custom size and generate new super_fixed.bin with the repair script and fastboot flash it manually to your super partition.
After that everything should work as expected.

adb shell
su
cd /data/local/tmp/systemrw_1.32
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=50

I started getting bad returns like "mount: '/system' not in /proc/mounts" as I never flashed rw super image...

/system is only in Android 9 and earlier. In Android 10+ it's called /

 

[Ricardo Cruz]

Hi @Ricardo Cruz. Thanks for your feedback. It looks like your device is not recognized by adb?

Did you get the sysrw_repair script to work inside your Linux environment? What was the problem?

Was super_fixed.bin created successfully and did you fastboot flash it to your super partition yet?
What is the result? Can you do this now?

Well, in my case, the device was not detected when running the script in linux lubuntu live, what I did was create a usb with permanent storage. but later I faced the problem of the space in the usb for the img files, and passed the sysrepair folder to the Windows hard disk, where there was space. I ran the script, rebooted in fastboot and when finished reboot. I probe with root xplorer and I was able to switch to r / w, in fact I already modified an xml file in the vendor folder and I keep the changes on save and reboot. Thanks.

 

[krasevalex]

Hi @Ricardo Cruz. Thanks for your feedback. It looks like your device is not recognized by adb?

Did you get the sysrw_repair script to work inside your Linux environment? What was the problem?

Was super_fixed.bin created successfully and did you fastboot flash it to your super partition yet?
What is the result? Can you do this now?

Hi @krasevalex. Thanks for your feedback. Please send me your log files from this folder. Thanks.
/data/local/tmp/systemrw_1.32/log/

You can successfully boot device after flashing super_fixed.bin AND you can remount partitions as R/W? That sounds like a success to me. Congratulations!

I think you need to run script again with larger custom size and generate new super_fixed.bin with the repair script and fastboot flash it manually to your super partition.
After that everything should work as expected. Enjoy a fully read/writeable device!

adb shell
su
cd /data/local/tmp/systemrw_1.32
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=50

/system is only in Android 9 and earlier. In Android 10+ it's called /

in fact I ran script with size=50 but as I wrote I have got an error code 73... i flashed super_fixed.bin manually besides i did it twice, first from FASTBOOTD (it was sent 8 sparses out of 8) and second time i flashed it from just BOOTLOADER (strangely only 6 sparses out of 6)... anyway in both cases i had problems with build.prop file and RW system and in both cases I executed command:
mount -o remount,rw /


here is an attached zip file with my logs...

 

[Pachacouti]

Can this be adapted better using this method in anyway?

I continue to use my back up pulled, have tested countless methods, then found a way for your script to work better for me, but that's out of my league, I hope you can use this:

https://xdaforums.com/t/hahahack-dis-no-magisk-required.4337361/post-85683523

 

[lolvatveo]

except using lucky patcher to modify system apps on android 6.0.1 and android 7, i can't modify in any way, need help because above guide is only for android 10

 

[flaxx187]

- extract Bundle
- Flash the flashable file
- beeing happy

amazing work

testet with Poco F1

on /system/media I can create/rename new Files, but not move via root explorer why ?






on my redmi Note 10 Pro I got an error via TWRP, so I did it via adb
what is a super partition ?how I can check it ?


tried:

adb shell
cd /data/local/tmp/systemrw_1.32
chmod +x sytemrw.sh
./systemrw.sh

finally I got my rw system


I don't have to do this:

su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor

right ?

 

[lebigmac]

- extract Bundle
- Flash the flashable file
- beeing happy

amazing work

testet with Poco F1

on /system/media I can create/rename new Files, but not move via root explorer why ?






on my redmi Note 10 Pro I got an error via TWRP, so I did it via adb
what is a super partition ?how I can check it ?


tried:

adb shell
cd /data/local/tmp/systemrw_1.32
chmod +x sytemrw.sh
./systemrw.sh

finally I got my rw system


I don't have to do this:

su
mount -o remount,rw /
mount -o remount,rw /system
mount -o remount,rw /product
mount -o remount,rw /vendor

right ?

Hi. Thanks for your feedback.

on /system/media I can create/rename new Files, but not move via root explorer why ?

Usually if you can only rename system files or create empty system files this means you must run script again with larger custom size. Try for example size=50 or size=100
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=50

Regarding error 255 in some recoveries this is already fixed in next version

Enjoy a fully read/writeable device!

 

[flaxx187]

Hi. Thanks for your feedback.

on /system/media I can create/rename new Files, but not move via root explorer why ?

Usually if you can only rename system files or create empty system files this means you must run script again with larger custom size. Try for example size=50 or size=100
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=50

Regarding error 255 in some recoveries this is already fixed in next version

Enjoy a fully read/writeable device!

so shall I do it again with adb shell but write ?:
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=50


50 mbmore ? that would be helpfull

thanks I helps

but i have still issue, but it is bc the app or my zip file idk.

The Size is now there, thanks made !

 

[Pachacouti]

Is it possible to make the system partition contained in super to auto resize itself using your script?

I was reading how to resize system and cottoned on to a method to have the available space adjust itself automatically, like if I deleted the product partition, the system would adapt to the availble space?

From what Ive read here, we're one step away from a completely rw system in this so called ro system...

It's like this as I see it:

So we resize, and change the format to a rw format, this is to make it rw perm, and have the resize we need to adjust automatically to any freed up space on the fly


Found:

For those looking for the actual resizepart command, I think this is what the OP had in mind: sudo parted /dev/mmcblk0 resizepart 3 100% where /dev/mmcblk0 is the drive and 3 is the partition


Can the above be added/adapted to the script? (for each partition within super?) - oh, and to super itself?? (random idea, mount bind super.img to super.img on sdcard...)

Ps, this will fix no space left problems

Ps, found here:

Auto expand last partition to use all unallocated space, using parted in batch mode

Long story short, I need to perform this all automatically on boot (embedded system). Our engineers will flash images to production devices. These images will contain a small partition table. On b...

unix.stackexchange.com