Database Develop

Nexus not recognized by ADB

SO recently got a nexus one and for some reason i cant get it to be recognized by adb, i have tried everything, updating drivers, reinstalling adb, trying diferent usb cables, different usb ports, but for some reason no matter what i try adb doesnt recognize any device. it recognizes my atrix just fine, but not the nexus. and the nexus is also rooted and has cwm but somehow the bootloader says ship s-on. it all seems prtty wierd. any ideas?

I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217

Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.

baseballfanz said:
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
already tried that driver and same thing
Theshawty said:
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
Click to expand...
Click to collapse
still nothing with reinstalling
gunna try restoring stock firmware and see what happens
not even going back and flashing stck firmware will let it connect to adb

USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"

Aceyo said:
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Click to expand...
Click to collapse
as i told the other 2, it is not a driver issue, it turns out the guy i got it from had work done on it before it was shipped, thinking something internal is the issue

How I fixed the MTP issues on Nexus 7

Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits.
Yesterday, I checked the optional Windows updates and noticed a new Samsung MTP driver. So I updated the driver and when I connected the tablet running on 4.1.1, the device was not detected. Today, after I got the OTA update, I tried again to connect the tablet and it failed to detect the device properly.
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
2) Right click on it and select Properties.
3) Click on Change Settings button.
4) Go to Driver tab and click on Uninstall button.
Make sure you check the Delete Driver option, when you uninstall the driver.
I did not have to reboot the computer, by simply connecting the tablet Windows detected the new hardware and reinstalled the proper drivers.
Now I can access both my Nexus phone and tablet, using the same cable and through adb.
Not sure if the combination of both 4.1.2 and new Samsung drivers helped, but the above steps fixed the MTP detection issues I had. Check the Microsoft driver date, is from 2006???
{
"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'm on Android 4.2.1 and I tried your method but I got a "No Driver Found" error.

Fixed !
I'm on 4.2.1 stock ROM too and it worked perfectly for me, as described !
Thank you very much !:good:

Teck, nobody online aside from you could do anything with this, your instructions fixed it.
So, two questions. Do you have a paypal, and if you do, what's the price of your usual beer?
I'm buying you one.
also any idea on how to fix the same issue on an ipod touch?

If anyone having problems turn off USB debugging and device will show up
Sent from my HTC One X using xda premium

acidspider said:
If anyone having problems turn off USB debugging and device will show up
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I had to do. Just place your files inside your internal memory before you turn on your debugging.
Sent from my Nexus 7 using xda app-developers app

Another way of fixing this on Windows 8: This problem may happen because you have the Google ADB driver from the Android SDK installed. Windows will pick the ADB driver over the MTP driver, even when USB debugging is turned off on the Nexus 7. It also comes back when you upgrade from Windows 8 to Windows 8.1. To fix this:
Plug the Nexus 7 in and make sure USB mode is set to MTP
Run devmgmt.msc
Locate the ADB driver, which may be under "Android Devices" or "ADB Devices"
Right-click on it and select "Update driver software"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
With "Show compatible hardware" checked you should see two drivers under "Model":
"Android ADB Interface"
Either "MTP USB Device" or "Composite USB Device"
Select "MTP/Composite USB Device" (that is, the one that isn't "Android ADB Interface") and click Next.
Device should now appear as an MTP device.
Confirmed working with the Nexus 7 2013 as well.

Thank you, that worked exactly how you listed it.

TheBeano said:
Another way of fixing this on Windows 8: This problem may happen because you have the Google ADB driver from the Android SDK installed. Windows will pick the ADB driver over the MTP driver, even when USB debugging is turned off on the Nexus 7. To fix this:
Plug the Nexus 7 in and make sure USB mode is set to MTP
Run devmgmt.msc
Locate the ADB driver, which may be under "Android Devices" or "ADB Devices"
Right-click on it and select "Update driver software"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
With "Show compatible hardware" checked you should see these two drivers under "Model":
"Android ADB Interface"
"MTP USB Device"
Select "MTP USB Device" and click Next.
Device should now appear as an MTP device.
Click to expand...
Click to collapse
Reinstalled ADB drivers to try this... MTB device does not appear on list.
Why can't someone just post a link to the drivers needed for MTB to work?

drumtrucker said:
Reinstalled ADB drivers to try this... MTB device does not appear on list.
Why can't someone just post a link to the drivers needed for MTB to work?
Click to expand...
Click to collapse
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!

Hi. Totally confused Nexus 7 noob
TECK said:
Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits....
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
Click to expand...
Click to collapse
I've been reading and searching and reading and.... on my Win 7/64, there is no "Other" or "Unspecified Devices" in Device Manager. There is no Nexus 7 under any option in Device Manager. {sigh} Device Manager also does not show either "Android Devices" or "ADB Devices."
I've tried having Windows search for new hardware (it found my wireless router, not my Nexus 7).
I've swapped out the USB cables and tried different USB plugs on the CPU and on a powered hub (the plugs all work with other USB devices).
The Nexus WILL read a thumb drive, so the plug on the Nexus works
I tried turning off the Nexus, rebooting the computer and then plugging the Nexus back in and turning it on. Nothing, Windows did not see it "arrive."
"Safely remove hardware" does not see it.
I looked for a folder on the C: drive that has google drivers in it, no such folder.
I unlocked Developer Options and tried switching between Camera and MTP modes.
I turned off USB debugging.
I have a semi-solid memory that I WAS able to plug the Nexus in and TRF files across a USB cord when I first got it (mid-December) -- but I'm not 100% sure (I'm old and my brain leaks...).
My Win 7 is completely updated, according to MS. I'm baffled. What can I try next? Thanks. (Sorry this is long -- I DID watch the funny noob movie when I registered, and tried to balance: "be short" with "provide all the info.")

It works for me, thank you very much!

SnowTao said:
My Win 7 is completely updated, according to MS. I'm baffled. What can I try next?
Click to expand...
Click to collapse
Try usbdeview from Nirsoft, it will show you what device (if any) the Nexus 7 is registering as when you plug it in.

Doesn't Nexus 7 Toolkit (the tool for rooting and all) also install some drivers?
I haven't really have any problems connecting N7 to W7 (lol) stock, but since I've rooted it (and the toolkit installed their own drivers), I've had even less problems.
Only thing I don't like is MTP itself, I'd prefer removable drive, so I could easily manage files and all from total commander, but that's a design flaw, not a bug.

stalnie betw.
drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
You the man! This worked for me too...was getting really frustrated seeing that MTP yellow error icon and not having my N7 appear in explorer during USB debugging mode.

thanks!
TECK said:
Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits.
Yesterday, I checked the optional Windows updates and noticed a new Samsung MTP driver. So I updated the driver and when I connected the tablet running on 4.1.1, the device was not detected. Today, after I got the OTA update, I tried again to connect the tablet and it failed to detect the device properly.
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
2) Right click on it and select Properties.
3) Click on Change Settings button.
4) Go to Driver tab and click on Uninstall button.
Make sure you check the Delete Driver option, when you uninstall the driver.
I did not have to reboot the computer, by simply connecting the tablet Windows detected the new hardware and reinstalled the proper drivers.
Now I can access both my Nexus phone and tablet, using the same cable and through adb.
Not sure if the combination of both 4.1.2 and new Samsung drivers helped, but the above steps fixed the MTP detection issues I had. Check the Microsoft driver date, is from 2006???
Click to expand...
Click to collapse
Thanks! Simple and brilliant

