Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot write files #927

Open
4 tasks done
CMSZ001 opened this issue Jan 22, 2025 · 1 comment
Open
4 tasks done

Cannot write files #927

CMSZ001 opened this issue Jan 22, 2025 · 1 comment

Comments

@CMSZ001
Copy link

CMSZ001 commented Jan 22, 2025

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:13.5.4.r1049.0e53409
  • Mode: adb
  • Android version:13
  • Device: (optional)OPPO

Logs:

Related full logcat.

**Describe the bug:**Cannot write file after re-entering shizuku

A clear and concise description of what the bug is.

Additional context:

java.io.FileNotFoundException: /storage/emulated/0/Android/data/moe.shizuku.privileged.api/starter: open failed: EACCES (Permission denied)
	at libcore.io.IoBridge.open(IoBridge.java:574)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:236)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:186)
	at rikka.shizuku.nk0.a(SourceFile:34)
	at rikka.shizuku.nk0.h(SourceFile:88)
	at rikka.shizuku.ks$f.l(SourceFile:35)
	at rikka.shizuku.t9.n(SourceFile:12)
	at rikka.shizuku.kk.run(SourceFile:119)
	at rikka.shizuku.hz.run(SourceFile:13)
	at rikka.shizuku.om0.run(SourceFile:3)
	at rikka.shizuku.kg.l(SourceFile:1)
	at rikka.shizuku.kg$c.d(SourceFile:15)
	at rikka.shizuku.kg$c.n(SourceFile:29)
	at rikka.shizuku.kg$c.run(Unknown Source:0)
Caused by: android.system.ErrnoException: open failed: EACCES (Permission denied)
	at libcore.io.Linux.open(Native Method)
	at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
	at libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
	at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
	at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8249)
	at libcore.io.IoBridge.open(IoBridge.java:560)
	... 13 more

Add any other context about the problem here.

@dilworks
Copy link

I'm experiencing (almost!) the very same error, but my device is a Android 12 tablet, BLU M10L Plus.

Apparently some applications fail to create its own data directory under /storage/emulated/0/Android/data on this tablet for no reason at all, causing weird crashes or failures like this one, and yes, this means Shizuku is unusable on this device. But unlike the OP, I get a ENOENT because the directory doesn't exist:

java.io.FileNotFoundException: /storage/emulated/0/Android/data/moe.shizuku.privileged.api/starter: open failed: ENOENT (No such file or directory)
	at libcore.io.IoBridge.open(IoBridge.java:575)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:236)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:186)
	at rikka.shizuku.nk0.a(SourceFile:34)
	at rikka.shizuku.nk0.h(SourceFile:88)
	at rikka.shizuku.ks$f.l(SourceFile:35)
	at rikka.shizuku.t9.n(SourceFile:12)
	at rikka.shizuku.kk.run(SourceFile:119)
	at rikka.shizuku.hz.run(SourceFile:13)
	at rikka.shizuku.om0.run(SourceFile:3)
	at rikka.shizuku.kg.l(SourceFile:1)
	at rikka.shizuku.kg$c.d(SourceFile:15)
	at rikka.shizuku.kg$c.n(SourceFile:29)
	at rikka.shizuku.kg$c.run(Unknown Source:0)
Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
	at libcore.io.Linux.open(Native Method)
	at libcore.io.ForwardingOs.open(ForwardingOs.java:567)
	at libcore.io.BlockGuardOs.open(BlockGuardOs.java:273)
	at libcore.io.ForwardingOs.open(ForwardingOs.java:567)
	at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:7825)
	at libcore.io.IoBridge.open(IoBridge.java:561)
	... 13 more

FWIW, I'm using also a 128GB MicroSD card as application storage, but moving apps between SD and internal storage make no difference. Manually creating the moe.shizuku.privileged.api folder using the internal Files app turns the error into a EACCESS, as expected (since the directory is not owned by the app). I don't have a clue on what could be failing on this tablet, since some apps CAN create their own data subdirectories! Short of trying a factory reset or getting rid of the SD card for app storage (which I do not want to do as this tablet only has 32GB of internal flash), I'm running out of ideas here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants