Develop Bugs

[Q] Can't Install Drivers

Hello everyone. Yesterday I was trying to Odin the stock EL26 but my computer would not recognize my phone. I decided to uninstall and reinstall drivers, since my computer was not automatically installing them. However, when I try reinstalling, the Installer always freezes up. I've removed all traces of the Drivers on my computer that I know of, but I always still end up getting 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"
}
I proceed with the install anyways, and around 5 seconds after it starts installing, the window freezes up with this:
Anyone know how I can get the drivers on my computer?
Also, I am running Windows 7 Home Premium 64-bit. My computer is known to have USB problems where it doesn't detect everything either.

Where did you get the drivers? I got mine from sfhubs thread and no issues. Did you restart your comp after uninstall?

bigtoysrock said:
Where did you get the drivers? I got mine from sfhubs thread and no issues. Did you restart your comp after uninstall?
Click to expand...
Click to collapse
Used sfhubs (the same one I first used to install the drivers when I got my phone) and that didn't work so I downloaded them directly from Samsung, which also didn't work. And yes, I restarted :/

iniz94 said:
Used sfhubs (the same one I first used to install the drivers when I got my phone) and that didn't work so I downloaded them directly from Samsung, which also didn't work. And yes, I restarted :/
Click to expand...
Click to collapse
Try installing kies also.

bigtoysrock said:
Try installing kies also.
Click to expand...
Click to collapse
Already did haha. The ADB Driver installs, but the main phone one always fails

Yes, 64 bit Windows 7 can be a *****.
Just out of curiosity have you tried creating a new windows profile and running everything from there?
Also, open device manager to see the progress of it initializing your drivers when you plug the phone in. I noticed it takes a while sometimes in Win7 64 bit to initialize all the adb drivers. You think it's done but it's still loading.

tdunham said:
Yes, 64 bit Windows 7 can be a *****.
Just out of curiosity have you tried creating a new windows profile and running everything from there?
Also, open device manager to see the progress of it initializing your drivers when you plug the phone in. I noticed it takes a while sometimes in Win7 64 bit to initialize all the adb drivers. You think it's done but it's still loading.
Click to expand...
Click to collapse
I don't remember exactly what I had to do but remember having a problem with this initially. Downloaded an alternate set of drivers from Samsung's site if I remember correctly and it worked. Haven't had issues since and I use this every time I push a new TAR through ODIN.
In this case device manager is your friend. Install the driver package first, turn USB debugging on and then plug into PC. That's the only other thing that I can recall on this issue. Hope this helps!

Had similar issues with my Asus G73, Kies was the problem, sometimes would not recognize phone, got worst and then laptop stop recognizing phone altogether. After several d/l attempts had to totally delete Kies and drivers and did a disc clean up on laptop, after was able to install drives , so far so good. No Kies installed, just drivers.
Pp.
Sent from my tofu plasma converter.

Cant connect to my Phone (adb / fastboot)

pls delete this thread, wiping my pc again and make an format.
Install windows fresh and hoping the best.

KornY10 said:
pls delete this thread, wiping my pc again and make an format.
Install windows fresh and hoping the best.
Click to expand...
Click to collapse
Did it work?

Didnt done it. Maybe today or tomorrow, dont know -.- How can i complete deinstall USB Drivers?
Installed now:
Android SDK
ADB install 1.4.3
Oneplus3 Drivers
Device is detected as: Kedracom?! And then - Kedracom Device, after clicking on "driver update" i can change it to "Android ADB Device" then ADB Sideload works.
When i boot then to Fastboot the Device is detected as "Android Bootloader Device" or so...then i cant install nothing, and i cant connect to the Phone.
Im Using the USB ports from behind, dont use the front one.
Any tip? What can i do? screws me up -.-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

KornY10 said:
Didnt done it. Maybe today or tomorrow, dont know -.- How can i complete deinstall USB Drivers?
Installed now:
Android SDK
ADB install 1.4.3
Oneplus3 Drivers
Device is detected as: Kedracom?! And then - Kedracom Device, after clicking on "driver update" i can change it to "Android ADB Device" then ADB Sideload works.
When i boot then to Fastboot the Device is detected as "Android Bootloader Device" or so...then i cant install nothing, and i cant connect to the Phone.
Im Using the USB ports from behind, dont use the front one.
Any tip? What can i do? screws me up -.-
Click to expand...
Click to collapse
I'm sitting in the same boat xD
ADB is working fine phone Will be recognized. But in Fastboot Mode nothing.....
On my PC is Windows 10 installed and on my phone OOS 3.2.7

Same here, really strange, or a rly ****ing Noob fail and I don't get it. If someone else could read and help ...would be good

So, dont know...read so many things, all is fine and adb connected but wtf is fastboot not work -.-
are u trying some thing?

