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.
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....
Hi
I have a problem in unlocking my redmi note 5 pro.
I followed every steps which said guide but im stuck in step when i have to turn on xiaomi unlock tool.
After entering fastboot and connecting to laptop, windows recognize my phone as fastboot devices i can use every command possible to use. But if only i run any xiaomi tools fastboot become inactive it shows: "press any key to continue".
I tried almost everything, windows reinstall, drivers reinstall, didnt work. PLZ help me.
It`s because i5-8xxx or i7-8xxx.Try another computer which isn`t these.
Try another port of USB, don't use 3.0 USB port. It's fix mine.
I have intel celeron :x
I tried both on usb 2.0 and 3.0 didnt work.
I have Redmi Note 5 Pro (Indian Version)
When I connect my phone using fastboot or ADB it gets detected and connected properly. ADB commands are also working properly. The "fastboot devices" command shows the device connected initially, but whenever I try to flash something or try a command in fastboot mode the phone automatically gets disconnected and a small text appears at the top of the phone's screen stating "Press any key to Shutdown" and the PowerShell window states "FAILED (write to device failed (too many links))". Even while using MI Flash or MI Unlock the same thing happens.
The fastboot commands were working properly on my old laptop (SONY VAIO SVE15136CNB) but after I got a new laptop (ACER Predator Helios 300 PH315-51) the fastboot commands stopped working. The fastboot commands still work on my old laptop.
I have tried using many different fastboot drivers (also the one that works on the old laptop) in the new laptop but no luck. I have tried different USB cables and also the original one. Tried to use every USB port but same error occurs. I have tried 2 other Note 5 Pros and a Note 4 in the new laptop but same error occurs.
So, I have concluded that the error has something to do with my new laptop and it is probably about the USB port version of my new laptop. If someone has experienced similar error, I would appreciate getting some help about this matter. I have tried searching about the error on google but I couldn't find much information. I hope someone could help me.
I have been following this forum for years and thanks to all the geniuses here through their guides I have always managed to make all the modding I needed.
But not this time, I'm going crazy.
As the title suggests I have a Samsung Galaxy Tab S3 SM- T825 Qualcomm MSM8996 Snapdragon 820 to which I want to root by mounting twrp recovery and magisck.
I've been trying for days but to no avail.
I state that I have adb fastboot odin latest versions, updated drivers etc.
The problem that occurs is this, adb recognizes the device in normal mode.
I flash twrp and everything is fine I go to twrp, I do the steps of ext2 ext4 file system otherwise it will not read the data and again, all is ok.
But as soon as I reconnect the tablet to the usb cable for adb sideload, my windows 10 no longer reads the device, it does not even emit the classic usb sound ... So it does not read it or adb of course, but neither does the pc.
Just flash with odin rom stock android 9 pie, review the tablet both pc and adb again.
Obviously all the procedures with oem unlocked and usb debugging active in file transfer mode.
I've been going crazy for six days to complete the operation, but I can't ....
I have no idea how many guides, tutorials, videos, possible resolutions I have consulted and applied but to no avail
Can someone please help me sort out or figure out what the hell is wrong ...?
I'm about to set fire to my tablet and pc ....
Thanks in advance and sorry for the not perfect English