yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Pachacouti:
Its best if I dont quote 2 much so to answer as much as I can in a one-er...

I tested this and it works. To a point.

I tested it extensively...

In a nutshell, clean slate, adb pushed your zip, though unzipped, to /storage/emulated/0/Download

Followed your commands, all went well. The first time I did it, I managed to and pull (but lost) a copy of the super_fixed from the img folder in your root dir, to store for further tests, put that aside, and continued the test's.. so I reboot from ORIGIONAL recovery, see, I Didn't have a twrp at this point, I made my own magisk'd bootloader, so have magisk but cant su offline, so flash the apk, got su, and dm-1, 2, or 3 read only.

I then get a working twrp from lopstom, and suss whats wrong, for I see the mounting of system_root. I never wanted to mount this till I see you mention it, so I test it, and yes... I can enable it, but no writes... yet.. Once twrp was flashed to recovery, I could see system_root in red. this is because after the super flashing reboot, I then flashed stock bootloader and reflash twrp, booting back into recovery, test it, no su in the twrp tho, (soon sort that) so reboot to reflash my bootloader offering the magisk greyed out on desktop once rebooted, but before going into gui, I go back into twrp and nothing is writable, dm-1, 2, 3, which I learn is system/vendor etc... but I can mount them in twrp. What now? reboot into gui and flash magisk apk, reboot back into twrp, voila, your script works... but not in gui when rebooted (my aim)

And writes are not saved. I put this down to we can fool the root and system, but not the basic point of user builds. If they cant flash a magisk bootloader in gui, your script will act same.

I'm not really a developer, but I guess I'm good at finding things, and creating new things, by giving others ideas that lead to the scripits I need, I'm too out of touch nowadays, man, my first pc was a zx81....

Edit: I forgot, once you've made your super_fixed bin, you can reflash this super after, say a bad flash, without need for the script, just use the vbmeta before you flash it... just a positive note for ya :)

Ps, remember my notes, a usr build will fail to mount your partitions once booted into fone, hence folks think it dont work. It does in twrp, if you have a rooted bootloader, but user builds freeze system changes if vbmeta is false, like we use... this is why magisk fails to flash in the gui... variant=user

All pie are using variant=eng, but they are for PIE, Pie works, but I'm on android 10 a only arm64-v8a... so no go, but can get you to flashing magisk manually from a twrp recovery.
[Android Software/Hacking General [Developers Only]] b4minee:
Sure bro let me find out.
[Android Software/Hacking General [Developers Only]] Pachacouti:
your requested file, magisk eng converter thingy module, load in magisk 20.1 I think.. Never tested it but I believe it's good... it wont work in latest canary build.
[Android Software/Hacking General [Developers Only]] Facebooook:
Here is screen shot
[Android Software/Hacking General [Developers Only]] Jr.17:
I keep Getting Error Code 73
[Android Software/Hacking General [Developers Only]] FredMontteiro:
Hi @Lebigmac

I always mounted this exact same device (on the same Android 9) as RW. Suddenly changes made to /System/priv-app revert to original after reboot. I used to mount RW with any root file manager app. It's a mystery.

I got it in a way that I don't like, but I'll share the solution:

I flashed twrp and through the twrp file manager I did what I wanted, which was to install a third-party app in Priv-app.

As I don't want a custom recovery, I flashed boot.img in slots A and B to remove the twrp, of course I lost root access too, and the app I installed in Priv-app disappeared, but then I just reinstalled magisk in the form "without twrp" and everything came back including the app in Priv-app. And of course without twrp which is what I wanted.

I have attached the result of Termux to the code you gave me. Thanks!

Edit:

A method like the "app systemizer" magisk module is not useful for me, as I want my app to resist a factory reset.
[Android Software/Hacking General [Developers Only]] gravityz3r0:
Thanks, tried it using termux in android add it works now. However, I'm unsure how to manually "flash" the generated .bin file in the bootloader, can't seems to find the guide anywhere. I only know the auto using "kalibass" method but manual wasn't mentioned. Also, just to confirm this script will ultimately turn /system partition into R/W?
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi walid. Unfortunately I cannot help you with decrypting your /data folder in TWRP as I have never experienced this issue before. Usually all I have to do in TWRP is enter my pin code and it will automatically decrypt my /sdcard folder. Why it would encrypt your /data folder is a mystery to me.

