Recently, I have not been able to get my Nexus 4 to show up in my computer. I am able to use ADB and the drivers work fine, but when I connect my Nexus 4 it will not install the drivers for MTP. Rather, it will say it has the correct drivers installed, but it cannot start (Code: 10) and the icon for the device has a yellow exlamation mark next to it. I tried switching it between MTP and PTP as well as enabling and disabling USB Debugging, but it wont show up. Next, I decided to try to switch ROMS, as well as uninstall and re install all the drivers for the phone. No matter what I do I am able to connect to the phone through ADB, but MTP will give me the same error over again. Even on PTP my PC wont install the drivers for the phone.
I have looked through numerous threads and tried all kinds of solutions people have suggested, but none of them have worked for me. I've even tried switching between USB ports, cords, and computers (32 bit, 64 bit) and have tried plugging it into a new computer which i have never plugged the phone into, and nothing at all will work.
I am really at a loss here as I have spent many hours going through the solutions posted on these forums and others. I use USB for backing up my device as well as adding files etc. , and I dont want to do anything with my phone without being able to connect to it by USB at the very least. Airdroid will work as a temp. solution but it is way too slow when i transfer bigger files. My Nexus has worked fine with MTP since I bought 3 months ago, and even after rooting and updating the MTP has still worked regardless. I am running Windows 7 ultimate 64 bit, and my phone is on 4.3.
To anyone who will tell me to look on other threads I realize there are a ton of them out there, but I have tried using so many of the methods described, and none of them have worked.
Is there anyone that can help me with this problem? My phone is having issues and I need to backup up my stuff so I can flash to stock, factory wipe, etc.
Sent from my Nexus 4 using xda app-developers app
What rom and kernel are you running? Have you tried on stock firmware and stock kernel, with USB Debugging turned off? It sounds like an issue with the software in your phone.
Also when you connected your device, look in Device Manager and tell me the exact name listed for your Nexus 4, it should be saying "Nexus 4" or "Google Nexus 4 ADB Interface".
You can back up your files through adb: adb pull /sdcard/ C:\backup\
Instead of AirDroid you can try WorkGroup/Samba sharing. Enable a Workgroup shared folder on your PC then use ES File Explorer to access it and transfer file that way.
Here is my system info:
{
"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"
}
I have tried enabling and disabling debugging but it doesn't make much of a difference. It'll show up as MTP USB Device under portable devices with a yellow exclamation mark next to it, as well as Google ADB Interface Device under Android Device. Sometimes it will show up in Other Devices as Nexus 4, but then it install the drivers for ADB and it goes away.
I have also tried getting it to connect with AOKP milestone 2 (4.2.2) and the latest version of Carbon ROM which was also 4.2.2. I had Franco.kernel installed on both of these. The only thing I haven't done is a factory reset of all my data or flash back to stock rom.
Thanks for the backup tips I'll try those to see if I can get everything off it.
Sent from my Nexus 4 using xda app-developers app
Try uninstalling the driver, select the checkbox option to delete the files as well. Then reconnect it while in ADB mode and use the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=2263822
Also this will sound strange, but on your Pc, go into "Disk Manager" and make sure there are no blank partition or disk that might vaguely resemble your device. If there is one and without a driver letter, assign to it any drive letter.
Make sure there aren't conflicting ADB or USB drivers from other Android device, if there are, remove them.
Try live booting into Ubuntu 13.10, if it still can't copy your files, the phone is the problem.
Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.
Well let me know when it stopped working.
sent from xda premium app
Oh, one more thing. Is there a way for me to know what I can put onto the folder that shows up in the windows file explorer. Sometimes, I will put a folder in /sdcard, and it won't show up on the computer. It is really confusing sometimes when I need to move certain files to my computer.
Microsoft's MTP is a ****ty protocol, that's just my opinion.
The new files won't show up if it's not been read by the Media Server (I think), you have to do a media scan and replug the phone. If you still don't see it, just reboot the phone and let it scan the files for a few seconds before plugin it in. You should be able to move any files to the phone, just ignore the warning if it say the file might be incompatible.
sent from xda premium app
I often have to disable/uninstall the ADB device in Windows device manager to get MTP working...but that was on a Windows XP machine.
afff53 said:
Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.
Click to expand...
Click to collapse
Something similar happened to me once. I reinstalled the drivers several times unsuccessfully and then it just started working. It seemed like a Windows 8 issue to me but I never determined for sure what caused it. Good luck.
I solved my problem at this way. Maybe it will help.
Related
I'm on rooted 4.3. When I connect my N4 to the PC in MPT mode, the device doesn't show up in "My Computer. When I connect in PTP mode, it shows up as "internal storage". When I click internal storage, it shows two folders, "DCIM" and "Pictures". It used to show a higher root folder like "sdcard", I think. How do I get it back to show sdcard. I've tried different USB cables and usb ports. I've also tried to connect to the pc with the N4 screen both unlocked and locked.
I've also tried uninstalling the device in device manager (when plugged in) and reconnecting the phone to reinstall.
shobuddy said:
I'm on rooted 4.3. When I connect my N4 to the PC in MPT mode, the device doesn't show up in "My Computer. When I connect in PTP mode, it shows up as "internal storage". When I click internal storage, it shows two folders, "DCIM" and "Pictures". It used to show a higher root folder like "sdcard", I think. How do I get it back to show sdcard. I've tried different USB cables and usb ports. I've also tried to connect to the pc with the N4 screen both unlocked and locked.
I've also tried uninstalling the device in device manager (when plugged in) and reconnecting the phone to reinstall.
Click to expand...
Click to collapse
What about other PCs?
shobuddy said:
I'm on rooted 4.3. When I connect my N4 to the PC in MPT mode, the device doesn't show up in "My Computer. When I connect in PTP mode, it shows up as "internal storage". When I click internal storage, it shows two folders, "DCIM" and "Pictures". It used to show a higher root folder like "sdcard", I think. How do I get it back to show sdcard. I've tried different USB cables and usb ports. I've also tried to connect to the pc with the N4 screen both unlocked and locked.
I've also tried uninstalling the device in device manager (when plugged in) and reconnecting the phone to reinstall.
Click to expand...
Click to collapse
What drivers and OS?
Thanks for the responses. I just tried another computer with the same usb cable and it connects fine in MPT mode. It shows up as Portable Devices --> Nexus 4 under device manager.
On my computer where its not working, its Windows 7 and in device manager its listed as Android Device -- Android ADB Interface. I'm not sure what to do to get it to work on my computer as it does on the other one.
shobuddy said:
Thanks for the responses. I just tried another computer with the same usb cable and it connects fine in MPT mode. It shows up as Portable Devices --> Nexus 4 under device manager.
On my computer where its not working, its Windows 7 and in device manager its listed as Android Device -- Android ADB Interface. I'm not sure what to do to get it to work on my computer as it does on the other one.
Click to expand...
Click to collapse
Completly uninstall and reinstall every Android related driver on your PC.
abaaaabbbb63 said:
Completly uninstall and reinstall every Android related driver on your PC.
Click to expand...
Click to collapse
I uninstalled the drivers and selected the delete driver files option when uninstalling. I then plugged the phone back in to PC and it reinstalled one of the drivers and I am now able to see all the folders I'm supposed to in internal storage. There is one driver that didn't install, however. The screenshot below shows the portal devices --> nexus 4 drivers installed, however, the other devices --> nexus 4 drivers didn't install. I don't know if this is an issue or not but i'm happy i'm able to access the internal storage now.
{
"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"
}
shobuddy said:
I uninstalled the drivers and selected the delete driver files option when uninstalling. I then plugged the phone back in to PC and it reinstalled one of the drivers and I am now able to see all the folders I'm supposed to in internal storage. There is one driver that didn't install, however. The screenshot below shows the portal devices --> nexus 4 drivers installed, however, the other devices --> nexus 4 drivers didn't install. I don't know if this is an issue or not but i'm happy i'm able to access the internal storage now.
Click to expand...
Click to collapse
I think that the error is adb driver related.
I too had the same problem in my office laptop. I just unchecked USB debugging option and it started showing the folders which it used to show.. I'm not sure whether this will fix your problem now, since you have reinstalled things..
PS: When I connected it to my personal laptop, I did not have this problem.
Sent from my Nexus 4 using Tapatalk 4
Hello, since the update to android 4.3 my Nexus 4 is no longer recognized by my Windows 7/8 computers.
I have tried many drivers and software NRT, I also formatted several times.
I've used both connections (MTP and PTP) and USB debugging mode.
Several micro usb cables
Now I know what to do and the problem is that the phone to bootloader unlocked so I do not know if Google agree to exchange it for free.
Desolated if I make mistakes but English is not my native language
Thank you in advance
I don't think you need to exchange it and Google should exchange it even if the bootloader is unlocked, provided you factory reset it I guess. And to re-lock the bootloader you just have to boot it into fastboot mode and type in the command line: fastboot oem lock
(Just follow this guide to return the phone to stock if you need: http://forum.xda-developers.com/showthread.php?t=2010312)
As for recognizing the device, maybe the MTP driver become unrecognized or conflicted, check in the Device Manager of your computer it should be called "Nexus 4" under Portable Devices. If it's not, right click on it and uninstall it. Then reconnect the phone and let it reinstall the driver, also try switching on and off USB Debugging option in the Developer mode.
If that still don't work, try this method: http://forum.xda-developers.com/showpost.php?p=35667806&postcount=23
Because this is likely a driver issue even if you get a new Nexus 4 your computer still might not recognize it. The issue is likely on your computer side, unless your phone's microUSB port is damaged somehow.
Thank you for answering.
I tried the command to lock the bootloader but it does not work because my device is not recognized
That catches image
{
"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"
}
You need to install the adb/fastboot driver, again, follow the link I posted for instruction. But you can download the Universal Naked Driver here: http://forum.xda-developers.com/showthread.php?t=1996051
sent from xda premium app
I tried to update the drivers but Windows told me that the driver is already up to date
Uninstall it and also check the option to delete the driver, then rescan the devices and reinstall it.
sent from xda premium app
Without success
In that case I suggest do a clean Windows 7 installation and reinstall the drivers on a clean system . Or wipe out Windows completely and install the latest Ubuntu which will detect your device automatically.
OK I installed ubuntu, I 'll let you know
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
androboy06 said:
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
Click to expand...
Click to collapse
Did you try to update sdk manager, provided it is installed on your C: drive?
This 1st step has proven to be helpful for re-installing drivers which let you access adb and fastboot.
Bonne chance, mon ami
Yes, the SDK is installed and the drivers google
Merci
androboy06 said:
Hello, since the update to android 4.3 my Nexus 4 is no longer recognized by my Windows 7/8 computers.
I have tried many drivers and software NRT, I also formatted several times.
I've used both connections (MTP and PTP) and USB debugging mode.
Several micro usb cables
Now I know what to do and the problem is that the phone to bootloader unlocked so I do not know if Google agree to exchange it for free.
Desolated if I make mistakes but English is not my native language
Thank you in advance
Click to expand...
Click to collapse
I had simular issue.However if i am connected to USB and activate USB debugging, then windows sees the Nexus4 again as an MTP device, and stops as soon as i disable it. I know you said you tried that but still, thought i'd let you know.
I've ssay but thank you anyway
androboy06 said:
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
Click to expand...
Click to collapse
Don't exchange it. After uninstalling the drivers, go to pdanet and get the drivers there. I was having the same issue and that fixed it
I've tried, maybe my problem is hardware and not software
androboy06 said:
I've tried, maybe my problem is hardware and not software
Click to expand...
Click to collapse
can you be precise bro
is it windows 8 or windows 7??
I have two PCs, one with Windows 7 and one with Windows 8
USBDView(download it), remove anything android and nexus involved, reboot and replug
Sent from my Nexus 4 using xda app-developers app
Hello, I have the same problem.
My phone is in the official service center,and the last information I have is that it needs logic board replacement which costs aproximately 230 euros.
They would repair it under warranty if it wasn't rooted and flashed with TWRP. Of course, I dont want to pay that amount of money, so I'll try to find to buy a N4 with cracked screen and/or back and take the board from it.
So, if anyone has the same problem, the only solution is replacing the logic board or using ADB over wifi if the kernel supports that feature. Nothing else will work
When I plug my Nexus 4 into a PC (only tried Win7 so far but multiple systems) Windows reports 'The USB device has failed, please remove device'. It repeatedly tries to communicate with the Nexus 4 while plugged in and connects and disconnects every few seconds but at no point is recognized as a Nexus 4 or do I get a chance to install drivers. This occurs with USB debugging on/off, MTP on/off, CWM/TWRP USB mounted or not. I have tried various ROMs all with the same result. It still charges though.
I recently changed the USB daughterboard as the socket was becoming temperamental while charging. I can't remember the last time I transferred data with a cable as I normally use bluetooth, wireless FTP etc so I can't be sure the problem has only been occurring since installing the new USB board.
Interestingly enough, I discovered after not being able to boot a ROM, that I could still push data to the device via fastboot. To me it seems if the hardware was faulty then it would not allow data to pass in any mode. Correct me if I'm wrong but as far as I know USB always uses pins 3+4 for data and 1 + 4 for +5V and ground respectively so it's not like the hardware is being used differently.
I have ordered another LG USB daughterboard along with a new battery as mine is on deaths door, so I'm hoping this new USB board will solve my problem...
Do you know why can I only pass data over the USB and get the device recognized in bootloader using fastboot?
Have you checked your usb in device manager when you're normally booted or in recovery? It uses different usb drivers than when you're in the bootloader. Check to see if its a driver issue.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Have you checked your usb in device manager when you're normally booted or in recovery? It uses different usb drivers than when you're in the bootloader. Check to see if its a driver issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is half the problem. Because Windows enters a sort of loop where it keeps trying to recognize the device, it does not show up for more than a split second in device manager and when it does, it is recognized as unknown device. If I am fast enough to right click on the unknown device and try to manually point drivers at it, Windows tells me the best drivers are already installed. Obviously Windows has no idea what my Nexus is at this point.
I have connected in bootloader and the phone shows up normally in device manager as Android Device etc. I have updated the drivers manually pointing Windows to C:\android-sdk\sdk\extras\google\usb_driver but this does not help trying to connect in fully booted MTP mode when the recognition loop starts again.
I have been working my way through this thread with no luck so far. Other people appear to have had the same problem and just given up.
I am going to try my Nexus on an XP machine tomorrow and see what happens.
I recommend using the nexus root toolkit and following the driver installation guide. I've had similar problems in the past but reverting to this program and following the basics has always led to working results.
Sent from my Nexus 4 using XDA Free mobile app
Solved!
Ok, so I know this may not help many people apart from simply reiterating the fact USB sockets do fail so if you get stuck with Windows recognizing the device bear this in mind. Although one thing I have learned is that it is possible for such a failure to occur which allows data to still be passed in boot loader but not in MTP mode. I would still be interested to hear if anybody knows why/how this is possible?
After hours of trying different combinations of peoples methods of installing drivers It turns out the USB socket/daughterboard was to blame.
I replaced both the USB board/socket and battery and my Nexus is like a brand new phone. As soon as I plugged it in to my PC (using an old non LG cable) Windows recognized it, installed drivers and mounted it ready for me to browse. No manual driver installation required. Data can be transferred normally. It just works as I expect an Android phone to.
Thank f**k for that
{
"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 I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.
ahs646 said:
So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can't reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.
Click to expand...
Click to collapse
Press and hold Volume + and Volume - with Power toghether.
Stay press until it don't self-reboot itself.
When the logo about bootloader will load up, you can choose what to do :
1 ) Reinstall the stock roms 4.4.4 (https://dl.google.com/dl/android/aosp/occam-ktu84p-factory-b6ac3ad6.tgz)
2) If you still have a modify recovery (CWM or TRWP) you can run it and install zip from sideload. Put the rom zipped you wanna install where did you have adb tools and run "adb sideload <file.zip>" and wait it should be install.
If that dosen't work, you need to use download mode from LG ( for the moment i can't found a guide to do it, check on XDA / Google).
Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.
ahs646 said:
Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.
Click to expand...
Click to collapse
Did you try download mode ?
{
"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"
}
I don't think I've seen this "download mode." Where is this - on the phone (in recovery?) or through adb or sideload. The problem seems to be (and I see there are a few others right now with the same problem) that windows sees that the phone is connected, but then there seems to be a driver error such that the device doesn't show up in explorer, and abd and fastboot can't see the phone either.
I've tried different drivers, but haven't systematically gone through every single option so far, which is my next stop. Is any one driver option more failsafe than the others? Also, perhaps related - in the past, any time I've installed the drivers and connected to my phone from my pc, it never seems to "stick." Invariably, I can't access the phone through MTP after a short while (maybe after a reboot?). Recently I found updating the driver to just a Portable Device/Standard MTP USB device driver (i.e. not Google, Samsung, Android, etc) made it work. So now I feel the driver troubleshooting part is even longer and more complicated - go through all of the uninstall/reboot/install with the four Android options, then all of the generic Windows options. So I was just hoping that someone out there might have already cracked this and could point me in the right direction.
Also, in digging through some posts on reddit on related problems, someone said that Windows Media Player is somehow critical for MTP functionality. Is this the case? I had never heard this before. I don't have WMP installed, and in trying to install it, have come up with a Windows error. I'm not clear on the relationship between MTP and ADB/fastboot. Is MTP necessary for the file transfer, or is that not relevant here?
And one final question - to use adb/fastboot, do I need to be in bootloader or in recovery? To install the drivers, do I need to be in either bootloader or recovery?
Thanks so much.
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.