Develop Bugs

[Q] samsung drivers wont install

hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks

After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5

Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...

Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium

i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks

Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?

no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.

Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done

I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?

i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.

Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?

fastboot not detecting phone

I have an HTC Incredible 4G LTE. I underwent the process detailed here to unlock the bootloader.
When i got the HTCDev website, i ran a fastboot command and it just says <waiting for device>. I tried to detect the device with adb devices, and fastboot devices, but with no success. the THC Sync manager is not installed. HTC drivers should be installed. I am plugged into a USB 2.0 port, the same one used through out the process (i even tried the other one).
I am at a loss as to what is happening. I do know that the device manager sees my phone, and shows the drivers as the latest version. It does give this message:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
The device manager is listing the driver as version 2.0.7.3.
EDIT: Was able to get driver updated to 2.0.7.18
Also, when connected to the computer normally an orange light shows near the speaker. I wasn't concerned at first as I know the Android OS is not actually up and running on the phone, but do wonder if it doesn't indicated a problem.
Another note, I am running Windows 8.
EDIT 2: More research has yielded the following "Android Bootloader Interface". Every reference installing this from the usb_driver in the ../extra/google/usb_driver folder. When I attempt to do so from the device manager Have Disk ui I receive the following error
The folder you specified doesn't contain a compatible software driver for your
device. If the folder contains a driver, make sure it is designer to work with
Windows for x64-based systems.
Click to expand...
Click to collapse
EDIT 3: Removed entire android sdk, redownloaded and installed. Removed all HTC software and drivers. Booted phone into fastboot, and windows detected an "Android 1.0" device, installed the Android Bootloader Interface driver from the google usb_driver successfully. However, fastboot devices still does not detect the phone, and device manager still shows code 10.
As of now:
No HTC Sync, or HTC Driver
phone booted into fastboot, phone displays "FASTBOOT USB"
phone is set to usb debug
phone is connected to pc with good cable to a usb 2.0 port
I have:
rebooted pc, re-installed drivers, changed usb cords, changed usb ports, even tried a usb 3.0 port, i have tried some generic fixes for code 10 errors, and completely run out of ideas
EDIT 4: After using a different computer running Windows 7 I was able to complete the process, however, i would very much like toresolve the issue with my own PC, as the Win7 laptop is not mine. I utilized the adb/fastboot/winapi files from my Win8 machine. Win7 automatically found HTC drivers (2.0.7.18) and everything seemed to work just fine. Any ideas?

[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!

Driver LGE Android MTP Device

This thread is about the defective installation of the LGE Android mtp device driver. Note that when the phone is on all the drivers seem to work correctly (LGE mobile ADB interface under "android device", G4 driver under "portable devices" and LGE mobile USB serial port).
The issue presents when i switch the phone to "download mode"; in this mode the "G4" driver (which is the LGE Android MTP device) appears not to be working.
The problem persists on three different PCs, either with windows 10 or windows 7 and either with a LG G4 or an LG G3.
I would like to root my G4 device following the firmware flash procedure 10E, but I am not sure that I can flash the device if there is this kind of issue with the drivers. Is it normal that the device appears not to be working?

I am having the same problem as you were. I am using Windows 7 and several versions of the LG drivers with the same result; Everything is fine when my device (a G4) is booted normally but in Download mode I get the same error as you (This device cannot start. (Code 10)).
I have tried everything I can think of, I have uninstalled all the old Android drivers with USBDeview, disconnected the internet to stop windows update installing its own drivers, different USB ports and cables.
Did you ever get your device rooted?

SO... in my case (YMMV - be careful) it turns out there is no need for the device manager to be error free when the phone is in download mode.
I just got root using this procedure from the "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread with no issue. I thought it would work because the LGMobileSupportTool was reporting as being connected to my phone despite the error (This device cannot start. (Code 10)) in device manager. Sure enough everything worked fine. I wish it hadn't taken me (literally) 20 hours of fecking around with drivers to get to this point though...
ETA I have a G4 H815 (EU)

i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?

012512 said:
i had a problem too. my device is rooted and i cant access mtp after... what might be the problem?
Click to expand...
Click to collapse
Edit. Performed a factory reset and it worked as it is.

I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.

PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
But in my case only greenify is installed module,
Why you only post that After I factory reset my phone. Haha anyway thanks for the information.

PDAlama said:
I had this problem too. It turns out that problem was in Xposed module "Xposed Media Scanner Optimizer". If this module is loaded up, I can't connect via MTP with same error Code 10 in Device manager. So, if you have Xposed, try to uncheck all modules and restart.
Click to expand...
Click to collapse
This helped me so much when I was trying to upgrade to Android M. After un-checking all my xposed modules, both my pc and laptop were finally able to read my LG G4 and install drivers, mtp, and others correctly without fail.

Same problem here with an AT&T G4. I've tried 2 different Win7 laptops (one of which has never had any Android drivers/tools installed previously), 3 cables, and even performed a factory reset. MTP Drivers work when booted normally, but fail ("Code 10") when in download mode. Any additional suggestions?
EDIT: As suggested by other posts/forums, this issue can be ignored, and isn't an actual problem. ADB works successfully, even if the MTP device isn't working in Windows' Device Manager. (This MTP device appears in Windows' Device Manager the same as it does when a USB Debugging connection hasn't (yet) been authorized on the Android side. My guess is that since Android isn't fully booted while in Download Mode, there's nothing to approve the connection. Either way, it doesn't affect the function of Download Mode, as long as the other Android-related devices in Device Manager have their drivers loaded successfully.)
TL;DR version: When in "Download Mode", as long as the other Android-related device(s) in Windows' Device Manager are working, ignore the "Code 10" error / "yellow triangle" on the MTP device. It's not needed for Download Mode to work.

usb not recognized after flash wrong kernel

------------
the problem is solved i just don't know how to delete this thread
-----------
in fact the device is still not yet recognized under twrp but does work under bootloader mode, it's just it's not adb connection but fastboot connection that i got confused
for anyone who have a similar problem, you might find it helpful in the following links that i tried before i realized my stupidness...
http://sciologness.com/download/903...-configuration-descriptor-request-failed.html
http://adbdriver.com/downloads/
http://developer.samsung.com/technical-doc/view.do?v=T000000117 // this is the samsung page, but after installation you might find in your usb driver compatibility list something like "samsung adb interface" and that might do the trick
--------------original post-----------------
hey guys,
i just followed this page to root my device
http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
everything went fine until i flashed the xceed kernel.img for my stock rom...
and when booted into twrp and connect to pc meanwhile, the tablet it's not recognzied via usb anymore, and it says 'unknown usb device' error code 43. the tablet can either be rebooted into the system or recognized under the bootloader mode
i tried to install the google usb driver manually but it says
'This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)'
anyone please help
i don't think it's the problem of my cable or the connecting ports...
my os is win10 64
thanks all
G