Related
Hello,
I've been googling around for a workaround but I cannot seem to find one that actually works. The problem is, when I try to connect my phone to the PC and, for example, want to flash it with an official rom - it simply cannot find it. It can find the SD card when I mount it.
When I put it in, Windows attempts to install a few drivers but fails at the ADB. According to several sites, I can just use the one from HTC Sync or from the Android SDK. It installs fine but it still doesn't seem to be able to contact my phone. I cannot sync it either.
Anyone got an idea? I seem to be on my last nerve.
I dont have any problems here. What windows beta release do you use?
Final version. Released today. It's Windows 7 Professional.
First, set the phone to debugg mode...
Ok here we go (at least it works for me)...
1.- Remove the drivers actuaslly installed (it might get tricky, as I don't know exactly how to remove the registry keys)
2.- Once you have cleaned windows from the drivers, connect the phone to the computer and let it recognize everything (Probably it would not recognize the ADB drviers, so far we are good)
3.- After the drivers are installed, go and check in control panel/Devices Administration (or something like that... I have Windows in spanish so I don't know exactly how is called on english... By the way, sorry if my english sound a little bit weird =P..)
4.- Here you should see probably a device as "not recognized" or what ever is called... Here is the part where you need to select the driver manually.
5.- Check the phone driver folder (you should have it, if you don't get them)
6.- When you see the different options, select the one called HTC Dream Composite ADB Interface
7.- You are done =D...
I hope I made it clear enough for you...
If you have any doubt, add me to MSN xnofrostx - hotmail.com (I don't put the @ because I hate spam xD so you should add only the xnofrostx =P...
Hope you can get it to work...
I couldn't, for the life of me, get it to work so I put Windows XP on a vmware and flashed it through there. Works wonders.
Sorry for not being able to help.
I run Windows 7 Evaluation copy. I have had no problems. In fact there was nothing for me to set up, it just saw it on first attempt.
trillex said:
Hello,
I've been googling around for a workaround but I cannot seem to find one that actually works. The problem is, when I try to connect my phone to the PC and, for example, want to flash it with an official rom - it simply cannot find it. It can find the SD card when I mount it.
When I put it in, Windows attempts to install a few drivers but fails at the ADB. According to several sites, I can just use the one from HTC Sync or from the Android SDK. It installs fine but it still doesn't seem to be able to contact my phone. I cannot sync it either.
Anyone got an idea? I seem to be on my last nerve.
Click to expand...
Click to collapse
I'm on Windows 7 Ultimate. Driver from AndroidSDK and HTC Sync works perfectly for me. I can access everything except cannot sync with HTC Sync.
Rogers Magic
Rooted
CyanogenMod 4.1.9999
I cannot sync either, when installing the sync program it gives an error but continues installation, then my phone says it cannot detect htc sync on my computer, but im gonna try this link http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
trillex said:
I couldn't, for the life of me, get it to work so I put Windows XP on a vmware and flashed it through there. Works wonders.
Click to expand...
Click to collapse
I'm glad you decided to upgrade back to XP!
IE_DSM said:
I'm glad you decided to upgrade back to XP!
Click to expand...
Click to collapse
LOL, Windows 7 is a damn nice release and a lot faster than both xp and vista compared to the hardware available at the moment off release.
i am also using windows 7 beta and final
no issues at all. and i also think, that win7 is really good piece of software. far superious to win xp
Hey guys,
Reviewed alot of the posts here, but can't find out what the status is with the native functionality of cell modem access on Win 7...
I just got Windows 7 Pro installed (it isn't the beta, or hacked, it's retail), Everything is working (touchscreen, aero, etc...) with the exception of the native cell modem internet sharing.
I do know there is a hack by using the USB tool to get it working, however I'm just curious if anyone has it working the proper way as intended by HTC?
I'm noticing there are no devices missing drivers in the device manager, the HTC control app works fine, and even can control the modem on the snapvue side of things...
But there is still no "virtual" network adapater inside of the Network adapters on the system...
Scratch that...
I'm a tool. My shift has been sitting for 6 months after not being used until today when I decided to upgrade...
Totally forgot the virtual adapter only shows when no other connections are present...
Everything is working now
Hi!
How did you get the TS to work?
I've been trying to get the touchscreen to work with the latest W7 but no soceess. I've followed the guide on XDA and all tips on XDA but no sucess.
Could you maybe write down how you did even if it was just a regular installation? I've reinstalled and all but the ts just won't work!
Josasp said:
Hi!
How did you get the TS to work?
I've been trying to get the touchscreen to work with the latest W7 but no soceess. I've followed the guide on XDA and all tips on XDA but no sucess.
Could you maybe write down how you did even if it was just a regular installation? I've reinstalled and all but the ts just won't work!
Click to expand...
Click to collapse
To be honest, I was an idiot and had a horrible install... Here's what I did if you dare try..
1. Install all the drivers (NOT using compatibility mode and "Run as Admin")
Only a few things worked, it was horrible...
2. Re-installed ALL the drivers, using the list that HTC recomends. Keep in mind that the device manager will show some of the devices as not working, after you install all the drivers in Compatibility mode, along with "Run as admin". Go to the Device manager, and right click on all the problemtic devices and select "Uninstall".
3. Restart the computer, then Aero will start bluescreening and crashing. Boot into safemode (with networking). Go to the device manager and disable both Video card adapater shown.
4. restart and go to Intel's website and download the latest Chipset INF installer, and Video drivers for windows 7. Install the Chipset INI first, then video drivers...
5. At this point I can't remember but I thinnk the touchscreen didn't work. I just ran the Touchscreen installer one last time, and BANG it worked...
Sorry for my horrible instructions, it was a messy install, but everything is working for me now.
Thanks!
I't looks similar to how i've been fooling around with my shift.
Well, at least it's gratifying to know that i may get it to work if keep messing with it
Zhariak said:
Hey guys,
Reviewed alot of the posts here, but can't find out what the status is with the native functionality of cell modem access on Win 7...
I just got Windows 7 Pro installed (it isn't the beta, or hacked, it's retail), Everything is working (touchscreen, aero, etc...) with the exception of the native cell modem internet sharing.
I do know there is a hack by using the USB tool to get it working, however I'm just curious if anyone has it working the proper way as intended by HTC?
I'm noticing there are no devices missing drivers in the device manager, the HTC control app works fine, and even can control the modem on the snapvue side of things...
But there is still no "virtual" network adapater inside of the Network adapters on the system...
Click to expand...
Click to collapse
Hi just have a quick question: When you upgraded your vista to Win 7, do you used the upgraded disk or start from the OEM win 7?
I actually didn't upgrade.
I used a Open Business Volume disc I have that was issued to my company. I guess it's the same thing as a retail copy.
I did a fresh install.
Zhariak said:
I actually didn't upgrade.
I used a Open Business Volume disc I have that was issued to my company. I guess it's the same thing as a retail copy.
I did a fresh install.
Click to expand...
Click to collapse
Thanks! It is OEM Disk. And one more think are you install the Win 7 pro or the ultimate? Thanks again. I really appreciate your help.
I could be wrong, but I think I did Win 7 Pro
Thanks again...I will try to install win7 pro on mine. I think 7 ultimate for Shift is too much coz the processor itself is only 800Mhz.
I have been having problems on XP(not regarding flashing). I am just tired of XP so i was thinking on using Ubuntu. Im going to get to the point now, Is there any software that i can use to flash my phones on linux?
I dont think so really. I have been using linux for a few years and not really seen anything for flashing wm phones. One option i was thinking of was setting up an xp install in a virtual machine and then trying that. I guess you could also try using the windows flashing app via wine but i just havent had time to do this yet.
If you do find a solution please can you report back here as it would be useful to know.
try microSD instead
well actually I am running a Gentoo OS here and tried flashing in XP in virtual machine in VirtualBox, but it did not work for me (after a certain time a timeout occured). From now on I will always flash via microSD card, I have a spare one I can always use for these purposes. Already flashed two different ROMs and works OK, so no need for XP anymore.
An odd one....
I have one of the HD2 Android releases on my phone, and it's working fine EXCEPT....
USB tethering does not work.
Now here's the odd part.
1. I have two machines. Both running Win7/x64.
2. One loads the RNDIS driver and works fine. The other can't find the driver on Windows Update.
I have no clue what's going on, but the USB signature is VID_0bb4&PID_0FFe, which is valid for the HTC Sapphire.
And, like I said, the other machine -also running Win7 - finds it just fine.
Any ideas?
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
i'm running Windows 7 x64 and when i start usb tethering from android on HD2 there is Android Device driver missing in Device Manager, I've read that Windows 7 already have Remote NDIS support so no need for seperate driver download if you have Windows Mobile Device Center but it ain't working, the same problem as you had.
Luckely, your solution and this separate driver works, Windows 7 complains about unsigned driver but who cares, USB tethering is working
Thanks!
didn't work...
i attempted installing the driver OEM106.inf, but received an error once it was loaded on my pc:
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"
i was having similar problems as Genesis trying to tether my Android phone via USB to my pc and receiving a Remote NDIS driver problem (same as above). I successfully tethered my phone to my PC once (and only once), but after I woke the computer from sleep mode, my pc began giving me errors on the "Remote NDIS based Internet Sharing Device" stating that windows cannot load the drivers ("rndismpx.sys" & "usb8023x.sys"). I haven't been able to tether via USB since then.
Windows Update states the driver is up to date, and when I tried Genesis3's driver fix, it only gave me the same error.
Any ideas?
Running win7/x64 on a toshiba i3, and a HTC nexus 1 running android 2.2.2
The files referenced have somehow been damaged or destroyed. Find them from another machine and put them back, and the OEM file I posted will work.
Those two files have to be on your machine - the OEM file is the pointer to them, but the base-level drivers have to exist.
you may need the latest version of htc sync
i did all my flashing on an xp computer and when i got win7 i just could not get any drivers to work. i downloaded the latest version of htc sync and all the drivers loaded just fine. time to flash this thing again ive had the same rom for two weeks
This is what I was looking for, and it worked for me, thanks!
PISSA! Tried for a while to get usb tethering to work and this did it! Took a minute for windows to sort things out after the driver update but its working! THANK YOU!
DL DesireZ V3.4 final HD2 TMOUS
Hey guys..
This thread popped up first on google and im quite a noob so pls tell me how you include this driver in windows(win7 x64)
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
Worked like a charm, thanks! I just had to update driver with provided file and it started working. Thank you very much again! Bump may not be a bad idea, maybe few more users will solve their problems with this. HD2 isn't a native Android device, so it wasn't that strange that it didn't worked out-of-the-box even with Win7 RDNIS (or sth like that) native support.
raven_raven said:
Worked like a charm, thanks! I just had to update driver with provided file and it started working. Thank you very much again! Bump may not be a bad idea, maybe few more users will solve their problems with this. HD2 isn't a native Android device, so it wasn't that strange that it didn't worked out-of-the-box even with Win7 RDNIS (or sth like that) native support.
Click to expand...
Click to collapse
After I have Device Manager opened, what do I do next?
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
thaaaaaaaaanks.
I have been trying many drivers and tools. This one worked like a charm
I lOVE YOU!
Thanks so much man. you saved me from reverting back to windows mobile, i had about given up on usb teathering with android but you saved me. Im very greatfull.
Not a problem!
still not working
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
I tried this and others ( htc sync, intel android drvrs,) but no success. Any clue what's missing?
i have windows xp, sp3....android 2.3.7 htc wildfire.
oem.inf
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
I would like to share my solution. I modified the oem.inf file in the oem.zip(above) ,by changing the manufacturer name and device id as given in the PC 's device manager(unknown device).
It should work for xp,seven,vista.
Hi!
If you're here, Windows 10 got in your way. Let me explain why.
You see, Windows 10, for some reason has an administrator permission... No, not that administrator permission. Because reasons, Windows 10 has TWO admin permissions! You are the standard one. The superior one is hidden, as a separate user! I don't get it either.
There's a command prompt that unlocks the primary admin account. A quick Google search will yield multiple guides on this matter.
Many, if not all your problems will be solved via this account. I spent 3 hours trying to install some drivers, before I was dumbstruck by the "God Account"... Install everything through that, and use your account normally!
I recommend hiding God in your PC after, since it has total power and some clever virus software might simply hijack it to install itself in the depths of your system, where no antivirus has permission to touch it...
God account on Windows 10 - Cause We hate You! Now, buy a subscription for solitaire!!
Windows 10 if f**k**g $hit.....
Previously I spent days trying to get drivers/ADB working. Impossible. I then used my spare laptop having Windows 8.1, effortless and no issue, the whole process of unlocking bootloader, flashing recovery and SuperSU was instant.
It was not possible with Windows 10 but with Windows 8.1 it was so easy and no issues with drivers or software. Windows 10 is cancer.
kanej2006 said:
Windows 10 if f**k**g $hit.....
Previously I spent days trying to get drivers/ADB working. Impossible. I then used my spare laptop having Windows 8.1, effortless and no issue, the whole process of unlocking bootloader, flashing recovery and SuperSU was instant.
It was not possible with Windows 10 but with Windows 8.1 it was so easy and no issues with drivers or software. Windows 10 is cancer.
Click to expand...
Click to collapse
Well, maybe not cancer, but a really annoying co-worker, that keeps putting your stapler in Jell-O. Xp
kanej2006 said:
Windows 10 if f**k**g $hit.....
Previously I spent days trying to get drivers/ADB working. Impossible. I then used my spare laptop having Windows 8.1, effortless and no issue, the whole process of unlocking bootloader, flashing recovery and SuperSU was instant.
It was not possible with Windows 10 but with Windows 8.1 it was so easy and no issues with drivers or software. Windows 10 is cancer.
Click to expand...
Click to collapse
It's possible that you guys just had previous drivers installed that were conflicting. I doubt it's Windows 10, as mine connected easily and quickly. Some phone drivers tend to stay in your system eventhough you might not clearly see them. I also used the 15 seconds ADB installer, for what it's worth. Maybe you guys should try that.
radiohead14 said:
It's possible that you guys just had previous drivers installed that were conflicting. I doubt it's Windows 10, as mine connected easily and quickly. Some phone drivers tend to stay in your system eventhough you might not clearly see them. I also used the 15 seconds ADB installer, for what it's worth. Maybe you guys should try that.
Click to expand...
Click to collapse
Even when trying the 15 second ADB installer, made no difference...
For this very reason, I upgraded my PC from Windows 10 to Windows 8.1, couldn't of been any happier.
I second the adb installer. It's easy, although the topic is more related to drivers that are outright rejected by the system. Sometimes, it's the fault of the certificate, or the lack of~. If there were old drivers, the device would've been recognised, and not treated as an "unknown device". I was livid when my Nexus 7 wouldn't work. XP It's basically a method of avoiding possible bugs or certificate issues. Again, you're correct in suggesting the adb installer! It takes the faff out of the job!
kanej2006 said:
Even when trying the 15 second ADB installer, made no difference...
For this very reason, I upgraded my PC from Windows 10 to Windows 8.1, couldn't of been any happier.
Click to expand...
Click to collapse
I dunno. I would start with a clean install of Windows 10, cause , to my surprise, it's different than the upgraded version! It's utter madness. The clean one is more stable, faster, less glitchy, AND DOESN'T BREAK MY WoL SETUP AFTER EVERY F...UPDATE!!!... I'm not mad... ?
Rayman1113 said:
I dunno. I would start with a clean install of Windows 10, cause , to my surprise, it's different than the upgraded version! It's utter madness. The clean one is more stable, faster, less glitchy, AND DOESN'T BREAK MY WoL SETUP AFTER EVERY F...UPDATE!!!... I'm not mad... ?
Click to expand...
Click to collapse
I have a clean install of Win 10 also. Maybe that's why I didn't have connection/driver issues. Reason I mentioned old drivers being hidden was because that's exactly what happened to me with a Nexus 6 before doing a clean install. My computer wouldn't recognize it also, and it just kept showing unknown device. I had old Samsung and ZTE drivers still hiding in my system, and the only way I found them was when I used this Nexus tool: https://forum.xda-developers.com/showthread.php?t=1766475
Hii to all having issues with windows and android..
One thing
I have already the fall creators update before it is even released ( Oktober 17 it will be official )
Love to use windows and usually do not have trouble with android and Windows
The thing is, if you need the extra administrative privilege you need to go under
Settings then
recovery then
advanced then
restart the system for advanced options
And then choose for some drivers like adb fastboot and other stuff.. choose some opitons
You will be given like options from 1 to 9 or 10..
then you press the number 7
Number 7 means you will remove the extra driver signature the windows is asking for every driver
After pressing 7 the system will reboot..
then you need to reinstall the adb fastboot drivers
Now it will give you a window with red color .. asking you.. do you want to install this driver without the signature that is usually required..
and then you click on yes..
from that point on you will allways have that driver installed and
working in the way it should or let me say in the way every driver works after you install it..
And yes it is trouble sometimes to get adb and other android stuff working on windows 10
couse it sometimes is the way that you have all the correct files and did all the correct steps
But the thing is it is not working couse windows 10 is in that point not letting you to do that thing
couse it things its harmfull for you system or sometimes you just need to put one setting off or on
and Voillaa everything is working..
So do not give up on things try to google out the solution by the error or you tube is having
often some good tutorials on what and how it needs to be done in windows 10