search

ibilux / MobyDroid

Android Device Manager with a Graphic User Interface (GUI) – Manage Android on Linux, Windows and MacOS.
Apache License 2.0
127 stars 20 forks source link

App has no full root access (v0.4) #12

Open mr-gittes opened 3 years ago

mr-gittes commented 3 years ago

still v0.4 doesn't work on android 10 rooted with magisk and root permissions set in app: when accessing some root folders with the file manger (e.g. /efs) there are no files shown inside...!? it seems the app has adb without root. only adb (root) shell works...

ibilux commented 10 months ago

The phone must be rooted and you have to click the SuROOT icon to activate root for the selected device. SuROOT icon: SuROOT

mr-gittes commented 3 months ago

It is rooted and su root permissions in settings are set, but when i click on SUROOT nothing changes! I can browse into the root folders but no files inside these folders are shown: /efs is empty, /data is empty etc.

ibilux commented 3 months ago

It is rooted and su root permissions in settings are set, but when i click on SUROOT nothing changes! I can browse into the root folders but no files inside these folders are shown: /efs is empty, /data is empty etc.

Can you send me the logs of MobyDroid from %HOMEPATH%/.mobydroid/MobyDroid.log ?

mr-gittes commented 3 months ago

18/04/2024 12:12:52 - [INFO] - [Logger] : initialized. 18/04/2024 12:12:55 - [INFO] - [JadbLauncher] : Launched. 18/04/2024 12:12:57 - [SEVERE] - [GetDeviceProperties] : I: command failed: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.. 18/04/2024 12:12:57 - [SEVERE] - [CheckBinaries] : I: command failed: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.. 18/04/2024 12:13:14 - [SEVERE] - [SuRoot] : I: command failed: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.. 18/04/2024 12:13:50 - [SEVERE] - [EjectedDevices] : java.util.ConcurrentModificationException. 18/04/2024 12:13:55 - [SEVERE] - [GetDeviceProperties] : I: command failed: device still authorizing. 18/04/2024 12:13:55 - [SEVERE] - [CheckBinaries] : I: command failed: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.. 18/04/2024 12:13:57 - [SEVERE] - [EjectedDevices] : java.util.ConcurrentModificationException. 18/04/2024 12:14:00 - [SEVERE] - [GetDeviceProperties] : I: command failed: device offline. 18/04/2024 12:14:00 - [SEVERE] - [CheckBinaries] : I: command failed: device still authorizing. 18/04/2024 12:19:44 - [INFO] - [Logger] : initialized. 18/04/2024 12:19:44 - [INFO] - [JadbLauncher] : Launched. 18/04/2024 12:19:46 - [SEVERE] - [CheckBinaries] : java.io.FileNotFoundException: /home/user1/Desktop/bin/busybox-arm (No such file or directory). 18/04/2024 12:20:40 - [INFO] - [Logger] : initialized. 18/04/2024 12:20:41 - [INFO] - [JadbLauncher] : Launched. 18/04/2024 12:20:42 - [SEVERE] - [CheckBinaries] : java.io.FileNotFoundException: /home/user1/Desktop/bin/busybox-arm (No such file or directory). 18/04/2024 12:22:32 - [SEVERE] - [EjectedDevices] : java.util.ConcurrentModificationException. 18/04/2024 12:22:39 - [SEVERE] - [GetDeviceProperties] : I: command failed: device offline. 18/04/2024 12:22:39 - [SEVERE] - [CheckBinaries] : I: command failed: device still authorizing.

ibilux commented 3 months ago

@mr-gittes your adb server isn't running with the right privileges. Try this in terminal before running MobyDroid:

adb kill-server
sudo adb start-server

PS: did u install MobyDroid from package manager? If not, download the full zip that contains the arm binaries MobyDroid_v0.6.zip cause they are missing.