drumtrucker said:
Reinstalled ADB drivers to try this... MTB device does not appear on list.
Why can't someone just post a link to the drivers needed for MTB to work?
Click to expand...
Click to collapse
TheBeano said:
Another way of fixing this on Windows 8: This problem may happen because you have the Google ADB driver from the Android SDK installed. Windows will pick the ADB driver over the MTP driver, even when USB debugging is turned off on the Nexus 7. To fix this:
Plug the Nexus 7 in and make sure USB mode is set to MTP
Run devmgmt.msc
Locate the ADB driver, which may be under "Android Devices" or "ADB Devices"
Right-click on it and select "Update driver software"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
With "Show compatible hardware" checked you should see these two drivers under "Model":
"Android ADB Interface"
"MTP USB Device"
Select "MTP USB Device" and click Next.
Device should now appear as an MTP device.
Click to expand...
Click to collapse
I tried this, but it did not work for me. With "MTP USB Device" driver installed, I still could not see my Nexus 7 in Window Explorer. I tried deleting drivers, installing, updating, to no avail. Finally, one of the times I picked "Let me pick from a list of device drivers on my computer", I saw a "USB Composite Device" in the list. I picked it. It installed, and suddenly my Nexus 7 was visible in Windows Explorer. Here is the info on the driver:
Driver Provider: Microsoft
Driver Date: 6/21/2006
Driver Version: 6.1.7600.16385
Digital Signer: Microsoft Windows.
I have a Nexus 7, running Android version 4.2.2
The computer I was having trouble with is running Windows 7 Pro. I have another computer, running Windows 7 Home Premium. It has always been able to see the Nexus 7 in Windows Explorer. It has the same *old* driver installed. I did not know where to get that driver from. I just hit on it using the procedure above.
Here are some of the drivers which did NOT work for me:
Driver Provider: Google Inc.
Driver Date: 5/24/2012
Driver Version: 6.0.0.0
Driver Provider: Google Inc.
Driver Date: 8/27/2012
Driver Version: 7.0.0.1

drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
this worked perfect on my n4 win8x64
thanks
stupid google and lg, thanks a lot for not providing good drivers or usb disk mode (like nokia)

worked fine for me also, thnx a lot

Thanks Bro!!!
TECK said:
Since I got Nexus 7, I was not able to use it as MTP device in Windows 7 64bits.
Yesterday, I checked the optional Windows updates and noticed a new Samsung MTP driver. So I updated the driver and when I connected the tablet running on 4.1.1, the device was not detected. Today, after I got the OTA update, I tried again to connect the tablet and it failed to detect the device properly.
These are the steps I completed, that fixed the MTP issue:
1) Open the Devices and Printers in Control Panel, the tablet should be listed under Unspecified devices.
2) Right click on it and select Properties.
3) Click on Change Settings button.
4) Go to Driver tab and click on Uninstall button.
Make sure you check the Delete Driver option, when you uninstall the driver.
I did not have to reboot the computer, by simply connecting the tablet Windows detected the new hardware and reinstalled the proper drivers.
Now I can access both my Nexus phone and tablet, using the same cable and through adb.
Not sure if the combination of both 4.1.2 and new Samsung drivers helped, but the above steps fixed the MTP detection issues I had. Check the Microsoft driver date, is from 2006???
Click to expand...
Click to collapse
Literally banged my head on computer before finding your solution.. Just was not deleting the old drivers. Uninstalled it so many times. Deleting the old drivers is the key.
However, still my TV is not liking the MTP. Banging my head on TV now.

Nexus 7. Windows 8.1 connection

Hello I'm trying connect my Nexus 7 (2013) Tablet to pc and its doesn't working for me.
Windows 8.1 64 Bit.
Please Help.

Ok I Fixed a ADB drivers but now i cant connect Tablet -> PC ( MTP)

Dude, this is already a known problem with the first generation and second generation nexus 7s when connecting via USB to a windows 8 laptop. I've had this problem myself and I contacted Asus support which was really helpful but the Asus representative could not fix my problem. There was some talk of a PC-sync update which would be carried out to nexus 7 devices, but it has been proven untrue. This problem however occurs 85 percent of the time when attempting to obtain adb with the computer.
There are some things you can try though,
1. You can go to nexus 7 developer options and turn USB debugging on and turn on camera type connection at the same time. Delete any former file connections which were installed on the computer at first attempt FIRST!
2. Disable windows 8 signature check. Please Google how to disable drivers check windows 8.
3.download drivers from many different sources, I recommend the Asus drivers, universal or Google drivers for the nexus 7 then install the drivers manually on PC.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 06:53 PM ---------- Previous post was at 06:50 PM ----------
eWich said:
Ok I Fixed a ADB drivers but now i cant connect Tablet -> PC ( MTP)
Click to expand...
Click to collapse
Use ptp with USB debugging and turn off mtp. That method worked for my first generation nexus 7 when trying to confirm adb on windows 7.
Then to check if it is working, please open your command line or cmd from your windows 8 computer and type in adb devices exactly as I just typed it and if the command line picks up your device, good to go. Remember the device has to be plugged first.
Sent from my Nexus 7 using XDA Premium HD app

Nothing Working ;/

eWich said:
Nothing Working ;/
Click to expand...
Click to collapse
Well my friend for now there is no solution, my suggestion is that you use an alternate method to share file with your nexus 7 to your computer, use a app called airdroid. Download it for free at the Google play store, let's you easily transfer files from your device to the computer using the internet, turn on airdroid on your device and then go to the airdroid website on your computer, log in and then you are good to go. Sorry that you couldn't fix the issue as well.......
Sent from my Nexus 7 using XDA Premium HD app

Thx for help

No one here can help. It's a Windows/Driver issue. Thank Microsoft.

GldRush98 said:
No one here can help. It's a Windows/Driver issue. Thank Microsoft.
Click to expand...
Click to collapse
Try this with usb debugging on and MTP selected as a media device:
http://forum.xda-developers.com/showpost.php?p=46440030&postcount=25

