-
Notifications
You must be signed in to change notification settings - Fork 271
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
Can't use root mode in versions 3.x.x #948
Comments
It is failing because the internal storage in your device is set to read-only for App Manager which shouldn't happen. Check if any of the other software is messing with App Manager, examples include Xposed or similar frameworks and Storage Redirect. Also check if the path |
Muntashir thanks for answering. After installation '/storage/emulated/0/Android/data/io.github.muntashirakon.AppManager.debug' is present on storage, containing empty FIles subdirectory. Thanks in advance. |
Not sure. You could do onething: Run AM Debug in no-root mode, grant file permissions. Then open the app details page of AM Debug, navigate to Activities tab, find FmActivity and open it to see if it can display anything. |
I have the same issue. I'm also using a Xiaomi device (Mi 11 Ultra). As path, I'm having the same as @Zafrkant when opening FmActivity. |
By the way, in case it matters, when opening FmActivity, I don't have permissions to view /android/data - probably that's causing the problem? |
I've updated to Android 13 and MIUI 14 today - still the same issue. Any update on this @MuntashirAkon ? |
I've upgraded Xiaomi EU to v14.0.3.0, App Manager to v3.0.4 and it is working fine now. |
Hope it keeps working for you. Still doesn't work for me on MIUI 14 and Android 13. I will install the latest weekly and see. |
Sorry, no updates. If you're willing to help, I will publish some debug builds to figure out the issue first. |
Sure, would appreciate to help figuring this out. |
Here's the log file/export - in case it helps you. Installed the latest build today. |
Can you build a debug build @MuntashirAkon ? Been waiting long 😄 |
Try 35d8c3b |
I don't understand what to check. There is nothing to download from the link provided |
Same. I never compiled into an apk file. If you can make a beta/test build, would be awesome @MuntashirAkon. Thanks! |
Downloaded the Debug Build from your telegram. It crashes on start and cannot run. Here's the error log I could get: Thanks! |
Try#2: 77b1f5d |
Same. Re-installed. It tells me the key, then ask for root and after I give permission it crashes / closes the app. |
This is very weird. The shared storage clearly exists as per your previous comments, but App Manager is unable to use them somehow. In a Terminal, run the following with root:
|
@unRekable: Screenshot was not uploaded properly. |
Hi! I have the same problem after updating to Android 14 (crDroid). Upgrade procedure included formatting data from recovery (OFox Recovery 12.1_FBEv2) and flashing "legacy to retrofit dynamic" ZIP which changes the partition table with a script (OTA for A/B devices without dynamic partitions). May be related somehow. Ping me if you need more logs or other info.
|
I hope this log helps you |
I meant from logcat, not the crashlog. |
I hope that helps you out. I used adb logcat | findstr "AppManager" |
Logcat cannot filter using package name, you can only filter by UID. |
What's the command I should use then? And how do I get the IUD? Otherwise it's too much log |
My device: Xiaomi Mi 9T Pro Here is my logs from LogFox (another LogCat reader) |
https://pastebin.com/GvmFFRm1 that are my logs from logfox. |
This is where it's failing: https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/app/ContextImpl.java;l=802;drc=2f1bbc2bb14dba88a0f033fb4ce32bbf20df25ed Here are my remarks:
Regardless of 3, this does look like a permission issue, and I hardly think there's anything I can do regarding this in the app as the problem is in the OS-level (probably caused by broken encryption/SELinux/root). So, I think the only alternative is the hack that I previously talked about and/or factory resetting the device. |
Can't you manually create the folder from cli and set the right permissions or fix the encryption? A factory reset really sucks, meh 😅 |
Btw. I were able to run it with root mode, doing: mkdir -p /storage/emulated/0/Android/data/io.github.muntashirakon.AppManager/cache Let's see if everything works! |
Let me know how it goes. In addition, you could try the following after emptying the directory: chmod 771 /storage/emulated/0/Android/data/io.github.muntashirakon.AppManager
chown $UID:1015 /storage/emulated/0/Android/data/io.github.muntashirakon.AppManager
restorecon /storage/emulated/0/Android/data/io.github.muntashirakon.AppManager Replace |
I really wonder - why isn't the |
The use of external cache directory is mandatory for privileged users. |
I'll try to add a workaround for it since the affected users seem to have a wide range of issues (e.g., encryption issue, kernel issue, bad ROM issue, and so on). This, I believe, has something to do with SELinux context because only this can explain all the problems as the issue occurs only after App Manager is granted root. The workaround, it appears, is simply creating the cache directory. |
Could anybody facing the issue post a crash log from 82de588? Thanks in advance. |
Any updates? |
I also have this issue Where would I find logs? |
Crash reports are accessible through the notifications if you have them enabled. |
Nightlies work perfectly for my legacy-to-retrofit configuration above after your fixes. |
You can also test with the latest debug builds. |
Please check before submitting an issue
Describe the bug
I'm using Xiaomi Mi 11i, Xiaomi EU 13.0.13.0, App Manager Debug 2130.
I've tried multiple 3.x.x versions but results are the same, I can't use root mode. On v2.6.5.1 everything is working fine.
Full system log will be provided.
To Reproduce
Expected behavior
No root access will be provided.
Screenshots
No response
Logs
Log is provided via Mega due to it's large size, GitHub: There was an error creating your Issue: body is too long, body is too long (maximum is 65536 characters).
https://mega.nz/file/e5clkSSB#hvEJ_JSzxOQnmcPzXHC5uKnEfK8VOe4n3bifOGxyZL4
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: