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

[lebigmac]

Yes auto-resize feature is easy to do. Don't worry I will add it soon when I have more time

If you check the amazing superrepack tool by @munjeni (link in first post) he has already implemented this special feature long time ago. I'm only beginner programmer but that guy is a real expert

 

[The_Tablet]

hey @lebigmac! i finally figured out the issue. basically, i'd extracted systemrw_1.32_flashable.zip into a folder in /data/local/tmp called "systemrw_1.32", making the directory structure look like this:

data/
├─ local/
│  ├─ tmp/
│  │  ├─ systemrw_1.32/
│  │  │  ├─ systemrw_1.32/
│  │  │  │  ├─ tools/
│  │  │  │  ├─ config.ini
│  │  │  │  ├─ systemrw.sh

as a result, systemrw.sh was unable to find the tools directory because it was actually located in a subdirectory within the expected directory, which the script obviously doesn't know about as the location is hardcoded as "/data/local/tmp/systemrw_1.32/".

so after moving everything in that rogue subdirectory up one directory, so it looked like this (as intended) :

data/
├─ local/
│  ├─ tmp/
│  │  ├─ systemrw_1.32/
│  │  │  ├─ tools/
│  │  │  ├─ config.ini
│  │  │  ├─ systemrw.sh

the script finally worked! (see attached logs).

i booted into twrp and flashed the images, and my system is now finally(!) r/w!

sorry for the wild goose chase there, and i send my sincerest thanks over to you and everyone else who made this possible! :3

 

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

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 /

I repeated all procedure (./systemrw.sh size=50 => error code 73 in the phone => repair script in Ubuntu) and result this time is very good. The system is RW, nothing wrong with build.prop. Now I have full root.
So far everything's great. Thank you very much for this script.

 

[fire7ly]

sir I`m tried this earlier but I'm not getting Success I'm try it again today and got error 255
idk why it occur..
my device Spec are:-
Realme C3 RMX2027 Helio G70
rn on Realme UI 1.0 Android 10.

 

[Pachacouti]

View attachment 5419775
sir I`m tried this earlier but I'm not getting Success I'm try it again today and got error 255
idk why it occur..
my device Spec are:-
Realme C3 RMX2027 Helio G70
rn on Realme UI 1.0 Android 10.

This error is a twrp error I believe, seems twrp no longer correctly interprets the adb sideloaded file name as package.zip, notice package zip in log?

Bet your sideloaded zip was NOT called package.zip, I've seen this in stock recovery too

Something is trying to flash a zip, or has renamed your file, or is looking for a file called flashable.zip, most likely a typo in the script.. or twrp... or recovery lol.. I'm betting incorrectly imported twrp recovery...img

 

[fire7ly]

This error is a twrp error I believe, seems twrp no longer correctly interprets the adb sideloaded file name as package.zip, notice package zip in log?

Bet your sideloaded zip was NOT called package.zip, I've seen this in stock recovery too

Something is trying to flash a zip, or has renamed your file, or is looking for a file called flashable.zip, most likely a typo in the script.. or twrp... or recovery lol.. I'm betting incorrectly imported twrp recovery...img

I'm using pbrp sir it`s something mounting issue I guess.

 

[Pachacouti]

I'm using pbrp sir it`s something mounting issue I guess.

Yup, the file package.zip not found because no file called package.zip exists.

(Should say name of zip being used, not 'package.zip')

I find exploit's, I dont know how to patch them, because they're patched as soon as I mention them..

 

[fire7ly]

@lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..

 

[fire7ly]

Yup, the file package.zip not found because no file called package.zip exists.

(Should say name of zip being used, not 'package.zip')

