[Android Software/Hacking General [Developers Only]] lebigmac:
Hi again @xda general. You never sent me your log files from script folder...

Are you sure you can't mount your system as RW after running my script on your Redmi Note 9 (merlin) ?

Here you said that it works on your device. According to your screenshot you can mount all your important partitions as RW including your system partition:

Now compare to my screenshot:

If you don't get the '/dev/block/dm-0' is read-only error that means it works! Congratulations! :love:(y)

Why would you format or erase your partitions after running my SystemRW script? That doesn't make any sense at all.

You must only reboot device once after running the script! That's all! ;)(y)

Have fun debloating and customizing your fully read/write-able device! :love:(y)

Hi @jis251

Thanks for your positive feedback. I'm happy that the script works perfectly on your OnePlus Nord 2 device.

Have fun debloating and customizing your fully read/write-able device! :love:(y)

Hi @JLamp thanks for your interest in this project. I'm sad to hear that you were not able to get the script to work on your Motorola device. Don't worry I'm sure we can get it to work. Please send me your log files from this folder:

/data/local/tmp/systemrw_1.32/log/

Hopefully in next version I can finally fix that annoying error 73 that some motorola users experience.

Sadly I don't have access to a Motorola device or else I could've fixed this annoying issue a long time ago...

To undo all changes performed by my 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).

Then it should be no problem to run the amazing superrepack tool by @munjeni on your stock read-only super image. Even though both tools pretty much do the same thing but in a different way (his tool does the job in a much more sophisticated way and on the fly) you should have better luck with his tool because that guy is a real professional. Remember I am only beginner programmer that's why my script is not perfect yet but don't worry I'm constantly working on improving it so please keep your feedback coming. Thanks! ;)

Hi again @jhayprince. Your first log looks good. Your second log is empty.

It looks like script successfully removed shared_blocks read-only feature from your most important partitions including /vendor :D(y)

Please run this code below while device is in Android mode and upload this file here/sdcard/my_tune2fs_output.txt

Thanks! (y)

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

Hi @Toreton thanks for your log files.

You replaced this line of code

if [[ "$imgName" == *"system"* || "$imgName" == *"product"* || "$imgName" == *"vendor"* ]]; then makeRW $fName; fi

with this line of code?

makeRW $fName

That's a great idea! Why only make RW system, product and vendor if you can make them all RW? :D

I shall make this the default behavior in next version. Thanks for your feedback!(y)

I'm happy you got everything to work properly after running script a second time with larger custom size (y)

Have fun debloating and customizing your fully read/write-able device! :love:(y)