Related
I have my 2.1 DamageControl ROM running fine (thx damage!). I'm just trying to connect to adb. I'm on win7, 64bit.
I used to connect fine when I was on fresh 1.1.
I thought it was b/c I had an outdated sdk, which I did. I upgraded from v3 to v5, and made sure I downloaded all the latest, including the latest usb driver.
I also checked to make sure I have HTC sync 2.08.
but I just keep getting this.
C:\android-sdk-windows\tools>adb remount
error: device not found
Click to expand...
Click to collapse
anyone else getting this issue, or know the solution?
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
crunchybutternut said:
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
Click to expand...
Click to collapse
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Try this,
adb kill-server
abd start-server
illogic6 said:
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Click to expand...
Click to collapse
Ah hah.. thanks for the heads up. Here's the correct link. I also fixed my original post.
thanks for all the advice! I'll give them all a try.
This is what makes this website awesome. I'm glad everyone has come back together after all of that madness.
Tipharet said:
Try this,
adb kill-server
abd start-server
Click to expand...
Click to collapse
FYI, this one didn't work.
@crunchy - hm, I don't see any adb driver reference
I also went to device mgr in win7, and yeah, it has the !, but when I tried to update, it still failed. I even tried pointing to the usb driver folder in my android sdk, but it didn't like it. maybe something specific to win7 64bit?
Maybe I need to install the drivers manually? But what driver should I look for, for this Damagecontrol 2.1 ROM Sprint Hero now?
Did you make sure to enable debugging?
I don't have a link handy, but just go to the HTC support site for the Eris and download the latest HTC sync. It will fix your drivers, no fuss and straight forward.
smw6180 said:
Did you make sure to enable debugging?
Click to expand...
Click to collapse
Yes, tried with it off, and on. I also tried reinstalling HTC sync 2.08.
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
actually, I didn't read your post yet when I posted my statement that I installed 2.08. I was responding to someone else. I'll try out your tip. thx.
obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
Try your own link. It doesn't have a link to the Eris page.
EDIT: the joys of technology. When I used google chrome, the download link didn't work - when I used firefox, it did.
FYI, HTC sync 2.0.25 for the Eris didn't work.
ro_bro said:
Try your own link. It doesn't have a link to the Eris page.
googled and found it myself:
http://www.htc.com/us/support/droid-eris-verizon/downloads/
edit: ugh, the download link leads to a general support page again.
Click to expand...
Click to collapse
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
Yes, I had 2.0.8 installed, but i uninstalled first before installing the 2.0.25. but I haven't tried the pc reboot, nor the kill server yet, I'll give those a try. thx!
obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
This advice got me further... but here's what I get:
C:\>cd android-sdk-windows
C:\android-sdk-windows>cd tools
C:\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\android-sdk-windows\tools>adb kill-server
C:\android-sdk-windows\tools>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell
error: device not found
C:\android-sdk-windows\tools>adb devices
List of devices attached
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
FYI, I still see a '!' beside my 'Android Phone' icon in my device manager.
Try to download and Install
HTC Sync Version 2.0.18 from HTC Support and it must work for you
Thanks
My nexus cannot be rooted because the adb drivers WON'T install.
I downloaded the sdk and installed the google usb drivers.
But, when my PC finds NEW hardware I point to the google usb drivers and I get the error CANNOT INSTALL HARDWARE. Running VISTA.
I have been reading and trying everything but I just cannot figure it out.
I finally said I will just have to post and HOPE you guys can give me a hand here.
Thanks.
My nexus cannot be rooted because the adb drivers WON'T install.
I downloaded the sdk and installed the google usb drivers.
But, when my PC finds NEW hardware I point to the google usb drivers and I get the error CANNOT INSTALL HARDWARE. Running VISTA.
I have been reading and trying everything but I just cannot figure it out.
I finally said I will just have to post and HOPE you guys can give me a hand here.
Thanks.
BTW, Im on 2.1.3. Is that why perhaps I'm having issues?
JasjarMan said:
My nexus cannot be rooted because the adb drivers WON'T install.
I downloaded the sdk and installed the google usb drivers.
But, when my PC finds NEW hardware I point to the google usb drivers and I get the error CANNOT INSTALL HARDWARE. Running VISTA.
I have been reading and trying everything but I just cannot figure it out.
I finally said I will just have to post and HOPE you guys can give me a hand here.
Thanks.
Click to expand...
Click to collapse
JasjarMan said:
BTW, Im on 2.1.3. Is that why perhaps I'm having issues?
Click to expand...
Click to collapse
try installing the drivers this way, i havent seen this not work for any android phone. install the free pdanet software from their site onto your computer http://junefabrics.com/android/ follow the instructions that they give you. it will install the proper drivers in a few minutes. btw, pdanet is a tethering program that works side by side with a android app, but you dont need it. you are just using it so that itll install the driver. good luck!
btw, you can get the answer here too http://forum.xda-developers.com/showpost.php?p=12657095&postcount=2
i answered you in your other thread with the same title
http://forum.xda-developers.com/showpost.php?p=12657038&postcount=3
simms22 said:
i answered you in your other thread with the same title
http://forum.xda-developers.com/showpost.php?p=12657038&postcount=3
Click to expand...
Click to collapse
THANKS, GOT IT! Now when I type adb shell it works, BUT than I type SU and I get PERMISSION DENIED?
I just want some SIMPLE instruction and I don't find anything.
Btw, I cant get SUPERSUSER installed. I did go to the market and installed it that way and I can see it in the app drawer but now what?
You have to flash superuser.zip in recovery (install zip from sdcard then choose zip from sdcard and you have to choose your superuser.zip on your internal memory). BEFORE you have to mount /system in recovery.
Sent from my Nexus S using Tapatalk
I don't want to look rude, but I think both of these threads will be cleaned in less than a few hours...
JasjarMan said:
THANKS, GOT IT! Now when I type adb shell it works, BUT than I type SU and I get PERMISSION DENIED?
I just want some SIMPLE instruction and I don't find anything.
Click to expand...
Click to collapse
I don't want to be rude. But
Why for ****s sake are you so damn desperate.
It seems like you demand something.
And just flash a custom rom and you will have superuser
Sent from my Google Nexus S using XDA App
Hi: I'm a long time lurker here on xda-dev, but I'm a first time rooter and this is my first time posting here.
I appreciate any help that I can get, and I will try to be as descriptive as possible so that I don't waste anyone's time. You should know that I am running OS X 10.6.7 (which is 64 bit if that makes a difference). I know that it's possible to root from OS X because I've been in contact with a fellow xda'er about his success with it and my subsequent problems. You will notice from the screenshots that I have a bootcamp partition because I plan on installing Windows 7 at some later time. I think that this may be a driver issue, but really dunno why I would have this driver problem if the person who I know has had success with OS X 10.6.7 didn't have any problems. Not sure if this matters, but I am using this sdcard: http://amzn.com/B003WGJYCY
Things that I've done that you might ask me if I've done:
-Debugging is on (I've toggled it a few times too)
-temprooted with Visionary
-Extracted the Shift file to the root of my sd card
-Checked the md5 of the file in Shift using Terminal emulator (it matches what the guide says it should be)
-Reinstalled the SDK
-Reinstalled Visionary
-Re-Extracted the 'Shift' file to my sdcard.
I am trying to root my shift following this guide : http://forum.xda-developers.com/showthread.php?t=932153
I have installed Android SDK and for have installed the packages that you can see in this screen shot: http://oi55.tinypic.com/2dvimb6.jpg
I then temprooted using Visionary: After a few failed temproots, I did get a successful temproot, which I am verified by gaining SU with the app Terminal Emulator.
I open up command prompt and do the commands that you can see in this screenshot and as you can see after ./adb shell I get "error: device not found" : http://oi51.tinypic.com/2ztcymt.jpg
As you can see, I can open adb, but the adb shell command returns an error that no device is found. I've also done this: http://oi51.tinypic.com/264t6o5.jpg
So, what do you think?
i forgot to mention that my phone is in charge only mode when I execute ./adb shell
is it connected to a 2.0 USB port?
Also have you tried restarting your phone and mac?
I also saw on another forum that Superuser had to be uninstalled then try temp rooting again.
Also are you keeping an eye on your phone while trying to gain su access? You have to click yes when it asks if you wanna give permission.
You could always try rooting via terminal on the phone. That's what I did, no PC involved.
^ Shift Faced
Thanks for your responses.
I assume these are USB 2.0 ports on my 2010 MacBook Pro. I've uninstalled superuser a couple of times, but when I use terminal emulator to check if I'm temprooted, it shows back up in my apps list.
I have never had the option of giving adb superuser permissions, but yes I have kept my eye on the phone to make sure that the phone wasn't requesting this.
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
dubs.law said:
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
Click to expand...
Click to collapse
That's what I did. Had been waiting for perm root so long and was so excited I couldn't stand to wait until I got home and just put the commands into terminal on the phone. Just make sure that you input all commands EXACTLY. It was recommended by others to do it from desktop so you can be sure and copy and paste the commands so as to cutdown on errors but I'm not sure why... I can copy and paste from the phone It's just kinda a pita.
^ Shift Faced
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
dubs.law said:
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
Click to expand...
Click to collapse
Nope.
^ Shift Faced
So, there is no adb commands, you just flash the "eng spl" , correct?
I rooted without a computer. Thanks!
dubs.law said:
I rooted without a computer. Thanks!
Click to expand...
Click to collapse
Awesome! I was coming on to tell you I don't really remember all the details as it was a long time ago and that I couldn't help any
Exciting doing it from the phone, right? The fear of bricking is fun
^ Shift Faced
So running into a problem. I have downloaded and installed ADB but the version installed is 1.0.32. And my computer doesn't find any devices when I type adb devices.
Is this because I need a later version of ADB and if so any clue how to install it on Ubuntu? I have searched the WEB and can't find it.
Cheers!
swehes said:
So running into a problem. I have downloaded and installed ADB but the version installed is 1.0.32. And my computer doesn't find any devices when I type adb devices.
Is this because I need a later version of ADB and if so any clue how to install it on Ubuntu? I have searched the WEB and can't find it.
Cheers!
Click to expand...
Click to collapse
i am not a Ubuntu user (using Win10 for now), but i found this
https://www.howtoinstall.co/en/ubuntu/xenial/adb
hope that helps
DrakenFX said:
i am not a Ubuntu user (using Win10 for now), but i found this
https://www.howtoinstall.co/en/ubuntu/xenial/adb
hope that helps
Click to expand...
Click to collapse
Thanks DrakenFX for trying. I had already looked at that one. I looked some more and I guess Ubuntu has been having some problems with MTP. The answer for the problem is found at HERE if anyone is running into the same issue.
I use linux as well, but instead of installing the whole Android development kit, I went for the leaner, no-install-required platform-tools, which is the linux equivalent of "Minimal ADB and Fastboot". You can download it directly from Google here: https://dl-ssl.google.com/android/repository/platform-tools_r23.0.1-linux.zip
Unzip it, open up a terminal in the folder, and type " ./adb devices "
swehes said:
Thanks DrakenFX for trying. I had already looked at that one. I looked some more and I guess Ubuntu has been having some problems with MTP. The answer for the problem is found at HERE if anyone is running into the same issue.
Click to expand...
Click to collapse
man this was driving me nuts , LoL :silly::silly:
just did Step 1 and 2 and my issue got fix ,
just got back with dual boot Ubuntu 16.04.1 + Windows 10 and even installing the drivers couldn't get adb to detect my axon 7...till came across your thread and post reply to the other thread....thanks man
DrakenFX said:
man this was driving me nuts , LoL :silly::silly:
just did Step 1 and 2 and my issue got fix ,
just got back with dual boot Ubuntu 16.04.1 + Windows 10 and even installing the drivers couldn't get adb to detect my axon 7...till came across your thread and post reply to the other thread....thanks man
Click to expand...
Click to collapse
Glad I could help.
adb devices on ubuntu 16.04
swehes said:
Glad I could help.
Click to expand...
Click to collapse
Just to document this in case it would benefit someone else: I have been trying everything I could find on the net to get my A7 recognized by adb devices. The list always came up empty. Yet, on my windows 10, adb devices for my A7 worked. And my htc m7 on ubuntu was also recognized. Finally, I removed the famous 51-android.rules (which had a line for my A7 but not for my m7; on /etc/udev/rules.d) and then adb devices showed the A7.
EDIT:
The day after having written this, I lost the device again: adb devices no longer showed the A7. Again tried everything with no success. Then I downloaded the Android SDK, which comes with version 1.0.39 of adb. Ran that and it worked. Go figure. So I still cannot really put my finger on what made the difference.
I searched the Entire web for my problem but unfortunately, i didn't get the solution...
I know, I'm a noob in this but i did everything correctly without any mistakes (because, I've verified more than 15 times!) but I'm facing the same issue... Can anyone suggest me a solution?
My problem is shown in this below image.
PiXinCreate said:
I searched the Entire web for my problem but unfortunately, i didn't get the solution...
I know, I'm a noob in this but i did everything correctly without any mistakes (because, I've verified more than 15 times!) but I'm facing the same issue... Can anyone suggest me a solution?
My problem is shown in this below image.
Click to expand...
Click to collapse
ADB does not work with Powershell. You need to use a command prompt CMD.exe
Doktaphex said:
ADB does not work with Powershell. You need to use a command prompt CMD.exe
Click to expand...
Click to collapse
I even tried with that but i got a message saying that the command adb doesnot exist.
Could be unrelated, But what about Nokia drivers?
CarbonGTR said:
Could be unrelated, But what about Nokia drivers?
Click to expand...
Click to collapse
I don't know much about it when i connected my phone, it's drivers got installed automatically. Even adb is also installed...(adb interface)
Adb.exe doesnot open
1.)Add platform tools to your PATH variable in Environmental Variables
2.)you can try .\adb.exe devices
karandpr said:
1.)Add platform tools to your PATH variable in Environmental Variables
2.)you can try .\adb.exe devices
Click to expand...
Click to collapse
Anyway thank you everyone for your support...
I had thought that it might be a mistake from the computer side or something else... But it was my mistake... I had didn't changed the directory to adb folder, instead i was doing lamely....
Now, i know my mistake and i did it...
Again-- thank you ?