so i just tried to install adb using this tool
http://forum.xda-developers.com/showthread.php?t=2588979
then i tried "adb devices" but it said
but it said
"List of devices attached
FA43xxxxxxxx unauthorized"
can anyone help me?
kevintran.98 said:
so i just tried to install adb using this tool
http://forum.xda-developers.com/showthread.php?t=2588979
then i tried "adb devices" but it said
but it said
"List of devices attached
FA43xxxxxxxx unauthorized"
can anyone help me?
Click to expand...
Click to collapse
I take it you activated usb debugging mode in the developer options settings? Maybe check and try again.
Unplug the device and turn on the screen. Then plug it back in and type adb devices and wait for an authorization prompt to appear on your devices screen. Accept it.
Hello guys!
I have been searching and searching for a solution to my problem and i have been with this for hours.
First off,
i have uninstalled, installed , uinstalled again... but nothing works for my device to be recognized by my computer so i can get pass RSA code (confirm through phone).
USB-Debugging is still on and i get this :
http://imgur.com/ebhh18n
Seriously i dont know what to do anymore. I have even reset my phone and its on stock 5.0 L..
I have been deleting the folder .android for adbkeys but still the window will not pop-up...
Thanks in advance,
Fozec
Have you already tried this?...
adb kill-server followed by adb start-server
(on device) Settings -> Developer Options -> USB Debugging -- switch off and on
I have tried that so many times and it still doesnt work. My computer still thinks its unauther...
Hey fellow members,
Since a few days my ADB is not working with my phone. Every time I try to connect it as an ADB device I get an error (See attachment) that my device is unauthorized.
I've read a dozen threads about this problem and I think it is the RSA Fingerprint. I don't get that pop-up anymore, when connecting my device to authorize the PC.
Here's what I've tried already
1.
Code:
adb kill-server
Code:
adb start-server
2. disable and enable USB-Debugging-Mode
3. Copy the adb key from C://user/me/.android. to the phone's directory /data/misc/adb
4. reinstall drivers on PC
5. Reboot PC and Phone
None of that worked. None. I'm desperate. Been looking for 6 hours yesterday and couldn't fix it.
If anybody has had these kinda problems I would be totally grateful for an answer.
I have the intl version of H815, bootloader unlocked, TWRP and SuperUser working fine. I'm currently on V20C (6.0 Marshmallow)
Any help would be extremely nice.
Best regards
Hi,
Did you solves this as I am having the same problem after doing a factory reset?
Cheers
Follow_and_Feel said:
Hey fellow members,
Since a few days my ADB is not working with my phone. Every time I try to connect it as an ADB device I get an error (See attachment) that my device is unauthorized.
I've read a dozen threads about this problem and I think it is the RSA Fingerprint. I don't get that pop-up anymore, when connecting my device to authorize the PC.
Here's what I've tried already
1.
Code:
adb kill-server
Code:
adb start-server
2. disable and enable USB-Debugging-Mode
3. Copy the adb key from C://user/me/.android. to the phone's directory /data/misc/adb
4. reinstall drivers on PC
5. Reboot PC and Phone
None of that worked. None. I'm desperate. Been looking for 6 hours yesterday and couldn't fix it.
If anybody has had these kinda problems I would be totally grateful for an answer.
I have the intl version of H815, bootloader unlocked, TWRP and SuperUser working fine. I'm currently on V20C (6.0 Marshmallow)
Any help would be extremely nice.
Best regards
Click to expand...
Click to collapse
pinn___________ said:
Hi,
Did you solves this as I am having the same problem after doing a factory reset?
Cheers
Click to expand...
Click to collapse
Unfortunately no. I've really tried everything. I even flashed a complete new kdz (at least upgraded to one), to no avail.
And this thread doesn't get enough recognition or any advice from a pro, so I'm heading dead ends.
I'll let you know, when I found a possible solution and post it in this thread.
Cheers
Hi,not a solution as such but I wanted adb to get into the bootloader. Instead I installed a terminal emu and got into it that way. Not sure what you are trying to achieve but this may be of some help.
Same problem for me... Device unauthorized, no rsa prompt... Tried it factory fresh, no success.
pinn___________ said:
Hi,not a solution as such but I wanted adb to get into the bootloader. Instead I installed a terminal emu and got into it that way. Not sure what you are trying to achieve but this may be of some help.
Click to expand...
Click to collapse
I want to access my device via ADB, e.g. pushing files to my phone, installing, wiping, etc.
Which I can't, since my computer, or my device is unauthorized to do so.
I just can't enter ADB commands, which is pretty annoying, since I often use it to push files to my phone or print out a logcat.
Well nothing's working so I gotta be patient until anybody comes up with a solution :good:
The strange thing is, i do also own an oneplus 2. It doesn't get authorized too, but is asking for fingerprint. Do you have win10, like me?
Trinaaa said:
The strange thing is, i do also own an oneplus 2. It doesn't get authorized too, but is asking for fingerprint. Do you have win10, like me?
Click to expand...
Click to collapse
Yes I have win 10. You're one step further than me. I don't even get an RSA prompt. Don't know why yet
Follow_and_Feel said:
Yes I have win 10. You're one step further than me. I don't even get an RSA prompt. Don't know why yet
Click to expand...
Click to collapse
Refer the below thread, hope this helps
http://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300
EXPERT FROM THE ABOVE LINK:-
I was not getting the RSA fingerprint pop up on my phone.
I had to go into the C:\Users\.android\adbkey and adbkey.pub
files, delete those and then do kill and restart of adb server. I had to stop and restart the debugger and connecting as USB in PTP mode.
Because the RSA authorisation key was getting stored in this path, killing and restarting the adb server didn't help.
Just wanted to reiterate the person above me as it helped me with my problem. So in case anyone out there on the internets runs into the same issues try these instructions.
1. boot your phone into recovery
2. now try doing adb devices in your command prompt - it should show up as LGH815xxxxxx recovery
3. type adb shell
4. type cd /data/misc/adb
5. type rm adb_keys -- this will delete any existing adb key from your device **
6. type exit to leave the shell and then reboot your device as normal
7. in windows find C:\Users\<your username>\.android
8. delete the existing adbkey.pub file
now you can proceed as normal with running adb devices, and you phone will prompt you to confirm.
** note you can also delete the adb key from android from within your android OS. go to settings > developer options > revoke USB debugging authorizations. i guess you can do it from recovery just to make sure.
Hi, all
Just got myself new OnePlus 3, wanted to try new OOS 3.5.2
to my surprise, i have a mac and after doing all the necessary steps
Developer settings- activating debugging, android file transfer working with file transfer mode.
As soon as i start ./adb devices it does not show up on devices attached, and it also does not ask me on device to authorise mac.
Please help
Hi, I have found the solution myself
Just follow this
https://code.google.com/p/android/issues/detail?id=152172
Basically used this command
$ adb devices -l
it returned as unauthorised device
again tried ./adb devices
and device asked for authorisation and its sorted.
May be this will help someone
I have a Pixel 3a xl, I fix its screen after a crash but even though I have registered my finger print, I forgot the password. I've been learning how to use ADB and FASTBOOT, but with no success. I'm totally a beginner. I've tried to run "adb shell" but it shows me "closed" and the only way to list my device with "adb devices" is when I reboot my phone in "RESCUE MODE", I run adb devices and it shows:
List of devices attached
94GAX0DZ1U rescue
However when I run adb "shell" "usb" "backup" the response is always: ERROR: closed
My debug mode is probably unable, i do not remember if y/n
I'm using:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Installed as /Users/admin/Library/Android/sdk/platform-tools/./adb
add: unable to connect for backup: closed
I've read about TWRP but i do not know if it means erasing my userdata "which is what i want to keep on my phone" Photos/videos etc
Please, I really appreciate any help about what you recommend me to do
kristianss27 said:
I have a Pixel 3a xl, I fix its screen after a crash but even though I have registered my finger print, I forgot the password. I've been learning how to use ADB and FASTBOOT, but with no success. I'm totally a beginner. I've tried to run "adb shell" but it shows me "closed" and the only way to list my device with "adb devices" is when I reboot my phone in "RESCUE MODE", I run adb devices and it shows:
List of devices attached
94GAX0DZ1U rescue
However when I run adb "shell" "usb" "backup" the response is always: ERROR: closed
My debug mode is probably unable, i do not remember if y/n
I'm using:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Installed as /Users/admin/Library/Android/sdk/platform-tools/./adb
add: unable to connect for backup: closed
I've read about TWRP but i do not know if it means erasing my userdata "which is what i want to keep on my phone" Photos/videos etc
Please, I really appreciate any help about what you recommend me to do
Click to expand...
Click to collapse
stupid question did you enable USB debugging on your phone
tap build number till you see developer options, turn on USB degugging?
try using ADB link for windows you should be able to get bonito shell