[Android Software/Hacking General [Developers Only]] lebigmac:
Daily download limit has been exceeded yet again...

Don't worry, the download link should work again in about an hour. (y)

Hi @Gentisz

Can you try it in Android 10 ? Maybe it works in Android 10 on your device? Then you know for sure it's an Android 11 related issue.

Your script log looks good and you don't even have any cow files in lpdump.txt !

I don't know what is causing bootloop on your device. I wish there was a way to read the log in real-time during early-init boot stage.

Hi @jc-b could you please send me your log files from /data/local/tmp/systemrw_1.32/log/

Did you try remount partitions as r/w yet? What was the result?

Hi @_BГ@ckθut

Thanks for the feedback! Congratulations! Enjoy customizing your device to your liking!

To include /odm partition simply replace line #238 of systemrw.sh with these 2 words and save file makeRW $fName

@flypatriot size=15 is just the default value. For some devices this value is either too low or too high!

If you use size=0 or you omit this parameter completely, then script will resize each partition to minimum value.

size=50 works well on most Xiaomi devices. Not so sure about the other manufacturers... For some OnePlus devices this value is too high and it will fail with errorcode 70 (insufficient size).

I've not had the time yet to implement the auto-resize feature that was suggested a couple of pages ago. That should be added in one of the upcoming versions.

You shouldn't have to install any Magisk modules in order to run my script successfully. All you need is the script and custom recovery and shared_blocks feature basically.

@bseosbseos I'm happy you finally got it to work successfully on your Google Pixel 4 XL (Coral) device! All you had to do was run script with size=50 parameter. That's great news!

I'm surprised size=15 would result in this error and size=50 doing the trick. Usually this insufficient size error only happens when size=0 (shrink each partition to minimum size) is used.

Thanks for your feedback! I will check your logs.

You shouldn't have to flash the script more than once but it's not a problem if you do flash it more than once ;)

Please see my answer to @Danymq below as it also applies to you. Good luck!

Hi @Syrop

Cannot flash this partition in unlocked state

What the hell?! I've never seen this fastboot error before and it must really suck to experience it. I feel sad for you.

Please send me your log files from this folder (/data/local/tmp/systemrw_1.32/log/) if you want me to take a closer look at your problem.

Thank you!

Hi @KenIC1101

The BUNDLE file contains both the FLASHABLE.zip file that you can flash in custom recovery directly to your device as well as the sysrw_repair linux only script (to fix error 73).

Try to flash the flashable.zip in custom recovery.

You have a great device. This script would not be possible without the Poco X3 NFC device. I used this amazing device to develop the original script. Thank you Xiaomi!

Have fun debloating your device and customizing it to your liking! Be careful when debloating system apps though!

Hi @mslezak

Thank you for your additional info regarding COW files. So what you're basically saying is that COW files are safe to delete and are not required by the system during the boot-up sequence. This is great news for most OnePlus users. Now you can use all that wasted hard disk space for more useful things!

Yes I finally fixed the COW error simply by skipping all cow files when launching lpmake to create new patched super image before flashing it to device.

It was an easy fix but not easy to figure out since I don't have access to OnePlus device. Xiaomi user here.

Please feel free to give the script a try! Good luck!

Hi @samsungics120

/system and /product is r/w but /vendor is still r/o?! That's weird!

Please send me your log files from this folder (/data/local/tmp/systemrw_1.32/log/)

Thank you!