This issue relates to the fact that /system is absolutely read-only and the mount -o,rw is no longer allowed on recent versions of Android.
To modify anything in /system you need to use Magisk ability to replace files by creating a magisk module.
Enable developer options and USB debugging of your phone:
Open Settings, then select About.
Tap on Build number seven times.
Go back, and select Developer options.
Scroll down, and check the Android debugging or USB debugging entry under Debugging.
Plug your phone into your computer.
For debugging Android studio via WiFi install Wifi Adb Ultimate plugin
update : only solutions i found is to either try to use a microusb mouse or to wait till phone is dead, download fastboot plug phone into pc, boot into fastboot mode (on huawei long press down volume key) till you get a screen, then enter command fastboot devices , if you see a number then use fastboot reboot
android-svc makes this way easier.
android-svc --adb list-packages'
List all methods of a service:
android-svc --adb list-methods clipboard'
Get method signature of a service method:
android-svc --adb method-signature 'clipboard.setPrimaryClip'
Call a service method:
android-svc --adb call 'phone.dial("555-0199")'
You can also ...
The energy consumption by Android devices is estimated based on the amount of time certain hardware components are residing in different states (e.g., WIFI ON, WIFI OFF, etc.). For each hardware component, there is a power value for each state of the component provided by the manufacturer. So with the amount of time a hardware component resides in a certain ...
No difference. Ultimately both set sys.powerctl property to reboot,<reason> (1, 2). init then handles the property to proceed a proper shutdown or reboot (3). reason string optionally describes why the device was rebooted (see persist.sys.boot.reason property after reboot).
When executing adb shell reboot you make adb run shell: /system/bin/sh which ...
The only way to fix a bootloop is to remove the cause of the bootloop. Yes some phones reject the magisk patched image because recenctly i wanted to change a phone from system to systemless root. Phones which i think have no problem with magisk are Samsung phones.
Sincd you said you had downloaded a firmware, flash the original boot img that you patched with ...
On Android 11 sdcard path seem to have changed. The path /mnt/sdcard still exists but via adb you don't the permissions to access this path.
But there are alternatives. On the an emulator running Android 11 I can see for example path /sdcard. This path however is a soft link to /storage/self/primary which again is a soft-link to /storage/emulated/0.