Related
So I tried following one of the guides posted here at XDA to retrieve my MSL#.
** EDIT **
XDA FORUMS WILL NOT allow me to post links, because I have a new account, and it hasnt been approved. So I am just going to post the links to the screenshots without the "http" in front. I also had to remove the "." from the first part of the web address. So "google.com" would be "google com". You will have to manually copy and paste the URL, and add the periods to first part of the address.
IF A MOD IS READING THIS CAN YOU PRETTY PLEASE APPROVE MY ACCOUNT? Thanks!
I followed this guide:
forum xda-developers com/showthread.php?t=697487#
I downloaded the pre-requisites, and started to follow the steps.
I am on Windows 7 32bit, and these instructions are for Windows 7 64bit.
Once I cam to the section where I chose my drivers I chose the ones for x86 since I am running 32bit.
It installed the drivers fine. However, it installed the device under the "PORTS" section of the "Device Manager".
The screenshots for the instructions show the device being installed under the "MODEMS" section.
So I thought I did something wrong, and before doing any further research, I decided to delete the device that was installed under the "PORTS" section. I figured by doing this I could start from scratch, and correct whatever it was that I did wrong. Dumb move!!!
I removed the drivers from "C:\windows\system32\drivers" and also from "C:\windows\system32\driversstore\filerepository"
I unplugged my phone, rebooted my machine, dialed "##3424#" to enter diagnostic mode, connected my phone to the computer, and it DID NOT recoginze any new hardware.
I also tried removing any references from regedit for "htcdiag", which is the driver that was installed.
This produced the same result.
I have attached screenshots of the devices currently in my device manager.
Device Manager Screenshot #1:
img46 imageshack us/img46/8923/screenshot1ka.jpg
Device Manager Screenshot #2:
img163 imageshack us/img163/1479/screenshot2m.jpg
Device Manager Screenshot #3:
img202 imageshack us/img202/9158/screenshot3hj.jpg
Please help me get this working!
Thank you!
Have you tried msl reader from the market ?
mendez_v said:
Have you tried msl reader from the market ?
Click to expand...
Click to collapse
No, but at this point I am less worried about the MSL, and more worried about getting the android phone to show up properly under the device manager. When I rooted the phone I installed a modified HTC USB Driver, and then my phone showed up under device manager. As you can see from the screenshots my phone does not show up in device manager AT ALL anymore.
I know this was a rookie move, but someone must have done this before, or at the VERY least must have some suggestions on how to get the drivers reinstalled on my machine for my phone.
Anyone.... Bueller? Bueller?
** ONE MORE BUMP **
Perhaps all the useful contributors were on an extended Labor Day vacation.
guht said:
No, but at this point I am less worried about the MSL, and more worried about getting the android phone to show up properly under the device manager. When I rooted the phone I installed a modified HTC USB Driver, and then my phone showed up under device manager. As you can see from the screenshots my phone does not show up in device manager AT ALL anymore.
Click to expand...
Click to collapse
Have you plugged the phone in and tried "scan for hardware changes"?
Still no luck.....The HTC website has a support section with drivers you can download.
OR-
Do you have the android sdk installed on your computer? There is a usb driver package you can use in the sdk.
If you still cannot get it to connect, then flash a rooted stock rom and see if your computer can connect then.
As far as your MSL, just call Sprint and ask them. The rep will ask why you need it. Just tell them your phone has been acting odd and that you are going to do a reset, which you have done before in the past ; ). They will then transfer you to a tech which will ask you again why you need it. Just respond the same about doing a reset, which you have done many times before.....you will then have your MSL - takes only a couple of minutes.
Hello everyone first time writing in the forums and need a little help. I am looking to root my HTC Evo for the first time and going to use it through a MAC with Unrevoked. I downloaded the reflash and I have Snow Leopard 10.6 on my comp and for whatever reason when I am prompted to connect my phone along with the debugging active on the phone as well, nothing seems to happen at all and in some instances even freezes up my comp. I was wondering if I have to update my phone to the newest update(3.70) which I haven't done yet? will that make a difference? any advice or help will be so appreciated, thank you!!
Try installing & uninstalling HTC Sync if you haven't already. It should be on your SD card if you haven't deleted it. Just make sure that it, along with anything else that syncs with your phone, is uninstalled prior to running the reflash package.
htc sync doesnt work on a mac. are you on an admin account? if not, i'd try it on one. and yes, you need to be on 3.70, but i dont know why your comp would reboot. also try updating the comp if you can. if upgrading and admin doesnt work, try opening terminal.app in the utilities folder, and type
sudo /users/yourUserName/applications/reflash.app or wherever you have it. that might work.
try setting the phone to disk drive instead of charge only before running unrevoked, it worked for me..
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
THANHVO31 said:
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
Click to expand...
Click to collapse
That link you posted doesn't use my same ids
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
EDIT: and I made a huge mistake and i had not put in the bootloader (FIREFIREFIRE) on my bricked kindle, however, I took extra precaution and put it on my working kindle and to prevent it even further I am not using any roms and only using GoLauncher EX, googleframework, Superuser(root), and Market
as some roms are unstable and ALWAYS have a problem that something is not working correctly!
umarsl said:
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
Click to expand...
Click to collapse
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Th3-Chronikk said:
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Click to expand...
Click to collapse
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\Vid_1949&Pid_0006&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006
Click to expand...
Click to collapse
And try again.
Goodluck
THANHVO31 said:
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
And try again.
Goodluck
Click to expand...
Click to collapse
Didn't work
Th3-Chronikk said:
That link you posted doesn't use my same ids
Click to expand...
Click to collapse
The hardware IDs in that link look identical to yours, and I think every other Kindle Fire I've seen. Yours don't look unusual.
I'm having the same damn issue, my 6.2.2 kindle is not recognized by adb. The weird thing is that sometimes it does see the device and then it disappears? The driver ID's that are posted are identical to the ones that are included with KFU.
If anyone figures this out please let me know!
Troy.
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
p-niiice said:
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
Click to expand...
Click to collapse
android update adb
add 0x1949 on its own line to adb_usb.ini in C:\users\<username>\.android\adb_usb.ini
save the file
adb kill-server
adb start-server
adb devices
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
jcc2z said:
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
Click to expand...
Click to collapse
Thanks - doing this plus the hardware ID lines earlier in the thread got me further, but adb still isn't picking up the composite device.
androidcues said:
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Click to expand...
Click to collapse
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
K3nDroid said:
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
Click to expand...
Click to collapse
Interesting that you had such an issue with getting windows to work. I have rooted 2 Kindles(took an hour total to get them set up, rooted, recovery and Gapps installed), Samsung Epic 4g, Multiple Evo 4gs, Optimus M, Hauwei Ascend, and HTC Hero and never had an issue with drivers or having to uninstall them. I am running Windows 7 and each one I plug in it recognizes.
Hey guys
I specialy registered to this forum for my next question/problem.
First of all, I'm using Wildfire s, 2.3.7, CyanogenMod-7.2.0-RC1-marvel.KANG + i'm using Windows 8 Consumer Preview.
I was trying to install
"[Tool] Android Screencast 0.4 (open-source)"
http://forum.xda-developers.com/showthread.php?t=557717
But when i connect my htc to pc with usb debugging it fails to install the driver. I've downloaded many usb_drivers from all over internet and tried to install them manually using device manager but it doesn't seem to work.
Finly i found the "HTCDriver3.0.0.007.exe and it worked on other computer (Win7). when i tried to install it in win 8 it gives an error telling that Driver installer in not supported for this OS. tried to run in capatibility mod but no luck.
Also tried to modify the usb_driver files "android_winusb" my adding lines in end etc.. still didn't work.
usually i don't ask help from any forum rather i google things and read other ppl posts. which worked.... until now So now i'm asking for help at this topic, i've been through almost every post in xda telling about Device not found, without any luck there eith.
If needed it's possible to remote controll my pc with teamviewer.
Help is really appreciated.
ps. device manager shows that yellow attention mark.
TEMP FILES / Extract .msi~
I got it work myself after all.
If you need help to install the device, mail me.
[email protected]
why not just post the answer?
had trouble getting drivers for windows 8 64 to work when trying to flash ruu update. could not find drivers online or a thread on xda, eventually downloaded the google drivers from sdk, and they worked perfectly after manually installing them for the android phone and then again for the android 1.0 device when it boots to hboot.
Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either
MKD73 said:
Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either
Click to expand...
Click to collapse
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?
Alcolawl said:
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?
Click to expand...
Click to collapse
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.
MKD73 said:
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.
Click to expand...
Click to collapse
Would you mind doing something for me before performing the steps I'm going to list below? Go into Device Manager with the phone plugged in and installed as the stupid "TP-Link" BS and find it in the list of devices. Should probably be under Portable Devices or something. Right click it and click Properties, go to the Driver tab and click "Driver Details". All of the drivers should be located in the 'system32/DRIVERS' folder. Mind giving me the names of those drivers listed? Naming convention is typically driverName.sys.
Additionally, we're going to try a Group Policy change. Hit Windows Key + R and type 'gpedit.msc' and hit enter. A window labeled "Local Group Policy Editor" should come up. Then do the following:
Expand Computer Configuration (Left hand side, the navigation panel)
Expand Administrative Templates
Expand System
Expand Device Installation
Click Device Installation Restrictions
On the right hand side, now, there should be a list of restrictions. Somewhere in that list there should be an item "Prevent installation of devices not described by other policy settings". Double-click that and another window named the same thing should pop up. In the top left, set it to enabled and click Apply, then OK.
Unplug your phone and get rid of that ****ty driver if you haven't already and then restart and try connecting the phone again to see if the same incorrect driver install occurs.
@MKD73 You ever get this sorted out?
Sorry been away on holiday for the weekend , I'll be taking a look in the morning :victory:
Please give update
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838
kalikotpepot said:
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838
Click to expand...
Click to collapse
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?
loeage said:
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?
Click to expand...
Click to collapse
I did it. Execute :
Code:
rundll32.exe newdev.dll,DeviceInternetSettingUi 2
and prevent driver from being installed.
Help me please!
Did you guys manage to fix it? I tried everything you people said but it didn't work. I have a Blu Vivo Xi+ and my PC only recognizes it as TP-LINK Android Phone. I dumbly deleted it's OS and all it's data when trying to update it. I only have access to TWRP and fastboot, is there a way to fix it? I would love if someone could assist me ?.