All I can suggest to you is to thoroughly search here in the XDA forum. I'm sure somewhere in this forum there is a solution to this specific TWRP related problem. Good luck!
[Android Software/Hacking General [Developers Only]] Ayoub$#:
You can now download and install the tool and then copy the system files and paste them into / sbin / magisk / modules / terminal_systemize / system.

and reboot phone
[Android Software/Hacking General [Developers Only]] walid77dz:
i tried to copy data folder but the copiyng operation finished by a faillure
[Android Software/Hacking General [Developers Only]] Ayoub$#:
You must have magisk and root explorer pro

magisk last version

Try changing a specific application to the system by typing in the terminal type systemize then 1 and then type any application you want to place in the system
[Android Software/Hacking General [Developers Only]] lebigmac:
Guys this thread is about discussing my script not about discussing magisk or other things. Please stay on topic.
[Android Software/Hacking General [Developers Only]] Ayoub$#:
Well, I forgot and made a mistake

I think the new version of lebigmac will be universal because no one gives us how to format the read and write system. On version 10 or later

I hope this new version will be via phone or windows without twrp
[Android Software/Hacking General [Developers Only]] lebigmac:
Good news. New hotfix available HERE

I got rid of that buggy get minimum size function and reworked the size querying algorithm a little bit. Should be more stable now.

Next step will be to make the script compatible with those devices that have empty partitions embedded inside their super partition...

Also ronnie was complaining about syntax error but I have yet to find the syntax error... If anyone finds it please let me know so I can fix it. Thank you!
[Android Software/Hacking General [Developers Only]] Ayoub$#:
Hi I run script and it work but partition still read-only on my umidigi . Please help
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi Ayoub thanks for your feedback.

It looks like the script worked and successfully resized your embedded super partitions. It also looks like it successfully removed the shared_blocks feature of the partitions.

If you run tune2fs -l /dev/block/dm-0 you should be able to verify this.

This is the feature that's causing many stock Android 10+ phones to be read-only.

I really don't know why you still can't mount root as r/w . Anybody know why? Maybe umidigi have double or triple read-only protection?
[Android Software/Hacking General [Developers Only]] lebigmac:
try running

mount -o remount,rw /

and at the same time check logcat output. Maybe it gives a hint about what's wrong
[Android Software/Hacking General [Developers Only]] lebigmac:
Ayoub I think I know what is your problem. You did not disable dm-verity and verification! Did you check is there Orangefox custom recovery available for Umidigi? Inside custom recovery you can easily disable dm-verity!
[Android Software/Hacking General [Developers Only]] Ayoub$#:
Please show me how to disable it
[Android Software/Hacking General [Developers Only]] lebigmac:
boot into custom recovery and then execute these 2 commands. Try with orangefox if you have no twrp

adb disable-verity

adb shell avbctl disable-verification
[Android Software/Hacking General [Developers Only]] Ayoub$#:
thanks
[Android Software/Hacking General [Developers Only]] lebigmac:
Even if you're using a custom ROM that is already read write, you should still be able to use my script to resize your partitions inside super. For example you can give each partition 100 MB extra free space or more (system, vendor, product, odm,...).

Or you can use the script to shrink down each partition to its minimum size.

I checked your log file and your snapdragon is compatible with newest version of the script.
[Android Software/Hacking General [Developers Only]] BlazingKahn35:
My device (OnePlus 8T) doesn't support TWRP. Is there a way to do it without TWRP?
[Android Software/Hacking General [Developers Only]] lebigmac:
Yes it' will be possible to run script directly in Android in next version!

Have you tried searching for Orangefox custom recovery for your device here at XDA subforums?
[Android Software/Hacking General [Developers Only]] BlazingKahn35:
Yes both orangefox and twrp not available
[Android Software/Hacking General [Developers Only]] lebigmac:
Great news! Flashable zip is almost ready! I'll upload it later today. Any volunteers want to beta test the new flashable zip to help me iron out any bugs? Please send me a message. Thanks!

