Develop Bugs

Device not recognized on ADB?

I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.

i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038

b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.

in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu

b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.

I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913

The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.

in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...

I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>

Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk

I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb

Its seems i should give up

Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.

Push push push it

tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks

Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.

Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device

Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?

Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.

The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.

[Q] Root Kindle Fire 6.3.2

I am trying to Root my Kindle Fire version 6.3.2, and am looking for the correct Kindle Fire Utility. I do not want to download the wrong one as the ones I have seen were for version 6.3.1 or 6.3. Anyone have suggestions?

Ichigo said:
http://forum.xda-developers.com/showthread.php?t=2192818
Click to expand...
Click to collapse
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark

mrlee1999 said:
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
Click to expand...
Click to collapse
Put everything back where it belongs first. Also, your computer recognizes the kindle as an Android adb device in device manager? You are on 6.3.2 also?
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2

mrlee1999 said:
Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
Have you tried running KFU under compatibility for Windows XP SP3? Once you do that, it'll automatically ask for admin privileges.
Also, does your device show when you run the command
adb devices
Click to expand...
Click to collapse
on a terminal (or command prompt, on Windows) window?
Sent from my Muffin masquerading as a phone in the coffin.

Thanks
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark

The one that ichigo said is good.

So I was using the new KFU 9.8+ on my first gen kindle (6.3.2)
and during the procedure while I think it was attempting to install FFF bootloader it was on <waiting for device>, my laptop lost batter life and shut down. Upon booting up my computer and trying KFU again
ADB Status: Offline
Boot Status: Unknown
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?

HypothermicInferno said:
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?
Click to expand...
Click to collapse
It is on the orange logo? And it won't boot properly? So the kindle just stays on that screen without getting dim or anything, right?
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Bricked as well
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.

mrlee1999 said:
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark
Click to expand...
Click to collapse
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks

nugroho2 said:
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks
Click to expand...
Click to collapse
The .android folder is found under the root of your sdcard or you ext-sd. To remover the drivers:
If you are on Windows 7/8:​
Hit the "Start" button on the keyboard, and when the homescreen (Windows 8) or the Start dialogue (Windows 7) pops up, type in "Add or remove".
Hit enter on the highlighted option, which should be "Add or remove programs". (Note: You may have to go into the settings tab if you are running a search on Windows 8)
This will show you a window where all the apps that are currently installed on your computer shows up. (Metro apps don't show up here.) Look through the list until you find your KF drivers. This should be listed as something like this: Kindle Fire Drivers
Highlight the driver and look towards the top of the window. You should see that a "Change/uninstall" button has popped up. Click on that and follow the on-screen instructions to uninstall the drivers.
You're done!
If you are on an older version of Windows:​
The procedure is the same, only you have to go into Control Panel > Add or remove programs to do this.
Good luck rooting your KF. :good:

Kindle Fire Tool
My company is making a Kindle Fire Tool for Windows and Mac. Their are several options that might help you like "Toggle Unbrick" You can also root on Android 6.3.2.
Contact me if you have any questions: [email protected]

thebane90 said:
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.
Click to expand...
Click to collapse
I had the Same issue found it was just stuck in Fastboot mode and Windows does not handle it well at all. I was getting a USB device not recognized error and wouldnt let me change the driver for it. To get back booting again I used
http://forum.xda-developers.com/showthread.php?t=1850038
Followed the direction and everything was good.... Almost I found no matter what computer I use fastboot always comes up as a bad device. :crying:
But that should help you with the "Brick"

Kindle Fire 6.3.2 successfully rooted
mrlee1999 said:
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark
Click to expand...
Click to collapse
I have the same error.
What i did was...
1. Download KFU 0.9.9 (http://forum.xda-developers.com/showthread.php?t=2192818)
2. Download TWRP (http://techerrata.com/browse/twrp2/blaze)
3. Download FFF (http://forum.xda-developers.com/showthread.php?t=1369405)
4. I rename them as "twrp" and "fff" respectively and place them in the "recovery" folder in KFU
5. I manually install the drivers
6. I check in the device manager to show me "Android Phone - Android Composite ADB interface"
7. I run the KFU
and that was all...
I check the root was complete with the https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ..

not visible on my pc.
Hey, I took the first step to root my kf on 6.3.2. I can no longer see the devise on my computer to do anhything else. I only loaded the utility file onto the devise and now what? I can't even delete it. Any thoughts?

Okay... here goes!
Vlasp said:
The one that ichigo said is good.
Click to expand...
Click to collapse
*Takes a deeeeep breath* okay, I thought it looked like the most promising instructions I've found so far too... so, from a TOTAL novice at all of this, here goes! Thanks for the endorsement ( I will definately thank him too! )

So, I went through all the steps outlined by xarenmi, but it STILL doesn't recognize my kindle when I try to use the run tool.
I'm not the best with all this, so...

Help...
Hey, I finally got the google winusb driver installed (I had to do it via SDK manger) but it still recognizes my kindle as "kindle" under "other devices" in the device manager. Also the KFU will not recognize it.. period. just nothing and I'm getting really fed up.
I have followed all instuctions to the T and I am still having issues.

[Q] loading xbmc file to fire tv

Hello: need some help please.I am able to connect to my fire tv but every time I try to install xbmc the computer says unable to find the file.How do I make this work?
Thanks Duett

duett said:
Hello: need some help please.I am able to connect to my fire tv but every time I try to install xbmc the computer says unable to find the file.How do I make this work?
Thanks Duett
Click to expand...
Click to collapse
Are you typing the full path, where XBMC is located? I normally just drag and drop the file in to the terminal after adb install. For example adb install '/home/fatfarley/Downloads/xbmc-13.1-Gotham-armeabi-v7a.apk'

Amazon FireTV Side App Installer
Try using the Amazon FireTV Side App Installer (http://forum.xda-developers.com/showthread.php?t=2736774) as it gives everything you need to install XBMC and all the goodies.
EDIT: Be sure to place your version of XBMC apk in the XBMC folder within FTV.

1) Turn on USB Debugging in settings, check the IP of the device as well
2) Install ADB on your PC
3) Go on to CMD and enter the path that leads to ADB (usually in *\android\sdk\program-tools)
4) Enter "ADB connect <insert IP of your fire tv>
5) after it connects, enter "ADB install xbmc.apk
6) then afterwards go back to settings > applications and bam its there

[Q] Driver install problem w/ Mac

I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).

creaky said:
I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).
Click to expand...
Click to collapse
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.

uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.

Do you have installed the android sdk?

creaky said:
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.
Click to expand...
Click to collapse
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices

uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
wadamean said:
Do you have installed the android sdk?
Click to expand...
Click to collapse
I had to reinstall - that was the problem. Thanks!
uly609 said:
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices
Click to expand...
Click to collapse
Thanks again for the help. Problem solved.

Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.

wadamean said:
Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.
Click to expand...
Click to collapse
Not root, used Debloater tool to block updates. Would love to see a Mac root method released.

oh i see then. i will keep patiently waiting for a simpler root method. this one is already but for sure there has always been even more simpler methods surfaced.

ADB Device Unauthorized

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.