This is NOT WORKING for the MOTOROLA phone, specifically the MOTO ONE 5G ACE. The script did not unlock the partitions as they separated in lpmake. I looked at the files on Windows and Linux, and they are all as they were before. Why this is only working on the Xiaomi and the One Plus is beyond me. Anybody got this working on LG, Sony, Moto, Samsung?
Similar story I have, everything goes successfully, but after downloading to the system any file manager with rut access can't change system, vendor, product. Tried to stitch created super_fixed.bin as an image through adb, everything has passed successfully, but there is no result. Ulefone armor x7pro, 10 android.excellent, i did it and it finally finished with a message saying Congratulations...
but when it reboots the system partition is still read-only. the twrp and magisk are in place and i have su but "mount -o rw,remount /" says it's read-only and the partition can't be written. i've tried it multiple times with the same result. what should i do ?
Yes！SONY can't use it !
Device : Xperia 1 Mark II
PS C:\adb> adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-02-02 16:40 super -> /dev/block/sda23
POCO X3 pro, doesn't work
Similar story I have, everything goes successfully, but after downloading to the system any file manager with rut access can't change system, vendor, product. Tried to stitch created super_fixed.bin as an image through adb, everything has passed successfully, but there is no result.
adb shell cd /data/local/tmp/makesysrw_1.27 ./tools/bin/lpunpack ./files/super/super_fixed.bin
adb pull /data/local/tmp/makesysrw_1.27/files/super/system.img sudo su mkdir /mnt/dir mount -t ext4 -o loop,rw ./system.img /mnt/dir
A question please regarding to Xiaomi.eu - did you use it with the recent MIUI 12.6 like 21.4.1 or 21.4.7Working on my POCO X2 Device with super partition using v1.24....
Working on MIUI 12 global stable ANDROID 11 and Latest Xiaomi.eu beta roms...
I tried it on latest xiaomi miui 12.6 roms.... Working..... Tried dirty flashing weekly 21.4.7 rom over rw system partitions and it makes the system read only... U have to make it rw again ....A question please regarding to Xiaomi.eu - did you use it with the recent MIUI 12.6 like 21.4.1 or 21.4.7
And actually more important question - did you try to update Xiaomi.eu from e.g. 21.4.1 to 21.4.7 while having the previous system mounted as read-write?
Xiaomi.eu does not update by OTA but by downloading and flashing the zip file from TWRP, but I'm interested if dirty flashing the new Xiaomi.eu zip file works fine when the previous Xiaomi.eu was mounted read-write and wether maybe the newly flashed (updated) Xiaomi.eu automatically remains writable?
I have a Moto G Power and I get Error! Failed to create super_fixed.img file. I am on stock Android 10 and rooted. Since we have the same phone, Did you ever run into the same problem as I did and how did you fix it? Or did it complete without the error?Confirmed working on my moto g power (sofia) XT2041-4ss (Super Partition)
Confirmed working on my moto g7 (river) XT1961-1 (No Super)
Nice work!! Keep it up
Similar story I have, everything goes successfully, but after downloading to the system any file manager with rut access can't change system, vendor, product. Tried to stitch created super_fixed.bin as an image through adb, everything has passed successfully, but there is no result. Ulefone armor x7pro, 10 android.
su mount -o remount,rw / mount -o remount,rw /vendor mount -o remount,rw /product
Tried it and I get the same error creating super_fixed.bin I am about the throw in the towel and forget about it.
Can any one help mylogs! Oneplus 8 android 11
If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeni
automated bash script by lebigmac for Android 10 and above
Creation date: February 2021
Updated: April 2021
current status: experimental
Please click my like button below if you like my work! Thanks!
Confirmed working on these devices :
Xiaomi Poco X3 NFC
Xiaomi Poco X2 - Android 10/11
Xiaomi Poco X2 - Android 11 - v1.24
Xiaomi Poco F2 Pro - Android 11 - v1.26
Xiaomi Redmi Note 9 Pro joyeuse - Android 10
Xiaomi Mi 10 T Lite - Android 11
Xiaomi Mi 10 T lite - Android 11 - TWRP
Xiaomi Mi 10 - Android 11
Xiaomi Mi 10 Ultra - Android 11
Xiaomi Mi Note 10 Lite - Android 11 - OrangeFox
Xiaomi Redmi 9T - Android 11 - TWRP
Xiaomi Redmi 9 - Android 10
Xiaomi Redmi 9 - Android 10 - v1.26
Xiaomi Redmi K30 - Android 10
Asus Rog Phone 3 - Android 10 - TWRP
OnePlus Nord - Android 11 - v1.24
Doogee S96Pro - Android 10 - v1.26
F150 model B2021 - Android 10
Realme C12 - Android 11
WOW. I'm searching for something like this for days. But let me do a noob question.
At this momento am using a custom MIUI rom with Android 10. I tried to use another rom with A11 but ever got my storage encrypted and ever when I need to update my rom, need to do that [email protected]#$#$% format data as you can see in my screenshot. After installing this script my storage will be decrypted ever? Ever when I back to recovery everything will be there (decrypted)? I really hope so.
Thanks for your work bro.
cd /data/local/tmp/makesysrw_1.31 ./makesysrw size=20 out=/external_sd/super.img
chmod +x /data/local/tmp/systemrw_*VERSION*/systemrw.sh
# Run this command *IF YOU HAVE NO SUPER PARTITION* ./systemrw.sh # Run this command if you're first time user *AND YOU HAVE SUPER PARTITION* # Specify the extra free space in megabytes for each partition: ./systemrw.sh size=15 # Plug an existing super image into the script like this *ONLY IF YOU HAVE SUPER PARTITION* ./systemrw.sh in=./img/super_original.bin size=15 # Specify both the input file as well as the output destination *ONLY IF YOU HAVE SUPER PARTITION* ./systemrw.sh in=./img/super_original.bin out=./custom/path/super_fixed.bin size=15
adb shell "ls -l /dev/block/by-name/super"
I try to redo the procedure, i want to change the size. but i get error, can't remove lock.
I am happy to say that, all the things went fine with my Realme C12.
I have removed original super.img right after lpunpack finishes. This makes me use your tool with just 15GiB free space.
A small thing is that, in your update-binary, please create a dir /data/local/tmp if it does not exist.
If it does not exist, your tool will fail to install.
It will be not present if a person clean flashes your tool(wipe data).
Also system RW works fine, but vendor RW gives operation not permitted.
Do I need use chattr with the block of vendor?
Also, we can use like this sh makesysrw.sh. Advantage of this is that, we don't need to make it executable and shebang is ignored.
No Orangefox recovery too for Oneplus 7T , unfortunately. Oneplus really messed up 7T's decryption with android 10. I'm hoping for it to fixed with OOS 11 update which too, got delayed because they didn't care for its decryption issues in the first place. Its mind boggling that the 7T doesn't have a working TWRP even after 1 ½ years of being launched.
But is it a new version or what?
Does it work without disabling DM-verify?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img