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
Related
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.
I cannot seem to get Novacom drivers installed for my Touchpad. I've tried rebooting both machine and touchpad, taken TP in and out of dev mode, tried every command line I could find for running the novacom installer, etc. I am at a loss, cannot get it to work at all. Tried searching but didn't come up with anything for novacom
I'm trying to do this while at work and am on a netbook with windows 7 starter.
Appreciate any help
OK sorry for sounding stupid but have you run the universal novacom installer? If so, what happened?
Sent from my HTC Desire S using xda premium
dan-fish said:
OK sorry for sounding stupid but have you run the universal novacom installer? If so, what happened?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Yes, I get a message that says it has been successfully installed, but when I plug in the TP it isn't recognized. Cannot mount as USB either
Doesn't sound like a novacom issue. Maybe someone else can spread some light here
Sent from my HTC Desire S using xda premium
Would be much appreciated.
FWIW, I did get it to be seen by quick install the very first time I plugged it in but it immediately dropped it and hasn't seen it since.
I got it to see it briefly on a different computer. Now when I put it in recovery mode it comes up as unknown device again. I want to throw this [email protected]#$& thing!
Please, can someone help me out here.
I have gotten it to the point that it is seen until I put it into recovery mode. Once I put it in recovery mode and plug it in, I get device not recognized.
In an effort to remedy that issue, I wiped everything touchpad related on my computer clean to start again. Now I'm back to square one. Device not recognized and cannot mount to USB Mass storage. What the F am I missing here. Why does it work one second and not the next?
In vein, I tried to install using my old iBook but even that didn't work(thanks Steve!)
I've also moved from the netbook I was trying to install from last night, to my normal win7 machine.
Would really appreciate it if anyone is willing to work with me to resolve this
Haha. I had this same issue. i wish it would be added to the tutorial's OP. Anyway, make sure you are putting acmeinstaller in the folder . Crogram Files, Palm, Inc where the actuall Novacom drivers are. Then enter the C prompt and you're good to go. If you don't have x64 put the ACMEInstaller file wherever your computer has Palm Inc and that is the directory you CD to.
i.e. for me it was cd c:/program files/ palm inc
Ended up using an XP machine to install. Took just a few minutes. Drivers were found right away unlike in 7.
blackwrx02 said:
Ended up using an XP machine to install. Took just a few minutes. Drivers were found right away unlike in 7.
Click to expand...
Click to collapse
My issue with Win7/64bit were the path/file location.
Even if you download the drivers and install them correctly, you still have to execute the novacom ext.
It's in the prog files\palm folder, as said.
Had a heck of a time myself until I realized this.
dajogejr said:
My issue with Win7/64bit were the path/file location.
Even if you download the drivers and install them correctly, you still have to execute the novacom ext.
It's in the prog files\palm folder, as said.
Had a heck of a time myself until I realized this.
Click to expand...
Click to collapse
For people searching for the answer.
I'm on win7 64 bit. The universal novacom install went fine. Plugged in touchpad and ran command, but novacom did not find device.
Moved usb connection to different usb port on my computer, magic.
Novacom commands worked and installed cyanogen 9.
If moving usb ports doesn't work. Disconnect usb cable, uninstall novacom via control panel, software removal. Then, reinstall novacom, and use 2nd usb port.
I seached the web, and none of these questions about novacom not finding device was answered. The above is the answer. Move usb ports.
Goodmornig everyone..!
I just bought an Archos 80 G9 Turbo 16GB and I cannot connect it with my computer that runs Windows 7 64bit
When I plug it, it is detected as an Unknown Device (error code 43) and nothing is mounted.. (but tablet is in "slow charge")
In an old Win XP computer is working good, this made me think it's not completely tablet's fault..
here what I've tried, deeply searching on internet:
-Downloaded ADB android Drivers (in Archos site, on internet, various sources), forced installation of them, problem come out: Drivers are not for a 64 bit Os
-Uninstalled Kies, LG Pc suite and rebooted after every change..nothing changed
-Unactivate and reactivate after reboot Windows Media Player 12..no change
-Changed Usb Mode in tablet from MTP to PTP.. nothing changed
-Installed a lot of USB apps in Google Play and tried changing values..no change
-Upgraded tablet from GingerBread to ICS, deeply wiped and restored several times, and in every configuration, I allways had same results..
-Changed USB cable, several of them tested..and guess?? Nothing..eheh
-Tried shouting at it, tried kissing and asking for his forgiveness..but nothing
I'm stuck on Stock! i cannot upgrade it with XDA custom, I can only connect to pc via FTP server....!
Any Clues?!?!
Thank You to all!
1. To root and to enable SDE menu you need only adb driver
2. You can transfer archos.ext4.update files using FTP from pc to tablet
3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download.
This worked for me on Windows 7 Ultimate.
Ooops overread something... forget it!!!
Have you checked for the correct MTP driver package...
Regards,
scholbert
gen_scheisskopf said:
1. To root and to enable SDE menu you need only adb driver
2. You can transfer archos.ext4.update files using FTP from pc to tablet
3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
Click to expand...
Click to collapse
Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS)
Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it..
xcen3x said:
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download.
This worked for me on Windows 7 Ultimate.
Click to expand...
Click to collapse
Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing..
scholbert said:
Ooops overread something... forget it!!!
Have you checked for the correct MTP driver package...
Regards,
scholbert
Click to expand...
Click to collapse
Dowloaded and istalled a few from windows... the problem is, if it would be an MTP problem, I should not have it in PTP mode... I suppose...
EDIT: tried disabling Integrity Checks for non signed drivers with these string in cmd:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
nothing changed
indyjones83 said:
Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS)
Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it..
Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing..
Click to expand...
Click to collapse
For Gen9 you need Archos modified driver
gen_scheisskopf said:
For Gen9 you need Archos modified driver
Click to expand...
Click to collapse
These are the first one I tried.. From their site.. Not working.. Thankyou!
I wrote them in Contact and support in that site, copying and pasting the same I wrote here, they answered me, two days later.. Excited in what solution they could give me,from the heights of their knowledge, I suddenly opened and the answers was:
Please write the email in English.
Are they kidding me? This makes me suppose they have not even tried in reading it.. Well.. 1000 thanks for you and you support..!
Sent from my Optimus 2X using XDA
Second reply from Archos, this time they read it, but only first few lines..
their reply is:
"We invite you to connect the device to a 32 bits system and then to check if the Archos is seen by the pc."
Already done, and it's working with that (WIN XP)
Did you try to install manually the MTP driver from the device manager of the PC ?
YES.
any new clue from here?
Thankyou!
Try this
Sent from my ARCHOS 80G9 using XDA
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port?
I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
pittnuma said:
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port?
I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
Click to expand...
Click to collapse
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
indyjones83 said:
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
Click to expand...
Click to collapse
Did you try the link in my previous post? I'm running win7 64 bit and it worked for me!
Maybe just try adding the file in your USERPROFILE directory first!
Sent from my HTC Sensation using XDA
bobjbain said:
Did you try the link in my previous post? I'm running win7 64 bit and it worked for me!
Maybe just try adding the file in your USERPROFILE directory first!
Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse
Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43).
I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean?
and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system...
It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG....
but it works with win xp...! I tried again..!
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
indyjones83 said:
Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43).
I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean?
and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system...
It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG....
but it works with win xp...! I tried again..!
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
Click to expand...
Click to collapse
OK try this :-
Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them).
Attache your G9 then go into device manager.
Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled.
Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point.
Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file.
If you get unsigned warnings click on the "trust me" or whatever it says.
Driver should now be installed.
The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist).
You can test adb connectivity by using "adb devices" from the command line.
Hope this helps
indyjones83 said:
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
Click to expand...
Click to collapse
I think this is probably because your USB cable only has 2 internal cables, not 4.
IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power.
If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless.
Are you using the cable you got with the G9??
bobjbain said:
I think this is probably because your USB cable only has 2 internal cables, not 4.
IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power.
If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless.
Are you using the cable you got with the G9??
Click to expand...
Click to collapse
Yes, I'm using the cable i got with the g9.. I could have a dual cable (the one they give to you with an external hdd), but it's mini usb, not micro...
bobjbain said:
OK try this :-
Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them).
Attache your G9 then go into device manager.
Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled.
Click to expand...
Click to collapse
And this is the problem.. I don't have any driver to uninstall, as if my device is an "Unknown Device" no service, no adb no mpt recognized.. only an "unknown device".. even with new drivers, the only driver it lets me install are Samsung drivers.. but obiously doesn't work!
I now tried in installing it as this samsung, just to have something to uninstall...
bobjbain said:
Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point.
Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file.
If you get unsigned warnings click on the "trust me" or whatever it says.
Driver should now be installed.
The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist).
You can test adb connectivity by using "adb devices" from the command line.
Hope this helps
Click to expand...
Click to collapse
You are really amazing, archos is not caring at all..
Before I tried your firs suggestion in USERDEVICE and for a minute it found my device as Error 10 and not Error 43 (unknown device)... and that's the only moment my pc saw the tablet...
Thankyou!!
indyjones83 said:
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
Click to expand...
Click to collapse
I too have run across this problem--AFTER woprking for 6 months with it under ADB just fine. Not just my work computer, home devices as well. Did you ever get this fixed?
So I have a Samsung Vibrant(just got it recently) and I'm having problems when i connect it to the computer. It gives me an USB device not recognized on my windows 8 computer. I have spent all morning searching and reinstalling drivers and trying my old pc and new cables and i found out that my old windows 7 computer with 4GB of ram and an overloaded hard drive will detect my device the problem there is it not my main computer and i dont want to have to connect all the vga cables boot it up connect mouse and ect to use this computer just to be able to copy files, and do other things from my computer to my phone I dont know why my main computer dell inspiron windows 8 will not work when it was a couple of days ago when i had a problem with conectivity and had to flash back to stock but now it wont connect. could someone help me? Here's a list of things i've tried
installing kies
installing adb again
aoi tool and then drivers
a bunch of diffrent drivers found on the fourms
diffrent usb cable
i would like to be able to do it on my main computer but its not working if someone could help that would be great
also please dont hate on me for having windows 8 jk i dont care :good:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Vono123 said:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Click to expand...
Click to collapse
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
apples723 said:
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
Click to expand...
Click to collapse
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Vono123 said:
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Click to expand...
Click to collapse
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
apples723 said:
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
Click to expand...
Click to collapse
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Vono123 said:
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Click to expand...
Click to collapse
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
apples723 said:
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
Click to expand...
Click to collapse
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Vono123 said:
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Click to expand...
Click to collapse
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
apples723 said:
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
Click to expand...
Click to collapse
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Vono123 said:
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Click to expand...
Click to collapse
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
apples723 said:
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
Click to expand...
Click to collapse
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Vono123 said:
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Click to expand...
Click to collapse
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
apples723 said:
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
Click to expand...
Click to collapse
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
binaryfalcon said:
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
Click to expand...
Click to collapse
didnt make a difrence still getting error i think its something with my system so i guess without a full diagonostic it wont work
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..... (??)