I am on A13 on a pixie 7 pro running the November update and the kirisakura kernel. I’m rooted with magisk v24.2 with lsposed latest version using aosp mods and xprivacy lua. I had bbs v.24 and it wasn’t working. I updated to the latest version on play store. The app had already been granted root with the old version. The new version didn’t request root permission. BBS did flag me with the message that it needed more permissions. I entered:
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.PACKAGE_USAGE_STATS (needed starting on Lolipop)
adb -d shell settings put global hidden_api_policy_pre_p_apps 0
adb -d shell settings put global hidden_api_policy_p_apps 1
adb -d shell settings put global hidden_api_policy 1
Notice I modified the global hidden api policy to a 0 above because I thought this was some global setting.
At first the device would boot but return right to the Lock Screen upon entering my PIN. After entering safe mode I can get in the phone but after a few seconds or minutes of booting up the UI freezes up and I have to get reboot. I imagine when something starts up now I’m getting the issue.
Any idea of how I fix this up? Any ideas or guidance is appreciated.
The lock screen thing happened with aosp mods. But an update fixed it.
the phone will run in safe mode. i can get in long enough to uninstall magisk- and i did- but it still freezes after 30 seconds or so and then reboots after being frozen for another 30 seconds. i am running and adb logcat but have no idea what to look for
Related
I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.
Any help for enable more stats
realme 5 pro android 10 without root
im try
adb shell pm grant com.gsamlabs.bbm.pro android.permission.BATTERY_STATS
adb shell settings put global hidden_api_policy 1
adb shell settings get global hidden_api_policy 0
adb shell settings get global hidden_api_policy
nothing changed
+1
~Fix nightlight in MIUI~
For what is it?
Sometimes it happens that the Google setup activates the "classic" Nightlight mode from AOSP.
This one doesn't work like MIUI handles this feature.
This means that deactivation via the settings is not possible and your display will get every day to same time yellowish.
Will I have to do this after every new installation?
No, when you use the backup function from Google it will sync this settings and bug is fixed until you restore a old google backup or one from a other phone.
Post 2:
Rootless guide via PC (Mac/Windows/Linux/Other Phone with adb binary)
Post 3:
Root guide via termux (or any other terminal emulator)
•rootless•
For PC: *
Open either powershell or cmd or terminal, this depends on your installed system and run one after the other the following commands:
adb shell settings put secure night_display_activated 0
adb shell settings put secure night_display_auto_mode 0
\_That's all!_/
This star is talking to you
↓
*
You have to install adb binarys for your system before you can run this command.
Installation guide: https://wiki.lineageos.org/adb_fastboot_guide.html#installing-adb-and-fastboot
•rooted•
For termux**:
Open termux and run one after the other the following commands:
su
env -i USER=shell "$(PATH=/system/xbin:/system/bin:/su/bin:/sbin:/magisk/.core/bin which su)" shell --context u:r:shell:s0 --shell /system/bin/sh --command settings put secure night_display_activated 0
env -i USER=shell "$(PATH=/system/xbin:/system/bin:/su/bin:/sbin:/magisk/.core/bin which su)" shell --context u:r:shell:s0 --shell /system/bin/sh --command settings put secure night_display_auto_mode 0
\_That's all!_/
This stars are talking to you
↓
**
You need a magisk rooted device and termux
Download: https://play.google.com/store/apps/details?id=com.termux
Everyting was working fine using the SHELL Command in order to remove bloatware from my device to remove any application using ANDROID 12 ONEUI 4.1.1
After updating to ONEUI 5 ANDROID 13 on December 6 2022, now im not able to get the ADB SHELL Command working it gives me and error.
Can someone let me know if there is a fix for this? like i said everything was working before upgrading to ONEUI 5 ANDROID 13
MacBook-Air platform-tools % ./adb shell
b4q:/ $ pm list packages
Exception occurred while executing 'list':
java.lang.SecurityException: Shell does not have permission to access user 150
com.android.server.am.ActivityManagerService.handleIncomingUser:14870 android.app.ActivityManager.handleIncomingUser:4802 com.android.server.pm.PackageManagerShellCommand.translateUserId:3499
at com.android.server.am.UserController.handleIncomingUser(UserController.java:2672)
at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:14870)
at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:4802)
at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellCommand.java:3499)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellCommand.java:965)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellCommand.java:861)
at com.android.server.pm.PackageManagerShellCommand.runList(PackageManagerShellCommand.java:720)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:222)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6922)
at android.os.Binder.shellCommand(Binder.java:1085)
at android.os.Binder.onTransact(Binder.java:903)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4909)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6906)
at android.os.Binder.execTransactInternal(Binder.java:1321)
at android.os.Binder.execTransact(Binder.java:1280)
Look here:
Getting "java.lang.SecurityException: Shell does not have permission to access user 150" when uninstalling apps from Samsung Secure folder using ADB
I am using Samsung Galaxy A50, Android 11, One UI 3.1. I use Samsung Secure folder. There are many bloatware in it and I could not find a way to uninstall (and disable) them via ADB. Owner profile ...
android.stackexchange.com
xXx yYy said:
Look here:
Getting "java.lang.SecurityException: Shell does not have permission to access user 150" when uninstalling apps from Samsung Secure folder using ADB
I am using Samsung Galaxy A50, Android 11, One UI 3.1. I use Samsung Secure folder. There are many bloatware in it and I could not find a way to uninstall (and disable) them via ADB. Owner profile ...
android.stackexchange.com
Click to expand...
Click to collapse
Well actually im not trying to delete applications from Secure Folder, im removing only bloatware from the device that are outside, like i mentioned this was working perfect on ONEUI 4.1.1 ANDROID 12 but as soon i upgrade it broke things up, im just trying to remove Chrome, Gmail, Facebook apps that come wth the device, hopefully some dev can see this post and look into the issue and fix it if possible, or else i may have to downgrade back to ONEUI 4.1.1 to get things working again.
jonatansuarez said:
Everyting was working fine using the SHELL Command in order to remove bloatware from my device to remove any application using ANDROID 12 ONEUI 4.1.1
After updating to ONEUI 5 ANDROID 13 on December 6 2022, now im not able to get the ADB SHELL Command working it gives me and error.
Can someone let me know if there is a fix for this? like i said everything was working before upgrading to ONEUI 5 ANDROID 13
MacBook-Air platform-tools % ./adb shell
b4q:/ $ pm list packages
Exception occurred while executing 'list':
java.lang.SecurityException: Shell does not have permission to access user 150
com.android.server.am.ActivityManagerService.handleIncomingUser:14870 android.app.ActivityManager.handleIncomingUser:4802 com.android.server.pm.PackageManagerShellCommand.translateUserId:3499
at com.android.server.am.UserController.handleIncomingUser(UserController.java:2672)
at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:14870)
at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:4802)
at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellCommand.java:3499)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellCommand.java:965)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellCommand.java:861)
at com.android.server.pm.PackageManagerShellCommand.runList(PackageManagerShellCommand.java:720)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:222)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6922)
at android.os.Binder.shellCommand(Binder.java:1085)
at android.os.Binder.onTransact(Binder.java:903)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4909)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6906)
at android.os.Binder.execTransactInternal(Binder.java:1321)
at android.os.Binder.execTransact(Binder.java:1280)
Click to expand...
Click to collapse
Hi, I'm also having the same issue on my Galaxy ZFold3 when trying to show installed packages in adb shell. See my error output below. I'm looking to understand why adb shell would no longer have permission to list packages not installed inside the Secure Folder. Not seeking to uninstall the Secure Folder ideally.
: adb shell
q2q:/ $ pm list packages
Exception occurred while executing 'list':
java.lang.SecurityException: Shell does not have permission to access user 150
com.android.server.am.ActivityManagerService.handleIncomingUser:14870 android.app.ActivityManager.ha
ndleIncomingUser:4802 com.android.server.pm.PackageManagerShellCommand.translateUserId:3499
at com.android.server.am.UserController.handleIncomingUser(UserController.java:2672)
at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.jav
a:14870)
at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:4802)
at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellComman
d.java:3499)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellComman
d.java:965)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellComman
d.java:861)
at com.android.server.pm.PackageManagerShellCommand.runList(PackageManagerShellCommand.java:7
20)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java
:222)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageMana
gerService.java:6922)
at android.os.Binder.shellCommand(Binder.java:1085)
at android.os.Binder.onTransact(Binder.java:903)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4909)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerS
ervice.java:6906)
at android.os.Binder.execTransactInternal(Binder.java:1321)
at android.os.Binder.execTransact(Binder.java:1280)
255|q2q:/ $ exit
Hello. Please forgive my bad English. My Asus ZE500KL phone with Android 6, almost died. I have collected various things in it, phones, notes, passwords... and I had the stupidity of not having any backup. Sometimes it starts, but it throws up countless signs like "Unfortunately com.android.XXX Has Stopped". To do anything with the phone I have to be able to close them and I have very little time, it can be used and restarted in seconds. It behaves similarly in safe mode. Otherwise, it enters fastboot mode and adb, but I don't know how it got stuck there. Any ideas what I can do? A week ago I installed "SWAP no root", could it be from that?
Do a LOGCAT to get the very reason why you get this notification.
logcat is first thing you should do. you can redirect > into file and upload here
Code:
adb logcat '*:W' -b all > logcat.txt
try to uninstall some recent apps from adb maybe it stabilizes. the -k flag preserves app data
Code:
adb shell 'pm list packages -e'
adb shell 'pm uninstall --user 0 -k <pkgname>'
if you don't close any of that pop-up is phone rebooting anyway? if stable enough you can do backup and pull files (confirm blank no password)
Code:
adb pull -a /sdcard
adb backup -apk -shared -all
jwoegerbauer said:
Do a LOGCAT to get the very reason why you get this notification.
Click to expand...
Click to collapse
E:\platform-tools>adb devices
List of devices attached
G6AZCY00W177EUE recovery
E:\platform-tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
E:\platform-tools>adb logcat
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
- waiting for device -
* daemon still not running
error: cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: N
o connection could be made because the target machine actively refused it. (1006
1)
aIecxs said:
logcat is first thing you should do. you can redirect > into file and upload here
Code:
adb logcat '*:W' -b all > logcat.txt
try to uninstall some recent apps from adb maybe it stabilizes. the -k flag preserves app data
Code:
adb shell 'pm list packages -e'
adb shell 'pm uninstall --user 0 -k <pkgname>'
if you don't close any of that pop-up is phone rebooting anyway? if stable enough you can do backup and pull files (confirm blank no password)
Code:
adb pull -a /sdcard
adb backup -apk -shared -all
Click to expand...
Click to collapse
logcat.txt is empty
do this in android, not recovery
aIecxs said:
do this in android, not recovery
Click to expand...
Click to collapse
If I to load Android, the phone works for 20-30 seconds maximum and when I plug in the USB cable, it restarts immediately.
let usb plugged and adb logcat waiting while phone boots