I`m run this in system and result here!

@lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..

 

[lebigmac]

@lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..

Hi @fire7ly thanks for your log files.
I noticed you made a little mistake with the file path but script still worked nevertheless when launched manually. I'm surprised.

According to your script log everything went well. All read-only restrictions have been successfully removed from your super image. I'm not sure what exactly is causing bootloop on your device. Some devices don't like modified super images... There must be some kind of special protection feature inside your device that prevents it from booting into the super image if it has been modified. That's my guess. You could try to check logcat while device is trying to boot to find out more info about the exact bootloop reason.

Can you undo bootloop simply by flashing original stock super image? You might have to flash stock vbmeta as well. Good luck!

 

[fire7ly]

Hi @fire7ly thanks for your log files.
I noticed you made a little mistake with the file path but script still worked nevertheless when launched manually. I'm surprised.

View attachment 5420301

According to your script log everything went well. All read-only restrictions have been successfully removed from your super image. I'm not sure what exactly is causing bootloop on your device. Some devices don't like modified super images... There must be some kind of special protection feature inside your boot.img that prevents the device from booting into the super image if it has been modified. That's my guess. You could try to check logcat while device is in bootloop to find out more info about the exact bootloop reason.

Can you undo bootloop simply by flashing original stock super image? You might have to flash stock vbmeta as well. Good luck!

sir as you say I'm take log and my dev friend read and say me its problem from My_Product partition which is causing issue that My_Product is custom partition by Rui inside super, script decrease size of that partition. I'm flashed all vbmeta to disable verification & verity. this is the right path as you suggest in your tutorial I'm using "*" coz idk right name of folder that time... this have version name too so I'm just add * to assume to get right path by chmod command..
main thing is was under /data/local/tmp/systemrw_1.32/systemrw.sh
can you look into this again in attached my device log earlier..
thanks in advance

 

[Dobrozol]

Great job! Tell me, how can I return the system to read-only mode?

 

[fire7ly]

Great job! Tell me, how can I return the system to read-only mode?

flash super_orignal.bin from fastboot
as you flash super_fix from fastboot

 

[Dobrozol]

flash super_orignal.bin from fastboot
as you flash super_fix from fastboot

Thanks. But you can tell in more detail. Where to get the super_original.bin and super_fix files. Please write detailed instructions.

 

[fire7ly]

Thanks. But you can tell in more detail. Where to get the super_original.bin and super_fix files. Please write detailed instructions.

this script have 2 mode one is from recovery flash as zip second have run it in android environment.
if you run this in recovery then it patch and flash super automatically.
second if you run it in android environment with as mention location of /data/local/tmp/here_your_script_folder/here_script.sh then it create a "img" folder inside of script folder then pull super from your device make a backup and rename that to super_orignal.bin then extract that super and patch r/w capability then make that again super and rename it as super_fix.img so simply you get two bin files inside "img" folder
if you wanna r/w your device flash super_fix.img from bootloader.
if you wanna go back to original state "flash super_orignal.bin" from bootloader.
directory tree will like this :-
data/ ├─ local/ │ ├─ tmp/ │ │ ├─ systemrw_1.32/ │ │ │ ├─img/ │ │ │ │ ├─super_orignal.bin │ │ │ │ ├─super_fix.bin │ │ │ ├─ tools/ │ │ │ ├─ config.ini │ │ │ ├─ systemrw.sh
thanks this for @The_Tablet
That's it!

 

[fire7ly]

@lebigmac sir I'm unpack super with lunpack and compare both of super_fix.bin and manually pulled one super.img
and there are something like mounting issue. partition name not show its just show version.0001.img insted of my_company.img can you check this out.. idk what`s wrong with it..I can send compare list to you..
soon..

 

[daintycloud]

thank for sharing

 

[Jr.17]

so I did Everything ran First Script gave error code 73 so booted up my linux ran recovery script it after 10-15 minutes said it was succesful and it was all unlock so i did a quick check on my phone and im still locked.
went back to the P.C did a remount
mount -o remount,rw /

and gave me no output checked phone again same thing files looked so i assume i missed something

 

[Jr.17]

Which method are you using?

I'm dumb I have the same phone how did you set yours up?

 

[fire7ly]

So, I'm Successfully make my system R/W...
I want to describe my device spec again so you guys take a look into this..
Device:- Realme C3
Vendor:- Realme Stock Vendor
Android Version:- Android 10
SDK:- 29
Running UI Version:- Realme Stock UI ( Realme UI 1.0 ) A65 ( Latest At Experiment Time Now A67 )
SOC:- MediaTek Helio G70
Ram / Rom:- 4 / 64
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Summery
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I'm try this script approx 2 months ago that time it not work for me so I'm leave a reply and wait for script update version..
as update come I'm try again and it give me same error in pbrp so I'm decided to try this in android environment. and flash from bootloader mode but it not work for me I'm make again and flash from bootloader it works but I'm get error not enough space on system so I'm create patch super again with custom size and try to flash with bootloader but it not work this time I'm try with vbmeta still fail to boot it reboot back to bootloader I'm confuse to much. so I'm decided to make with lower custom size so I'm choose 20 still same method same problem, after many tickle I'm find the problem of vbmeta and auto resize partition problem coz As I'm say I'm use Realme UI so Realme implemented oppo_product partition of 7mb and when I'm use custom size it become fatty
so I'm decide to use custom size of 2 mb and make it again and flash via bootloader again but it still fail..
now I'm very disappointed. now I think if I'm flash super via sp tool.. And after successful flash it work.. Without any problem..

I'm recommend to all of you Take a nan droid backup of rom and try sp tool method to flash super so no error you get like dm-verity corrupt loop to recovery loop to bootloader actually I'm get many loop to recovery and bootloader and many time dm-verity corruption error.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Screen Shot​

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

My Old Posts:-
july 21:-
First Attempt
july 24:-
Try From Recovery But No luck
Sept 27:-
Tried From Recover
Tried From System
Sept 28:-
oppo_product Error But Actually Was Encryption
sept 30:-
Blindly compare stock and edited partitions
https://xdaforums.com/t/script-andr...t-system-read-write-r-w.4247311/post-85708413