Develop Bugs

[SIGNED DRIVERS x64] Eugenia Project MTTY USB SIGNED Driver for Windows Vista/7 x64

Hi all, I'm the Eugenia Project developer!
As you know, for making your device to work with mtty on Windows Vista or Windows 7, you had to reboot, disable signed driver control, install the driver and go on with mtty.
Ouh, and after a reboot you'll get a not working device if you don't restore the "old - new" driver!
From now, you won't have this problem anymore!
With the Eugenia USB x64 Signed Driver you will only install the driver without any reboot or disabling driver signature controls, and it works even after rebooting!
This driver will work with MTTY and RUUs (including CustomRUUs) flawlessly and without any complicated procedures!
What's included in the package:
*- A signed certificate for the driver,
*- The driver,
*- The installer.
Installing the driver:
*- Decompress the archive
*- Make sure your device isn't connected to USB
*- Run the file named "RunThis"
*- Connect your device to USB.
If the device won't work, you have to tell your system to use the new driver.
To do that (on Windows 7):
*- Right click on Computer, then click Properties.
*- Click on Device Manager
*- Expand "Mobile devices" and double click HTC USB Sync (or unknown device if it is recognized like that)
*- Click on the "Driver" tab, then click on the "Update Driver..." button
*- Click on "Browse my computer for driver software", then on "Let me pick from a list of device drivers on my computer"
*- Click on "Have disk..." and select the driver in the folder where you've uncompressed the archive.
*- Double click on Eugenia HTC USB Sync
It will say that it's not digitally signed from Microsoft, but install it anyway. It will work.
As the result, you'll have.....
....screenshot:
Download:
Version 1.0: EternityProject Website
Hope you like it!

Well I will try, because from now I use VMWare to Flash in Win7 x64 !

I don't know if it work, because finally Windows found a driver on windows update and install it (11.9 Mo, if I remember).
I flash a new ROM and it's OK !

I am using Windows 7
trying to install the driver, and go into the device manager.
I can not find "mobile device" from the list. why?
What next to ensure it is using that driver?

Hi,
i ust tryed this and it didnt install anything, it just said the driver was present and didnt do anythin.
when i checked my device manager it didnt say "Eugenia HTC USB Sync"als when i tryed using the driver without restarting and pressing F8 to remove the Driver signing, MTTY doesnt show USB.
could this be because there s already a working driver?
Thanks for help
MG

That what I've done:
1. Reset my diamond to bootloader.
2. Connect to my win 7 x64.
3. The HTC Usb sync appears in Device Manager.
4. Update to your Eugenia USB driver.
5. Done .
But the connection in bootloader mode doesn't change to usb - it's serial - I can't use mtty.
PS: My norton AV 2009 detected security risk in Runthis.exe and removed it
{
"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"
}

jamit018 said:
I am using Windows 7
trying to install the driver, and go into the device manager.
I can not find "mobile device" from the list. why?
What next to ensure it is using that driver?
Click to expand...
Click to collapse
Ya same here i installed it and could not flash rom before i was able to flash in "signature disabled"mode but now it also don't work... i can not find the mobile device in the list it just said unknown device ... the only i got around was by running back up in PC and going bacck to the time before installing this driver...

On my 3 PCs running Windows 7 x64 all works.
Don't worry about the antivirus warning, it's all clean.
It recognizes it as a virus because the .exe file is compiled from a batch, but I repeat, it's all virus free.
However, have you tried to tell to your PC that it MUST use the Eugenia USB Driver?
I mean in Device Manager!
I'm using it right now on my HTC HD2 (Leo) for playing with the stock SPL and it works flawlessly even on that device.
Let me know...
IF it still doesn't work, I'll retest all on other PCs.
P.S.: As the last "hope", try to delete the old drivers used without the signature enforcement

Workls like a charm for me!

Guys the download link is no longer working... Can someone please re-upload?

i've hit 3 issues:
(1) I ran runthis.exe as non-admin by accident.. ran it again as admin and got error that cert already existed etc but the problem is:--
(2) "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)". the device works 'ok' when i boot win7 x64 into disable driver check via f8
(3) but mtty stops responding when i type 1 letter
but this looks good! thank you for your work

binary64 said:
i've hit 3 issues:
(1) I ran runthis.exe as non-admin by accident.. ran it again as admin and got error that cert already existed etc but the problem is:--
(2) "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)". the device works 'ok' when i boot win7 x64 into disable driver check via f8
(3) but mtty stops responding when i type 1 letter
but this looks good! thank you for your work
Click to expand...
Click to collapse
Hi,
for Windows 7 x64 try the driver install on post 3 here
MG