Installing the script has never been this easy. Simply swipe with finger inside TWRP and it's automatically installed to correct location on your phone.

Then it checks a config file for any custom script execution arguments and launches the script with these arguments depending on whether or not your phone has a super partition.

Let me tell you it was not easy to create this flashable zip installer but I had lots of fun learning about this whole flashable zip concept the past few days.
[Android Software/Hacking General [Developers Only]] gravityz3r0:
I managed to flash the super_fixed using fastboot, but ended up in bootloop :( when i enter TWRP again, it throws me some "Failed to mount /odm (invalid argument)" error as well.
[Android Software/Hacking General [Developers Only]] lebigmac:
Hey @FredMontteiro I'm happy you found a solution to your device specific problem (y)

Hi. Please send me output of mount command.

adb shell
mount>/sdcard/mymount_facebooook.txt

Hello. Please use the included sysrw_repair script in a Linux environment to fix error 73. Good luck!

Hi. Bootloop it's always very sad. Which device is it?

Can you undo bootloop by flashing back original stock super image?

dm-verity and verification was successfully disabled by script or not? You can find this info in log file...

Good luck!
[Android Software/Hacking General [Developers Only]] Pachacouti:
It will if your bootloader shows variant=debug or variant=user-debug when opened in hex, check beginning of bootloader, you'll know...
[Android Software/Hacking General [Developers Only]] gravityz3r0:
It's a Xiaomi 10 ultra on xiaomi.eu ROM, tried flashing back the original super image but get error : Invalid sparse file format at header magi. Yes, dmverity and verification is disabled during the creation of the image.
[Android Software/Hacking General [Developers Only]] lebigmac:
That's not an error but only a warning. Fastboot should still be able to flash raw image file. You can sparse the file using the included img2simg tool if you want but it shouldn't make a difference.

adb shell
su
cd /data/local/tmp/systemrw_1.32
./tools/img2simg ./img/super_original.bin ./img/super_original_sparse.img

If flashing back stock read-only super image doesn't fix bootloop you can try restoring original stock vbmeta as well. It should be inside your stock MIUI firmware which you downloaded from your manufacturers website (or Xiaomi.eu in your case). Good luck!
[Android Software/Hacking General [Developers Only]] gravityz3r0:
Hmm, it doesn't proceed to flash beyond the warning though. Just terminated afterward. vbmeta reflashed to no avail. In the end, i just do a format and re-flash the ROM all over again from the scratch.
[Android Software/Hacking General [Developers Only]] b4minee:
Well that's what I get brother 🤡
[Android Software/Hacking General [Developers Only]] lebigmac:
Hey. To add Android 12 support simply open systemrw.sh with text editor and add these 2 new lines between line #408 and line #409. Then save file and try again. Good luck!

elif (( $sdkVersion == 31 )); then
android=12

Have you tried yet superrepack tool by munjeni (link available on front page)? What results do you get with his tool?

Hi again Pachacouti. What do you mean no su in the TWRP? Custom recovery is engineer build and has root user by default!

I still don't understand what a rooted bootloader is supposed to be? Please show screenshots of what you're talking about and send me your log files! Thanks.
[Android Software/Hacking General [Developers Only]] c_eduardogomes:
It worked on my Poco X3 Pro(vayu). Thank you so much man! :D
[Android Software/Hacking General [Developers Only]] Pachacouti:
A rooted bootloader... hmmm... take bootloader, patch with magisk, <--- These are the correct instructons aren't they?

So your rooting BOOTLOADER to flash to RECOVERY to mount SYSTEM to root fone.

Flash said remixed bootloader into recovery and wonder what you just did. Magisk put itself into the bootloader, rooting the boot, that is then useable in recovery to do what you do.

Your actually rooting the bootloader. Yeah, its fake, symlinks to system bin but if system aint loaded, magisk cant patch bootloader ANYMORE if variant=user. BOOTLOADER wont mount after fone boots, with =user, but variant=eng does.

Who am I to argue with myself.. lol...

John wu is clever enough to know this, user variant wont cut it, that's why no-one mentions it... but being paid by apple means apple want him selling apple not rooting android, preventing us buying apple, just business.. this creates a conflict of interest, I mean, I can patch my recovery and it will also boot, but boots twrp when loaded as boot.img, so a magisk patched bootloader is a rooted bootloader. it's loaded to recovery.#

#So to john wu, explain please? Why your magisk cant patch a bootloader when system is YET to be mounted? variant=user, because variant=eng WORKS!

And hence all are using pie with ENG at the begining of their bootloaders, failurs after PIE are due to build variant, which is USER since PIE. I rest my case.

And google have made this very clear, yet no word from john wu, respect!!

Google are no longer releasing eng/debug builds, as stated by them. And they're about to kill all older android fones, betting it's those with variant eng bootloaders.. ;)
[Android Software/Hacking General [Developers Only]] bouyakasha:
Is there a list of phones this works with? I'm about to do with with OnePlus N200, but there's no MSM tool yet out so if I brick it... there's no way back.
[Android Software/Hacking General [Developers Only]] bouyakasha:
I found the list, and since Nord + 11 was listed, I though it would work on my N200.

