Related
Hello,
I just received a used g tablet I purchased online.
From what I can tell the tablet has Vegan v1.0.0B5.1 installed android 2.2.
Here are my problems upon turning on the tablet. Cannot connect to wifi, starts then disconnects.
Plugged in the usb cable , tablet not recognized by laptop does not see it as a separate drive.
should I return this G Tablet or is there a way to fix this.
The previous owner told me he wiped the tablet to get all his info off but i think he went about it the wrong way.
Any advise?
In order for the lap top to recognize the device you will need to download the driver for g-slate to the lap top
Sent from my LG-V909 using XDA App
Can anyone point me to a link with the driver, I am having no luck
Okay, I found the driver,
If anyone can post directions on how to get the driver installed on windows 7 i would be greatful
If you talk about adb driver then here is the link:
http://forum.xda-developers.com/showpost.php?p=10385457&postcount=1
Using adb you can have access to android os from your laptop. But for your tablet looks like USB disk your don't need driver. When you connect USB - android will ask : do you want to activate USB share?
You tap yes and your laptop will see internal sdcard as USB drive.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
Run the trouble shooting guide in KIES to re-install the drivers . Also, use KIES AIR, that only needs WiFi and you can access files and folders via your pc browser. Hope that helps
unistaller old driver. go to samsung website download lastest driver and install it
depzaj said:
unistaller old driver. go to samsung website download lastest driver and install it
Click to expand...
Click to collapse
Yup that to. BUT, often on the Samsmug site the software version available is one version behind behind that available via online updates Kies.
Tried that
Hi, I have already done all of the above more than 3 times ive removed the drivers, kies and re installed and my computer will always just keep saying usb device not recognized with code 42.
This is what microsoft have to say:
"Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer."
I have to go out just now. I'll take a looky see when I get back.
error 43
oh im sorry its not error code 42 but 43
windows detectded problems with this device....
Do you have a Linux OS under the hand? It would give you a lot more information than Windows does... If you dont have but want to try, you can download the disc image from ubuntu.com or any other distro like linux mint or fedora etc.
Just to get information on your phone you dont have to install it, just starting on the liveCD, plugin the phone in and running comands like dmesg, lsusb and maybe hwinfo would be able to tell you what is happening with your phone.
Sent from my Nexus S using XDA
error 43
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
pacificblue03 said:
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
Click to expand...
Click to collapse
This is why I suggest you to try to plug it in a linux machine and run those commands, there is obviously a problem with your device and Linux could help you to define what it is since it gives more information on the hardware.
If you are unfamiliar with dmesg output you can create a pastebin and link it here I will try to help with it. The output of lsusb may provide interesting info too. (as hwinfo but I don't think it is available by default in Xubuntu)
Sent from my Nexus S using XDA
error 43
well i will try if i can but it will be in a day or two as im packed to the top with assignments
Also I did not mention that but you can access your phone via the wifi network starting an ssh or ftp server on it, the one I use is connect bot from the market. This way you can manage you music and files over the network.
Sent from my Nexus S using XDA
error 43
yes i have done it using kies air that works. i will try the ubuntu method as soon as i can. thanks for all your help so far everyone.
Can you confirm that your usb ports on the PC is working with other devices. Its starting to look like a faulty phone. Have you tried a different usb cable, or can you check the current one with another device. We need to exclude all other factors before we conclude it is a faulty phone.
error 43
other devices work yes.
OK, looks like a croaked phone. Last ditch effort. If you go over to the forums at http://www.sevenforums.com/ have a good search for that error 43 code, there might be an answer that I've missed. We could also have a good look at the windows error logs, but I don't hold much hope as you have proven the PC hardware works, and you have checked and cross checked the drivers. All the error logs will show is an expanded view of the error.
I would consider returning the device with a view to a new replacement. Sorry. :-(
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Got the same issue on 3 different W7 pc's. Got my sgs3 like 3 days. first day USB connection worked just fine but now there's no way of connection it to pc with USB. offcourse you can connect with WIFI but with USB link is much faster
Galaxy S3 drivers issue...resolved!
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
I had the same problem and could not figure out why...here is the deal:
Prior to SGS3, I had the old Samsung Galaxy S/Vibrant and was using the USB cable which came with it...then I thought; maybe the USB cable in the box of GS3 is different or superior...i tried it and VOILA! it worked...so that is all I had to do...all these reboots and re-installing drivers was just a waste of time...PS> I am running Win 7 64bit
USB ERROR
I still cant connect with 3 different cables, i am going to do a factory data reset and tell you all how i go in about 15 minutes...
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
ericdg said:
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
Click to expand...
Click to collapse
ADBSetup will get you the drivers you are looking for:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Worked for any Android phone I tried.
Thanks, I'll give that a shot and see what happens!
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
ericdg said:
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
Click to expand...
Click to collapse
Easiest way to tell is open up a command prompt in the folder that adbsetup installed to (C:\ADB I think) and type:
Code:
adb devices
If all is well, then the device will be part of the listing.
Thanks Joel.............I think it worked.
The ADB command came back with:
List of devices attached
HT22_______7 device
That's not a number that I've ever seen associated with my phone, but I assume that's it.
Confirmed.................I was able to reboot the phone by ADB!
Excellent! This will also mean the fastboot commands needed to unlock your bootloader will work too.
.........one would think so, Joel, but I can't get fastboot to do anything. ADB recognizes the phone, and will reboot into bootlocker, but once there it'll do nothing. Windows pops up a message shortly after bootlocker opens that says something to the effect of "there was a problem with USB device not recognized". I tried the command "fastboot devices", but got nothing. I know that I'm darned close, and it's probably something simple, but just can't get it to work. Maybe I need additional drivers for fastboot, or need to move it to another directory?
Thanks,
~E
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
joel.maxuel said:
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
Click to expand...
Click to collapse
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
ericdg said:
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
Click to expand...
Click to collapse
Dont know where you got your HTC drivers, but you should try the ones in this post (step one - hopefully its still live - if not I can dropbox it for you):
http://forum.xda-developers.com/showthread.php?t=1801106
Sent from my LG-D520 using XDA Free mobile app
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
ericdg said:
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
Click to expand...
Click to collapse
Uh-oh. Either the link was dead when I went through this process back in April, or I had bad organizing skills at one point and didn't put the file in the Doubleshot folder before completing a purge. Either way, I don;t have the file.
Nor did I really need it. The second Doubleshot I rooted I ended up using it in my native Linux environment (no drivers needed), vs my Windows XP emulated through VirtualBox. That's what you could do. Get a live Debian DVD (Im like the XFCE desktop version), boot in, get fastboot:
Code:
sudo apt-get install fastboot
And then use fastboot:
Code:
sudo fastboot ...
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
ericdg said:
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
Click to expand...
Click to collapse
Just need the one. My recommended file to download is this:
http://cdimage.debian.org/debian-cd...ybrid/debian-live-7.6.0-i386-xfce-desktop.iso
Burn the image (not the file) onto a DVD (can be a rewritable) and reboot with the disc in the drive. Once it's fully loaded, you can either enter commands by clicking on the "terminal" icon on the bottom of the screen (preferred), or press Ctrl + Alt + F1 to get a prompt (may have to log in as "user", there shouldn't be a password). Hope this helps.