works perfectly on my Win 7 RTM x64 !

Windows Phone Driver Error

I'm suddenly having a problem with my Nokia Lumia 800. For some reason my PC is failing to install the Windows Phone 7 portable device driver. I get an "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" error.
I've tried un-installing the drivers and reinstalling them but I still get the same problem? Any ideas? Thanks
{
"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"
}

mickfarr said:
I'm suddenly having a problem with my Nokia Lumia 800. For some reason my PC is failing to install the Windows Phone 7 portable device driver. I get an "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" error.
I've tried un-installing the drivers and reinstalling them but I still get the same problem? Any ideas? Thanks
Click to expand...
Click to collapse
Make sure that you have the automatic driver downloading from Windows Update turned on. You can turn it on in the "Installing device drivers" screen when you plug in a USB device.

jessenic said:
Make sure that you have the automatic driver downloading from Windows Update turned on. You can turn it on in the "Installing device drivers" screen when you plug in a USB device.
Click to expand...
Click to collapse
No luck with that.

Uninstall the drivers for Windows Phone 7 and Windows Phone USB.
Restart the PC and then attach the phone.
Try to use a different USB port.
If that don't work then i'd suggest a new USB cable

I've tried a different USB cable that's working with another Nokia Lumia 800 in the office and still the same problem. I've tried different USB ports and I've also tried this USB Cable and Lumia on a different PC and it installed the drivers correctly and worked fine.
Is there any settings that I may have changed that could have casued the error code 31. The phone charges up fine from the USB port, what ever is causing the 31 error is the problem?

mickfarr said:
I've tried a different USB cable that's working with another Nokia Lumia 800 in the office and still the same problem. I've tried different USB ports and I've also tried this USB Cable and Lumia on a different PC and it installed the drivers correctly and worked fine.
Is there any settings that I may have changed that could have casued the error code 31. The phone charges up fine from the USB port, what ever is causing the 31 error is the problem?
Click to expand...
Click to collapse
Try this:
Unplug your phone
Uninstall Drivers
Uninstall Zune
Reboot
Install Zune
Plug your phone

Tried that and I still have the same problem!

Hi,
Search google on how to uninstall disconnected devices in windows and remove the old device( something like "show_nonpresent_devices" in device Management. )
Sorry for previty, can't search the Link right now
Regards
Donpromillo

i had this issue with my Focus. It was the USB Plug on my phone. I did an warranty exchange. The Rep tried it with his usb cable on a computer in the store and got the same error.

Did you try to use the Windows Troubleshooter ?

Strike_Eagle said:
Did you try to use the Windows Troubleshooter ?
Click to expand...
Click to collapse
One of the most useless pieces of windows 7 "help" I've seen. I like the "help" it provides in diagnosing wifi errors. Priceless.
A quick google of the error showed me its a port problem on the phone.

ohgood said:
One of the most useless pieces of windows 7 "help" I've seen. I like the "help" it provides in diagnosing wifi errors. Priceless.
A quick google of the error showed me its a port problem on the phone.
Click to expand...
Click to collapse
There's nothing wrong with the phone, its the PC.

bennyj71 said:
i had this issue with my Focus. It was the USB Plug on my phone. I did an warranty exchange. The Rep tried it with his usb cable on a computer in the store and got the same error.
Click to expand...
Click to collapse
The phones fine, its the PC I have the problem with.

donpromillo said:
Hi,
Search google on how to uninstall disconnected devices in windows and remove the old device( something like "show_nonpresent_devices" in device Management. )
Sorry for previty, can't search the Link right now
Regards
Donpromillo
Click to expand...
Click to collapse
Great idea! I didn't think of that. It's my office PC so I'll give it a go on Tuesday when I'm back in the office.
Thanks!

ohgood said:
One of the most useless pieces of windows 7 "help" I've seen. I like the "help" it provides in diagnosing wifi errors. Priceless.
A quick google of the error showed me its a port problem on the phone.
Click to expand...
Click to collapse
Not at all.
It helps me solve several problem with driver on Windows 7.
It is useless most of the time but it is useful sometime...

