Related
This is intended for people which run KIES and device is not seen, neither the message "connecting..." appear on KIES, and MTP application does not start on Samsung galaxy.
If you moved com.android.* and com.sec.android.* into some path which is not /data/data you may have this problem. At least this is what happend to me, after I moved file back MTP start and Kies recognize the device.
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
disabling launcherpro fixed it for me.
im told other launchers cause issues too
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Yes, you MUST run TWlauncher (standard launcher in Touchwiz) and if you got Windows 7, you might wanna download some third party drivers.
I'm on Windows 7 64bit and I downloaded the win7 x64 samsung galaxy s drivers form softpedia.
well the mtp driver doesnt install on my 64 bit computer.
It works on windows 7 32 and 64 bit just fine
No third party drivers and no magic. It's all down to individual system config otherwise it would be the same for everybody.
Incidentally, there is an update out for Kies taking it to version 1.5.1.10074_45
g0c said:
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
Click to expand...
Click to collapse
have you googled for FileSearcherforKiesFix and tried that? the only thing that fixed it for me.
Strange. Kies works fine on my both computers: Win7 x64 and WinXP. Had some issues before, but new Kies works without any issues.
hello all,
i got the gt-i9000 like 2 months back the kies s/w was workin fine for the first few days now the app itself fails to lauch even if the fone is not connected.
I have uninstalled and reinstalled kies s/w like a million times.
The installation is always successful but when i click on the kies icon to start the program nuthin happens :s
Please help.
Oh yeah i am running Win7 32bit legit.
BronzedDroid said:
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Click to expand...
Click to collapse
Works fine for W7 32bit flawlessly to. Also for me on 2.2 it works under launcher pro as well, added bonus of not having to use home switcher (or the like) every time I connect the phone
rocketpaul said:
well the mtp driver doesnt install on my 64 bit computer.
Click to expand...
Click to collapse
It works fine on my copy of Windows 7 64bit, but I have to switch to touchwiz, and go to driver recovery in the kies menu.
I use XP at home and at work.
From home with JP6 and Kies 1.5.3.10093_82 I can connect fine using a cheap USB cable and with phone having Samsung Kies as default running LauncherPro.
At work Kies cannot connect to the phone... it just says connecting, please wait.... all the time, its wierd...
I guess I have to remove all the USB hubs on the work computer.... Will install Windows 7 Pro 64 bit at work soon so... maybe ill just wait until then...
Kies not working with LauncherPro. You have to create a shortcut to MTP Application, when you connected the phone and selected Kies need to start with this shortcut.
This is the only way to connect Kies with LauncherPro.
Somewhere I read about this, LaucherPro not recognised like TW.
Hope this helps.
The only way I have ever ever gotten kies was following these steps:
1. Completely close kies
2. Connect your phone
3. Open up device manager, find I9000 (should be under portable devices), right-click and disable (if device manager lags after you click disable then unplug the phone)
4. Replugin the phone and wait for it to say connected on the phone's screen
5. Re-enable I9000 in device manager
6. Fire up Kies and it should connect
These steps have worked every time for me
ps: I'm on Windows 7 x64
http://arvindgaba.com/computer/sams...o-install-for-samsung-galaxy-s-kies-resolved/
Not tested but seems to be approved
I'm on linux so i never used kies. Jusi odin all the way and i have nothing to complain about
This issue has become rediculous. Samsung fail so much with this usb ****. I run Win 7 32 bit and kies previously worked and even when it occassionally wouldn't I used odin.
Now unfortunately the phone just isn't recognised even after various driver and spftware reinstallations and registry deletions etc... etc... etc....
Can not in any way get windows 7 to acknowledge my defy in bootloader or USB debugging mode no matter what I try.
Have an old WinXP laptop that I do all my rooting needs on, but I would like to know why the heck the motorola drivers for win7 don´t recognize their own product?
Have recently uninstalled the motorola package and reinstalled, letting the computer restart sufficiently in between, but nothing...
It finds the s flash omap3630 by name, but no driver for it. I have even let it search through the entire windows folder for it but nooo... nooooo!
Annoying to say the least.
Plus the fact that it works like clockwork (!) on the XP computer tells me that there´s something terribly wrong with motos win7 coding attempts.
Well... I'll probably try this for another week or so then give up and stab myself in the heart with a used fork!
...unless anyone wants to chip in!
/J
Which "Motorola package" did you install? You need the USB driver.
http://developer.motorola.com/docstools/USB_Drivers/
Works like a charm for me on Win 7.
Problem Solved:
Had to go into the computer's Device Manager, find the OMAP3630 device, choose update driver and then browse the computer manually.
Pointed it to
c:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers\
-Then it installed correctly in bootloader mode.
Whew... I searched the motorola log file to see where they installed to (the drivers) and finally I cracked this nut! (Takes a nut to crack a nut)
There go! If anyone else has problems with this then here's the solution!
/Jimmy
k1337Ultra said:
Which "Motorola package" did you install? You need the USB driver.
http://developer.motorola.com/docstools/USB_Drivers/
Works like a charm for me on Win 7.
Click to expand...
Click to collapse
Just did this and worked a charm for me as well...thanks mate!!
k1337Ultra said:
Which "Motorola package" did you install? You need the USB driver.
http://developer.motorola.com/docstools/USB_Drivers/
Works like a charm for me on Win 7.
Click to expand...
Click to collapse
Yep, that is one of the packages I tried... That and 4.8.0 and a whole bunch of others (uninstalling inbetween) but no driver for bootloader or USB debugging in windows 7.
I really had to find the install folder myself and point the omap device to that folder manually.
Why the hell do they leave the device drivers in a "Program Files" folder instead of a "Windows" folder (like the ones drivers are supposed to go)?
And why does the installatiion package work flawless for most people but not for some?
Anyway... I don't care at this point. Problem solved.
If you have this problem, search for the driver manually in the folder I specified above. Then it kicks in!
/J
I'm from the Evo 4G section of xda and just bought an Epic 4G from a friend to play around with. I've rooted and fully customized my Evo 4G and my uncle's Samsung Infuse. So I am not new to the rooting side of these phones. However, I just can't seem to get this to work no matter how hard I try.
Ok so I have done Google searches and sifted through the various "fixes" here on xda....I cannot, no matter what I do, get my epic 4g to be recognized on my Windows 7 64 bit.
I've downloaded and installed about 3 or 4 different USB driver files. I've gone through 2 different cables. I've uninstalled and even updated drivers via Windows. And I've installed and updated Kies. I bought the phone from a friend of mine who had done a full system restore before he gave it to me. So if there were any system issues they should be gone. When I plug in one of the cables the phone shows that the USB cable is connected and I have USB debugging on. But my computer shows "Uknown Device." Does anyone have any suggestions for me please?
I've included screenshots of what my computer shows me. Any help, or reference literature that I may have overlooked, that you guys can provide would be extremely helpful.
There's a few reasons this could be happening. You may want to try different USB ports on your computer or connecting through a USB hub. Also, make sure you're using the official Samsung drivers (you can search for them on XDA).
Otherwise, go to the dialer on the phone and punch in ##8778# and under USB make sure PDA is checked instead of modem. Hope that helps.
I too could never get win7x64 to work but had no problem on other pc running win7x86. I wasted hours trying. Uninstalled everything, removed all references in registry, used usbdevview, device manager, different usb ports, win update, and on and on and on. Gave up since I had other computer and it just worked 1st try. Please pm me if u find the solution. Would still like it to work on 64 bit. My thought is the 64 bit driver, but I hear others are working. :-O
Sent from my SPH-D700 using XDA App
BillyBob3 said:
I too could never get win7x64 to work but had no problem on other pc running win7x86. I wasted hours trying. Uninstalled everything, removed all references in registry, used usbdevview, device manager, different usb ports, win update, and on and on and on. Gave up since I had other computer and it just worked 1st try. Please pm me if u find the solution. Would still like it to work on 64 bit. My thought is the 64 bit driver, but I hear others are working. :-O
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Mine works fine on my 64bit Laptop. I had to update drivers once though since going to GB leak broke it. On my desktop it will only work if connected in the rear USB port.
Sent from my SPH-D700 using XDA App
I've used atleast 3 different computers with 64 bit windows 7, I never did anything special except for download the drivers from samsungs website...
I don't know what it is because I couldn't get the computer to recognize my phone on my uncle's laptop (which runs Vista 32). It kept giving me the same "Unknown Device" message when I went to look at the drivers.
Concordium said:
I don't know what it is because I couldn't get the computer to recognize my phone on my uncle's laptop (which runs Vista 32). It kept giving me the same "Unknown Device" message when I went to look at the drivers.
Click to expand...
Click to collapse
Where it says unknown device double click on that then go to update driver then browse to location of unzipped samsung drivers.
Sent from my SPH-D700 using xda premium
Welcome to the Epic 4g xda section! It just so happens I was looking for Windows 7 64-bit drivers earlier today.
Here's where I found them: http://forum.xda-developers.com/showthread.php?t=798067
Then scroll down to the section "2.3 – ROOTING" and you'll find the listed drivers there.
jdawg101 said:
Welcome to the Epic 4g xda section! It just so happens I was looking for Windows 7 64-bit drivers earlier today.
Here's where I found them: http://forum.xda-developers.com/showthread.php?t=798067
Then scroll down to the section "2.3 – ROOTING" and you'll find the listed drivers there.
Click to expand...
Click to collapse
That post and those drivers are old...
Go here and get the drivers from Samsung:
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
AFAIK, that package should install the correct drivers for the OS.
GL
=]
I install 32 and 64 bit drivers for the i9000
Sent from my SPH-D700 using Tapatalk
I have literally the same problem, phone was reconized and connected fine when i was running xp 32 bit, installed windows 7 64 bit and nothing i do will work. Was your problem ever resolved?
All i can say is try extracting the drivers thru 7zip
then extract the files it gives you
then u should see like a folder and then copy and paste the
folder in the c: program files
and then go back to device manager and then actually manaually search for
drivers and that should work cuz it worked for me im using Windows 8
unfortunately that is one of the exact ways I tried to do it, thanks for the input tho. Just incase I over looked something searching for the driver manually, what sub category should my phone be under in device manager? thx
For those having trouble getting the drivers installed in Win7(x64/x86).
A workaround could be to use WUBI (Ubuntu's windows based installer that adds an option to boot to Ubuntu, while allowing it [Ubuntu] to be uninstalled from windows like a "normal" program).
Install WUBI, boot to Ubuntu, problem solved!
If the point of installing the drivers it to get Odin working...
The WUBI workaround would still work, you would just replace Odin with Heimdall (which is 100x better/more stable than Odin anyway).
I realise this is a lot to do for resolving a driver install problem, but... Heimdall pwns Odin anyway.
GL
;]
apugslovesxda said:
unfortunately that is one of the exact ways I tried to do it, thanks for the input tho. Just incase I over looked something searching for the driver manually, what sub category should my phone be under in device manager? thx
Click to expand...
Click to collapse
It will show up under USB.
Sent from my SAMSUNG-SGH-I717 using xda premium
kennyglass123 said:
It will show up under USB.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
and if your in download mode when you hook your phone up
it will show up under modem it wil not show until you connect your phone
Ok I had to do the following inorder for it to work on my windows 7 x64 bit
I download the samsung epic 4g driver samsung_mobile_driver_v1.3.800.0.msi
I then used 7zip to extract the file
I then used the msi file and installed it
I then used 7 zip and extracted the samsung_mobile_driver_v1.3.800.0.msi file to a directory
I then DISABLE ALL INTERNET ACCESS ON THE LAPTOP BY TURNING OFF WIFI AND OR PULLING THE LAN CABLE OUT THE PC.
I then plug the phone into the pc usb slot
let the pc find the drivers
if it does not find them point to the extracted directory you did above and it will be good.
now do ##8778# and place the bottom into pda and if it cant find drivers point it to the extracted directory.
now turn phone off and go into download mode 1 key and power button and let windows find the drivers
jmuru said:
There's a few reasons this could be happening. You may want to try different USB ports on your computer or connecting through a USB hub. Also, make sure you're using the official Samsung drivers (you can search for them on XDA).
Otherwise, go to the dialer on the phone and punch in ##8778# and under USB make sure PDA is checked instead of modem. Hope that helps.
Click to expand...
Click to collapse
Oh... my... god. I spent hours today trying to figure out how to get this phone I picked up to show me its sd card as a drive. Everyone on the internet seemed to be saying it was the lack of the right drivers, though they all disagreed on what the right drivers were. I tried so many different drivers, no luck.
That above, that I quoted: all it took. Why would it possibly be misconfigured out of the box in such a weird, impossible-to-locate way? Jeez.
(Anyway, I know I'm bumping a super old thread with this first post, but I felt compelled not just to thank this person for restoring my sanity, but also to bump up this thread's relevance for future googlers going as crazy as I was going.)
Good Evening folks,
I'm posting here after spending the better part of 2 days trying to figure out why this doesn't work.
So, i have the following:
model: GT-N7100
Version: 4.1.1
Build: JRo03C - ALJ1
I run a PC with windows 7 and also have a laptop with windows 8.
Now, initially i only wanted to root my device to install an addblocker on it and get rid of some bloatware. so i went and got samsung note2 toolkit here on XDA. (also tried others)
but no matter how i tried the pc (nor laptop) would see the note 2. it would plug in, it would charge... but windows ignored it otherwise.
i have tried al 8 of my USB ports on the desktop, and all 3 on the laptop. none of them work
3 different USB cables.
re-booted more then times then i can count.
i have manually installed the samsung drivers.
i have tried installing the windows MTP Porting kit
all to no avail.
So before i can even START to root... i need it to to play nice with my machines... anyone have ANY suggestions on what the hell is going on here.
If your main priority is to root then use exynos abuse
Sent From Samsung's Galaxy Note II Using Internet
UtkarshGupta said:
If your main priority is to root then use exynos abuse
Click to expand...
Click to collapse
hi,
Thanks for that! found the APK file and got it on the phone through email and it's rooted, so my mission is accomplished...
but my problem still persists:
why oh why wont windows just play nice with the phone?
Did you install Kies on your PC? That program needs to be open when you connect your phone and then it will install the needed drivers.
Sent from my GT-N7100 using xda app-developers app
el_roy1985 said:
Did you install Kies on your PC? That program needs to be open when you connect your phone and then it will install the needed drivers.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Or install the drivers using the Note Toolkit http://forum.xda-developers.com/showthread.php?t=1923956
Does it show as an unknown device in windows under device manager?
I'm having the same issue but I have a suspicion that its the USB port on the phone itself as my gnex can use the same cable/USB port and show up as mtp.
Sent from my GNote 2 using xda premium
my windows is same
My Note 2 N7100 is 'seen' by my windows 8 machine, but it doesnt seem to copy/ paste anything. Pops up with an error. The same happens on a Mac Lion machine. Installed the Android File Transfer app, but the moment I connect my phone, it pops up a message saying please restart your device so that it can be detected. I am tired of transferring individual files over AirDroid Any help?
anirudh412 said:
My Note 2 N7100 is 'seen' by my windows 8 machine, but it doesnt seem to copy/ paste anything. Pops up with an error. The same happens on a Mac Lion machine. Installed the Android File Transfer app, but the moment I connect my phone, it pops up a message saying please restart your device so that it can be detected. I am tired of transferring individual files over AirDroid Any help?
Click to expand...
Click to collapse
What's the error message?
Happened to me before, un install kies on your pc reboot, download from Samsung website and install again, should work
Sent from my GT-N7100 using xda app-developers app
first of all I forgot to mention that this should've been posted in Q&A section
for the problem try the following steps. after each one of them try connecting again. keep net disconnected while you follow the steps.
if it starts working then stop other wise continue.
1)use a diff comp, but you already did that , use a different cable, you didn't mention it
2)try uninstalling drivers via programs and features.
3)try installing drivers - preferably via mskip's toolkit
if you have windows 7, then directly install it
if you have windows 8, then first disable driver signature enforcement via this guide's last question.
4)try re installing windows. if you don't wanna do that then
open device manager
in view -> show hidden devices
delete each one that says samsung, note ii or note 2, android, google, adb, gt-n7100, n7100
this will ensure that you truly remove drivers
follow step 3) after this.
Hope I helped
All the usual and helpful ideas have been listed and you should definitely work thru those to make sure you are not missing something obvious but critical. I also use Win8 (64) and all was well with my Note2 showing up as an MTP device and wll working then one day, seemingly spontaneously, it suddenly didnt! When I would plug my Note2 in, Windows would give me a USB error telling me it could nto recognise the device! To cut a long story short, I tried my wife's S2 and IT appered fine as an MTP device happily enough, so that ruled out the cable, the port and the computer/OS.
I then tried my Note2 on my laptop, and once again it came up as USB error, so the problem was following the DEVICE around....
After a lot of googling, I tried on thing that fixed it instantly:
On the phone, go into Settings, Security and delete all the "Device Administrators" which in my case was just my Email app. That did delete my email account from my phone (contacts, email etc) but didnt matter as phone is just a dumb client to the mail server so no loss of any real data.
Once removed, I then plugged phone in and BOOM! MTP device happily appeared! I then went back in and just re-added my email account and re-activated Device Administrator when asked. Working ever since.
Not saying this is your problem, but it was an eye opener to me that the Device Administrator could 'lock out' the USB connection of the device....
Hope this helps.
APK
Temko Firewing said:
hi,
Thanks for that! found the APK file and got it on the phone through email and it's rooted, so my mission is accomplished...
but my problem still persists:
why oh why wont windows just play nice with the phone?
Click to expand...
Click to collapse
Did the APK file automatically root your note2?
Arikara said:
Did the APK file automatically root your note2?
Click to expand...
Click to collapse
Yup it do
Sent from my GT-N7100 using xda premium
i have problem in xp .it doesnot install driver properly but gud in win 7.first uninstall all drivers then installed drivers without connecting phone.when instal done then connect phone
nabilsweet007 said:
i have problem in xp .it doesnot install driver properly but gud in win 7.first uninstall all drivers then installed drivers without connecting phone.when instal done then connect phone
Click to expand...
Click to collapse
I would also recommend checking your Windows Update log - especially if you have it set to automatic updates. After I installed the drivers off of the Samsung website, Windows Update tried to "Update" my drivers to an older version (I do manual Windows Updates). The first time it asked, I let it, and my phone couldn't connect anymore. Once I stopped that silliness I stopped having problems.
same problem usb not conecting with my pc windows7
all this is my same problem which I facing help me about how to slove this matter
Temko Firewing said:
Good Evening folks,
I'm posting here after spending the better part of 2 days trying to figure out why this doesn't work.
So, i have the following:
model: GT-N7100
Version: 4.1.1
Build: JRo03C - ALJ1
I run a PC with windows 7 and also have a laptop with windows 8.
Now, initially i only wanted to root my device to install an addblocker on it and get rid of some bloatware. so i went and got samsung note2 toolkit here on XDA. (also tried others)
but no matter how i tried the pc (nor laptop) would see the note 2. it would plug in, it would charge... but windows ignored it otherwise.
i have tried al 8 of my USB ports on the desktop, and all 3 on the laptop. none of them work
3 different USB cables.
re-booted more then times then i can count.
i have manually installed the samsung drivers.
i have tried installing the windows MTP Porting kit
all to no avail.
So before i can even START to root... i need it to to play nice with my machines... anyone have ANY suggestions on what the hell is going on here.
Click to expand...
Click to collapse
I was having the same problem, but I was using a USB cord that I had from my old phone. Switched to the white one that came with my Note 2 and it started working.
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.