[Android Software/Hacking General [Developers Only]] Pachacouti:
Not your usual tut... it's more a bit of advice. Respect.

When I first tried to flash a rooted recovery, it all failed until I read of vbmeta. I jump through the vbmeta route, then I realise something VERY important.

When you flash a blank vbmeta, you wipe the structure of much of your fone. You never were supposed to WIPE your vbmeta structure.

Magisk needs YOU to do this. YOU dont.

A test resulting in Proof:

How many do this?

fastboot flash vbmeta blank_vbmeta.img

fastboot flash boot boot.img

fastboot flash recovery twrp_recovery.img

Or

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot --disable-verity --disable-verification flash boot boot.img

fastboot --disable-verity --disable-verification flash recovery twrp_recovery.img

Both are wrong. What if: dm-1,2,3 cant mount?

Where are they if you wiped vbmeta? Does your fone know?

You WILL need vbmeta after this.

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img 2>nul >nul

fastboot flash boot boot-debug.img

-allowed me to then do what I want?

How to add su to fone.

Follow the busybox link I posted. Do it manually in twrp.

Flash back to stock boot/recovery

Discover $ and # mean nothing

Discover I got full access with no app's adapted for such use...

Ask why they still use pie..

It's the only tutorial you'll need with a boot-debug.img

Let this be a warning.

It is the ONLY warning you'll get...

with your vbmeta blank'd you will be constantly trying to bypass safetynet

Warning time is up...

Flash back to stock after getting su to work with $ instead of #

su is no longer true root, so $

(system_as_root IS root, su comes AFTER, and so goes from # to $ in the structure of things.)

su is no longer used in # it's a role reversal. # is now $ if u get me.

in my fone...

$ su --context u:r:system_app:s0 -c "pm uninstall --user 0 com.google.android.apps.wellbeing" < /dev/null

$ success

$ su --context u:r:system_app:s0 -c "pm uninstall --user 0 com.android.emergency" < /dev/null

$ success

$

That's why I posted adb logs, proof is in the order of what you see... notice I started with

fastboot --disable-verity --disable-verification flash whatever

and as I progressed I no longer used anything other than

fastboot flash boot whatever.

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img 2>nul >nul is HOW to disable vbmeta without WIPING it in a variant=user build

Wipe it if you want. I dont. Magisk wants you to when it is un-neccessary.

Because when removing the boot-debug and flashing stock back, my fone pass's safety.net, after re-locking bootloader, even with an unorthodox method produced by su when it is supposed to crash android 10 is it not? Magisk kills su by commandeering it's location, not android 10.

I'm not saying DONT use magisk using this method, it wont work. Side effects of magisk installed, with this is dead adb period Nada!

I'm saying by installing magisk, which takes over (patches) your vbmeta, the boot-debug.img becomes useless, just another boot with no vbmeta structure to follow...

Now one of you need to separate my notes from my commands, keep commands in order, and SEE.

Cause I rooted my fone. Here.#

Ps, at no point in this post did I use a blank vbmeta.

To properly disable verity, load boot-debug.img, reboot, type:

adb root

adb disable verity

adb reboot

That's it! it stay's across boot flashing etc... so bang goes --disable-verity, not needed after.

This is where you'r all going WRONG.

As aquarian, I swim where the fish sink... through their dead bodies that are not of the sea, I raise us all to immortality, by simply producing all 3 in me, jesus, lucifer, and the monkey.

It never was physical ;)