Database Develop

[Q] Captivate & Windows 7 64bit Drivers

Hey Guys,
Firstly just got my captivate a couple of days ago and i am still struggling to get to install drivers and have my pc detect the phone. I am totally new to android (coming from iphone)... there might be some obvious things that I might be missing here...
Here is what has happened so far
I have pretty much tried all the drivers on the web and I am still unable to see the drives on my PC. Driod explorer is unable to detect the phone. Device manager is showing a USB device by the name "SAMSUNG Android USB Composite Device".
In the phone i have enabled usb debugging. Once the cable gets connected, I also open notification and enable USB storage.
I am still not able to see the drive or have any applications in my pc detect the phone. What am i missing?
A simple usb device installation has never given me so much trouble. Starting to get frustrated.
Appreciate any pointers in resolving this issue.
Thanks

So you chose "Mass Storage" in settings? And once you connected, pull down the drop down men you, press USB, and then press the "Mount" button?
Mine worked just fine on WinXP and Win7 64 bit once I enabled mass storage and then confirm "Mount" each time you connect.

yes I did choose mass storage option & mount it.

I am able to see the usb drives in windows xp. But cant resolve the issues with win 7 64bit. I am using the following drivers
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip

s1lverdream said:
I am able to see the usb drives in windows xp. But cant resolve the issues with win 7 64bit. I am using the following drivers
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
Click to expand...
Click to collapse
I know a few people who had connections problems too. They were able to fix it using this driver: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Some others were also able to do it using the Samsung Kies program.
Just one thing, though. You said in your post you're selecting 'Mass Storage'. Did you try selecting 'Kies' (this is even without installing the Kies program)? Try doing that. Also, try having USB debugging off when you perform the aforementioned test.

All I can get with debugging on or off and mass storage is this
{
"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"
}
no matter what drivers i use. I cant mount it on Windows 7 but I can on vista

My desktop is running Windows 7 64-bit, and I couldn't get it to recognize my phone for anything, even with the drivers from Samsung. The computer doesn't even pick up the phone as a device, much less one it recognizes. I had to use my netbook (Windows 7 32-bit/Linux) to do all my phone-related hacking stuff.

I'm using Win 7 64-bit and here's what I did after reading some suggested steps in another thread:
Install Samsung Kies first, before ever connecting the phone.
Run the program, then connect the phone to a USB port on the motherboard. Not one on the front of the case.
Windows SHOULD start installing the drivers.
I think I selected the Kies option on the phone the first time. Three or four different drivers were installed I believe. When I connected the phone again and selected Mass Storage, two or three different drivers were installed by Windows.

Does this mean I have proper drivers:?
Hi guys,
I just bought a new hp computer with win 7 64 bit os. I am able to use microsoft synctoy to syn itunes to my cappy. Does this mean that I have the proper usb drivers installed on my computer for my phone. I was thinking about rooting my phone and wanted to have the correct drivers installed.
Thanks, I consider myself a newby to the forum and to rooting, so any help would be appreciated.
drewfs7270

Has any headway been made on this as I just got windows 7 64 bit, and am having a similar problem. Tried various drivers and whatnot but still cant seem to get the usb to mount like a flash drive. It is being recognized and can receive commands like reboot into download mode from AOI toolbox, but no mounting.. Kinda driving me up the wall bc Ive been stuck on the same rom for a few weeks now and Im itching to get back to flashing all the fresh new cm7 stuff out and just in general new roms.

The newest Kies will install a driver pack when you download it now.
MAkE SURE YOU REMOVE ANY SAMSUNG DRIVERS THAT ARE CURRENTLY INSTALLED
1.) download the newest Kies http://www.samsungapps.com/about/onPc.as?COUNTRY_CODE=CAN&LANGUAGE_CODE=ENG
2.) Install it. While it's installing it will install a driver pack.
3.) Plug your phone in.
This works for X64. I just used it on my own pc last week.

jack_slapped said:
Has any headway been made on this as I just got windows 7 64 bit, and am having a similar problem. Tried various drivers and whatnot but still cant seem to get the usb to mount like a flash drive. It is being recognized and can receive commands like reboot into download mode from AOI toolbox, but no mounting.. Kinda driving me up the wall bc Ive been stuck on the same rom for a few weeks now and Im itching to get back to flashing all the fresh new cm7 stuff out and just in general new roms.
Click to expand...
Click to collapse
Turn on USB Debugging.