me too no Fastboot at all
OP3 : 3.2.7
It maybe bcz the last update, or that old OP3 tool

Hello again
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733

Ok, so i could install win7 as second OS? Have enough Harddisks, so its np.
Think i try this, PC is fresh installed, so if its not good or buggy i kill it again :/

Ok, Installed Windows 7 and all works fine... damn. thx for the tip

I had this exact issue and fixed it. Fastboot would never see my device, and the device manager shows "Kedracom" no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers. If you're seeing "Kedracom" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
One you've done this you, you can do a forced install of the drivers you downloaded for the OP3.

MTP Not Working Windows 10

I am unable to get Windows to mount my Pixel XL in MTP mode. I have the Pixel's screen turned on and unlocked, and the connection option on the phone's pull down menu is set to transfer files. Windows is able to mount the phone when it is in picture transfer mode, but not in MTP mode.. When I look in Window's device manager I can see that the MTP device is connected but I'm getting a yellow triangle exclamation, as in the driver is no good. I uninstalled the driver and tried letting Windows reinstall to no avail. I have searched the web for MTP drivers for Windows, but I can't really find anything. The specific version of Windows that I am using is Windows 10 Education 64.
The main reason for my concern is that I am about to attempt to apply the new root method that is available, and I wasn't sure if I needed to be connected successfully via MTP before I get the ball rolling with ADB. I do have the ADB drivers installed, along with ADB and fastboot and that seems to be working fine. When I run the command 'adb devices' the console shows that my Pixel XL is connected. I am assuming that I should be good to go on that front, but I still want to know why MTP is not working on Windows, and how I can fix it. Any suggestions would be greatly appreciated.
Here's a screen shot of what Window's device manager is showing me.
{
"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"
}

norcal61 said:
I am unable to get Windows to mount my Pixel XL in MTP mode.
Click to expand...
Click to collapse
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.

Scott said:
Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/
Personally I installed the latest SDK which comes with the latest drivers.
Click to expand...
Click to collapse
I tried that already. I stumbled across it while searching for a solution. The adb and fastboot parts worked well but not the regular mtp drivers. I think maybe the problem has to do with Windows itself.

I had a similar issue with my Pixel C tablet. I don't remember which driver that I had to use but I eventually got it to work. I believe that I ended up needing PDANet to resolve. I am using the same computer for my Google Pixel phone. I have successfully been able to use MTP on my Google Pixel phone and have access to all the files via file explorer.

I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.

plug your phone to your computer then check the notifications,tap on the USB charging this device for other options...just tick the usb to transfer files ....

Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI

defens23 said:
I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.
Click to expand...
Click to collapse
Believe it or not have seen / owned many devices that exhibited this behavior.
Switching back and forth always fixed.

awesome thanks for that video!!
peejayw said:
Check out this Youtube video, fixed it for me.
https://www.youtube.com/watch?v=fUHQzqxxsZI
Click to expand...
Click to collapse

This was from Microsoft's site, is a little quicker. It would be nice if this got fixed.
(1) Go to C:\Windows\INF
(2) Type "wpdmtp.inf" in search bar provided to the right of the address bar in Windows 10.
(3) Once you found it, just right click on it and select install. It will take a very few seconds.
(4) Connect your device to the pc.

I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?

triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app

triumvirant said:
I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?
Click to expand...
Click to collapse
bobby janow said:
Nope. Coincidence.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:

i'm running an ASUS MB too...perhaps there are more variables to this equation than we want to believe.

Jammol said:
I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.
I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:
Click to expand...
Click to collapse
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.

bobby janow said:
I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.
Click to expand...
Click to collapse
Windows! Lol.

USB Data transfert not working

Hello everyone,
Since few days, I have a really enoying issue with my Pixel 2 XL.
Android Auto is not working anymore.
after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode
Does anyone have the same issue ?
What can I do ?
thank you for your help !
PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo

MrMoi said:
Hello everyone, Since few days, I have a really enoying issue with my Pixel 2 XL. Android Auto is not working anymore. after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode Does anyone have the same issue ? What can I do ? thank you for your help ! PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo
Click to expand...
Click to collapse
Have you tried revoking USB debugging authorizations and then re-enabling? It is the option just below the USB debugging toggle. Taking AA completely out of the equation, if after you have tried more than one USB-A to USB-C cables on more than one PC and cannot get MTP working you probably need to do a factory data reset. This will confirm whether you have a hardware issue or not. It is also the first step Google will require you to do prior to allowing an RMA.
Edit: You can also test if fastboot is working in bootloader mode, and if adb is working in recovery mode.

thank you for your help..
I've tried adb, fastboot and factory reset...:crying:

MrMoi said:
thank you for your help.. I've tried adb, fastboot and factory reset...:crying:
Click to expand...
Click to collapse
I'm not sure you understood... my suggestion was to test the phone in bootloader mode and send fastboot commands to it from your PC (eg. fastboot devices) -and- while in recovery mode (eg. adb devices). This is of course with adb debugging enabled. You also didn't answer my question about revoking adb in Developer Settings and then re-authorizing it? I still suspect you have a cable/pc driver issue.

Oups sorry my answer is not really clear.
Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.
I can't see the device in my w10 computer in device manager

MrMoi said:
Oups sorry my answer is not really clear. Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.I can't see the device in my w10 computer in device manager
Click to expand...
Click to collapse
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?

v12xke said:
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?
Click to expand...
Click to collapse
no conflicts in my device manager, nothing change after removing all my drivers
{
"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"
}

MrMoi said:
no conflicts in my device manager, nothing change after removing all my drivers
Click to expand...
Click to collapse
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked

wkJason said:
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked
Click to expand...
Click to collapse
thank you, but still not working

Did you ever get this problem resolved? I am having the same issue on my XL 2

I experience this problm as well but I just try different USB ports then it magically works. Quite annoying.

Boiler_81 said:
Did you ever get this problem resolved? I am having the same issue on my XL 2
Click to expand...
Click to collapse
Hello,
I had to send it back to the Google store. I never knew what the problem was.

Thank You
MrMoi said:
Hello,
I had to send it back to the Google store. I never knew what the problem was.
Click to expand...
Click to collapse

Bootloader driver issues on Windows 10?

I made this post to hopefully help me help you help us.
My Razer Phone is currently unable receive any commands while in fastboot mode/bootloader.
This seems to be a fairly common problem that I see some people are running into without having any concrete solution. I have tried numerous suggestions and then some. Therefore, I want to provide as much information and background to the problem to try and help anyone with more experience that is willing to get to the bottom of this.
So for some background, I successfully rooted my Razer Phone with help from both of these threads:
Rooting Android 9 December Update With Magisk (No TWRP)(Global)
and
[TWRP + MAGISK] FULLPROOF Guide for all Razers! Wifi Fix!
I primarily used the first thread listed to achieve root.
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I am trying to revert to stock and relock my bootloader using Razer's guide HERE. When using the 'flash_all' script that the guide references, the script fails, because the phone cannot receive fastboot commands.
I followed Razer's installation guide PDF to install the adb/fastboot drivers.
I have also tried using ClockworkMod's Universal ADB Driver.
EDIT: I also tried using [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I'm pretty sure I have installed the adb drivers correctly. I can use adb commands while android is running. It's listed when using the "adb devices" command. It successfully restarts and enters the bootloader after typing "adb reboot bootloader", but after typing "fastboot device", it only outputs "< waiting for any device >" and waits. I have also tried using the command "fastboot -i 0x1532 devices" as suggested in a related thread, but this just returns "fastboot.exe: unknown option -- i" and fails.
I have also tried selecting "Android ADB Interface", as well as "Android Bootloader Interface" when installing the google usb driver. I even tried using the third option, no luck.
Now here's why I say that I'm pretty sure that I have the drivers installed correctly:
{
"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"
}
This is what is displayed in Device Manager when the phone is in fastboot mode and connected to my PC after installing the drivers.
It displays normal when android is running with or without USB debugging enabled.
I have tried this on a few Windows 10 PCs and get the same result. So, I wouldn't be able to tell if this is a Windows problem or if it is my phone:
This is what my bootloader shows. Besides the serial number I blocked out, notice how some data is missing? Could this be the problem?
I'm curious to know the method of root everyone else having this problem had used and whether their bootloader looks like this.
I understand the community for this phone isn't as active as it used to be.
So, thank you to anyone in advance for the help and your time.

This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.

tys0n said:
This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.
Click to expand...
Click to collapse
I forgot to mention that I had also tried this tool to install the drivers on a few different PCs. I did all of this (including other methods) after making sure to uninstall any drivers that were previously installed. The installation succeeds, but still has no effect on the phone being detected when it's in fastboot. Everything else, like file transfer and adb commands does.
Thank you for your time and for replying.

I've had the same problems you've had Waffle. I tried everything I could read in the forms, what ended up fixing the driver issues for me was to use Linux. I owe it to Linux's superior driver support that fixed the issue for me.

Well, I finally got it to work. I decided to try the tool tys0n mentioned again, and it worked. Not sure what I did differently this time, but I am thankful that it is now connecting properly.
Sorry for piggybacking onto my own post but now, after using the razer file to factory reset and lock the bootloader, the screen says "Your device has loaded a different operating system." on boot and some apps still say that the phone is rooted. When accessing the bootloader it says that everything is locked and the OEM Unlocking switch is disabled in developer options. Not sure what I may have done wrong, since it's just running a script for the most part or if it's just stuck like this since I rooted the phone in general.