Anyone here having issues on Windows 10 with ADB/Fastboot recognition?
I'm using the Android SDK Toolkit from the Google website, and I have both ADB and Fastboot installed. ADB recognizes the device, and started a shell on the device, everything is ok.
I reboot the device into fastboot mode, plug it into the same USB port where ADB was working, and nothing happens. It says "connect the usb cable". Frustrating as I'm looking to unlock the bootloader.
Tried rebooting from both MHP/PHP/Stock usb modes, which all opened an adb shell successfully, but fastboot mode is not recognized at all on the same usb port.
SOLVED see lower posts.
when you run the "adb devices" what does it show? If I had to guess it will show your device but say something about it being locked. I had to go into device manager, and manually switch my ADB device driver over to the correct one. I cant remember off of the top of my head which driver it was, but it took me nearly an hour to figure it out.
rodcpierce said:
when you run the "adb devices" what does it show? If I had to guess it will show your device but say something about it being locked. I had to go into device manager, and manually switch my ADB device driver over to the correct one. I cant remember off of the top of my head which driver it was, but it took me nearly an hour to figure it out.
Click to expand...
Click to collapse
List of devices attached
84BXXXXXXXXXX66 device
Looks like what I'm used to, as I said, adb shell works fine, I can change directory to system or whatever. Just doesn't recognize the device at all in fastboot mode.
hmmm, odd. Does it say "waiting for device" in adb when you are in the bootloader? Or is it telling you to plug in the USB on the bootloader screen (phone).
If the latter is the case, try and run your commands.
rodcpierce said:
hmmm, odd. Does it say "waiting for device" in adb when you are in the bootloader? Or is it telling you to plug in the USB on the bootloader screen (phone).
If the latter is the case, try and run your commands.
Click to expand...
Click to collapse
It's telling me to plug in the cord on the bootloader screen. "connect usb cable", I connect it. It still says "connect usb cable". However, in my device manager, I have an Android device that does not have a driver (Code 28).
go ahead and try and run your commands in ADB while on the bootloader screen.
rodcpierce said:
go ahead and try and run your commands in ADB while on the bootloader screen.
Click to expand...
Click to collapse
neither adb or fastboot commands work in bootloader mode on the same USB that ADB worked when phone was on.
The device is recognized in device manager (when in fastboot mode) but has no driver. Is it not the same usb driver responsible for ADB when device is on???
one second, let me plug mine in here quick and see which device driver is assigned.
---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------
here is what mine shows up as. I was hoping it would show me the driver file. If you have a device with no driver, I would point it to the google universal USB driver. (i believe that is what I used)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rodcpierce said:
one second, let me plug mine in here quick and see which device driver is assigned.
---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------
here is what mine shows up as. I was hoping it would show me the driver file. If you have a device with no driver, I would point it to the google universal USB driver. (i believe that is what I used)
Click to expand...
Click to collapse
Solution to the problem was right click on "Android Phone" that was beside other "Unknown Devices" -> Update Driver Software -> Browse My Computer For Driver Software -> Let Me Pick From A List Of Devices -> (Since the Google SDK platform tools were installed, but not even full SDK, containined generic choices such as adb interface, bootloader interface, hawaii hdb interface etc.) -> Chose Android Bootloader Interface.
Phone now registers as Android Bootloader Interface under "Android Phone" in device manager. Strange since when phone is on it registers in a different category. Also strange, as phone still says "Connect USB Data Cable" as if it isn't connected to the laptop. But just performed "fastboot devices" and it is recognized by the computer for fastboot activities! So good enough for all intents and purposes.
When the phone is on, it appears as a ADB Interface under Universal Serial Bus devices. When the phone is in bootloader mode it appears as Android Bootloader under Android Phone (the new driver). ADB works when the phone is on, but ADB does not work in bootloader mode. Only fastboot works in bootloader mode.
Magnetox said:
Solution to the problem was right click on "Android Phone" that was beside other "Unknown Devices" -> Update Driver Software -> Browse My Computer For Driver Software -> Let Me Pick From A List Of Devices -> (Since the Google SDK platform tools were installed, but not even full SDK, containined generic choices such as adb interface, bootloader interface, hawaii hdb interface etc.) -> Chose Android Bootloader Interface.
Phone now registers as Android Bootloader Interface under "Android Phone" in device manager. Strange since when phone is on it registers in a different category. Also strange, as phone still says "Connect USB Data Cable" as if it isn't connected to the laptop. But just performed "fastboot devices" and it is recognized by the computer for fastboot activities! So good enough for all intents and purposes.
Click to expand...
Click to collapse
yeah, I had to do something similar. I couldnt remember the exact steps. But took me forever to figure it out!
Sorry I wasnt more help my friend.
rodcpierce said:
yeah, I had to do something similar. I couldnt remember the exact steps. But took me forever to figure it out!
Sorry I wasnt more help my friend.
Click to expand...
Click to collapse
No, thank you! Glad the post is here for others now.
Ok. I runned into all of this issues. I finally discovered that after you went into recovery, the device was being installed as a kedacom USB device. So I researched a little and found the solution in the link below.
Short solution:
Right click on "Start Button" and select Device Manager
Find Kedacom, drilldown and right click to update driver
Browser Computer
Let me Pick...
Then Select ADB Driver.
That should fix it.
I hope it helps.
https://www.reddit.com/r/oneplus/comments/59ux5d/cant_root_because_windows_10_keeps_installing/
Related
I am attempting to root my HTC Panache (MyTouch 4G) with this guide.
The problem is with the first step which is installing adb and the USB driver. The guide referred to the cyanogenmod wiki on installing the android SDK. I believe that I followed all the instructions correctly but it does not show that my drivers are installed properly in windows device manager and CMD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So here is the entire process that I took:
installed java sdk exe
downloaded Android SDK zip file and extracted to root C:\
opened SDK Manager
installed "Android SDK Platform-tools, revision 6" (revision 4 not available) and "Google USB Driver package, revision 4" packages in SDK manager
went into control panel > system > advanced settings > environment variables > double clicked "Path" > added ";C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools"
downloaded and replaced the default "android_winusb.inf" file with the modified file from the cyanogenmod wiki
enabled "USB debugging" and ensured USB was in "charge only" mode in phone
opened CMD and typed in "adb devices", didn't show anything
opened windows device manager and found an "Android Phone" device with the yellow exclamation mark instead of "Unknown Device" with ADB listed under it as mentioned in the cyanogenmod wiki
right clicked and update driver software, clicked browse and located the "C:\android-sdk-windows\extras\google\usb_driver" folder with the modified .inf file
"Windows was unable to install your Android Phone"
I've been trying many things for hours so any help would be appreciated! Thanks in advance.
Try these drivers...
http://www.multiupload.com/HBVGRC92IP
Ace42 said:
Try these drivers...
Click to expand...
Click to collapse
Success!
All I needed to do was install the .exe you gave me, restart the computer, device manager > right-click the unknown android phone device and "scan for changes", then the driver automatically installed! confirmed with cmd > adb devices.
Thank you!
qayum said:
Success!
All I needed to do was install the .exe you gave me, restart the computer, device manager > right-click the unknown android phone device and "scan for changes", then the driver automatically installed! confirmed with cmd > adb devices.
Thank you!
Click to expand...
Click to collapse
Np, the generic drivers normally don't install anyway, have to use the htc ones instead.
Ace42 said:
Np, the generic drivers normally don't install anyway, have to use the htc ones instead.
Click to expand...
Click to collapse
Off-topic but, another problem.
I've successfully generated the CID with SimpleGoldCard but it seems that the gold card IMG generator website psas.revskills.de/?q=goldcard is down.
Will it be online again? Is there any other way to get the IMG file?
qayum said:
Off-topic but, another problem.
I've successfully generated the CID with SimpleGoldCard but it seems that the gold card IMG generator website psas.revskills.de/?q=goldcard is down.
Will it be online again? Is there any other way to get the IMG file?
Click to expand...
Click to collapse
I have no clue what the gold card is really, I last heard about it when people were rooting the magic. Since you mentioned CID, are you trying to unlock the phone fir other carriers ?
Ace42 said:
I have no clue what the gold card is really, I last heard about it when people were rooting the magic. Since you mentioned CID, are you trying to unlock the phone fir other carriers ?
Click to expand...
Click to collapse
No, I do not need to unlock it. The phone is from my carrier Mobilicity, but people referred me to use the Videotron HTC Panache guide (link to thread in OP) because it has a newer ROM version and making a gold card allows to "flash RUU files with a different CID to your own device - in other words, it allows you to flash files that were not made for your phone."
Basically, there was a back-to-school sale on the HTC Panache from Mobilicity and people who wanted to root (and unlock) it followed the guide above.
Please give me any suggestions, thanks!
Odin is not recognize by my phone since CM 10.1 been installen on my phone
Good day!
Since Cyanogenmod 10.1 nightly been installed on my phone, Odin does not see the phone anymore even is the USB debugging is active on the phone. I am able to see the phone using the command ADB devices -l. I need Odin back because I want to put back the stock firmware on my phone which is Jelly Bean 4.1.2. from Virgin Mobile.
Can someone tell me why ADB can see my phone and not Odin?
Thank you!
my problem started after i updated to oct 7 cm10.3 nightly. my pc and my mbp cant read my nexus storage.
searched for this problem and found some few n4 users that experienced this but my main problem is there is no android device listed on my device manager.
i checked for all possible solutions:
- uninstall driver on device manager and reconnect the phone to install the driver automatically (but theres no android device listed)
- changed the storage settings as to connect to mtp
- restore factory settings and wipe data
- tried different data cables
- changed my rom from cm to pa
- restart phone
- push adb but device not found (but my pc doesnt recognize my phone)
- turned on/off usb debugging (still cant read)
then out of frustration, i wiped my storage data completely
i cant flash any roms, no files found
i cant push adb because my pc cant find my phone even in recovery
any ideas? thanks in advance.
Boot into recovery and you should be able to see your device in ADB.
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 03:48 PM ---------- Previous post was at 03:48 PM ----------
Nvm, just read the end of your post haha. Are you on TWRP or CWM?
Sent from my Nexus 4 using Tapatalk 4
I had a quite similar problem after trying to install adb drivers (mtp wouldn't work). This is how I solved this:
Follow this guide (only the first part on installing adb driver). Once you have ADB drivers installed, go to device manager, right click on android adb device, choose update driver, pick from a list of device drivers on your computer and choose "MTP USB Device". Not only did I get storaging capabilities back, it preserved adb driver as well... found this method by frustratingly trying random things.
manpildo said:
I had a quite similar problem after trying to install adb drivers (mtp wouldn't work). This is how I solved this:
Follow this guide (only the first part on installing adb driver). Once you have ADB drivers installed, go to device manager, right click on android adb device, choose update driver, pick from a list of device drivers on your computer and choose "MTP USB Device". Not only did I get storaging capabilities back, it preserved adb driver as well... found this method by frustratingly trying random things.
Click to expand...
Click to collapse
ill try this one. thanks for replying.
MikeyCriggz said:
Boot into recovery and you should be able to see your device in ADB.
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 03:48 PM ---------- Previous post was at 03:48 PM ----------
Nvm, just read the end of your post haha. Are you on TWRP or CWM?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
my desktop cant recognize my phone, even in recovery. im on cwm
manpildo said:
I had a quite similar problem after trying to install adb drivers (mtp wouldn't work). This is how I solved this:
Follow this guide (only the first part on installing adb driver). Once you have ADB drivers installed, go to device manager, right click on android adb device, choose update driver, pick from a list of device drivers on your computer and choose "MTP USB Device". Not only did I get storaging capabilities back, it preserved adb driver as well... found this method by frustratingly trying random things.
Click to expand...
Click to collapse
hey, i tried it and still doesnt work.
my laptop sees it as an unknown device and even if i browse for drivers, can' install.
up
Water Dispenser said:
up
Click to expand...
Click to collapse
Have you tried the universal naked driver?
Link
Or in the past I've used WUG's tool kit just for the driver installation part WUG's
What OS are you using on your PC
mrhiab said:
Have you tried the universal naked driver?
Link
Or in the past I've used WUG's tool kit just for the driver installation part WUG's
What OS are you using on your PC
Click to expand...
Click to collapse
im using win7 and win8
when i plug my phone on win7, nothing happens.
but when i plug it in on win8, this shows up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then this shows up on the device manager
then if i install any adb driver, either wugs toolkit or nexus 4 toolkit, etc. this shows up
and then this again
I'm currently having the same issue now, on cm10 4.3 and now my crap doesn't want to read. I switched to another lap top and I'm keep getting this. I even tried switching USB cables and no luck at all.
Sent from my Nexus 4 using xda app-developers app
Android SDK?
Nexus 4 - PA rom and franco kernel
reiko09 said:
I'm currently having the same issue now, on cm10 4.3 and now my crap doesn't want to read. I switched to another lap top and I'm keep getting this. I even tried switching USB cables and no luck at all.
Click to expand...
Click to collapse
and now my problem is how will i flash a rom
be careful not wiping your phone.
also try what others told me, flash to stock rom. it might fix the issue
and also, if that fixed it, let us know. :good:
If someone has problems installing the official Motorola adb and fastboot drivers for Windows, try the following, this works for me:
1. download the UniversalADB driver from @Koush here: https://github.com/koush/UniversalAdbDriver
2. install it
3. locate the file android_winusb.inf in the folder (may vary) x:\Program Files\ClockworkMod\Universal Adb Driver\usb_driver
4. open it with any texteditor
5. add the following two lines (somewhere in the devices section) and save the file:
Code:
MotorolaADBInterface = USB_Install, USB\VID_22B8&PID_2E76&REV_0228&MI_01
MotorolaBootLoaderInterface = USB_Install, USB\VID_22B8&PID_2E80&REV_0100
6. let Windows install this driver from koush's directory once in adb mode and once in fastboot mode (two drivers!)
7. enjoy!
Work fine thanks
Is the phone recognized by RSD Lite in fastboot mode with these drivers?
I have the Motorola drivers, using Windows 7 SP1 32-bit.
With USB debugging enabled I get a "Mot Composite ADB Interface" device in device manager (Driver Version 2.0.1.0).
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
t-bon3 said:
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
Click to expand...
Click to collapse
Got the same with the universal ADB/fastboot drivers damn.
[edit]
The MotoG PID is missing in PST.ini and/or sdk_common.ini, maybe we have to add it manually or wait for a new RSDlite
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Worked great. Thank you
maty3ux said:
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Click to expand...
Click to collapse
Not yet, last version is 6.1.6
I do not understand this instruction:
shaftenberg said:
let Windows install this driver from koush's directory
Click to expand...
Click to collapse
Windows doesn't attempt to do anything when I connect the phone in ADB mode. Device Manager lists XT1034 under Other devices and says "The drivers for this device are not installed. (Code 28)". If I do "Update Driver Software" manually and direct it to the "ClockworkMod" directory, Windows says it cannot find driver software for the device. If I right click on the "android_winusb.inf" file and choose Install, Windows says the "file doesn't support this method of installation".
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Thank you!!
it works for me
i installed Motorola device manager and this application
reversegear said:
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Click to expand...
Click to collapse
that's right .. i didn't do that too and it works
I've tried this and when I try to install it, it says "The INF file you selected does not support this method of installation." What do I do?
Didnt work for my moto g
sir, i am really new at this backup thing.
i just want to backup my injustice save game, so that i can restore it to previous point if something goes wrong.
i downloaded latest version on universaladbdriver but still my laptop didnt recognised my MOTO G.
i want to use HELIUM/CARBON for backup and i cant proceed till this problem is removed
please help me, i am new to xda as well.
THANKS
my os is win7 32 bit
hey
same problem i cant install adb or motorola drivers in my pc windows 7 64bit. the links with drives dont work for me..any solution? i want to unlock my bootloaderrrrrrrrrrrr :silly::silly::silly: (when i start to install the adb drivers stuck )
https://www.youtube.com/watch?v=RDA8PpPSFuk here i found solution for me i hope u help guyz(turn the music off )
Gronnd said:
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
Click to expand...
Click to collapse
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
nuri-d said:
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
Click to expand...
Click to collapse
To solve this when u are in ADB go in device manager, find ur phone with yellow exclamation mark ( !), right click, insta driver-> manual-> android single sooner ADB interface! It will work like a charm!
Sent from my XT1032 using XDA Free mobile app
I had a similar problem on W7 x64, no driver available for my phone (Moto G LTE, XT1039) even with the Universal ADB driver from CWM and the two lines of the first post added in the INF file.
But, you can notice that all Motorola phones in the android_winusb.inf file refer to the same driver : MotCompositeInterface.
So I went to the Device Manager, found my phone, chose to Update the driver, Find a driver from my computer, Choose from List (sorry if the names are not accurate, my Windows version isn't in English).
Then, you can select ClockworkMod, scroll down to Mot Composite ADB Interface and choose it as your driver.
It worked for me (both in adb and fastboot mode), I was able to unlock my bootloader and flash a recovery using it.
Hope this helps !
Hi, I tried all the solutions in this post unsuccessfully, but I found one here: stackoverflow.com/questions/22217792/android-moto-g-mobile-doesnt-show-in-the-devices-list-of-eclipse
that is the simplest and the only one that worked for me.
Download 'Adb Driver Installer' from here adbdriver.com/downloads/
after this connect your Moto G and start the AdbDriverInstaller.exe it will list your device and then press install.
Click to expand...
Click to collapse
Hello N4 Owners/Users.
lately I've been working on IOS & iCloud Activation Lock Security, which is a Job I honestly do not wish you have, because is not a great business at all but, going more deep in this post I'm glad to post it because I've been trying to send iCloud Accounts stored on a PDF at my Nexus 4, a device that I've purchased last month at eBay and is incredible how this device with Unofficial ports runs faster and without bugs, of course using PURE Nexus ROM.
first things first, I must specify that I was sideloading ZIP's, APK, ROMS through ADB SIDELOAD commands, so that the first sign of a properly working USB Port, I didn't noticed yet that I was unable to set up my device as MTP and transfer photos or WhatsApp Folder to my PC.
2 weeks later I've noticed that MTP was not working, even changing "Charge Option" to "Transfer Files" so I just put my knowledge on going, the first thing was download the USB driver at Google SDK webpage, which delivers USB Drivers apart instead with the whole SDK, I've just proceed to download it, I've installed it and for my surprise the MTP was still not working...
what do now ?
Steps:
1. Download the proper driver designed by google
Google Nexus 4 Drivers.
2. Make sure your PC is not on secure boot, for this you should reboot your PC and enter to BIOS Setup to make sure secure boot is not activated, if it is, please turn it off.
3. reboot again and let your PC boot, you may notice that the boot sequence UI display a little messed up, but is normal.
4. go to UWP Settings and Select "UPDATE & SECURITY"> "RECOVERY"> "Advance startup" and hit at "Restart Now"
5. your PC is going to restart again & you'll see a menu of likely 10 or 9 options, we need deactivate the option 7.
7). Disable Driver Signature Enforcement.
Click to expand...
Click to collapse
doing this your PC will restart again or maybe it just boot the Windows or UEFI Logo.
6. Find & Run CMD as administrator and execute the code below.
bcdedit /set TESTSIGNING ON
Click to expand...
Click to collapse
Restart your PC Again.
wait, you need the MTP or really are you craying for such restarts?
okay, that's what I though.
7. Disable ADB on your device and connect it to PC, Open device manager and look for "Android ADB Interface"
8. Right Click on the device and select "Update driver", Select "Browse My Computer for driver software"
9. locate drivers folder you've already downloaded following this guide and after that, you must have this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select "Let me pick from a list of available drivers on my computer"
If are 2 MTP entries, install them and reboot your PC, and that's all people, MTP working.
Now go back at CMD as Administrator and set this
bcdedit /set TESTSIGNING OFF
Click to expand...
Click to collapse
Now Restart and enter at BIOS, restore secure boot, done!
Hit "thanks" button if this helped you recovering MTP Access and your PC at your N4.
If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.
I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.
Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.