Lol I know how to enable USB debugging man. What I'm saying is windows wont allow it to mount for some strange reason. Going to try the kies driver mentioned earlier. Maybe that will work.

So I tried the kies drivers, and Im getting the same problem. The drivers will install and it will even trick me by showing the removable letters for my storage, but then after a second or so they disappear. When looked at under device manager they are just shown as unknown device. I just wanna backup my data like I used too.

jack_slapped said:
So I tried the kies drivers, and Im getting the same problem. The drivers will install and it will even trick me by showing the removable letters for my storage, but then after a second or so they disappear. When looked at under device manager they are just shown as unknown device. I just wanna backup my data like I used too.
Click to expand...
Click to collapse
I definitely don't want to insult anyone's intelligence here (which usually means I am going to). i assume we've tried restarting the computer again.....a couple of times.......and if that doesn't work, then manually uninstalling all the drivers which have been installed so far and then starting over using just kies?

Yea, all those mentioned have been tried.
Sent from my SAMSUNG-SGH-I897 using XDA App

I don't know if this means anything, but windows can recognize my device. Sorta. I tried flashing to stock in hopes that would fix the problem, but it didn't. Isn't it strange that I can flash my phone but not be able to mount my storage??
Sent from my SAMSUNG-SGH-I897 using XDA App

okay...
So i was able to connect to my Win 7 64 bit computer for a little while ... had to in order to update to Mini Keis 2.2 (ran into problems there but fixed it <if you have questions about it PM me>)
But now that i am in 2.2 i am not able to connect. I get an error saying drivers could not be installed. I have uninstalled the original drivers and installed the ones from AT&T and also tried the ones from Samsung... still same problem. Does anyone one have an idea as to what i can do to solve this problem.
Thanks to any one who can help

I've had luck by doing the following:
Had my phone plugged in - it went fubar - computer didn't recognize the phone.
Re-installed USB drivers (ones Design Gears posted and the ones linked in the Q&A sticky btw) over the top of the existing drivers with the phone plugged in - USB De-Bugging on.
Rebooted PC - winblows found the phone and everything was peachy. Windows 7 64 is definitely nice - but still has issues with detecting drivers and USB devices sometimes. Its still Windows after all
If it works on another PC than you know its a software issue with windows.
If your still getting the same error on another PC - then its possible that your internal card might be fubar.

Well I have tried EVERYTHING. Multiple drivers, uninstalling, reinstalling, rebooting, usb debugging on/off, flashed to stock....Nothing. Windows 7 64bit. I hate hate hate you and hope you die of viral infection.

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.

[Q] Stuck in *Daemon Started Successfully* during ROOT

Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.

retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.

I'm having the exact same problem here.
RooQemu hangs at *Daemon started successully* and nothing happens
when I try to enter "adb shell" in a cmd i get the error "device not found"
Kindle is shown correct in device manager as "Android Composite ADB Interface" and I can transfer files via explorer without problems.
Windos 7 64 bit and Kindle from amazon Germany Version 7.2.1_user_2040020
Tried on my Laptop and my PC, both with the same result.
At least someone seems to have the same problem as I do. Hope someone comes up with a solution. I tried the steps mentioned above, same result...

spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:

retroflashbacks said:
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:
Click to expand...
Click to collapse
Try this. Install the Android SDK in your computer reboot your kindle and the computer and try again. It worked for me

Darn..still not working...

This problem is due to the drivers!
You need to uninstall the drivers in the device manager, and manually install the drivers from the location you install the ADB drivers.
In my computer, the location is "C:\program files\amazon.com\kindle fire\drivers".
The wrong driver is like this: ”Android ADB Interface“
{
"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"
}
And the correct driver is like this:
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse

Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..

retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Try to do what PMcHargue explained, it didn't work for me but who knows? Locate the adb_usb.ini file and insert the last line.
PMcHargue said:
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse

retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Hey! I'm the one that had the same problem as you.
I tried everything... Then I installed Android SDK and followed this guide:
groovypost . com / howto / kindle-fire-hd-connect-adb-debug
Then it worked.
Hope that helps!

spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
I had the same problem but I did this bur turned my wifi off before step 2. The device appeared with a caution sign next to it in the device manager (no driver installed) but the adb commands started to work and I could root my kindle. Hope this works for you.
Sent from my KFTT using xda app-developers app

It didn't work for me with the drivers in this post, it worked using the Amazon drivers from Android SDK.

retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
What worked for me was to download the android SDK into the root folder of the PC...OR C: If you like....I still found that after every step I had to unplug the device and re-plug it (Is that a word) to continue as the device wasnt found. Im now told ADB tools works better? Gotta have another go since Super user didnt get root access....Guess were on the same journey!

I have the "Android ADB Interface" and not the Composite one and its worked fine for me

thanks alot mate ...
i have windows 8 and faced same problem ...
i did what u said n the root method worked like charm..
thanks again
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse

x64 problem?
I'm having the exact same issue, 'daemon started successfully' I think it has something to do with my OS being x64. I kpet the Task Manager open, and it seems like it opens up 2 adb.exe *32 at once. I tried closing one, and the program would continue. I'm using an Intel x64, and I noticed that the only drivers in the Amazon.com folder were *386, and AMD64. I'm not sure if AMD64. Not sure if this added info is relevant, since the original driver is prior to these directories. I hope an easier method evolves.

Update ... I tried downloading the android sdk, then copied the adb.exe over to the Root\stuff folder and it worked! once you copy the adb.exe, just follow the original OP's instructions.

Eu quero meu root

[ADB/FB/APX Driver] Universal Naked Driver 0.73

Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!

Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!

jadengore said:
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
Click to expand...
Click to collapse
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...

1wayjonny said:
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
Click to expand...
Click to collapse
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.

agrabren said:
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
Click to expand...
Click to collapse
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)

AndrewNeo said:
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
Click to expand...
Click to collapse
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.

PR0XIDIAN said:
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
Click to expand...
Click to collapse
The issue with the touchscreen is the driver. While it runs great in Android, it doesn't work in recovery, making a touch-based recovery a nightmare. Believe me, I already tried for a few days. I'm sure with enough time, I could get it working, but I didn't want to invest that much time with all the other things on my plate at the moment. I just don't expect recovery to come out this week with touch.

I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Fix Fastboot issues on Windows 8: http://www.youtube.com/watch?v=XSisjVwcPbE

wwjoshdew said:
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
Click to expand...
Click to collapse
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.

1wayjonny said:
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
Click to expand...
Click to collapse
haha. She's a trip though. Thanks a lot dude, you don't see to many "screen captures" that show the computer rebooting and everything! lol

Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.

Evo_Shift said:
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Click to expand...
Click to collapse
I had the SAME PROBLEM! I uninstalled the drivers, and chose from the list manually! Eventually you choose have disk and there is a long list of things. Find NVIDIA Fastboot from that list.
{
"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 swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.

Evo_Shift said:
I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Click to expand...
Click to collapse
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?

wwjoshdew said:
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
Click to expand...
Click to collapse
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.

I finally got it. I am pretty sure it is because of incorrect adb drivers getting auto installed on me when I plugged in the Shield. I wish you could force Windows not to autoinstall drivers when you plug something in and instead always choose your own location. Once I deleted enough of the incorrect drivers and installed the correct drivers to the SHield again it seems to work.

1wayjonny said:
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
Click to expand...
Click to collapse
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.

hmm...
I have only "Nvidia Shield" not Nvida Shield ADB in my devices Manager - adb is enabled
Code:
adb devies
List of devices attached
(none)

wwjoshdew said:
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
Click to expand...
Click to collapse
Had this issues so I installed the "manual" way and still commands wont work in fastboot
Edit: followed the video as opposed to the sceenshots above. Good to go now.

1wayjonny said:
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Click to expand...
Click to collapse
Is APX mode available on NVIDIA Shield? I've used APX mode before on my Notion Ink Adam (Tegra 2), but I have read that the OUYA (Tegra 3) has APX mode encrypted or something so you would have to know the key to use it.
Would be nice to have APX mode on the Shield, but probably not necessary.
~Troop

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.