Unfortunately, when installing the zip in TWRP it instantly restarted the phone, but this time directly into TWRP. Now I can't get the phone to start up to anything but TWRP. Am I bricked?
[Android Software/Hacking General [Developers Only]] Pachacouti:
No. Sounds like you flashed your twrp to bootloader instead of recovery... but you may need to reflash if you cant reflash your bootloader while in twrp. Try reflashing your file to recovery. If thats all it mounts, you have no system, so reflash stock and try aagin.
[Android Software/Hacking General [Developers Only]] b4minee:
Upss...…bootloop bro🤡

Upss...…bootloop bro🤡
[Android Software/Hacking General [Developers Only]] Pachacouti:
Must have been idea's night last nite while my street was ablaze, 6 fires in one street in one night, wowsers...

Anyway (clap in advance)...

Take, the system image instructions from here, use to insert a rw system for those who simply cant rw to system... (even custom os wont flash on my fone, yet chrooted nethunter works in gui...) my prob at present... dd the difference so size match's scatter file...

Android 10 Q system as root is harder than I thought...

Could someone give me a few lines to extract or insert a lineage system.img into my super to see if that works?

Even one that does the work while the script is running hint hint ;)
[Android Software/Hacking General [Developers Only]] c_eduardogomes:
See if it runs the right file. I did it using Recovery Orange Fox and flashing systemrw_1.32 zip file, I didn't configure anything, I just ran it.
[Android Software/Hacking General [Developers Only]] b4minee:
Script ran smoothly, but once I flashed super fixed it doesn't boot. It comes to the Google loading screen and fails. Then reboots.
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi @b4minee. Please send me your log files from this folder. Thanks.

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

Were you able to undo the bootloop simply by restoring original stock super image?

Hi @bouyakasha.

Please send me your log files from this folder. Thanks.

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

No it's not hard brick. Sounds like bootloop.

To fix bootloop simply restore original read-only stock super image. You might have to restore original vbmeta image as well. Good luck!
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi @c_eduardogomes. You're welcome. I'm happy script works flawlessly on your device. Enjoy a fully read/writable device!
[Android Software/Hacking General [Developers Only]] Ricardo Cruz:
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.
[Android Software/Hacking General [Developers Only]] 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.
[Android Software/Hacking General [Developers Only]] 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
[Android Software/Hacking General [Developers Only]] Pachacouti:
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...
[Android Software/Hacking General [Developers Only]] lebigmac:
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).
[Android Software/Hacking General [Developers Only]] lebigmac:
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! (y)
[Android Software/Hacking General [Developers Only]] 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
[Android Software/Hacking General [Developers Only]] 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!

Hello @Pablo_S please check first post in this forum thread for manual installation instructions. Good luck!
[Android Software/Hacking General [Developers Only]] Ricardo Cruz:
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.