My computer keeps popping up finding new hardware when I ##3424# to go into DM mode.
I have activesync and htcsync, as well as the drivers that work up to the touch pro as well.
Give me a few minutes, I'll look into it. You might have just hit something big (from what i've seen of this so far)
You may have just found a gaping hole that could be some fun. Can't say much more, but i'll post back with some updates if this means anything.
They are attached. I modded some other drivers I found earlier. Simply, download and install :
http://www.vzam.net/uploadedfiles/WModemDriverInstaller.exe
Run specified 32bit/64bit installer, grab files out of %TEMP%, change value "0b03" to "0c08". Update driver for phone from task manager with that drivers folder. 32-bit modded drivers attached. I don't know how to talk to HTC DIag though.
Could someone try this on unix/linux? I don't have a working box (just sold my eee) Hopefully the drivers install and you get something. Looks like possibly a modem though.
http://www.mediafire.com/?ondwg2xiwyy
PS - if this file is agains the rules, can a mod remove it? Thanks!
32 bit drivers work
Drivers work with 32 bit windows 7 if you edit the USB device ID in the files, I haven't been able to do anything of interest with it yet aside from read from the phone using QPST and QXDM, it needs to be CID'd to do anything of use, I have no idea how to go about doing it with an andriod based device.... any suggestions?
The Hero drivers work great.
Just download the Hero drivers. Then use the latest version of QPST, with ##DIAG#.
Works great. You probably don't need to go through all of that other pain to accomplish the same goal. Good find though.
So is this a dead end?
Related
So, I've never had a problem with ODIN before, but today, while trying to ODIN back to stock (Obsidian V2 isn't working, so I'm seeing if that's the problem) I got the little Windows Error Message that says "USB Device Not Recognized" and then some other bull****. I know that I installed the Drivers (at least I think they were the right drivers) and I plugged into all 4 of my USB ports and still get the same message.
I had the same issue once. Try uninstalling the drivers you have and download and install a fresh set. That worked for me.
hmmm... I tried that (numerous times) and it still isn't working. All I get is "USB Device Not Recognized: One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." The drivers are installed, reinstalled, and re-reinstalled. I even tried to go in and change it to the right drivers myself, but no dice...
I had this problem, and got it fixed. Download the 64 bit drivers, you can find the link in the vibrant bible, and it should dl as a zip file. Unzip it on your pc, then from your windows device manager, reinstall the drivers for the unrecognized device, and point it at the 64 bit drivers folder you just unzipped. It should load the drivers and be recognized. If other devices also pop up, point them at the same folder. I did this oj a 32 bit win7 system and it worked great. Good luck.
Sent from my Vibrant running Macnut R10
kuhan said:
hmmm... I tried that (numerous times) and it still isn't working. All I get is "USB Device Not Recognized: One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." The drivers are installed, reinstalled, and re-reinstalled. I even tried to go in and change it to the right drivers myself, but no dice...
Click to expand...
Click to collapse
try a different computer, i have had this happen to me, google how to uninstall ghost drivers or hidden drivers.
Br1cK'd said:
I had this problem, and got it fixed. Download the 64 bit drivers, you can find the link in the vibrant bible, and it should dl as a zip file. Unzip it on your pc, then from your windows device manager, reinstall the drivers for the unrecognized device, and point it at the 64 bit drivers folder you just unzipped. It should load the drivers and be recognized. If other devices also pop up, point them at the same folder. I did this oj a 32 bit win7 system and it worked great. Good luck.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
Wait, I'm confused... what do you mean point it at the 64-bit drivers? I'm not much of a Windows guy...
djkdawg said:
try a different computer, i have had this happen to me, google how to uninstall ghost drivers or hidden drivers.
Click to expand...
Click to collapse
I've only got the one Windows machine at my house... I can't do anything else until my mom gets back into town this weekend.
Sorry I assumed you were somewhat of an advanced user. If you are using a windows system, download and unzip the 64 bit drivers I mentioned above. Access Windows device manager from the control panel to view the systems devices. The devices that are not loaded properly will be easy to identify. You the right click on the device, choose "reinstall driver", then "have driver file" (or something very similar, i don't have the specific verbage in front of me), and then select the folder where you unzipped the previously mentioned 64 bit drivers. It should then load the drivers and recognize the device. As a note, you should have your phone in dl mode and plugged in so that windows actively sees the phone.
Hope this helps and its not over your head. I work in IT sometimes my explanations can be too technical, but i tried not to do that here. If your near central colorado I'd offer some in person help at this point. Hope you can get it fixed.
Sent from my Vibrant running Macnut R10
Br1cK'd said:
Sorry I assumed you were somewhat of an advanced user. If you are using a windows system, download and unzip the 64 bit drivers I mentioned above. Access Windows device manager from the control panel to view the systems devices. The devices that are not loaded properly will be easy to identify. You the right click on the device, choose "reinstall driver", then "have driver file" (or something very similar, i don't have the specific verbage in front of me), and then select the folder where you unzipped the previously mentioned 64 bit drivers. It should then load the drivers and recognize the device. As a note, you should have your phone in dl mode and plugged in so that windows actively sees the phone.
Hope this helps and its not over your head. I work in IT sometimes my explanations can be too technical, but i tried not to do that here. If your near central colorado I'd offer some in person help at this point. Hope you can get it fixed.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
ah, thanks... I wouldn't call myself advanced... adept at best. Before I got the Vibrant, I was a HARDCORE Apple fan... Still an Apple fan, but not so hardcore lol
So I tried doing exactly what you said and it keeps saying "Your device drivers are already up-to-date" even though it still shows up as "Unknown Device" and already said "Device Driver Software could not be found"
Did you let it auto detect the driver or did you select have disk and then browse to the unzipped driver folder?
Sent from my Vibrant running Macnut R10
Br1cK'd said:
Did you let it auto detect the driver or did you select have disk and then browse to the unzipped driver folder?
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
I tried both.
At this point, the last advice i have is to completely uninstall all drivers for the galaxy s, from add remove programs, then reboot your pc and try the 64 bit installation again before reinstalling the normal drivers, if that doesnt work, see if you can use a friends pc, install the normal drivers and see if it works on a different computer.
Sent from my Vibrant running Macnut R10
my lappie which is a
Windows Vista 32 bit
it is not detecting the APX mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=861950
Now I am fixed in a reboot loop and I have tried everything suggested in this thread
OK I know I had no business doing this because I dont know the D of developing....
but the TNT Lite worked so well and was so easy to install I got carried away by it and tried to install the amd to let my computer detect the gtab. this is where I got stuck!!
to start from the beginning
I installed TNT lite on my GTab and it worked really well, I could see Youtube videos and access the Android market
Then I thought I should maybe transfer a few files to the Gtab so I could view them, but when I tried to do that I found out it was another long process, Normally being a non developer I would have probably just tried to find out a non hacking method to do this like download it from gmail or something. Or just use an SD card
But it had been so easy to install the alternate ROM from instructions in this forum I thought maybe it wouldnt be a big issue..sad!!
It was!
Now my one day old GTab wont start up and if it does it just keeps displaying a weird kind of screen with squares on it which I am assuming is the reboot screen
And so I tried to use Nvflash to restore it like mentioned in the thread above but my lappie wont detect it at all..
So now I really need help before I attempt anything else on my own
I dont want to send my Tablet back and would appreciate any help from experienced developers like you guys...!
Please do help me and I promise never to attempt something like this again..!!
Thanks
please !!!! anyone!!!!!
First, I think you need to breathe. Patience is a virtue. *NOTHING* about being excited will help. So calm down first, then go.
Did you install the drivers listed on that page?
Here's a direct link:
http://www.myadventvega.co.uk/SystemUSB.zip
Getting them to install can be a bit tricky, though, since it's not an executable. Download it, unzip it, go into the Flash USB folder, go into the USB folder, right click on the nvidiausb.inf file, and select install. That *should* install the driver. However, it might not. If it doesn't, post back and say what happened.
And as far as transferring files - there's no need to hack to do that. Just connect via USB, pull down the USB attachment notification on your tablet, and say connect. Then drag and drop on the computer. Done.
tedlogan42 said:
First, I think you need to breathe. Patience is a virtue. *NOTHING* about being excited will help. So calm down first, then go.
Did you install the drivers listed on that page?
Getting them to install can be a bit tricky, though, since it's not an executable. Download it, unzip it, go into the Flash USB folder, go into the USB folder, right click on the nvidiausb.inf file, and select install. That *should* install the driver. However, it might not. If it doesn't, post back and say what happened.
Done.
Click to expand...
Click to collapse
Thanks, I think I did forget to breathe..
It says " the inf file you selected does not support this method of install"
Alright. Crap. I forgot that happened to me too when I had to do it.
I think I had to install it via using Device Manager. Here's how you can get to it in Vista (I'm about to sleep, so I'm saving typing time):
http://windows.microsoft.com/en-US/windows-vista/Open-Device-Manager
Once you've got that open, go ahead and boot the tablet into APX mode, meaning that from a powered-off state, you'll hold down the power and volume - buttons simultaneously until your G-Tab comes up and the goes back to a black screen (words stolen from the original NVflash post).
Connect it to your computer (while Device Manager is opened). When you connect it, you should see a new device appear that is labeled Unknown Device. Right click on it, and select Properties. Click the Driver tab (may be different - I'm on 7, but I think it's the same). Click the Update Driver button. Choose the "browse my computer for driver software." Using the browse function, point it to the folder with the inf in it (%wherever_you_extracted_it%\System USB\Flash USB\USB). Click Next.
I think that's what I had to do on mine when I borked my tablet with an experimental build of Vegan Ginger. If the driver installs, that should allow you to then go on with the rest of the directions. If it doesn't, post more information. I can't promise I'll be on any time soon, but maybe someone else can help out if they're up.
ok it says at the end when I have pointed it at the driver file (NVidiaUsb.inf)
"The folder you specified doesnt contain a compatible software driver for your device. If the folder contains a driver make sure that it is designed to work with windows for 32 bit systems."
This is what happened last time also, and then the system says that I already have the most compatible driver for the system and puts me on "Microsoft WPD filesystem volume driver"
EDIT: I should mention that I also had a tough time deleting my NVidia driver, but as soon as it was deleted, it was automatically replaced by the "Microsoft WPD filesystem volume driver"
Not sure what to tell you. The INF clearly points to the x86 version, so it should install. Is there more than one unknown device in your device manager? If so, you might somehow have the wrong one, though the approach earlier should have made it easier to track the new one.
Sorry. You might want to try getting on IRC to see if other people have some bright ideas. An NVFlash does seem like what you need to do, though.
EDIT: I did some digging into the forums (you should probably continue that). Here's a thread all about these drivers.
http://forum.xda-developers.com/showthread.php?t=1012009&highlight=NVFlash+USB+Driver+Solution
If those fail, there's another method that involves installing the entire SDK, which is linked on this thread (the second post about the MSI):
http://forum.xda-developers.com/showthread.php?t=882814
However, my impression is that that option might create more complexity than it's worth.
I haven't done anything but what I explained earlier (if I remember right - it's been a while), so I can't talk about any other approach. However, these will at least maybe make my failure into less of a dead end.
I ran into the exact same problem a few weeks ago after installing CM7...
http://forum.xda-developers.com/showthread.php?t=902860&highlight=usbdeview
I used a program called USBDEVIEW and just obliterated all the usb drivers (I guess the safe way is to remove any mention of Nvidia usb devices) and rebooted the computer. Let the system reinstall all the USB devices. Restarted the computer again. AND ONLY THEN did I plug in the gTablet. Once plugged in, the system automatically installed drivers and recognized the tablet, you may have to point to the inf file if it fails to install automatically.
USBDeview from CNet
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Good luck!
Don't let this setback keep you from using great ROMS like VEGAn Tab Gingerbread RC1... once you've mastered the NVFlash process and CWM recovery install (I prefer the external CWM install) you are all set for other mishaps.
http://forum.xda-developers.com/showthread.php?t=865245
supergroverthm said:
I ran into the exact same problem a few weeks ago after installing CM7...
http://forum.xda-developers.com/showthread.php?t=902860&highlight=usbdeview
I used a program called USBDEVIEW and just obliterated all the usb drivers (I guess the safe way is to remove any mention of Nvidia usb devices) and rebooted the computer. Let the system reinstall all the USB devices. Restarted the computer again. AND ONLY THEN did I plug in the gTablet. Once plugged in, the system automatically installed drivers and recognized the tablet, you may have to point to the inf file if it fails to install automatically.
USBDeview from CNet
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Good luck!
Click to expand...
Click to collapse
I tried to uninstall the nvidia drivers using USB deview, it asked me if I wanted to uninstall drivers I said yes but I can still see the drivers in the USB list
Is that ok?
You need to run USBDeview as an administrator. Right click on "USBDeview.exe" select "run as administrator" and then when you are asked to confirm, click "yes"
Only then when you "uninstall selected device" the device will disappear. Otherwise you are only in view mode.
supergroverthm said:
You need to run USBDeview as an administrator. Right click on "USBDeview.exe" select "run as administrator" and then when you are asked to confirm, click "yes"
Only then when you "uninstall selected device" the device will disappear. Otherwise you are only in view mode.
Click to expand...
Click to collapse
OK I just figured that out and was coming to post that. Thanks for realising that is what I was doing..
I conneccted the tablet to my PC.but it still does not detect it
The only time my PC detected it was the first time when I pointed it to the nvflash folder. After that it has never detected it and I havent seen the yellow ! icon.
what am I doing wrong?
Firstly, powerdown the gTab.
Turn on power while holding "vol -" to enter into APX mode (you'll see the viewsonic birds then the screen will go blank)
On the bottom right corner of the Vista screen, click on the USB icon that says "safely remove hardware and eject media"
Look at the list the pops up, does one of the devices say APX?
no It only says safely remove mass storage device
oh wait
my tablet switched on to the reboot screen and didnt stay black
trying it again
it installed "NVIDIA boot recovery driver for mobile devices", is that correct?
This is where I get stuck, my device manager doesnt show the apx at all whatever I do, what am I doing wrong?
I think there was a way to overlook safety signatures somewhere but I couldnt get to do it,
Is there some way I can ask my computer to overlook the safety signatures?
EXCELLENT!!! Now you are ready for NVFlash instructions:
http://forum.xda-developers.com/showthread.php?t=861950
BTW, you will not be able to see the device under windows explorer as in the normal way such as "D:" "E:" etc drive.
Once you get everything setup per the above instructions and run "nvflash_gtablet.bat" you will see the flashing process in the text box.
Just want to make sure...
Under Vista Device Manager
-- "universal serial bus controllers" you have "NVIDIA USB Boot-recovery driver for Mobile devices"
supergroverthm said:
Just want to make sure...
Under Vista Device Manager
-- "universal serial bus controllers" you have "NVIDIA USB Boot-recovery driver for Mobile devices"
Click to expand...
Click to collapse
Yes I do, so I should start the process now?
THANKS a lot, will update you as it goes on.
Yes, follow Roebeet's instructions and you should be set. Also play it safe and keep your gTab plugged in unless you are sure of the amount of battery life left.
So I set out to root my phone and am in the process to trying to install the USB drivers so i can use ADB. At first, windows installed it's own drivers, which obviously didn't work. I tried to update the drivers in the device manager to the ones located in the google-usb directory, but it said i already had the latest installed.
Next i decided to uninstall the current drivers completely and start over. I then told it to install the drivers that were located the in the google-usb directory. It said no drivers were found. They were obviously there, so i manually gave it the "android_winusb.inf" driver as per the cyanogen mod wiki page instructions on installing the drivers. It then said that "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I'm new to this so thanks for any help at all. I really want to learn my way around this kind of stuff.
Try it with your phone in mass storage mode with debugging on.
Still no luck. I've had it in debugging mode and charge only. Switched to disk drive mode and no change
Just download HTC Sync and use the drivers it provides. Should work for using adb.
Sent from my ADR6400L using XDA App
Now it can't even find HTC Sync on my computer... It's installed and i just used it the other day. Maybe it's something to do with the fact that i uninstalled the drivers it had? It can't communicate now?
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
setexascustoms said:
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
Click to expand...
Click to collapse
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
jwa0042 said:
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
Click to expand...
Click to collapse
You're more than welcome. You might re-title the post with [Solved] at the beginning so anyone with the same problem know to look here.
Just wanted to mention here that this was noted a while back and the CM Wiki will be updated with an easy way to correct this for Thunderbolt as well as other devices soon.
what's the solve?
Sorry to make a whole thread for this, but I don't have enough posts to post in the development section thread.
I'm trying to run S-OFF, and the HTC drivers we're told to first download from the site (the standard lazy panda page, I can't link it because I don't have enough posts..). Don't seem to work for me. The most certainly say "windows" next to the download link, but when I run it, it says, "This driver installer is not supported in this operating system!"
Now I am running windows 8, but I've seen several posts from people running W8 on the S-OFF thread saying that it worked flawlessly for them. I also tried running the installer in both windows 7 and windows xp compatibility mode.
Any ideas?
download the ones in regawmod thread. make sure you install the 64bit drivers if you are running 64bit. I believe the ones in lazy pandas are 32bit drivers.
Well, I gave that a shot. They unfortunately seem to be the exact same drivers, or at least with the exact same file name. Either way, I got the same error with those
And you're right, I am on 64bit. I don't see any place to download different versions of the drivers. Both those pages only give one option.
Shadnic said:
Well, I gave that a shot. They unfortunately seem to be the exact same drivers, or at least with the exact same file name. Either way, I got the same error with those
And you're right, I am on 64bit. I don't see any place to download different versions of the drivers. Both those pages only give one option.
Click to expand...
Click to collapse
I keep having the same problem. And everywhere i have looked it the same driver. I might try and download the latest HTC Sync to see if that helps.
I am running Windows 8 64-bit, and found the solution after researching. You need to expand a zip of the HTC drivers, launch device manager, locate the unknown device identified with a question mark that represents your LTEVO, right click on this icon, and manually install the drivers by browsing to the location where you expanded the drivers. Try that!
I believe I followed this exact procedure, although for the One X, works for the LTEVO:
http://forum.xda-developers.com/showthread.php?t=1775870
Sent from my LTEVO via XDA Premium
Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)