I am having trouble running my application on a particular phone. It runs correctly on a different phone and on an emulator. I have the standard unauthorized issue coming up in my ADB logs:
PropertyFetcher: AdbCommandRejectedException getting properties for device [My Device's ID]: device unauthorized. Please check the confirmation dialog on your device.
When I try to run the application anyway on the phone in question, it is able to target the phone and runs the app, but immediately hits a null pointer (that isn't present when running on the other phone or the emulator).
Before you insta-lock this question, I've tried everything in all of the duplicate questions. Specifically
I have set the target to show chooser dialog
I have reset the ADB server
I have revoked and re-accepted permissions, and tried changing the USB type
I have confirmed that Enable ADB Integration is checked
None of which worked.
Furthermore, the same phone was working earlier (not sure what changed), so it's not a bad USB cord.
The phone is a new Nexus 6, and the old phone that works correctly is a Samsung Galaxy S4.
Running adb devices in the android studio terminal shows:
List of devices attached
[My Device's ID] device
Which implies (?) that it is in fact authorized.
You have missed the Fingerprint Certificate Authorization popup in your phone when you connected it. To solve disconnect and plug-in again.Wait for some seconds and a confirmation popup will appear. Click OK.
Related
I have been experiencing a problem.
I'm trying to authorize my rooted android device (Asus Zenfone GO) for ADB.
Developer options are on and USB debug, as well. Unfortunately, if I plug the phone and start the ADB server on my pc, instead of showing the authorization popup on the phone, the following message is shown "Unfortunately, System UI has stopped." and the user interface crashes.
Any ideas about how to solve the problem?
Thank you very much!
I have LG Optimus L70, the system stopped working suddenly.
The problem was that the bootloader is corrupt, so I have to install a new one.
In order to do that, it would be easier to enable USB debugging mode, but the problem is:
When ever I check USB Debugging the phone vibrates indicating that it is connected to PC, when i go to Device Manager on windows, it showed that the device is connected as Single ADB Interface.
The key problem that the phone's system is corrupt even after hard resetting it, so no pop up is shown, so, no RSA authorizing pop up is shown.
How can I automatically accept RSA? or make my device usable in ADB at least?
I have tried all other posts mentioned here in stackoverflow, but non of them seems to solve the problem.
Settings -> Developer -> Revoke authorizations usb debugging
I am trying out this adb shell procedure to store all my android apps to the SD Card on my new samsung galaxy tab 4.i have tried the following shell command on my laptop while staying connected with my tab via usb cable and it showed me an error.i am attaching the screenshot here.it keeps on saying "Device Unauthorized".how can i resolve this?
Your device is unauthorized. This means that you either have USB debugging off, or the adb server has messed up.
If you have the USB debugging on, try to revoke the USB debugging and restart the adb server, as suggested in
https://stackoverflow.com/a/25546300/3970830
After connecting the device, you have to accept the connection in the dialog on the device screen.
The error message is giving you the solution. Check your device for a confirmation dialog. It should be asking you to authorize the computer to connect, or something to that effect.
So, what I want to do ,is to be able to run my applications from eclipse, directly on my phone.So when I run them, the .apk gets installed and the app runs on my phone, just like it would in a virtual device.
Although, the phone won't show up in my list of "Running Android devices".
I have tried this: http://developer.android.com/tools/device.html -did not work for me ,or perhaps it worked partially but I hit a little bump at the end.When I run the adb devices command, I get this:
List of devices attached
323052d0eae6c0ed unauthorized
Any ideas how to solve this would be highly appreciated!
NOTE: I am trying to do this on a macbook which runs OS X Yosemite.
It's likely that the device is no longer authorized on ADB for whatever reason.
1. Check if authorized:
<ANDROID_SDK_HOME>\platform-tools>adb devices
List of devices attached
4df798d76f98cf6d unauthorized
2. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean & Samsung GalaxyIII).
3. Restart ADB Server:
Then restarted adb server
adb kill-server
adb start-server
4. Reconnect the device
The device will ask if you are agree to connect the computer id.
You need to confirm it.
5. Now Check the device
It is now authorized!
adb devices
<ANDROID_SDK_HOME>\platform-tools>adb devices
List of devices attached
4df798d76f98cf6d device
After doing this Need to install the Samsung Kies to show up the phone in the list of "Running Android devices".
The screen of my android device is broken such that it can't be controlled anymore using touch and I'd like to access it via adb on my computer. Fortunately, when it was unbroken I enabled USB debugging. But now I'm using a new computer. On my new computer adb devices tells me that it's unauthorized. When I try to do something with adb I get the error message error: device unauthorized. Please check the confirmation dialog on your device. which I can't do because of the broken screen. But I still have my old computer where the phone is authorized. Is it somehow possible to tell the device via adb at the old computer that the new computer (it's also fine with me to do it for all computers) is allowed to access the device?