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?
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
Hi, I am looking for usb driver for viewpad 7 for using adb. Can anybody provide and link or pointers from where can I get the same.
Thanks,
Dang
There's no "real" driver...
Just connect your Viewpad 7 to your PC.
A window pops up where you can select "setup.exe" - select it.
Then a few drivers get installed (perhaps a restart is necessary)
Seems like the Viewpad 7 has a virtual drive which gets mounted when connecting it to a PC - it's shown up as virtual CD-drive for me under Windows XP and Windows 7.
PS: The drivers are also located on the virtual CD-drive in a directory.
Make sure you run the file from the virtual optical drive if you have autorun disabled.
Sent from my HTC Sensation Z710e using XDA App
plug youre viewpad in now youre pc see een cdrom right click and open use that adb.exe that one works
How to remove the virtual drive
I have already installed the drivers from this drive, but whenever I connect the device, the virtual CD-ROM drive still appears. Anyone know how to get rid of it?
LEGEND383 said:
I have already installed the drivers from this drive, but whenever I connect the device, the virtual CD-ROM drive still appears. Anyone know how to get rid of it?
Click to expand...
Click to collapse
I always open the Sync tool then (do nothing, no sync or so).
That's the only way my Windows 7 PC recognizes the tablet via ADB.
I have been doing that as well, but it's just annoying to have this extra drive that is of no use and just sits there taking up a drive letter.
Stupid question, ive never used adb, but does this mean i dont have to download it because already cames on that virtual drive, and so i only need to install it ?
Now i manage to install the drivers.
I go to the command line in windows and write :
adb usb
adb devices, and get this:
List of devices attached
FM6120420141
Then i do,
adb shell, and nothing happens.
Ive tried several commands and nothing works, what m i doing wrong here ?
Hi guys, i tried another pc with windows xp and everything worked perfect at first try. Thans for the help VPAD7, nice chating.
Bye all the other losers.
Hi VPAD7
Can you share the solution for "adb devices" not working on windows7? I am facing he same problem with my Viewpad7.
Thanks for your contribution to the forum.
---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------
VPAD7 said:
Now i manage to install the drivers.
Could you share how did you manage to get drivers installed on windows7? I am also seeing same issue with viewpad7. I am trying to root it.
Click to expand...
Click to collapse
Solved driver issue on windows7
Hi,
I was facing issue in connecting viewpad7 to windows7 machine. Even synchronization steps were failing. Manuall attempt to run "adb.exe devices" were unable to detect the device. Here is my steps that I did for rooting the device with SuperOnceClick(SOC)1.7-
1. Initially driver were not detected/installed on windows7. Only CDROM displaying setup was displayed and clicking "Setup.exe" is not installing drivers. Copy the All files on computer and say folder name is "v7Setup".
2. To Install drivers, Connect Tablet/Phone to windows7, select "USB Tethering in tablet" (This is needed to detect devices by Windows7), in windows7:check the "Device Manager", it can show "Others" two devices: HSUSB & RNDIS. Update the driver for both devices from "v7setup/RUT/*" folders.
3. Now start SOC1.7 and select "rageagainstthecage" and click root. It may wait at "Running rageagainstthecage..." message in SOC log window. Then disconnect the Tablet after waiting for 1-2 minute and connect again after beep sound from windows7. Here, again I needed to install the drivers as mentioned in step2. SOC1.7 will proceed and finally in poup message, it will ask to "push su" files. And Done.
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything.
I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect.
So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are:
I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both)
I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers
Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13
Click Start button, then right-click Computer, then click Manage
Click Device Manager
Expand Other devices, you should see SCH-I500 with the yellow exclaimation point
Right-click it then click Update Driver Software
Click Browse my computer for driver software
Click Let me pick from a list of drivers
Scroll up, highlight Show All Devices, click Next
Click Have Disk
Click Browse
Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury
Double-click ssadadb2.inf, click Open, Click OK
Highlight SAMSUNG Android Composite ADB Interface, click Next
You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes
You should see Windows has successfully updated your driver software, click Close
Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone
Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before)
Open a cmd prompt (start>run>cmd enter if you didn't know)
browse to where you installed adb and type "adb devices"
You should see your device and a serial number again....back in business
Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
Hi, I have a Scroll Excel tablet and was recently trying to flash CMW5 onto it using a recovery from the scroll forums, however in the command prompt whenever I type in the command ("adb push install-recovery.sh /data/" in case that helps) it says the daemon isn't running, then it starts the daemon, then it says "Error: device not found.
I've checked everything, I have correctly navigated to the folder which holds the recovery, I am entering the recovery name correctly, I do have the Google USB Drivers etc.. installed, the device is plugged in (and the computer knows it is, it detects it) but the prompt doesn't recognize the device.
There is one thing though, whenever I plug it in the computer tells me the device is not recognized, but it at least acknowledges that the device is there. Am I missing any drivers on my tablet's side or what? Thanks
Also, I attached a file of what the prompt tells me below v
I do not have this tablet so I cannot give you an exact answer. However, I would try uninstalling and reinstalling the drivers and restarting your pc. Also try a different usb port.
As stated in the post above, I would check my Drivers. I would also suggest checking your USB Cable. Make sure that it is good. Is your SDK Tools up to date ? BTW that seems like an odd path for your platform-tools folder.
prboy1969 said:
As stated in the post above, I would check my Drivers. I would also suggest checking your USB Cable. Make sure that it is good. Is your SDK Tools up to date ? BTW that seems like an odd path for your platform-tools folder.
Click to expand...
Click to collapse
It can't be the USB cable, I've tried 2 or 3. Also, yes. I updated the SDK tools yesterday. And I know it's an odd path, but I'm a bit OCD about keeping things in folders.
However, about the drivers, the computer says it doesn't recognize the device. And when it scans for the drivers it doesn't find anything to download. Regardless, Storage Options are willing to take a look at it for me (how nice, even with a technically void warranty.) Thanks for your help anyway.
I would definitely recommend re-installing the drivers. Then try again.
TEAM MiK
MikROMs Since 3/13/11
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