[Android Software/Hacking General [Developers Only]] Pachacouti:
Magisk is no more...

I present a new fool proof method of flashing su to Android 10_Q and above!!

I ranted and ranted about variant=user/user-debug/eng builds that I got no-where... people thinkin am dissin john wu, nah, I respect what I've learnt from his app forcing me to connect online, I want su without connecting, in order to secure my own fone.

Introducing proof!!

Simple. Instead of flashing boot.img

Flash boot-debug.img from stock.

This address's the lack of adb root.

Logs:

D:\0\AdbStation>fastboot --disable-verity --disable-verification flash vbmeta vb

lankmeta.img

Rewriting vbmeta struct at offset: 0

Sending 'vbmeta' (4 KB) OKAY [ 0.000s]

Writing 'vbmeta' OKAY [ 0.000s]

Finished. Total time: 0.016s

D:\0\AdbStation>fastboot --disable-verity --disable-verification flash boot boot

-debug.img

Sending 'boot' (32768 KB) OKAY [ 0.764s]

Writing 'boot' OKAY [ 0.515s]

Finished. Total time: 1.404s

D:\0\AdbStation>fastboot --disable-verity --disable-verification flash recovery

MyTwrp.img

Sending 'recovery' (26086 KB) OKAY [ 0.718s]

Writing 'recovery' OKAY [ 0.406s]

Finished. Total time: 1.139s

D:\0\AdbStation>fastboot reboot-recovery

Rebooting into recovery OKAY [ 0.000s]

Finished. Total time: 0.000s

D:\0\AdbStation>adb root

adbd is already running as root

D:\0\AdbStation>adb root

restarting adbd as root

D:\0\AdbStation>adb shell

Armor_X5_Q:/ # mount -o remount,rw /system_root

mount: '/system_root' not in /proc/mounts

1|Armor_X5_Q:/ # mount -o remount,rw /system

mount: '/system' not in /proc/mounts

1|Armor_X5_Q:/ # mount -o remount,rw /

'/dev/block/dm-1' is read-only

Armor_X5_Q:/ # su

/system/bin/sh: su: inaccessible or not found

127|Armor_X5_Q:/ # ls

acct d init.environ.rc metadata sbin

apex data init.rc mnt sdcard

bin debug_ramdisk init.usb.configfs.rc odm storage

bugreports default.prop init.usb.rc oem sys

cache dev init.zygote32.rc proc system

charger etc init.zygote64_32.rc product ueventd.rc

config init lost+found product_services vendor

Armor_X5_Q:/ # cd apex

Armor_X5_Q:/apex # ls

com.android.apex.cts.shim com.android.media@292000301

com.android.apex.cts.shim@1 com.android.resolv

com.android.conscrypt com.android.resolv@292000502

com.android.conscrypt@291900801 com.android.runtime

com.android.media com.android.runtime@1

com.android.media.swcodec com.android.tzdata

com.android.media.swcodec@292100201 com.android.tzdata@291900801

Armor_X5_Q:/apex # exit

D:\0\AdbStation>adb reboot bootloader

D:\0\AdbStation>fastboot --disable-verity --disable-verification flash recovery

recovery.img

Sending 'recovery' (20646 KB) OKAY [ 0.577s]

Writing 'recovery' OKAY [ 0.312s]

Finished. Total time: 0.889s

D:\0\AdbStation>fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.000s

D:\0\AdbStation>adb root

restarting adbd as root

D:\0\AdbStation>adb shell

Armor_X5_Q:/ # exit

------------------------

Pay attention, the first part above, I flashed a twrp...

Below, I flash stock images... without closing adb window.

--------------------------------------------------------------

D:\0\AdbStation>adb reboot bootloader

D:\0\AdbStation>fastboot --disable-verity --disable-verification flash boot boot

-debug.img

Sending 'boot' (32768 KB) OKAY [ 0.764s]

Writing 'boot' OKAY [ 0.499s]

Finished. Total time: 1.373s

D:\0\AdbStation>fastboot --disable-verity --disable-verification flash recovery

recovery.img

Sending 'recovery' (20646 KB) OKAY [ 0.484s]

Writing 'recovery' OKAY [ 0.328s]

Finished. Total time: 0.811s

D:\0\AdbStation>fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.000s

D:\0\AdbStation>adb root

restarting adbd as root

D:\0\AdbStation>adb shell

Armor_X5_Q:/ # su

/system/bin/sh: su: inaccessible or not found

127|Armor_X5_Q:/ # exit

D:\0\AdbStation>adb shell

Armor_X5_Q:/ # cd /system

Armor_X5_Q:/system # cd bin

Armor_X5_Q:/system/bin # ls

Edit'd not relevant.. too long the things we can do list pissed one off...

Armor_X5_Q:/system/bin #

No MORE MAGISK!!!

It'a a feature of Android 10 and over lol... says so in the android docs....

who needs su when you have root?

SYSTEM_AS_ROOT

Voila...

it's in the understanding.

YouRoot