Related
These are the steps i used to set up my drive(may not work for everyone dont see why though)
I don't include a step for installing HTC Sync and its drivers as ADB only worked for me when the phone was on and in sync mode, also because the pdanet install wrote over them when i installed
1.Download pdanet for android Here(this will install the proper drivers)
2.Install Pdanet on comp no need for it on phone so if it fails dont worry. Have phone plugged in during install
3.Boot into hboot(vol dwn+power)
4.Boot into recovery(vol up+power to see menu)
5.Unplug phone then plug it back in
Make sure you have debugger on before going into recovery
Now you should see your device as Recovery when you adb devices in command.
If you see 2 devices try disabling(not unmounting) your usb mass storage and then upluggin and plugin the phone back in
I really appreciate it but...
Well i woke up this morning to this new thread, tried your EXACT 5 steps with deleting all traces of the old HTC SYNC drivers and software. Still a no go. The device STILL shows up twice and then disappears. Also disabled through DEVICE MANAGER the MY TOUCH SLIDE USB MOUNT. Unplugging and plugging back in does NOTHING. I am so sick of this it hurts. FOR THE LOVE OF ROOT PLEASE HELP ME TO FIND AN ACTUAL SOLUTION.
According to another person in the forum, another couple of steps need to be added here.
check the #3 post of the other adb thread for more details (I can't link yet :-( )
After installing the pdanet: install htc sync, download the sdk, then install latest drivers.
Then continue with the rest of the process
I haven't had a chance to try it, but thought I would share to see if it will help.
If it helps, we should prolly amend the first post here.
thecracker said:
According to another person in the forum, another couple of steps need to be added here.
check the #3 post of the other adb thread for more details (I can't link yet :-( )
After installing the pdanet: install htc sync, download the sdk, then install latest drivers.
Then continue with the rest of the process
I haven't had a chance to try it, but thought I would share to see if it will help.
If it helps, we should prolly amend the first post here.
Click to expand...
Click to collapse
I believe you're talking about me. I would just point out that I was listing what I did, not nec the steps needed to get the phone to show up in adb devices. Its not clear you need to install pdanet or htc sync.
Both of those drivers let me see the phone in adb devices when it was on, let me issue commands like adb reboot recovery. But neither of those drivers ever had the phone show up except for briefly after clicking recovery from hboot and going away once the recovery triangle showed up.
Finally when I removed all traces of the device driver and installed the (r3) driver from the sdk. The next time I tried it, it worked out for me.
I think a lot of people are misreading the steps or being ham-fisted in their approach. This method is as much an art as it is a science at this point.
seek and you shall achieve.
- faylix / local
Mytouch slide rooted Eugene's Update-1
I'm sry, i was just trying to make sure that any successful attempts were communicated.
I hope i didn't cause more harm then good
dsamuels39 said:
Well i woke up this morning to this new thread, tried your EXACT 5 steps with deleting all traces of the old HTC SYNC drivers and software. Still a no go. The device STILL shows up twice and then disappears. Also disabled through DEVICE MANAGER the MY TOUCH SLIDE USB MOUNT. Unplugging and plugging back in does NOTHING. I am so sick of this it hurts. FOR THE LOVE OF ROOT PLEASE HELP ME TO FIND AN ACTUAL SOLUTION.
Click to expand...
Click to collapse
I did the same thing you did and had the same problems you had. I went to try it on my laptop which is windows vista 64bit (pc is w7 64bit). I was still having the same problem, not detecting anything and it would show up twice or three times then disappear. I installed sync that comes stock with the SD card (I had sync from the HD2 installed). I already had PDANET installed on my laptop. Anyways having doing the same thing over and over which seemed to be half a million times it all the sudden worked. So it will "catch" sooner or later. Just keep doing it. As long as you have the proper sync installed and you dont have an error with you android 1 in the device manager then it will work sooner or later. I know its a MOFO, I've been doing it for 2 days stright now and just barly got it rooted.
Good Luck.
alas it was a no go for me
I havent changed anything with my ADB since it was setup for my G1 and I can still find the device and enter commands like "reboot". Does this mean that my ADB is setup correctly for my Slide?
My HTC Hero CDMA Cellular South, the USB doesnt work what so ever. When I plug it in I get no message or sound of it connecting and it just starts charging. Its a stock ROM, on 2.1.... any help? I have tried rooting the device before but quit before doing any flashing of the ROM because of the lack of information of the tutorial I was following. Please guys I really want my usb back
So your phone charges when its plugged in? But you cannot connect it to your computer to mount the sdcard. You may want to try running the RUU in fastboot mode.
unCoRrUpTeD said:
So your phone charges when its plugged in? But you cannot connect it to your computer to mount the sdcard. You may want to try running the RUU in fastboot mode.
Click to expand...
Click to collapse
Could you tell me what exactly this does and how I can do it? RUU im pretty sure is the updater, am I updating the ROM again to maybe fix the problem?
Update: I checked the USB cable and swapped in a different cable and everything is working just fine. Sometimes it's the simple things!
I'm having the same problem on my Sprint Hero, running CM6 with Kernel #14. I just loaded kernel #14 last night and this is the first time I tried to use USB access.
It's like it's not connected to the computer...but it is charging.
Ive already tried a differnt usb port and cable so, how can I reflash my rom without usb support?
jwhistler said:
Update: I checked the USB cable and swapped in a different cable and everything is working just fine. Sometimes it's the simple things!
I'm having the same problem on my Sprint Hero, running CM6 with Kernel #14. I just loaded kernel #14 last night and this is the first time I tried to use USB access.
It's like it's not connected to the computer...but it is charging.
Click to expand...
Click to collapse
Okay, I just got done putting GodSpeed Recovery on my hero and toggled the usb and im still getting no indication of the usb working on my computer
You might want to look through manage applications in settings or some where in settings and clear the default for what to do when you plug your phone in.
Do you have a wireless router. You could install adbwireless from the market and get stuff to and from your phone.
Have you tried it on a different computer
You might want to delete the drivers on the computer for your phone, reboot computer and then plug the phone back into the computer and let it load the drivers.
Sent from my HERO200 using XDA App
unCoRrUpTeD said:
You might want to look through manage applications in settings or some where in settings and clear the default for what to do when you plug your phone in.
Do you have a wireless router. You could install adbwireless from the market and get stuff to and from your phone.
Have you tried it on a different computer
You might want to delete the drivers on the computer for your phone, reboot computer and then plug the phone back into the computer and let it load the drivers.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I have tried everything, I have reinstalled drivers used 3 differnt computer with 3 differnt operating systems. is there a way I can reflash the ROM without it being connected to the computer... say my sd card...?
I just hard reset the phone and still nothing...
When you connect your phone and do
Code:
adb devices
do you get anything?
I had this very same problem a few weeks ago. I was using the original usb cable that came with the phone when i got it back in march. Simply trying a new "stronger" looking cable did the trick for me.
Although, I think you have already tried this.
unCoRrUpTeD said:
When you connect your phone and do
Code:
adb devices
do you get anything?
Click to expand...
Click to collapse
What is adb devices? I get nothin when i connect it to my pc. My pc detect nothing when i go and look in device manager and my phone just start charging. Ive tried a differnt cord differnt os, differnt computer, sd card, etc.. Please help im really doubuting I will fix this and this is the only phone im going to have for a while.
adb is a program found in the android sdk. Do you have the android sdk setup on your computer? Are you rooted?
Sent from my HERO200 using XDA App
Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!
Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program
Thanks for the info!
I am away until tomorrow evening. I will try it then.
Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!
it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver
Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Stryder5 said:
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Yes, that's where I got the drivers (and that's how I got fastboot working).
I've taken the drastic step now of uninstalling the entire SDK thing and am currently re-installing it. We'll see how that goes.
EDIT: yeah, "adb devices" still gives nothing at all.
You need to turn it on first but Developer Options are hidden in Settings. Go into About phone and tap the build version. After 7 times you will have access and you can turn on USB Debugging
chinly43 said:
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
Click to expand...
Click to collapse
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
0.0 said:
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
Click to expand...
Click to collapse
While this was, admittedly, once my problem back in the early days of android, it's not the problem this time. USB debugging is on.
EDIT: I've also reconfirmed that fastboot is still working after the whole re-installation thing.
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
chinly43 said:
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
Click to expand...
Click to collapse
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
0.0 said:
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
Click to expand...
Click to collapse
That's all I can suggest as well, although I can't see what the issue could be
Yer try installing the SDK and downloading the "Google USB Drivers" from there to see if it helps.
Sent from my Nexus 4 using Tapatalk 2
Here try this. It's from the sdk. I just zipped it. https://www.box.com/shared/7sutkummukh4pup0rwoi
Sent from my Nexus 7 using Tapatalk 2
You can just get the windows executable from Google, r21
http://dl.google.com/android/installer_r21-windows.exe
Thanks, everyone who's been reading/trying to help. Unfortunately, it's still not working.
People suggesting the .exe installer - that's how I've installed it each time. Twice now I've uninstalled/reinstalled the SDK. When installing, I choose the SDK tools, SDK platform tools, the 4.2 API (which is probably unnecessary, right?), and the Google USB driver. Each time, ADB has worked *in general*, but will not recognize this device (via the "adb devices" command).
Here's how things are going right now. When I first plug the phone in (with debugging on), if it's not currently installed as a device then it automatically self-installs and shows up as an "mtp" device. I try ADB, doesn't work. I then go in and manually install the drivers found in various places around this board. When I do this, it no longer appears as MTP. This is weird, though, and I didn't notice this last night - when I look at the list of devices in Device Manager in Windows, the category it falls into is "ASUS Android Devices", under which it's listed as "Android Composite ADB Interface", and it still doesn't work.
Something seems wrong about it being listed as ASUS, though. I wonder if all these current difficulties are a result of the problems I had getting my Transformer Prime to work with ADB? If anyone sees anything above that looks like I'm doing something wrong, let me know; I think the next thing I'm going to try is doing this whole process on a fresh computer here at work that's never been exposed to android at all, see how that goes. I'll check back in after I do that.
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
EddyOS said:
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I have, and it still doesn't work on my laptop. However...
It's working! On a shared computed at work that had never had *anything* android-related installed before. Went through the same procedure I did on my own computer, so the problem is with my laptop, I guess. Which I'm more okay with than it being a problem with the phone. I guess I need to more thoroughly remove everything from the laptop, maybe?
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
chinly43 said:
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
Click to expand...
Click to collapse
I have to do that to my Nexus 7 before ADB will recognize it, so you're not alone there.
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
I had the same problem, here's what you need to do. When you plug it in, change the settings from MTP to Camera for USB settings. I don't know why, but you need to do it.
dcarpenter85 said:
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
Click to expand...
Click to collapse
I've got four other android devices that all worked (simultaneously, at that): T-Mobile/HTC G1, Nook Color, T-Mobile/HTC G2, and an Asus Transformer Prime.
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.