[EDITED]
WINDOWS TROUBLESHOOTING STEP-BY-STEP SOLUTION
(Step 0: Install zune)
e driver. To do this, follow these steps:
1. Click Start, right-click Computer, and then click Properties.
2. Click Device Manager, located in the left column.
3. A window will appear with the name of your computer and a list of files. If you don't see the files, click the name of your computer. The name of your Windows Phone should be listed under Portable Devices. If Windows Phone was incorrectly installed, it may be listed with a yellow exclamation mark . Or, it may be listed under Other Devices as a USB device or an unknown device.
4. On the Driver tab, click Uninstall.
5. Select Delete the driver software for this device and then click OK.
6. Return to the Device Manager window, click the Action menu, and then click Scan for hardware changes.
7. Open Portable Devices, double-click the name of your Windows Phone, and then click the Driver tab. Or, if you don't see your phone name, click unknown device listed under Other Devices, and then click the Driver tab.
8. Click Update Driver.
9. Click Browse my computer for driver software.
10. Click Browse, locate on the C drive the Program Files/Zune/Drivers folder, and then click OK.
11. Click Next and if you're prompted, click Install. You may only be given a Close option.
12. After the driver installation is complete, Close the open windows until you exit the Device Manager. If you're prompted to restart your computer, do so when you can.
(13. (In case of syncing problems) Go to Program Files/Zune and find Zune.exe, right click, select properties, then Compability, check run as administrator and hit ok. Run Zune a gain, and an admin prompt will appear)
Sent from my rooted SGS i9000 running Gingerbread. I also know stuff about WP7.5 and Zune.

Please just follow the steps and ignore the text between step 0 and 1. I edited the message too many times and can't cut it out.
Sent from my rooted SGS i9000 running Gingerbread. I also know stuff about WP7.5 and Zune!

Firemil said:
Please just follow the steps and ignore the text between step 0 and 1. I edited the message too many times and can't cut it out.
Sent from my rooted SGS i9000 running Gingerbread. I also know stuff about WP7.5 and Zune!
Click to expand...
Click to collapse
Tried all that and when I try to install the drivers from the Zune driver directory it tells me that my driver is up to date.

donpromillo said:
Hi,
Search google on how to uninstall disconnected devices in windows and remove the old device( something like "show_nonpresent_devices" in device Management. )
Sorry for previty, can't search the Link right now
Regards
Donpromillo
Click to expand...
Click to collapse
I set the device to display all the non present device drivers and I uninstalled loads!! I had old HTC Android drivers, HTC HD2, Nokia Lumia and even Blackberry not that I've ever had a blackberry
I unistalled all the USB storage drivers for windows phones and android etc and also the USB Composite drivers. This is the closest I've got to getting it to work but it is still not working.
My Lumia was working fine on this PC until I downloaded the Nokia care suite. I'm wondering if I did something them but I can't remember?
EDIT: Nokia Care Suite is picking up my Nokia Lumia 800 when connected just not Zune?

Help me, please!
I want restore/Install booloader to QLOAD/Qcom but:
NSS not find my phone.
NSS 0.47.0 Beta - Quick Install & Restore of the 710 bootloader - xda-developers

[Q] Waiting for device...

So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.

car_lost said:
So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.
Click to expand...
Click to collapse
I'm having the same problem.
In the device manager, you should see Android phone or some such near the top, as well as the drive you mentioned.
I tried to root my KF yesterday on 4 different Windows machines using 4 different OS's: Windows 7 Professional, XP Professional, XP and Vista. (Yes, I stil have a Vista machine)
No joy. <Waiting For Device> _
Matt

This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.

kinfauns said:
This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.
Click to expand...
Click to collapse
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"

car_lost said:
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"
Click to expand...
Click to collapse
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.

kinfauns said:
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.
Click to expand...
Click to collapse
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
On a stock device, booted up to the OS... some device in a category other than Disk drives or Portable Devices should come up when you connect it to your computer. I've never seen a situation where that did not happen. If you have another computer, I would suggest trying that.

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
is there a device named "kindle" ? - if yes delete it and try to unplug/replug
if this don't help try to use this method to show devices that are not connected atm:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
disconnect the kf and remove everything with adb or kindle
take care that you uninstall the driver too where you get the option to do this
now reconnect the kf - it should ask for the drivers like at the first connection

I'm formatting my computer and starting from fresh. Fresh copy of Windows 7 and a stock KF.
I'll report back.

regrouping
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.

Mattb4rd said:
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.
Click to expand...
Click to collapse
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

