-
Notifications
You must be signed in to change notification settings - Fork 119
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
BCR KSU #650
Comments
Make sure BCR is given root access in KernelSU (even though it doesn't actually need it). If you have any root hiding modules, please try temporarily disabling them. |
I'm on Xiaomi 12 Pro with Android 14 stock global MIUI HyperOS ROM, GKI_KernelSU_SUSFS Kernel, KernelSU Next manager, SuSFS for KernelSU v1.5.4, Zygisk Next, Play Integrity Fix v18.5 and Tricky Store v1.2.0. |
Please grab a logcat with |
Here it is. |
Thanks for the logs. The issue is this:
BCR is blocked from accessing some private Android APIs. BCR's module normally grants access to these APIs by installing a I'm guessing there's something in KernelSU itself or another module that's causing this file to be hidden from Android system components. Unfortunately, I have no idea what settings you could try changing to fix this. |
Can be useful if I grab the logcat with module installed (BCR crash anyway) and then the logcat with the module+manual apk installed? |
Sure, I can take a look to see if the error is any different. |
I tried flashing module and, after giving it all permissions and root privileges, now it works but, as you can see from the attached images (BCR icon and the name of app in the App permission page), there are some strange behaviors, also after rebooting again. PS: In the meanwhile I upgraded to SuSFS for KernelSU v1.5.5, but I'm not sure if it's really correlated. Here is the new logcat file, after I opened BCR, although it no longer crashes (for now): |
Thanks for the new logs! Yeah, Android definitely picking up the config file properly now:
That would explain why it no longer crashes. As for the icon, you'll probably need to extract BCR's APK and install it to work around the problem. This happens because something is still blocking parts of Android from accessing the module's APK in |
I was having a similar issue after migrating from Magisk to KSU Next + SusFS. I would open BCR and it would immediately crash with this error:
I don't know if my issue and this are related, but I was able to fix BCR by clearing it's app data and permissions and then making sure BCR was getting root permissions in KSU and not unmounting.
I was having the same issue where the package name would show as the app name and icon would be default. |
Yep, that crash is a similar issue, except Android was having trouble loading the list of supported languages from BCR's APK instead of the icon. The "not unmounting" part is likely what fixed it. |
On an unrelated but maybe actually related note, I updated my kernel from KSU next 12335 to 12437 and now BCR crashes whenever I open it.
When the crash first happened, I saw an alert saying there was an issue and I should clear the app data before using it again. However clearly app data did not fix the issue... |
Something is probably unmounting BCR's files again. That crash occurs if |
I had similar problem were BCR is not detected after some research I think similar issue was present with systemless hosts modules, and they solved by adding something like this to the services.sh of the module, to kind off force mount the module files mount --bind "${0%/*}/hosts" /system/etc/hosts i believe by doing so for every file of BCR module that needs to be injected into the system it could solve the above issues without disabling the Umount Modules for all modules which can affect root hiding maybe but I need yet to test Edit: tried adding those lines to services.sh mount --bind "${0%/*}/system/etc/permissions/privapp-permissions-com.chiller3.bcr.xml" /system/etc/permissions/privapp-permissions-com.chiller3.bcr.xml mount --bind "${0%/*}/system/etc/sysconfig/config-com.chiller3.bcr.xml" /system/etc/sysconfig/config-com.chiller3.bcr.xml mount --bind "${0%/*}/system/addon.d/51-com.chiller3.bcr.sh" /system/addon.d/51-com.chiller3.bcr.sh didn't work so...bad luck |
after installing bcr via ksu the application does not appear
The text was updated successfully, but these errors were encountered: