Related
Windows VISTA Config guide
NOTE: Vista Rom update Utility(attached at the end of post #4) is required when Flashing Roms on Windows Vista.
To Download This Guide as a PDF, click HERE
To Send This Guide as an E-Mail, Click HERE
To Print This Guide, Click HERE
Written by MrVanx <<ALL CREDIT GOES TO THIS MAN. This is a direct Copy of the original document.
Wednesday, 18 April 2007
(Thanks to invictive for the screenshots and testing) << I LINKED TO HIS SCREENSHOTS
UPDATE: Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first.
One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista x32
Drivers for Windows Vista x64
NOTE:: If you are using a x64 bit computer, you will need to boot up with driver signing enforcement turned off. To accomplish this, you will need to press F8 during boot up. If you do not do this, the 64 bit drivers will not install properly and this tutorial will not be of any use to you.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon.
In the connection settings menu untick "allow USB connections" then press OK. Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync". This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf" Vista x64 users select the file "wceusbshx64.inf" Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
Click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which Vista uses when the device is in bootloader mode.
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Windows Mobile Based Device.
Thanks!
I saw this same article somewhere else and already did this
Thanks for posting this here though! Also, it helps to use the windows mobile device center 6.1 update. It works both on my desktop Vista Ultimate computer and my mom's home premium laptop
Also, a little sidenote, if you want windows mobile device center to display your own phone as the image instead of the standard PDA/PPC Phone/Smartphone image when you sync follow these steps:
Disable USB connections in Windows Mobile Device Center
Uninstall the drivers for your device from device manager
Save the image you want to use as an icon file called sync.ico
Save the icon to the windows folder on your ppc
Disconnect your PPC and enable USB connections again
Wait for the computer to reinstall the device driver and it will sync with the new icon
Sorry, I don't remember who first suggested this. I take NO credit for this whatsoever.
Woooooooooow !!!
dharvey4651
Awesome!
Must say,cudn't have been better than this,commendable job.
zabardast_1 said:
dharvey4651
Awesome!
Must say,cudn't have been better than this,commendable job.
Click to expand...
Click to collapse
Thanks. It took me a while to type up but as long as it benefits the community, it was worth it.
thanks you very much for the write up
great bro, i will add it to TNT notes
works nice, but the Vista update tool is out of date. Cant flash my Wizard with it.
Doesn't work with G4.
neonkoala said:
Doesn't work with G4.
Click to expand...
Click to collapse
Have you tried my tutorial on how to dual boot your computer so that it has Vista and XP on it? I started having problems with my phone not flashing properly after like 2 weeks. I installed a few Windows updates and then the drivers stopped working so I set up my computer to have Vista and XP on it so that I can use Vista on a daily basis and only use XP when I'm working on my phone.
neonkoala said:
Doesn't work with G4.
Click to expand...
Click to collapse
Anybody have found a Vista Update Utility for G4?
Thanks!
This got my G4 to finally stop giving me connection errors in the boot loader!
Now I can finally get my G4 unbricked
I used the shelltool successfully in Vista 32bit, but the world isn't liking me for flashing in 64bit so far... Either way, thanks!
Also, you might want to update the tutorial to tell 64bit users to boot up with driver signing enforcement turned off (Press F8 on boot up) else the 64bit drivers won't take.
frazell said:
Thanks!
This got my G4 to finally stop giving me connection errors in the boot loader!
Now I can finally get my G4 unbricked
I used the shelltool successfully in Vista 32bit, but the world isn't liking me for flashing in 64bit so far... Either way, thanks!
Also, you might want to update the tutorial to tell 64bit users to boot up with driver signing enforcement turned off (Press F8 on boot up) else the 64bit drivers won't take.
Click to expand...
Click to collapse
Thank you very much for that piece of input. I will definitely update the tutorial as per your advice to better assist 64bit users.
Thanks again, Dan.
The Vista RUU doesn't crash as I was used to, but it doesn't run either (with a prophet that is) it 's complaining about "beeing outdated".
Are there any solutions yet known for this inconvenience? Thanks in advance!
Vista RUU
Is there a newer version of the ROM update utility? The one posted above doesn't run, but, rather, just complains that it's out of date!
The driver method detailed above works great (with the caveat for x64 users that they have to disable the driver signing restriction), but unfortunately I'm still no further along because I can't seem to find an RUU that will work!
If anyone knows of one that really works on Vista, please pass it one. (I've searched through all these postings, but none seem to work!)
Thanks much for the detailed driver instructions!
Thanks for the Vista instructions, helps me out! but I ran into a problem degradeing to unlock my CID. Im not sure its me,software,and/or myphone but I got a invalid Vender ID error 294. I am using a wizard 8125 for this and using Vista. This is my first time, but im loaded on knowlaege unless i missed somthing. Thanks in advance.
Still no luck with Vista!
Has anyone found a complete method to flash on Vista? As posted above, the RUU included with this thread doesn't work. It gets most of the way through and then, just before starting to flash, gives a "This utility is out of date" error and exits.
Again, the driver instructions given in this thread are sound, but without a working RUU they only give you half of the solution for flashing on Vista.
I have successfully flashed using Shelltool, but it works sporadically at best.
Does anyone have a start to finish solution?
I followed the instructions given in this forum and they seemed to work perfectly for me.
here is my 2 cents though i had initially flashed my device using the origional t-mobile rom (SPL/IPL 3.08 radio 2.69) and it worked without any problems. It was only when i tried flashing with a cooked rom that it gave me problems.
Here are the RUU file from that rom and hopefully someone can figure out why it worked
Hello,
I have already moved to Windows 7, which is very stable and much faster then Windows Vista...
There are some problems with the Windows 7 and USPL...
Is there a configuration guide, which explains the procedure, how I can manage the USB connection problems within Windows 7.
Many Thanks
Roman
You need to update the USB drivers.
The following post will explain how. This works for Windows 7 aswell as Vista.
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
One thing to note, you have to put your phone in bootloader and connect it via USB for it to show the Mobile Device - HTC USB in Device Manager.
One laptop I was on I knew I had to apply the fix on so hadn't tried without updating, and took me forever to find out why I couldn't find the driver to update.
I used a small program called "Driver Signature Enforcement Overrider 1.3b".
Its freeware for using unsigned drivers in Windows 7.
I'm using Windows 7 x64 and USPL works perfect now.
Thanks
standish said:
You need to update the USB drivers.
The following post will explain how. This works for Windows 7 aswell as Vista.
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
Click to expand...
Click to collapse
Hello,
Had to upgrade my Windows 7 to build 7077 first....!
Then it worked @ 1st try... ;-)
Roman
I have problem with installing driver on Windows 7 64-bit (build 7077). I always get error: This device cannot start (Code 10). Does anyone have solution for it?
I had to get to 7077 as well, i couldnt make it start on 7057 or 7068 either.
I just solved it, but I can't explained how... I tried it again and again.. did some restart of HD and of Windows 7 and finally I was successfull . My tip is to re-connect HD on USB before installation...
I use 7077 x64 and no issues with it whatsoever. I had no issues at all with any build and actually it gets the drivers and Windows Mobile Device Center automatically for me. Check your system drivers like chipset and usb controller for updated versions maybe?
Thanks
Many thanks for the solution that you give to us.
I have been testing every release of Windows 7 since 7000 and as long as you install WMDC (Windows Mobile Device Center 6.1) and then update the HTC USB Sync driver (put your phone into bootloader and update the driver in device manager with the one from the guide in my signature) you won't have any issues flashing roms. This is for both 32 and 64-bit versions of Windows 7.
The cyanogen rom 4.2.3 has USB tethering support, but I can not get it to work, mainly because of missing information/documentation.
In 'settings' 'wireless controls' there is a nice 'Internet tethering' option to switch it on. When I switch that on then my Windows XP PC shows an unknown device 'Andriod Phone' and would like to install drivers for it. Where can I get these drivers from ?
Markus
I would also like to know how the usb tethering works for a mac as well. Didnt find any information on that. Thanks in advance.
You may need to get the drivers from the Android SDK, but with regards to USB tethering, your phone should be recognised as an NDIS based network device and installed automatically by Windows. Not sure about XP, but it installs automatically on Vista and 7
Under Ubuntu Linux (from an end-user perspective), when a G1 is connected with USB tethering enabled, network manager connects as if the phone were a standard, ethernet connection.
Shane2 said:
You may need to get the drivers from the Android SDK, but with regards to USB tethering, your phone should be recognised as an NDIS based network device and installed automatically by Windows. Not sure about XP, but it installs automatically on Vista and 7
Click to expand...
Click to collapse
I have the Android SDK (1.6r1) and I point the driver install wizard at the usb_driver directory when he wants to install the device. Despite this the 'Found new Hardware' Wizard come up with 'Cannot install this Hardware'.
Markus
markusb said:
I have the Android SDK (1.6r1) and I point the driver install wizard at the usb_driver directory when he wants to install the device. Despite this the 'Found new Hardware' Wizard come up with 'Cannot install this Hardware'.
Markus
Click to expand...
Click to collapse
For xp you have to install drivers from htc sync software. Just google 'htc sync'. Should have been asked in q&a.
Nothing happens on Mac OS X 10.5.8 neither on 10.6.1
dumfuq said:
For xp you have to install drivers from htc sync software. Just google 'htc sync'. Should have been asked in q&a.
Click to expand...
Click to collapse
Isnt this Q&A? but I think this is it.... http://handheld.softpedia.com/progDownload/HTC-Sync-Download-81096.html
Im trying to get this to work also
I couldn't get it to work on my Windows XP SP2 computer at work. I get a code 10.
Guys, don't forget to use search! I've seen these issues brought up in at least 3 or 4 threads, and tons of posts.
bassderek said:
If you're running windows XP the driver isn't included on your computer. Some people have installed HTC Sync to get the drivers, personally I got them from this post:
http://forum.xda-developers.com/showthread.php?t=445436
I can confirm that the driver from that post works, I am using tethering with my laptop right now to write this post!
Click to expand...
Click to collapse
bassderek said:
Guys, don't forget to use search! I've seen these issues brought up in at least 3 or 4 threads, and tons of posts.
Click to expand...
Click to collapse
The search doesnt always give you what your lookin for if you dont word it a certain way man................
I think im gonna need a step by step.... I got the file... the computer recognizes the device.... But it doesn't register as a connection....
To everyone that is having problems tethering:
I was having the same issues. At first I wasn't able to get it to install, and then it would just keep saying the device couldn't start.
i found a very simple solution. I went into device manager, uninstalled all of my usb ports, and restarted my computer.
When it restarted, it automatically installed the usb drivers, and the tethering has worked ever since.
I could not get this to work either, finally after 3 days of messing with this on my work pc, I got it to work. First download htc sync from here http://www.htc.com/uk/SupportViewNews.aspx?dl_id=631&news_id=270 then unzip and install to your pc. Next tick on the option to usb tether while the phone is plugged in. It will say found Android phone Sdk or something like that. I did this on my xp pc at work that had no htc drivers previously installed. Next I went to my device manager and under network adapters you will see the yellow exclamation point, right click on that and update driver, 1st install from a specific location, 2nd Don't search I will choose driver to install. 3rd Have disk, 4th browse to C/program files/htc/htc driver/driver files/xp_86x then hit open and click ok. It might give a "stop warning" ignore it and continue. When its done installing you should be ready to go.....
badaphooko01 said:
I could not get this to work either, finally after 3 days of messing with this on my work pc, I got it to work. First download htc sync from here http://www.htc.com/uk/SupportViewNews.aspx?dl_id=631&news_id=270 then unzip and install to your pc. Next tick on the option to usb tether while the phone is plugged in. It will say found Android phone Sdk or something like that. I did this on my xp pc at work that had no htc drivers previously installed. Next I went to my device manager and under network adapters you will see the yellow exclamation point, right click on that and update driver, 1st install from a specific location, 2nd Don't search I will choose driver to install. 3rd Have disk, 4th browse to C/program files/htc/htc driver/driver files/xp_86x then hit open and click ok. It might give a "stop warning" ignore it and continue. When its done installing you should be ready to go.....
Click to expand...
Click to collapse
I'm so frustrated with this whole process. I've done every step you've outlined, and I still get a code 10 - cannot start the driver. And I still don't have USB tethering. What am I doing wrong?
nmw407 said:
I'm so frustrated with this whole process. I've done every step you've outlined, and I still get a code 10 - cannot start the driver. And I still don't have USB tethering. What am I doing wrong?
Click to expand...
Click to collapse
I had the same problem with Windows XP SP2. I installed SP3 and it started working flawlessly. What are you using?
Binary100100 said:
I had the same problem with Windows XP SP2. I installed SP3 and it started working flawlessly. What are you using?
Click to expand...
Click to collapse
eeepc 901 nlited XP SP2.
I'll try and push SP3 and retry again tonight. Thanks for the heads up.
nmw407 said:
eeepc 901 nlited XP SP2.
I'll try and push SP3 and retry again tonight. Thanks for the heads up.
Click to expand...
Click to collapse
That's your problem then. Yeah update to sp3 and you will be good. I promise.
I'm running into the same tethering trouble, but appear to meet all the criteria mentioned in this thread and other threads i've come across. the bottom line is i can connect with ADB access and mount my phone's SD card via the usb connection, but tethering doesn't work under several versions of Cyanogen on my laptop. currently I have CM 4.2.12.2 on my rooted Dream. I have windows SP3 installed (installed it twice because problem persisted). I've uninstalled all the USB ports per an above post, rebooted and plugged my phone in. The laptop reinstalls the USB ports, and finds the phone as an "ADB Interface" named "HTC Dream Composite ADB Interface". I can update the drivers with the google SDK USB drivers which makes the device an "Android Phone" named "Android Composite ADB Interface" instead. With either set of drivers installed, once I go to Settings on my phone and enable tethering, the device under windows goes away and instead i get yellow question mark "Other Devices" named Android Phone. I can try to force it to use the same USB drivers but it won't install them.
With tethering turned off, i can successfully type "adp devices" on my laptop console and see that my phone is there. once i turn tethering on, the same command shows no devices.
The Dream works with tethering just fine on my windows pc and shows up as a "Network adapter" named "Windows Mobile-based Internet Sharing Device".
My laptop is a compac presario in case that matters. what do i need to do on it to make tethering work?
just found the solution. a lot of posts were talking about installing microsoft active sync. sounded pointless considering it's an android phone, but it ends up being that the drivers for "windows mobile-based internet sharing device" are part of the active sync installation. i installed active sync, plugged in my phone, enabled tethering and then the laptop installed the correct drivers and it all worked without a hitch. hope this helps others!
hamx0r said:
just found the solution. a lot of posts were talking about installing microsoft active sync. sounded pointless considering it's an android phone, but it ends up being that the drivers for "windows mobile-based internet sharing device" are part of the active sync installation. i installed active sync, plugged in my phone, enabled tethering and then the laptop installed the correct drivers and it all worked without a hitch. hope this helps others!
Click to expand...
Click to collapse
+1
This is totally the problem. I spent hours trying different ways then finally googled it and came here
My PC has never been able to connect via adb, and after weeks of searching around, reinstalling drivers 99 times etc, I finally gave up. That was months ago.
Today I found my Nexus One wasn't able to connect either (yes, new drivers), I knew it was something with Windows. I am using Windows XP 64 bit and I found this:
Does adb not work on windows xp 64? I followed the directions and it didnt work.
no. But there is an unofficial driver for Vista x64 which works on XP x64 too. Read here.
http://www.modmygphone.com/forums/showthread.php?t=11031
Click to expand...
Click to collapse
Eureka! No wonder!!!
Unfortunately, the "fixed" file is extremely old, so it won't work for my G1, nor especially for the Nexus One.
Has anyone out there been able to use adb with ANY Android device on Windows XP 64 bit?
No. I used to use Windows XP 64-bit. You need to upgrade to a new operating system, trust me.
Edit: The one guy who says the drivers work on xp-64 is incorrect or simply lying. I wasted a lot of time thanks to that jackass post.
I'm on win 7 64-bit and it connected without a hiccup.
kozm0naut said:
No. I used to use Windows XP 64-bit. You need to upgrade to a new operating system, trust me.
Edit: The one guy who says the drivers work on xp-64 is incorrect or simply lying. I wasted a lot of time thanks to that jackass post.
Click to expand...
Click to collapse
THANK YOU
Finally, someone else in the same boat! People kept telling me to reinstall drivers a billion times. Now I know it's true. Thanks!
Rashkae said:
I'm on win 7 64-bit and it connected without a hiccup.
Click to expand...
Click to collapse
Windows 7 64 =/= Windows XP 64
Also just found this:
I think this has something to do with 64-bit Windows not being supported by the drivers.
http://code.google.com/p/android/issues/detail?id=1039
Click to expand...
Click to collapse
k0z you are incorrect. I just looked at my usb_driver folder included with the android sdk, it shows the files: androidwinusba64.cat, and a folder named amd64 for 64 bit installations, along with an i386 folder and androidwinusb86.cat for 32 bit installations.
melterx12 said:
k0z you are incorrect. I just looked at my usb_driver folder included with the android sdk, it shows the files: androidwinusba64.cat, and a folder named amd64 for 64 bit installations, along with an i386 folder and androidwinusb86.cat for 32 bit installations.
Click to expand...
Click to collapse
Just because there is a folder and some files for it, doesn't mean it works.
That's why I'm asking if there's anyone who has *actually used* adb on Windows XP 64 bit.
Paul22000 said:
Just because there is a folder and some files for it, doesn't mean it works.
That's why I'm asking if there's anyone who has *actually used* adb on Windows XP 64 bit.
Click to expand...
Click to collapse
actually, thats exactly what it means. the androidwinusb64.cat is the catalog for windows 64 bit.
EDIT: Just follow this guide, but use the latest adb drivers not the one provided in the link: http://forum.xda-developers.com/showthread.php?t=502010
Latest drivers are found here: http://djdoprkngutub.cloudfront.net/usb_driver.zip
While I'm sure a number of attempts have been made, and it's even possible that there are successful drivers out there now, I find this highly unlikely and I know that I personally wasted too much time trying to get this to work on my XP-64 machine.
There's really no support any more for Windows XP-64, in regards to Android or anything else as far as I can tell. Vista sucked, but it's time for you to make the jump to 7 I think
melterx12 said:
actually, thats exactly what it means. the androidwinusb64.cat is the catalog for windows 64 bit.
Click to expand...
Click to collapse
I found these files as well, none of them ever worked. Does this one work? Have you used it? Furthermore, it doesn't look like any of these indicate that they are for Windows XP at all.
well I am not sure that it works on XP 64, but It has been confirmed working on 64 bit Vista and 7.
melterx12 said:
actually, thats exactly what it means. the androidwinusb64.cat is the catalog for windows 64 bit.
EDIT: Just follow this guide, but use the latest adb drivers not the one provided in the link: http://forum.xda-developers.com/showthread.php?t=502010
Latest drivers are found here: http://djdoprkngutub.cloudfront.net/usb_driver.zip
Click to expand...
Click to collapse
Have you tried it? Do you know of anyone who has gotten it working? That's my point
Trust me, I've researched this for weeks on end. I know how to install adb.
And now that I see others with the same problem, I know it's just not possible.
melterx12 said:
well I am not sure that it works on XP 64, but It has been confirmed working on 64 bit Vista and 7.
Click to expand...
Click to collapse
Yes, I know. But not Windows XP 64. ([Edit]: Just updated the title for clarity.) Until there is someone who has gotten it working on XP 64, I am 100% sure it's not possible.
Tell you what. Make a video of you clearly showing that you're running Windows XP 64 bit and adb working, throw it on YouTube, and I'll donate $10 to you. Sound good?
Windows XP? do you know what year this is?
melterx12 said:
Windows XP? do you know what year this is?
Click to expand...
Click to collapse
I'm not sure what that has to do with anything. Just because a newer version is out, doesn't mean everyone on the planet will magically stop using XP.
If Microsoft had their way, we'd have arbitrary full OS updates every year. Obsolescence express!
I just spent the past 4 hours backing up 35 GB of data to DVDRs, reformatting my hard drive, installing Windows XP 32 bit, and reinstalling all hardware drivers etc.
I now just plugged in my G1, installed the usb drivers and BOOM, adb works perfectly.
I'm now 1000% sure that the Android usb drivers cannot be used in Windows XP 64 Bit. Hopefully this helps others out there.
Paul22000 said:
I just spent the past 4 hours backing up 35 GB of data to DVDRs, reformatting my hard drive, installing Windows XP 32 bit, and reinstalling all hardware drivers etc.
I now just plugged in my G1, installed the usb drivers and BOOM, adb works perfectly.
I'm now 1000% sure that the Android usb drivers cannot be used in Windows XP 64 Bit. Hopefully this helps others out there.
Click to expand...
Click to collapse
you spent all that time backing up jsut to install windows XP again? Why not upgrade to 7?
melterx12 said:
you spent all that time backing up jsut to install windows XP again? Why not upgrade to 7?
Click to expand...
Click to collapse
I have not purchased Windows 7.
I never said purchase
I confirm also here that USB drivers shipped with android SDK does not work on Windows XP 64 bit. The phone is correctly recognized by OS but ADB does not list any device.
Is there any news about this issue?
First off sorry I'm sure flammage is coming but I've looked and looked through google and through xda my last ditch effort is to make a post.
I can not get windows 7 to recognize my I've downloaded the latest SDK with usb drivers but each time I try and update drivers I get "windows has determined he driver software for your device is update. Please help me
Go look for the PDANet drivers. You may have to actually install PDANet, but it's painless. Install those drivers, and adb will work for you.
This is mentioned in various stickies and other guides around the board.
This option didn't work please help pda install but didn't overwrite the driver
You need to reboot and hit f8 I believe, then choose the option to allow installation of unsigned drivers. Then try to reinstall the drivers when you boot
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
disgustip8ted said:
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
Click to expand...
Click to collapse
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
codesplice said:
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Click to expand...
Click to collapse
Thank you so much for this help all I had to do was download usbdeview the actual program it self told win 7 what to do so now my nexus one works on win 7, thank you!
No problem! Glad I could help
codesplice said:
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
Click to expand...
Click to collapse
well played, i think youre correct.
ill have to grab that util for work...
disgustip8ted said:
well played, i think youre correct.
ill have to grab that util for work...
Click to expand...
Click to collapse
DSEO is a pretty nifty utility for sure. Provides easy one-click (okay, a few clicks, actually) access to disabling the driver signature enforcement - and even an easy way to eliminate the "Test Mode" watermark that would appear in the bottom-right of the desktop while operating in Test Mode.
There are other methods to bypass the signature enforcement without turning on Test Mode, but I've found that to be the best option. Other approaches use a boot-time hook to basically insert the F8 (and other keys as appropriate - down, down, enter or something like that) keystrokes to "automanually" disable driver signature enforcement for that boot. Any third-party application that accesses things that early in the boot process makes me a bit nervous!