[Android Software/Hacking General [Developers Only]] Pachacouti:
For those in doubt, test {Mod edit}

They never needed root in a system as root phone, and never sussed it... you dont use su anymore.. type root commands without su... it's really that simple, only those who lost a sight cant see it, so believe they NEED magisk.

All buy grand design... hhah...

The monkey king is the dna reset switch. Hack Dat!!

D:\0\AdbStation>adb root

restarting adbd as root

D:\0\AdbStation>adb remount

/system/bin/remount exited with status 2

remount failed

D:\0\AdbStation>adb shell

Armor_X5_Q:/ # su

Armor_X5_Q:/ # ^C

130|Armor_X5_Q:/ #

130|Armor_X5_Q:/ # exit

130|Armor_X5_Q:/ #

130|Armor_X5_Q:/ #

130|Armor_X5_Q:/ # ^C

130|Armor_X5_Q:/ #

130|Armor_X5_Q:/ #

130|Armor_X5_Q:/ # exit

D:\0\AdbStation>adb reboot bootloader

D:\0\AdbStation>fastboot flash boot boot.img

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

Writing 'boot' OKAY [ 0.575s]

Finished. Total time: 1.482s

D:\0\AdbStation>fastboot reboot

Rebooting OKAY [ 0.001s]

Finished. Total time: 0.006s

D:\0\AdbStation>adb root

adb: unable to connect for root: no devices/emulators found

D:\0\AdbStation>adb shell

Armor_X5_Q:/ $ su

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

mount: '/dev/block/dm-1' not user mountable in fstab

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

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

1|Armor_X5_Q:/ $ mount -o rw,remount /system_root

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

1|Armor_X5_Q:/ $ mount -o rw,remount /system_root/

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

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

mount: '/dev/block/dm-1' not user mountable in fstab

ho "it works! @ $x">$x/test.txt; cat $x/test.txt; rm $x/test.txt; done <

mount: '/dev/block/dm-1' not user mountable in fstab

/system/bin/sh: can't create //test.txt: Read-only file system

cat: //test.txt: No such file or directory

rm: //test.txt: No such file or directory

mount: '/dev/block/dm-0' not user mountable in fstab

/system/bin/sh: can't create /product/test.txt: Read-only file system

cat: /product/test.txt: No such file or directory

rm: /product/test.txt: No such file or directory

mount: '/dev/block/dm-2' not user mountable in fstab

/system/bin/sh: can't create /vendor/test.txt: Read-only file system

cat: /vendor/test.txt: No such file or directory

rm: /vendor/test.txt: No such file or directory

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

mount: bad /etc/fstab: No such file or directory

1|Armor_X5_Q:/ $ cd /system/app/

Armor_X5_Q:/system/app $ ls

ATMWifiMeta LongShotScreen

AdupsFota MDMConfig

AdupsPrivacyPolicy MDMLSample

AutoDialer MtkBluetooth

BasicDreams MyGene

BatteryWarning Nfc_st

BluetoothMidiService NonFrameworkLbs

BookmarkProvider OsuLogin

BuiltInPrintService PacProcessor

CarrierDefaultApp PartnerBookmarksProvider

CertInstaller PriDeskClock

ChildrenSpace PriImei

CompanionDeviceManager PriNotePad

CtsShimPrebuilt PriScreenRecorder

DebugLoggerUI PriSoundRecorder

EasterEgg PrintSpooler

EasyLauncher SecureElement

FMRadio SetupWizardNewOverlay

Gba SimAppDialog

GnssDebugReport TFaceServiceApp

GoogleExtShared Traceur

GooglePrintRecommendationService VZWRemoteSimlockService

HTMLViewer WallpaperBackup

KeyChain YGPS

LiveWallpapersPicker YTMusic

LocationEM2

Armor_X5_Q:/system/app $ mount -o remount,rw /

mount: '/dev/block/dm-1' not user mountable in fstab

1|Armor_X5_Q:/system/app $ mount -o rw,remount rootfs /

mount: '/' not in /proc/mounts

1|Armor_X5_Q:/system/app $ cd /

Armor_X5_Q:/ $ mount -o rw,remount rootfs /

mount: '/' not in /proc/mounts

1|Armor_X5_Q:/ $ exit

D:\0\AdbStation>adb shell stop

stop: must be root

D:\0\AdbStation>adb sync

adb.exe: product directory not specified; set $ANDROID_PRODUCT_OUT

D:\0\AdbStation>adb shell start

start: must be root

D:\0\AdbStation>adb shell

Armor_X5_Q:/ $ sudo

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

127|Armor_X5_Q:/ $ su

1|Armor_X5_Q:/ $ sudo

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

127|Armor_X5_Q:/ $ su

1|Armor_X5_Q:/ $ su

1|Armor_X5_Q:/ $ su

1|Armor_X5_Q:/ $ so su is working

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