Groid said:
Try this with usb debugging on and MTP selected as a media device:
http://forum.xda-developers.com/showpost.php?p=46440030&postcount=25
Click to expand...
Click to collapse
Nothing :<

I posted this a little ways back when I switched to 8.1:
http://forum.xda-developers.com/showthread.php?p=46589201
Windows 8.1 upgrade driver reinstall
Sent from my Nexus 7 using Tapatalk 4

annoyingduck said:
I posted this a little ways back when I switched to 8.1:
http://forum.xda-developers.com/showthread.php?p=46589201
Windows 8.1 upgrade driver reinstall
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
All I did was uninstall the adb composite interface driver, plug the Nexus back in and let it install on its own and I was back in business.
Sent from my Nexus 7 using Tapatalk 4

annoyingduck said:
I posted this a little ways back when I switched to 8.1:
http://forum.xda-developers.com/showthread.php?p=46589201
Click to expand...
Click to collapse
' Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP.'
I'm @ this moment and cant find MTP on list.. when i pick patch to google drivers its shows
{
"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"
}

For me I had to download Wugs Nexus Root Toolkit from the android dev section and use that to get all the drivers installed properly.

gamer649 said:
For me I had to download Wugs Nexus Root Toolkit from the android dev section and use that to get all the drivers installed properly.
Click to expand...
Click to collapse
I have NRT too ADB drivers are good but cant connect with MTP ...

Guys i found solution to connect Nexus 7 on Windows 8.1 YAY !!

Idont know what i did but when i connect nexus 7 (android booted up) it connect in mass storage mode. and when i boot into recovery or fastboot it loods into that mode auto. i guess i am having best of both words