b63 said:
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Already had tried that but did again for good measure. The driver installs as before but the KFU still hangs on "oops, something went wrong" and <waiting for device>
{
"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
Out of time right now and have to leave for a meeting. Will give it one more shot later.

you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000

So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.

This is what I get...

previous pic doesnt seem to be working..

car_lost said:
So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.
Click to expand...
Click to collapse
You're in an unusual spot... I figured a new Windows install would get it to work. In my opinion, if you can rule out Windows 7 as the problem, you're going to have to start looking at the KF as the possible cause. I haven't had stock on my device in a while, but if I was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the KF software from Amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a ROM to see if you can get adb working with that.

kinfauns said:
you're in an unusual spot... I figured a new windows install would get it to work. In my opinion, if you can rule out windows 7 as the problem, you're going to have to start looking at the kf as the possible cause. I haven't had stock on my device in a while, but if i was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the kf software from amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a rom to see if you can get adb working with that.
Click to expand...
Click to collapse
this worked! This worked! This worked! This worked! Thank you a million times!!

b63 said:
you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000
Click to expand...
Click to collapse
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.

Mattb4rd said:
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.
Click to expand...
Click to collapse
A factory reset isn't going to hurt, but you are in a different boat than Carlos. Based on your screenshot of the Device Manager, it looks to me like your computer is recognizing the device correctly and loading the right drivers since it says "Android Phone -> Android Composite ADB Interface" when it's hooked up. For whatever reason, KFU is not able to push the required files onto your device and get it into fastboot mode. I suggest taking KFU the middleman out of the picture and seeing what adb tells you when you try to use it directly. Try something simple like "adb devices" on the command line and see what you get. You'll have to use the command line to run the adb program located in the tools directory of KFU.

[Q] Win7 drivers not recognizing phone

It's my first try ever to install a new ROM. I was trying to install CM on my Note 2 (ATT) following the Install_CM_for_t0lte tutorial on cyanogenmod.
Everything was going smoothly until I try to push the CM build with ADB and find that ADB doesn't recognize any devices. I head over the Samsung to get the SGH-I317 USB drivers but the first driver (1.5.45.0) doesn't fix the problem. There's a second driver there (1.5.14.0) and I try it with no luck as well.
I've been searching for an hour and I still don't know what to do. Pretty much everyone says get drivers from Samsung, but they aren't working for me.
The Win7 Device Manager has an entry in "Other devices > SAMSUNG-SGH-I317" that says "The drivers for this device are not installed. (Code 28)".
Things I've tried:
- The drivers from Heimdall's zadig work for Heimdall, but apparently not ADB ("adb devices" is empty).
- I've tried both front and back USB ports with multiple cables.
- I've tried stopping and restarting the adb server
Without the drivers, ADB doesn't see my phone and I can't push a new build to my freshly wiped phone.
Please help!

7T Android ADB Fastboot Driver Issue on Windows

Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
{
"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've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.

raskulous said:
Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.
Click to expand...
Click to collapse
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.

Soapy! said:
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.
Click to expand...
Click to collapse
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.

raskulous said:
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.
Click to expand...
Click to collapse
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).

Soapy! said:
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).
Click to expand...
Click to collapse
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'

raskulous said:
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'
Click to expand...
Click to collapse
When you check the driver properties do they match what's in the attached image?

Soapy! said:
When you check the driver properties do they match what's in the attached image?
Click to expand...
Click to collapse
No, this is what I get after installing the "Composite ADB" driver from google.

raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
Have you tried to uninstall AND delete all android/android usb drivers, then reinstall oneplus drivers? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing

[QUOTE = "bynarie, postagem: 83974147, membro: 5375894"]
Você tentou desinstalar E excluir todos os drivers USB do Android / Android e reinstalar os drivers oneplus? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing
[/ CITAR]
Tank You

raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
I had the same problem before, with fastboot not recognizing the device and only "waiting for device.." appear when I'm on bootloader mode on the phone. I got it working when I chose bootloader driver (Google USB drivers) on Windows Device manager (under the same screen like your screenshot). Put your phone on bootloader mode, open Device Manager (Windows), plug your phone and Android devices should appear. The Google drivers should come up (assuming you installed them) when you click on Update Driver, then choose bootloader. If successful, device should appear under fastboot devices command. Fastboot should then work.

for "fastboot waiting for devices" problem check solution here https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/

Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

CheshireShorty said:
Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Click to expand...
Click to collapse
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.

_sky.captain_ said:
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.
Click to expand...
Click to collapse
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.

Battled a bit with this one... Just to let others know. I had no change to get it work with Win11. Using Win10 everything worked fine. Luckily I had other PC with Win10 so I got everything working.

ej8989 said:
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.
Click to expand...
Click to collapse
Thanks! I wasn't able to install the Google drivers manually with the device manager but this worked for me.
Just click on "View All optional updates" after checking for updates, expand driver updates and choose the Google - Android Bootloader Interface. I wasn't aware of that option in Windows update.