Hi
I am trying to enable some apps that I previously disabled using Alliance Shield X, which stopped working today.
I am able to authorize my device on ADB but whenever I try to enable a package, I get the following message:
/adb shell pm enable radiotime.player
Package radiotime.player new state: disabled
So, even though I tried to enable the app, the new state still says disabled.
Any idea what I am doing wrong?
My phone is neither rooted nor is my bootloader unlocked. Using Android 11.
Related
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Cheetohz said:
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Click to expand...
Click to collapse
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
PaisanNYC said:
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
Click to expand...
Click to collapse
I actually did nto check device manager. but I had the safely eject Nexus 6 show up in my task bar, so it was recognizing it as a nexus.
Hi, I accidentally locked myself out of my phone with android device manager, and forgot the password. I know I can change the password from https://www.google.com/android/devicemanager , but I had disabled wifi on my phone, so android device manager can't connect to it. I used adb with "adb -s TA2490FPAF shell "svc wifi enable", but I'm still not seeing the wifi icon at the top of my screen, and ADM still can't connect. I rebooted the phone many times to no avail. Can anyone assist?
Commands like "adb reboot" and :adb reboot recovery" work just fine, so why won't enabling wifi or data work?
Hello, looking for a bit of help with a problem. I broke the screen on my Nexus 6 a few days ago, and I'm trying to get access to the phone again. The screen is completely black, no image whatsoever, but the phone is still working fine (apparently, even the digitizer--the phone started ringing, so on a whim I swiped to answer the call and it worked fine). It was completely stock without root and with USB debugging disabled (I'm kicking myself for that, it was turned on until a week or so ago). It is locked with a PIN. I managed to use Wug's Nexus Root Toolkit to boot into TWRP, then used ADB to back up all the files on the device. Unfortunately, I'm waiting on a Nexus 5x to be delivered and won't get it for another few days, so I'm looking to access the text messages on the device. I've been trying to use this tool to access my phone from my computer, but the problem is that USB debugging is disabled. I tried following these instructions to enable USB debugging from recovery using ADB, but it doesn't seem to be working. First I received errors saying that the files were read-only when attempting to write to build.prop, but using this StackOverflow question and answer I remounted it and the commands seemed to work. However, after rebooting the phone it doesn't show up in ADB Devices. It does appear to have rebooted fully--I'm hearing notifications periodically again--but I'm guessing the method to enable USB debugging failed. Does anybody have any other suggestions for how I can get USB debugging enabled?
I just used adb pull to get the build.prop and default.prop, it looks like the build.prop had the changes I made in there, but the default.prop didn't. I made the changes manually and pushed my edited default.prop over, but it's still not showing in adb.
I just got an X2 Pro, my first Realme phone - coming from OnePlus. Besides the pretty horrible OLED lottery, I'm pretty satisfied so far.
Unfortunately, Realme seem to void their users warranty when rooting (but not for unlocking the bootloader or even loading custom ROMs) - so I'm working my way to a usable phone via ADB.
The biggest issue of modern Android - for me atleast - are the intrusive heads-up notifications.
To disable them, I usually use the "adb shell settings put global heads_up_notifications_enabled 0" command. On all other phones - even a Samsung S10 - this worked perfectly fine.
However, on my X2 Pro, I just get "Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS".
My bootloader is already unlocked, and I of course enabled ADB debugging over USB in the developer options. What am I missing? "adb root" didn't help either.
FIXED IT
"Disable permission monitoring", the last option in the developer options, must be enabled for ADB shell commands to work properly.
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
vulcanrvn said:
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
Click to expand...
Click to collapse
Go Here and download the Fastboot drivers. follow the directions on the razor dev portal. I had the same issue and this fixed it for me. https://developer.razer.com/razer-p...94.1708481542.1586624574-305520188.1586475530
If your adb-server is not started with root/admin rights, your phone will never prompt you for authorization unless you choose a different USB Mode (MTP, PTP, etc.) than Charge Only. I suspect this is done to prevent certain malicious actions being performed without the user being aware.
If you start your adb-server with root/admin rights (by typing "sudo adb start-server", make sure you've killed your existing daemons before doing so), you can use ADB while in Charge Only mode, provided you've subsequently authorized the PC to do so. However, unlike normal adb server, the fingerprint may occasionally change and you may need to redo the authorization again.