127|Armor_X5_Q:/ $ my fone tells lies lol...

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

127|Armor_X5_Q:/ $ mkdir test

mkdir: 'test': Read-only file system

1|Armor_X5_Q:/ $ sudo su

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

127|Armor_X5_Q:/ $ su sudo

1|Armor_X5_Q:/ $ ls -l dirname

ls: dirname: No such file or directory

1|Armor_X5_Q:/ $ ls -l

ls: ./init.zygote64_32.rc: Permission denied

ls: ./init.rc: Permission denied

ls: ./init.usb.rc: Permission denied

ls: ./ueventd.rc: Permission denied

ls: ./init.zygote32.rc: Permission denied

ls: ./init: Permission denied

ls: ./init.environ.rc: Permission denied

ls: ./init.usb.configfs.rc: Permission denied

ls: ./metadata: Permission denied

total 60

dr-xr-xr-x 78 root root 0 2021-09-27 16:45 acct

drwxr-xr-x 16 root root 320 2021-09-27 16:45 apex

lrw-r--r-- 1 root root 11 2009-01-01 00:00 bin -> /system/bin

lrw-r--r-- 1 root root 50 2009-01-01 00:00 bugreports -> /data/user_de/

0/com.android.shell/files/bugreports

drwxrwx--- 6 system cache 4096 2021-09-27 16:45 cache

lrw-r--r-- 1 root root 19 2009-01-01 00:00 charger -> /system/bin/charg

er

drwxr-xr-x 4 root root 0 1970-01-01 01:00 config

lrw-r--r-- 1 root root 17 2009-01-01 00:00 d -> /sys/kernel/debug

drwxrwx--x 55 system system 4096 2021-09-27 16:45 data

drwxr-xr-x 2 root root 4096 2009-01-01 00:00 debug_ramdisk

lrw------- 1 root root 23 2009-01-01 00:00 default.prop -> system/etc/p

rop.default

drwxr-xr-x 21 root root 4860 2021-09-27 16:45 dev

lrw-r--r-- 1 root root 11 2009-01-01 00:00 etc -> /system/etc

drwx------ 2 root root 16384 2009-01-01 00:00 lost+found

drwxr-xr-x 13 root system 280 2021-09-27 16:45 mnt

drwxr-xr-x 2 root root 4096 2009-01-01 00:00 odm

drwxr-xr-x 2 root root 4096 2009-01-01 00:00 oem

dr-xr-xr-x 551 root root 0 1970-01-01 01:00 proc

drwxr-xr-x 12 root root 4096 2009-01-01 00:00 product

lrw-r--r-- 1 root root 24 2009-01-01 00:00 product_services -> /system/

product_services

drwxr-x--- 2 root shell 4096 2009-01-01 00:00 sbin

lrw-r--r-- 1 root root 21 2009-01-01 00:00 sdcard -> /storage/self/prim

ary

drwxr-xr-x 5 root root 120 2021-09-27 16:45 storage

dr-xr-xr-x 14 root root 0 2021-09-27 16:45 sys

drwxr-xr-x 16 root root 4096 2009-01-01 00:00 system

drwxr-xr-x 14 root shell 4096 2009-01-01 00:00 vendor

1|Armor_X5_Q:/ $ which su

/system/xbin/su

Armor_X5_Q:/ $

Armor_X5_Q:/ $

Armor_X5_Q:/ $

Armor_X5_Q:/ $ TralaLALALA

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

127|Armor_X5_Q:/ $

127|Armor_X5_Q:/ $

127|Armor_X5_Q:/ $ which su

/system/xbin/su

Armor_X5_Q:/ $

do that again:

127|Armor_X5_Q:/ $ which su

/system/xbin/su <-No root!! working!!"!"!

Well, I guess I did it. I got the root I needed for my fone, and shared it with all. {Mod edit} a lil study of my adb will show 1 thing:

I name my files simply...

MyBoot.img = My magisk'd.

vblankmeta.bin = My blank vbmeta

MyTwrp.bin = lopestoms twrp he ported for me, respect...

stock images are simple. boot is boot, recovery is recovery, super is super, boot-debug.img is stock version of debug bootloader flashed over stock boot.img and your vbmeta needs to me REAL. I dont keep logs, I post my adb thats it... I test until I get what I want, then THEY patch it... be warned... it's patched quicker than you think...

After flashing the super_fixed backup, which clearly matched legit vbmeta that made it, I had rw access in twrp, still working on the actual system mounting, and even though su is installed to xbin,and bin, no crash, prob cause it's the arm64 version. but then I aint run it correctly with other apps yet, so on with that 2nite... I cant use the actual busybox apps or supersu yet to properly grant permissions, but then, I can do that in adb shell... su lol...

Or load up the boot-debug to grant the permissions...

{Mod: Edited disrespect out - Regards Oswald Boelcke}