Related
***IF THIS THREAD IS IN THE WRONG SECTION I WOULD APPRECIATE IT IF IT WERE MOVED TO THE CORRECT SECTION. I BELIEVE THIS IS CORRECT BUT I AM NOT SURE. IF ITS NOT MOVED THEN INFORM ME AND ILL POST IN CORRECT SECTION.***
Ok so here is my situation. I have a HP Touchsmart 520-1030 and I am wanting to use windows 8 with the touchscreen. That being said it appears that on both the Developer and Consumer release that the driver for it does not work well with Windows 8 even though it works fine on Windows 7 (I have it dual booted on seperate partitions).
So here is a description of what I have attempted so far.
Downloaded the Driver package from HP's Website and ran. Wouldnt install as gave OS version error.
So I ran in compatibility mode Windows 7 with admin permissions (also taken ownership). I get the same error about the OS version.
I then went to NextWindow's website and downloaded the original (older) drivers from there. It says its installed but does not work (device manager showing touchscreen with a ! on it.)
I then tried to update the driver in DM and search gives an error.
I then browsed to the installation folder of the drivers and it states cant find driver.
I then went back and compared it with windows 7 drivers and see the "touchscreen" driver is NextWindow Voltron Touchscreen. I then compared the Hardware IDs and sure enough they are the same ID's (I believe).
I then used a universal extractor and extracked the package for HP and NextWindow and attempted to manually update the driver through DM. It updates but I get an error with the HP packages (code:10 Device will not start) It shows correctly now but has ! next to the name
I rolled it back and updated with the NextWindow Drivers the same way. It installed successfully but when attempting to use the touchscreen no response. (also name is different NextWindow Multi-Touch Device)
so I rolled back and attemped to update manually without the extracted packages (using Windows Default ID's it has) I see one that states NextWindow and it seems to have the same information as the packages. I get the same errors.
So natrually now I see it seems to be the NextWindow Drivers are what is causing the problem. In doing research (reports on multiple forums) it appears that many all-in-one or overlaid monitor is having the same issue with the NextWindow Drivers. Now that being said I have seen what appears to be HP Touchsmart 610's running Windows 8 on youtube (developers build as the are older vids) and doubt that MS would have removed the drivers if they were working.
So the Bounty for me will start at $40 Dollars starting at the time of this post. Every 24 hours that this post remains unsolved I will dock $1 dollars from the total bounty (basically im looking for a quick solution not one after drivers have been redone by the NextWindow already.) If you can solve this its a quick $40 for just basically searching around and seeing something I couldnt figure out. This also may help ALOT of people that have All-in-ones as these drivers are made for multiple PC's with touchscreen devices (8 manufactuers total such as Sony, Lenovo, HP, ect.)
Good Luck (and I prefer to pay via Paypal to make things easy.)
Try locate the driver inside the System32 file on a Windows 7 computer then copy it to the Windows 8 computer, hit Update Driver and point it at the driver you just copied. Basically this is manually installing the driver without the .exe installer HP provided you (and gives the OS error). Almost all Windows 7 drivers work on Windows 8, just the package you use does not.
Right click My Computer > Properties > Hardware > Device Manager > Your Device > Right click it > Properties > Driver > Driver Details.
Click to expand...
Click to collapse
Try locate the driver inside the System32 file on a Windows 7 computer then copy it to the Windows 8 computer, hit Update Driver and point it at the driver you just copied. Basically this is manually installing the driver without the .exe installer HP provided you (and gives the OS error). Almost all Windows 7 drivers work on Windows 8, just the package you use does not.
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately that was a no go. Unless im not reading the driver names correctly I have copied them from on drive to the other and attempted to update it that way. Same results.
These were the drivers I copied and moved from System32
drivers\mshidkmdf.sys
drivers\NWTransLibV.sys
drivers\NWVoltron.sys
WdfCoInstaller01009.dll
Thanks for the input though.
ca2l3vin said:
Thanks for the advice. Unfortunately that was a no go. Unless im not reading the driver names correctly I have copied them from on drive to the other and attempted to update it that way. Same results.
These were the drivers I copied and moved from System32
drivers\mshidkmdf.sys
drivers\NWTransLibV.sys
drivers\NWVoltron.sys
WdfCoInstaller01009.dll
Thanks for the input though.
Click to expand...
Click to collapse
Maybe you could give a try at double driver (boozet.org)
Thanks for the reply. unfortunately it fails the install this way aswell.
you can try and modd the inf file i ont have the hw what you guys only i able to compare is the win 8 cp x64 and win 7 x64 amd radeon driver there are a lot difference
ca2l3vin said:
***IF THIS THREAD IS IN THE WRONG SECTION I WOULD APPRECIATE IT IF IT WERE MOVED TO THE CORRECT SECTION. I BELIEVE THIS IS CORRECT BUT I AM NOT SURE. IF ITS NOT MOVED THEN INFORM ME AND ILL POST IN CORRECT SECTION.***
Ok so here is my situation. I have a HP Touchsmart 520-1030 and I am wanting to use windows 8 with the touchscreen. That being said it appears that on both the Developer and Consumer release that the driver for it does not work well with Windows 8 even though it works fine on Windows 7 (I have it dual booted on seperate partitions).
So here is a description of what I have attempted so far.
Downloaded the Driver package from HP's Website and ran. Wouldnt install as gave OS version error.
So I ran in compatibility mode Windows 7 with admin permissions (also taken ownership). I get the same error about the OS version.
I then went to NextWindow's website and downloaded the original (older) drivers from there. It says its installed but does not work (device manager showing touchscreen with a ! on it.)
I then tried to update the driver in DM and search gives an error.
I then browsed to the installation folder of the drivers and it states cant find driver.
I then went back and compared it with windows 7 drivers and see the "touchscreen" driver is NextWindow Voltron Touchscreen. I then compared the Hardware IDs and sure enough they are the same ID's (I believe).
I then used a universal extractor and extracked the package for HP and NextWindow and attempted to manually update the driver through DM. It updates but I get an error with the HP packages (code:10 Device will not start) It shows correctly now but has ! next to the name
I rolled it back and updated with the NextWindow Drivers the same way. It installed successfully but when attempting to use the touchscreen no response. (also name is different NextWindow Multi-Touch Device)
so I rolled back and attemped to update manually without the extracted packages (using Windows Default ID's it has) I see one that states NextWindow and it seems to have the same information as the packages. I get the same errors.
So natrually now I see it seems to be the NextWindow Drivers are what is causing the problem. In doing research (reports on multiple forums) it appears that many all-in-one or overlaid monitor is having the same issue with the NextWindow Drivers. Now that being said I have seen what appears to be HP Touchsmart 610's running Windows 8 on youtube (developers build as the are older vids) and doubt that MS would have removed the drivers if they were working.
So the Bounty for me will start at $40 Dollars starting at the time of this post. Every 24 hours that this post remains unsolved I will dock $1 dollars from the total bounty (basically im looking for a quick solution not one after drivers have been redone by the NextWindow already.) If you can solve this its a quick $40 for just basically searching around and seeing something I couldnt figure out. This also may help ALOT of people that have All-in-ones as these drivers are made for multiple PC's with touchscreen devices (8 manufactuers total such as Sony, Lenovo, HP, ect.)
Good Luck (and I prefer to pay via Paypal to make things easy.)
Click to expand...
Click to collapse
Hi I did not figure this out but i'm having the same problem, I found this solution on the microsoft website questions and answers. Pleasr let us know if this works for you. Thanks. I had tried that but the install would not start because it didn't see the OS as valid.
BUT I did get it to work by doing a restore to factory settings (Windows 7) and rerunning the Windows 8 install directly from http://windows.microsoft.com/en-US/windows-8/download and selecting to KEEP the installed apps and user files. On my failed Win8 install attempt I used a Windows 8 ISO file and selected to NOT keep any apps or user files.
Not sure which if the 2 changes made the difference but the touch screen works now in Win 8.
Ok, I tried this out and it does work. I have a hp 520-1031 and now my touch screen works with windows 8
So only way around from what I see is to install windows 7 first then run windows 8 as an update. Though this isn't the solution I was hoping for (as now I have to install windows 7 on a partition first then rerun the install for windows 8) I do thank you for your efforts and the bounty is yours Tragicwayz
you can PM me your information and by the end of next week your payment of $27 will be in your box (this is calculated from the time of your first post of the solution from the time I started the thread)
Thanks again
You are welcome, I have tried many solutions as well but could not get the touch screen working. I hope this helps others with their touchscreen.
I have a TS 7320 and the touchscreen driver for Windows 8 didn't work either. Next I installed Win7 x64 to get it running before upgrading to Win8.
Unfortunately, my device won't install the drivers from de HP website, nor from NextWindow. I looked at the INF file and there is a difference in the device id. My PC shows a 'REV_0008&MI_02' addition to the VENID and DEVID. Altering the INF file manually makes the install work, but the driver fails with error 10 (won't start)…
Any suggestions where to get a working driver for Windows 7 x64?
(I wiped the disk to install Win8, so no recovery disk/partition from HP )
moved to general
ca2l3vin said:
***IF THIS THREAD IS IN THE WRONG SECTION I WOULD APPRECIATE IT IF IT WERE MOVED TO THE CORRECT SECTION. I BELIEVE THIS IS CORRECT BUT I AM NOT SURE. IF ITS NOT MOVED THEN INFORM ME AND ILL POST IN CORRECT SECTION.***
Ok so here is my situation. I have a HP Touchsmart 520-1030 and I am wanting to use windows 8 with the touchscreen. That being said it appears that on both the Developer and Consumer release that the driver for it does not work well with Windows 8 even though it works fine on Windows 7 (I have it dual booted on seperate partitions).
So here is a description of what I have attempted so far.
Downloaded the Driver package from HP's Website and ran. Wouldnt install as gave OS version error.
So I ran in compatibility mode Windows 7 with admin permissions (also taken ownership). I get the same error about the OS version.
I then went to NextWindow's website and downloaded the original (older) drivers from there. It says its installed but does not work (device manager showing touchscreen with a ! on it.)
I then tried to update the driver in DM and search gives an error.
I then browsed to the installation folder of the drivers and it states cant find driver.
I then went back and compared it with windows 7 drivers and see the "touchscreen" driver is NextWindow Voltron Touchscreen. I then compared the Hardware IDs and sure enough they are the same ID's (I believe).
I then used a universal extractor and extracked the package for HP and NextWindow and attempted to manually update the driver through DM. It updates but I get an error with the HP packages (code:10 Device will not start) It shows correctly now but has ! next to the name
I rolled it back and updated with the NextWindow Drivers the same way. It installed successfully but when attempting to use the touchscreen no response. (also name is different NextWindow Multi-Touch Device)
so I rolled back and attemped to update manually without the extracted packages (using Windows Default ID's it has) I see one that states NextWindow and it seems to have the same information as the packages. I get the same errors.
So natrually now I see it seems to be the NextWindow Drivers are what is causing the problem. In doing research (reports on multiple forums) it appears that many all-in-one or overlaid monitor is having the same issue with the NextWindow Drivers. Now that being said I have seen what appears to be HP Touchsmart 610's running Windows 8 on youtube (developers build as the are older vids) and doubt that MS would have removed the drivers if they were working.
So the Bounty for me will start at $40 Dollars starting at the time of this post. Every 24 hours that this post remains unsolved I will dock $1 dollars from the total bounty (basically im looking for a quick solution not one after drivers have been redone by the NextWindow already.) If you can solve this its a quick $40 for just basically searching around and seeing something I couldnt figure out. This also may help ALOT of people that have All-in-ones as these drivers are made for multiple PC's with touchscreen devices (8 manufactuers total such as Sony, Lenovo, HP, ect.)
Good Luck (and I prefer to pay via Paypal to make things easy.)
Click to expand...
Click to collapse
Why offer a bounty if you are not going to pay it.
So the solution is to upgrade from Win 7?
sounds more like a work around to me.
If it were me id mod the drivers, within the INF file for the drivers you downloaded it will state which OS versions are excepted. all you have to do is make Win 8s version an excepted version, then point the INF to the win 7 driver its self, usually the driver folder may contain drivers for several versions of windows if it doesn't the its just a case of adding win 8s version number to it.
Modifing the inf file and re-sign it.
Maybe you should follow the steps that I did to install Windows 7 display driver, but do it for the multi-touch driver. Since I can't provide a link, do a web seach for "running-angry-birds-on-the-build-samsung-tablet-with-windows-8-consumer-preview"
Alon.
Solution mate.. seems stupid but works!! Last posts on this..
http://h30434.www3.hp.com/t5/TouchSmart-PC/Windows-8/td-p/1314493/page/3
Trying to get the multitouch working. Downloaded these drivers from nextwindow http://www.nextwindow.com/nextwindow_support/windriver.html
The driver had no effect on the multitouch, so it's still single touch...
Does someone have a clue how to get multitouch working?
Solution !
Here's what you need to do to get Multitouch working on a HP Touchsmart 520 under Windows 8:
1.) download Intel Graphics Beta driver from downloadcenter.intel.com
2.) install the latest Voltron driver from HP driver base.
This isn't very stable unfortunately (screen freezes from time2time).
But it's the requested solution (4 the time being).
Cheers
No solution !
michaelreuss said:
Here's what you need to do to get Multitouch working on a HP Touchsmart 520 under Windows 8:
1.) download Intel Graphics Beta driver from downloadcenter.intel.com
2.) install the latest Voltron driver from HP driver base.
This isn't very stable unfortunately (screen freezes from time2time).
But it's the requested solution (4 the time being).
Cheers
Click to expand...
Click to collapse
Crap ! I have to correct myself. Due to the bugginess I reinstalled Win8. Now the Touchscreen driver won't install any more, no matter what display driver I use.
WTF ?
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
Hello,
Just an average XDA noob speaking here. Reason i'm creating this topic is because I'm having problems getting the ADB composite drivers right. Previously I've rooted a HTC Hero without any problems, but with my Huawei U8800 Ideos X5 I just can't fix it, I searched in all corners of the Internet. Below are my specs.
- Android 2.3.5
- Unbranded
I've also tried to root with SuperOneClick and by replacing the boot.img, but I can't get it to work because of the drivers.
When I get to recover mode (the pink/purple screen) it isn't showing me the IMAGE folder on my computer. Also tried to install new drivers for the ADB composite by using the H:/Mobile Partner disk on my phone but that isn't helping either. It says their isn't any new hardware found in the folder, but as you can see on the image, there are still exclamation marks. I Also uninstalled the drivers a few times and tried to re-install them but that isn't working neither. Firstly my phone was recognized as an Other device > Ethernet Controller in the device manager screen. But that was possible to solve by browsing to the H:\MobilePartner\Drivers folder.
By the way, when in recovery mode plugged in the computer, it shows me two drivers called "HUAWEI TECHNOLOGIES". I can't seem to find a good driver for those, they also show the !-mark.
Any help will be appreciated! :good:
The image. www(dot)dropbox(dot)com/s/tn2q2neo5362gd1/screenshot.1.png?m
maybe you can try to install this driver from huawei.. it worked for me..
https://www.box.com/s/ywqomlr1pj1ca4ls0wlm
Drivers
Get the drivers from here
http://forum.xda-developers.com/showthread.php?t=1876457
(if your problem solved click thx)
socioan said:
Get the drivers from here
http://forum.xda-developers.com/showthread.php?t=1876457
(if your problem solved click thx)
Click to expand...
Click to collapse
Sadly the password for the Quallcomm setting is not working :/ 0 and 0000 both didn't. Thanks for your help
@ first poster
Used that driver install, when the phone is connected and has USB Debug on this is the situation, screen: www(dot)dropbox(dot)com/s/y6x0ta8bwp1rqsr/screenshot.2.png
have u tried to uninstall/remove all related driver instances and try to do it afresh?
iamelton said:
have u tried to uninstall/remove all related driver instances and try to do it afresh?
Click to expand...
Click to collapse
What's the best way to do that? Just delete them from the device manager screen and letting them re-install automaticly by the phone? Or just download drivers from the internet and install it manually?
Jordy14 said:
What's the best way to do that? Just delete them from the device manager screen and letting them re-install automaticly by the phone? Or just download drivers from the internet and install it manually?
Click to expand...
Click to collapse
if u r doing manual driver installation, then its best to disallow auto-installation by windows..
delete all instances from device manager, or u may use an application called "USBDeview" to remove the usb drivers.. and i think this second way is probably doing it more cleanly..
iamelton said:
if u r doing manual driver installation, then its best to disallow auto-installation by windows..
delete all instances from device manager, or u may use an application called "USBDeview" to remove the usb drivers.. and i think this second way is probably doing it more cleanly..
Click to expand...
Click to collapse
Thanks man, gonna try that tomorrow after school.
Will keep you updated.
Sorry for the late update, forgot about the topic... I threw away all the drivers, got the pinkpurple screen and connected to my pc. It's now missing this drivers when connected, Windows can't install them itself. Check the printscreen below.
http://i50.tinypic.com/20qyzc0.png
Jordy14 said:
Sorry for the late update, forgot about the topic... I threw away all the drivers, got the pinkpurple screen and connected to my pc. It's now missing this drivers when connected, Windows can't install them itself. Check the printscreen below.
http://i50.tinypic.com/20qyzc0.png
Click to expand...
Click to collapse
this works 100%
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk/Attachments_2012_09_12.html
socioan said:
this works 100%
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk/Attachments_2012_09_12.html
Click to expand...
Click to collapse
Gonna try that out, do I need both?
The first one i have tested and it is for 32 bit win 7
The second one i havent test it it is for 32 and 64 bit win 7
Choose one acording your windows
socioan said:
The first one i have tested and it is for 32 bit win 7
The second one i havent test it it is for 32 and 64 bit win 7
Choose one acording your windows
Click to expand...
Click to collapse
Ok ty, I started over, deleted all the drivers and let Windows install the drivers themself. Still not working. I find it very strange why Android Composite ADB Interface pops up 4 times in the device manager... As you can see, he installed one by himself >> https://(w)(w)w.dropbox.com/s/lttgky3qozhraf9/kak4.png
I'll try your method.
Well guys I've been trying for hours now, whenever I try to install the USB drivers in order to unlock my bootloader, when I plug in my Nexus it installs the MTP drivers on it's own, if I try to install the google drivers downloaded from ADB all I get is a message saying the best drivers for my device are already installed and it doesn't let me overwrite them.
If I go with the use disk option it doesn't let me choose the usb_drivers folder because it just wants to use a .inf file, whener I follow the instructions the toolkit dictates I read the dead end with the "The best drivers for your device are already installed"
I'm so angry right now.... Please help me.
Are you on a Windows XP operating system by any chance? There are major issues with MTP mounting on WinXP regardless of the service pack you're on. Some people claim they've gotten things working by updating WMP, via a Naked Driver and even by installing the Android SDK. Let me know if you are indeed on WinXP & I'll get you some links
Did you try following Wug's Nexus Root Toolkit to install the drivers? That helped me. I cannot post a link so look around for it.
I'm running Windows 7 64 bit, thanks guys, I just gave up and did it in my sister's laptop, it worked on the first damn attempt, maybe the drivers of my N10 were screwing something up, that's my best guess.
Glad you got that sorted--just for future reference, a common recommendation for people having driver issues with their Nexus devices is to simply go into Win Device Manager, uninstall all your current Nexus & ADB drivers and restart. Then plug your phone in via USB and let the auto installation do its thing. Usually this fixes all issues w conflicting device drivers
hi everyone, i just upgrade my pc from 8.1 to windows 10.but after successfull installation there is no sound in pc..it shows that no audio device found.i attached screenshort below...
and i also clean install windows 7...but the problem still remained....i also install driver but not work.....need n help
Have you tried updating your driver's?
Sent from my BN Nook HD using Tapatalk
A AJAY said:
hi everyone, i just upgrade my pc from 8.1 to windows 10.but after successfull installation there is no sound in pc..it shows that no audio device found.i attached screenshort below...
and i also clean install windows 7...but the problem still remained....i also install driver but not work.....need n help
Click to expand...
Click to collapse
Install proper sound drivers
Sent from my Micromax A092 using Tapatalk
no driver worked......i try clean install of windows 7 and use my driver cd but,,there is no sound
So you formatted again and did another install of Windows 7, and it still doesn't show up? Is it onboard audio? Check the BIOS to ensure it's enabled.
Google brings up a lot of results, have you tried looking at them? What does Device Manager show?
If it still doesn't work, the sound card/motherboard if onboard might be dead.
I can't count on two hands how many people, including myself had this upgrade problem. Always audio or video.
Firstly, I'd check to see on the notebook/pc manufacturer website if they have Windows 10 drivers for your model. That's the best place to start.
Some older drivers are getting automatically updated through Windows Update. It seems Microsoft has encouraged some key driver updates. E.g. Intel integrated graphics.
Lastly, uninstall the driver, reboot your computer, now, install the driver again under compatibility mode for the version of Windows you have.
For audio, compatibility mode worked. Get this. My notebook came with Windows 7. The Windows 7 driver works (after about 20 attempts) but the Windows 8 driver doesn't. My understanding is that Windows 8 drivers are a bit more compatible with 10 than 7. But the 7 driver actually worked better.
Let us know how you get on.