Related
Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
bpdlr said:
Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
Click to expand...
Click to collapse
I had this problem and what I had to do was:
be sure no USB drives/memory cards were connected
connect the phone
uninstall USB Mass storage device from device manager under usb controllers
disconnect/reconnect the phone
install the driver from the sdk/usb_driver folder
Thanks, but...
I tried this, but still not luck with adb. I now see a new "ADB Interface" section in Device Manager, and an "HTC Dream Composite ADB Interface" device underneath, but adb devices command still returns no devices.
Sorted!
Well, I'm not sure how but I managed to get it to work, and am now the proud owner of a Magic running Cyanogen mod
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto
My daughter dropped her HDX 7 and the screen shattered. I was able to secure a new one for her but she had some serious sweat equity into a few games she was playing on the old one. I am trying to get the game files of the old one to move to the new one but the touch screen won't work and as such, will not take her password. (due to the drop).
Is there an easy way to bypass this? I am trying to access the kindle drive from my PC for purposes of copying the files (done a million times) but with the device technically locked, the device does not show in file explorer.
Any suggestions welcome.
Thank You!
Chris
Do you have Safestrap installed?
EncryptedCurse said:
Do you have Safestrap installed?
Click to expand...
Click to collapse
No I don't. The device is purely vanilla right as it came from the factory.
Chriss9, you should try to get adb working. That should allow you to pull data.
lekofraggle said:
Chriss9, you should try to get adb working. That should allow you to pull data.
Click to expand...
Click to collapse
Can you tell me where to get it and maybe some instructions? Thanks so much!!
Chris
Look into the rootkit in the dev section. That should install the drivers for you. Then, search for how to use adb. You may need to download the developer kit from Google as the toolkit is a little limited.
You need to pull the data to your computer then push it to the new Kindle.
ADB pull on locked phone? // Simulate input
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Grtschnk said:
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Click to expand...
Click to collapse
Thanks for the suggestion. I installed ADB on my PC and when I use "ADB DEVICES" my device does not show on the list though it does show in Windows explorer. Am I out of luck here?
Thank you again for your kind support.
Chris
Assuming you have the latest Fire OS 4.5.1 : (If you have the older version installed there may still be a glimpse of hope (see long answer))
Short answer: Sorry, looks grim.
Your ADB is switched off and there is no way I know of to switch it on.
I wanted to make sure it wasn't just a driver issue with your computer so I checked with my Kindle:
ADB set off: Kindle in Windows, but not detected by ADB-program
ADB set on: Kindle in Windows and detected by ADB-program
Long answer (may be frustrating to read because it states all the possibilities the Kindle lacks): On a nonlocked (in terms of bootloader, not screenlock) device there would have been some possibilities. Install a custom recovery that has ADB built in and pull the files or try to enable ADB from within recovery inside the ROM. If the device could act as a USB host a mouse or keyboard could have been hooked up. The Kindle supports Bluetooth input devices but they have to be set up first (from within the device, not possible without touch). If your device has older Fire OS you could try the mentioned steps, however that's beyond my expertise. So I don't know if it is possible/will work. You'd have to check other threads about flashing the device or hope that someone else posts advice in this thread.
I became a Kindle owner quite recently, so I can't guarantee everything I wrote is correct, but I believe as long as noone magically finds a way to unlock the bootloader the more experienced users will agree to my post.
Did you install the driver as well? I recommended the toolkit because comes with the driver and if you are not used to installing adb drivers on Windows, it can be a bear. But, Grtschnk may be right. I always enable it n all my devices. It is the first thing I do.
Just to be really sure about possible driver issue: You (chris) could try to connect an Android phone via ADB (I'm assuming you have one). Enable ADB on it and see if connects. Unfortunately this will only prove more that your Kindle turned into a piece of plastic :/
Grtschnk, unfortunately, that won't prove anything. ADB requires separate drivers for each device. Again, that is why I recommended the rootkit. It sets it up for you and can even test it.
That's why I compared with my Kindle, computer and S2 (CM11). Newly set up computer, no SDK, just Minimal ADB. Never installed special drivers for Kindle or S2. Newest Visual Studio (2013) runs on the machine, but without additional packages there is no Android support.
However if I was in the situation myself I would have also tried the full SDK.
I ran into a very weird issue lately. My PC running Windows 10 (previous Windows 7) and having gone through more than 4 phones with me without cleaning out my system had a ton of old drivers for different phones attached to the computer. Whenever I'd plug my Pixel 2 into the computer ADB worked fine but for some reason when I go into recovery it wouldn't recognize my phone. I rummaged through hours worth of forums/reddit posts guides/youtube videos and everyone kept coming up with the obvious answers being; install the latest adb drivers or force install the google ones or you're entering recovery completely wrong. Being quite savvy in this I tried everything and have sideloaded in the past through recovery on this very phone so it was a real head scratcher what had happened. I went through device manager uninstalled and reinstalled pretty much every adb/mobile device driver associated with the phone. However through some oversight it just wasn't clicking with me when I was in device manager my ADB was listed as "LeMobile Android Device" and even when I uninstalled restarted my computer/phone used different USB cables and ports it never clicked that it shouldn't say LeMobile Android Device because obviously my phone is a Google Pixel 2. Again seeing that I have used this very computer and phone before in the past and have sideloaded OTAs I assumed my old setting would've stuck. But I guess the latest OTA or something on my computer reverted my ADB drivers to a LeMobile Android Device thus causing my ADB to NOT work in recovery anymore but still functioned fine inside Windows.
Through more digging I found a guide on reddit: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
Pretty much the top comment/solution is as follows:
A few steps to get rid of the LeMobile pesky driver.
1-Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2-Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3-Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4-Go to the device manager. Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver like the one in location "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
5-And You're done! Cool thing is that you will have to do it again if you connect a tablet or something new and Microsoft decides the LeMobile driver is better then Googles driver...
So yes in the future I may have to do this setup again because Microsoft is just dumb and doesn't let settings stick but I went through the list and force deleted all my old phones from Motorola and Samsung as well so when I installed the ADB drivers finally the Google one's stuck. Hopefully this will fix many other people's problems when they can ADB in windows but NOT in Recovery. My other option would be to format my computer and have a fresh install but ain't no one got time for that. There are other guides online to fully delete drivers but it is very time consuming so I'm going to skip that for now.