I've solved it
So...
I've had almost the same problem with Nexus 7 (first gen) and 8.1 64 bit (non-prof).
Symptoms were almost the same - USB cable (to USB2 and/or USB3 ports) - and I was able to see Nexus 7 device in 'this comp' - and nothing more.
Solution to see (and transfer) folders/files _via_ usb cable is ridiculous, stupid and idiotic (all three together) - just turn on Bluetooth (and pair it with Win8.1 if it's not paired already) on Nexus 7 (usb connection remains in place)....
That's all...
exactly the same situation and solution to Nexus 7 (2013)

A solution... of sorts (here be dragons)
WARNING - this is how I fixed it on my system. I offer no guarantees that this will work for you. The folder and/or file names may well be different on your system. Do not delve into C:\Windows and C:\Windows\System32 without either knowing what you're doing (I've been administering Windows since 1998 and NT 4.0) or being prepared to restore from backup.
So, with that caveat out of the way, here we go.
After playing around with Helium, WugFresh, and more, while unlocking my Nexus 7, I had a rogue ADB driver on my system and no amount of uninstallation would kill it. This post (http://forum.xda-developers.com/showthread.php?p=46589201) gave me a clue. The "Nexus 7" device had three driver files, two of which were signed by ClockworkMod:
Code:
C:\Windows\System32\WdfCoInstaller01009.dll
C:\Windows\System32\WinUSBCoInstaller2.dll
So I deleted those two files and tried again. No dice. The driver files were restored and the device was still showing up as an ADB device instead of letting me browse the Nexus' storage via MTP.
I then went digging...
Windows 8.1 kept cached copies of those driver files in
Code:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_05f4ed2dfa7ff8b9
I removed that directory (the one beginning with "android") and reconnected my Nexus 7. This time Windows couldn't restore the ADB drivers from its cache (Plug & Play is useful, but not without its idiosyncrasies) so it installed the MTP storage driver just like I wanted.
I can now browse my Nexus 7 via USB on Windows 8.1

This worked for me.
I had this problem. What I did to fix it was that I installed WugFresh's Nexus Root Toolkit, removed the current drivers via Device Manager and removing the device USBDeview (from within NRT) and installed the Koush's drivers. I turned on USB Debugging with MTP selected and updated the driver software with Device Manager, selecting ClockworkMod -> Google Nexus ADB Interface.

Loganberry said:
WARNING - this is how I fixed it on my system. I offer no guarantees that this will work for you. The folder and/or file names may well be different on your system. Do not delve into C:\Windows and C:\Windows\System32 without either knowing what you're doing (I've been administering Windows since 1998 and NT 4.0) or being prepared to restore from backup.
So, with that caveat out of the way, here we go.
After playing around with Helium, WugFresh, and more, while unlocking my Nexus 7, I had a rogue ADB driver on my system and no amount of uninstallation would kill it. This post (http://forum.xda-developers.com/showthread.php?p=46589201) gave me a clue. The "Nexus 7" device had three driver files, two of which were signed by ClockworkMod:
Code:
C:\Windows\System32\WdfCoInstaller01009.dll
C:\Windows\System32\WinUSBCoInstaller2.dll
So I deleted those two files and tried again. No dice. The driver files were restored and the device was still showing up as an ADB device instead of letting me browse the Nexus' storage via MTP.
I then went digging...
Windows 8.1 kept cached copies of those driver files in
Code:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_05f4ed2dfa7ff8b9
I removed that directory (the one beginning with "android") and reconnected my Nexus 7. This time Windows couldn't restore the ADB drivers from its cache (Plug & Play is useful, but not without its idiosyncrasies) so it installed the MTP storage driver just like I wanted.
I can now browse my Nexus 7 via USB on Windows 8.1
Click to expand...
Click to collapse
Thanks brother, it works for me.

Cant write to storage via MTP (Or any other mode) from Windows 10 to OP3T

--- SOLVED see first post second page! ---
Hello XDA,
I am only able to read data on the phone when connected via USB on windows. On the phone itself I can change whatever I want ( Via ES-explorer for example) But in windows file explorer I can't. It will not tell me that I do not have proper writing rights, but instead just decides to freeze for 10 minutes everytime I try to make a file change, to eventually give me a beautiful
"windows explorer is not responding" pop-up
What I have tried :
-Rebooting,
-Reinstalling USB drivers,
-Switching USB debugging on and off,
-Reinstalling root,
-Installing the newest Oxygen OS update from February,
-used different cables (also an old micro USB with adapter) And nothing works.
This sucks because I was just trying to change my photography workflow from being Desktop based to being Android based..
Any suggestions ?
Greetings,
Thijs
www.instagram.com/thi_js
Edits: Clarify issue

i have the same problem be great to find a solution

Did you maybe noticed when this problem occurs to you? I know that one months ago it just did work. Should I reinstall Windows completely?

I've been talking to a few people and it's happening to them to on Windows 10 I think it's just a bug from a recent update try a roll back

lorfo123 said:
I've been talking to a few people and it's happening to them to on Windows 10 I think it's just a bug from a recent update try a roll back
Click to expand...
Click to collapse
How should one file a bug-report for windows 10 then, this can't be something that shouldn't keep unnoticed by them.
Did rolling back fix something for you, and how did you do so?

I've checked another Windows 10 computer which hasn't been updated and it recognises my one plus 3T so if you Google / YouTube windows 10 roll back it should work

Hmm this does suck. This means I cant be up to date on windows for now. Anybody have different suggestions?

1asbak1 said:
Hmm this does suck. This means I cant be up to date on windows for now. Anybody have different suggestions?
Click to expand...
Click to collapse
The only other thing I could suggest is using a virtual machine to run win 7

Did you try back usb ports?. My pc with windows 10 fails with the front ports.

Solution
Backup all the data in your internal memory and try the 'format data' option from twrp to wipe your internal storage. It could solve your problem, as it did in my case.

New solution, just done works!
Plug in your phone and on the computer go to device manager (have phone in MTP mode)
you'll find the phone as a unknowen device
right click on this select "update driver software..."
a window will pop up select "browse my computer for driver softaware"
then on the next bit select "let me pick from a list of device drivers on my comupter"
then you will have a box with "MTP Device" and "MTP USB device"
select "MTP USB device" hit next and it should work 100%

ayush2901 said:
Backup all the data in your internal memory and try the 'format data' option from twrp to wipe your internal storage. It could solve your problem, as it did in my case.
Click to expand...
Click to collapse
Which version of TWRP are you running? The thing is that If I afterward can't restore the data via USB haha, then the whole point of backing it up seems invalid

lorfo123 said:
New solution, just done works!
Plug in your phone and on the computer go to device manager (have phone in MTP mode)
you'll find the phone as a unknowen device
right click on this select "update driver software..."
a window will pop up select "browse my computer for driver softaware"
then on the next bit select "let me pick from a list of device drivers on my comupter"
then you will have a box with "MTP Device" and "MTP USB device"
select "MTP USB device" hit next and it should work 100%
Click to expand...
Click to collapse
This actually worked. Wauw.
Had to reboot a view times in order to get it in effect, nonetheless, THANKS let the creativity start again

Really,My A** is burnt while my phone showing messages to update,,, Fiunally donw..Thanks a lot...!!

super it works

This solution did not work for me. I am using W7 and OOS 5.0.3 rooted. Tried updating MTP drivers in W7, the phone shows up but no data shows in the drive. Still looking for a solution. Can someone please post W7 drivers that work for them? Thank you.

picollo7 said:
This solution did not work for me. I am using W7 and OOS 5.0.3 rooted. Tried updating MTP drivers in W7, the phone shows up but no data shows in the drive. Still looking for a solution. Can someone please post W7 drivers that work for them? Thank you.
Click to expand...
Click to collapse
When you connect the phone to pc do you get a notification on your phone with the USB options?

DirkGently said:
When you connect the phone to pc do you get a notification on your phone with the USB options?
Click to expand...
Click to collapse
yes I can select charge, mtp, ptp, or midi
in device manager sometimes the phone shows up with error 10, device cannot start
tried many different driver versions in updating driver

picollo7 said:
yes I can select charge, mtp, ptp, or midi
in device manager sometimes the phone shows up with error 10, device cannot start
tried many different driver versions in updating driver
Click to expand...
Click to collapse
I doubt there's much we can suggest that you haven't already tried. Try another cable/USB Port/uninstall device from Device Manager and let Windows find the driver. Hell, you probably did all that already.

DirkGently said:
I doubt there's much we can suggest that you haven't already tried. Try another cable/USB Port/uninstall device from Device Manager and let Windows find the driver. Hell, you probably did all that already.
Click to expand...
Click to collapse
Haha, yeah. Does anyone have links to the drivers that work for them?

Question Unable to send files via USB

Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?

CyanFrank said:
Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?
Click to expand...
Click to collapse
Airdroid. No need for a cable.

When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
If the MTP makes it stutter it could be a problem with MTP or simply that MTP does more traffic and is uncovering lower level problems.

CyanFrank said:
...There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
Click to expand...
Click to collapse
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.

manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.
Click to expand...
Click to collapse
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install

Renate said:
When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
Click to expand...
Click to collapse
No, phone is charging and debugging is enabled so that I see two notifications.
Tried the first command and phone started disconnecting just like with MTP enabled. ADB had stopped working.
manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager?
Click to expand...
Click to collapse
It used to, but apparently I messed up with drivers while trying to solve the issue, so it's not working right now.
hammered58 said:
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install
Click to expand...
Click to collapse
Yeah I noticed LeMobile drivers are available to download. There is Android Composite ADB device listed as "LeMobile" but ADB still not fixed.
And it seems like I'm back to sqaure one because there's the very first issue I had: after choosing MTP on my phone all options become gray and it returns back to "only charging" after few seconds. Sometimes it even starts disconnecting/connecting.

Yeah it seems something is particularly wrong with my home PC because MTP works flawlessly with my work PC. Didn't have to install any drivers etc.

Do you have the latest windows platform tools installed?

Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.

Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
Yes.
{
"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"
}
bobby janow said:
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.
Click to expand...
Click to collapse
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.

CyanFrank said:
Yes.View attachment 5774787
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.
Click to expand...
Click to collapse
That could be the one. If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one. I searched and there are a bunch of "solutions" out there and I hope you find the correct one before you have to reinstall the whole darn OS. I'll keep looking though. I was so frustrated by it I wanted to throw the laptop out the windows. lol. I still think it's one pesky driver.

I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.

EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.
Click to expand...
Click to collapse
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.

bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.
Click to expand...
Click to collapse
I mean I probably would do the same but if OP is already at the point of reinstalling Windows, I figured I would provide some less annoying options. Virtual machines have saved me immense amounts of frustration over the years and Player is phenomenal for something free of charge.

bobby janow said:
If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one.
Click to expand...
Click to collapse
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick.
Click to expand...
Click to collapse
Yeah, actually didn't think about that, thanks. I'll give it a try when I get enough time.
bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall.
Click to expand...
Click to collapse
As I said, I have no USB A-C cable that supports data transfer. But I'll borrow one to at least try.
And the thing is it might not fix the problem as well if drivers are screwed up.

If you have another USB-C port, I would try that as well. Sometimes different ports, even on the same controller, can have different results.

Unfortunately I have just one USB-C port.

CyanFrank said:
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
Click to expand...
Click to collapse
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.

bobby janow said:
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.
Click to expand...
Click to collapse
Yeah, I tried that as well.
And forgot to mention that I borrowed USB A-C cable and MTP actually worked. It's not as stable as it should be (sometimes it disconnects) but still it works.