adb shell sh /storage/emulated/0/Android/data/moe.Shizuku.privileged.api/start.sh
Please report bugs of Shizuku itself.
Requirements:
- [ ] Shizuku version is up-to-date
- [ ] Shizuku is downloaded from official channels (GitHub release or Google Play)
- [ ] Shizuku is not running in a virtual environment or broken ROM (GrapheneOS)
- [ ] (Root users) No Xposed installed / Xposed is not enabled for Shizuku
Change "[ ]" to "[x]" if it meets the requirements.
Reports not meet the requirements will be immediately closed.
Information:
- Shizuku version:
- Mode: [adb, root]
- Android version:
- Device: (optional)
Logs:
Related full logcat.
Describe the bug:
A clear and concise description of what the bug is.
Additional context:
Add any other context about the problem here.
Can you remove this? It's empty and clogs up the issues page...
This command is not working, my terminal giving me the message that there is no such file or directory exist. And I'm also not able to find the app folder after installing it manually from GitHub or Play Store, as mentioned in the command, there should be a folder available as moe.shizuku... something like that in either my sdcard storage or phone storage, but couldn't find the folder in either of them. Solve this issue please.
ADB Shell
[SOLVED] Hello all,
I just ran into this as well. Using a non-rooted Samsung Galaxy Tab S8 with Android 15 and the latest version (at this time) of Shizuku from F-Droid/Izzyandroid repo.
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
R52TC000YNK device
adrian_vg@lanfear2:~/Downloads$ ll moe.shizuku.privileged.api_1049.apk
-rw-rw-r-- 1 adrian_vg adrian_vg 3442426 feb 1 10:42 moe.shizuku.privileged.api_1049.apk
adrian_vg@lanfear2:~/Downloads$
adrian_vg@lanfear2:~/Downloads$ adb install ./moe.shizuku.privileged.api_1049.apk
Performing Streamed Install
Success
adrian_vg@lanfear2:~/Downloads$ adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh: No such file or directory
adrian_vg@lanfear2:~/Downloads$
Nothing in the /sdcard/Android/data/moe.shizuku.privileged.api folder:
Any ideas about this? Thanks.
[SOLVED] Hello all,
I just ran into this as well. Using a non-rooted Samsung Galaxy Tab S8 with Android 15 and the latest version (at this time) of Shizuku from F-Droid/Izzyandroid repo.
$ adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached R52TC000YNK device adrian_vg@lanfear2:~/Downloads$ ll moe.shizuku.privileged.api_1049.apk -rw-rw-r-- 1 adrian_vg adrian_vg 3442426 feb 1 10:42 moe.shizuku.privileged.api_1049.apk adrian_vg@lanfear2:~/Downloads$ adrian_vg@lanfear2:~/Downloads$ adb install ./moe.shizuku.privileged.api_1049.apk Performing Streamed Install Success adrian_vg@lanfear2:~/Downloads$ adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh: No such file or directory adrian_vg@lanfear2:~/Downloads$Nothing in the /sdcard/Android/data/moe.shizuku.privileged.api folder:
Any ideas about this? Thanks.
Hello again! Nevermind about my issue. I managed to get Canta working with Shizuku after some twiddling about. Samsung app bloat is now mostly removed! :-D
termux-change-repo
Por favor informe errores de Shizuku en sí.
Requisitos:
- [ ] La versión de Shizuku está actualizada[ ] Shizuku se descarga desde los canales oficiales (lanzamiento de GitHub o Google Play)[ ] Shizuku no se ejecuta en un entorno virtual o una ROM rota (GrapheneOS)[ ] (Usuarios root) No hay Xposed instalado / Xposed no está habilitado para Shizuku
Cambie "[ ]" por "[x]" si cumple con los requisitos.
Los informes que no cumplan con los requisitos serán cerrados inmediatamente .
Información:
- Versión de Shizuku:
- Modo: [adb, root]
- Versión de Android:
- Dispositivo: (opcional)
Registros:
Logcat completo relacionado .
Describe el error:
Una descripción clara y concisa de cuál es el error.
Contexto adicional:
Agregue cualquier otro contexto sobre el problema aquí.
https://github.com/RikkaApps/Shizuku/issues/547
Please report bugs of Shizuku itself.
Requirements:
- [ ] Shizuku version is up-to-date[ ] Shizuku is downloaded from official channels (GitHub release or Google Play)[ ] Shizuku is not running in a virtual environment or broken ROM (GrapheneOS)[ ] (Root users) No Xposed installed / Xposed is not enabled for Shizuku
Change "[ ]" to "[x]" if it meets the requirements.
Reports not meet the requirements will be immediately closed.
Information:
- Shizuku version:
- Mode: [adb, root]
- Android version:
- Device: (optional)
Logs:
Related full logcat.
Describe the bug:
A clear and concise description of what the bug is.
Additional context:
Add any other context about the problem here.
https://github.com/RikkaApps/Shizuku/issues/547#issue-2394231883
.
Give link plz
adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh
$ adb devices
- daemon not running; starting now at tcp:5037
- daemon started successfully List of devices attached R52TC000YNK device
adrian_vg@lanfear2:~/Downloads$ ll moe.shizuku.privileged.api_1049.apk -rw-rw-r-- 1 adrian_vg adrian_vg 3442426 feb 1 10:42 moe.shizuku.privileged.api_1049.apk adrian_vg@lanfear2:~/Downloads$
adrian_vg@lanfear2:~/Downloads$ adb install ./moe.shizuku.privileged.api_1049.apk Performing Streamed Install Success
adrian_vg@lanfear2:~/Downloads$ adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh: No such file or directory
adrian_vg@lanfear2:~/Downloads$
adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh
Vào 21:05, Th 4, 5 thg 11, 2025 freefire680088e-ops < @.***> đã viết:
freefire680088e-ops left a comment (RikkaApps/Shizuku#547) https://github.com/RikkaApps/Shizuku/issues/547#issuecomment-3491396481
adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh
— Reply to this email directly, view it on GitHub https://github.com/RikkaApps/Shizuku/issues/547#issuecomment-3491396481, or unsubscribe https://github.com/notifications/unsubscribe-auth/BVAX4QIPXU3EXI7DV567KB333H72DAVCNFSM6AAAAABKPWC5EGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJRGM4TMNBYGE . You are receiving this because you commented.Message ID: @.***>
@adrianvg
[SOLVED] Hello all, Hello again! Nevermind about my issue. I managed to get Canta working with Shizuku after some twiddling about. Samsung app bloat is now mostly removed! :-D
HOW did you fix it, this would help others.
Daspaly over oders app
[SOLVED]
@tripplehelix Had same issue on Honor MagicOS 9.0.0.182 on a V3. Used a complete other path and target file as following:
Check your Shizuku APP: -> at Android device start Shizuku -> Start by connecting to a computer -> View command => this is your current path and target file! Copy it and -> adb shell [copied_new-path-to/target-file] in a terminal
result: info: starter begin info: killing old process... info: apk path is [copied_new-path-to]/xxxxxxxx.apk info: starting server... info: shizuku_server pid is nnnnnn info: shizuku_starter exit with 0
Hope this is your goal, too!