Related
Help! When I try to root my evo shift with gui shift root and recovery all I get is an adb error message. I have installed htc sync on my laptop. I also cannot connect to sync. These problems may be related? I am running windows vista.
sounds like the drivers may not have installed... Where did you get the version of sync you installed? You're best bet is to use the one off the sdcard. I've had an occasion or two also where things got messed up, and I uninstalled it all and reinstalled. (under programs and features you'll find HTC sync and driver installer, remove both and reinstall if necessary)
I installed it off the sd card and have did the install/ uninstall at least 5 times. still no luck.
i had same error but i just did mine maually. theres a video now for manually rotting it. if you fllow the steps you will root your shift
candler72 said:
I installed it off the sd card and have did the install/ uninstall at least 5 times. still no luck.
Click to expand...
Click to collapse
I'm in the same boat no matter what I do it my shift won't connect to sync and when I run adb devices it kicks a blank line then right back to platform-tools I'm running Vista myself and messed with it for hours and no luck I'm mad because I have rooted my shifts already and don't know what went wrong with the drivers sync or my pc this sucks as I need to be able to adb to help test some things
Sent from my PG06100 using Tapatalk
You do have adb debugging on right... the only other thing I could think of.
Yes I do have debugging on.
have you tried getting sync from htc's website to be sure?
If I'm correct the old version of syn from sprints website was giving me problems loading the drivers. I used the newest version from htc website and voila I was good to go. U may want to try that. I just re rooted earlier use the gui and it worked like a charm
Sent from my PG06100 using Tapatalk
I have the sync from htc website. I still get error running adb try again. Ive used the same usb cord and ports with my archos pad and have no trouble transfering files.
What exactly does the error message say? And with what command?
Sent from my PG06100 using XDA App
Error running and. Try again
Sent from my PG06100 using XDA App
Adb
Sent from my PG06100 using XDA App
Maybe it's your sdk that is messed up... Maybe try downloading and installing again.
Sent from my PG06100 using XDA App
Ive got temp root now with visionary. And have it set to reroot when i turn my phone off/on. I have wireless tether (non adhoc) which is what I was wanting to tether my archos 101. I still can't connect to sync. Wondering if its a vistas issue?
danaff37 said:
What exactly does the error message say? And with what command?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I dunno what the other guys error is but I know on mine if I go to device manager there is an error code 37 with my HTC on my Vista pc.....I can cd to my c:\Android\Android-sdk\platform-tools
But when I hit add devices it kicks back and empty line after it starts the Damon on whatever then right back out to platform tools...it does the same thing with every sync I install, plus my phone can't find sync on my pc at all even if its open...and help would be really appreciated
Sent from my PG06100 using Tapatalk
candler72 said:
I have the sync from htc website. I still get error running adb try again. Ive used the same usb cord and ports with my archos pad and have no trouble transfering files.
Click to expand...
Click to collapse
I'm having the "error running adb try again" problem as well. Unfortunately when I try to run adb from the cmd prompt its output goes to a popup cmd prompt window which disappears before I can read it. My guess however is that it's blank like yours.
I'm convinced I've done everything they way I'm supposed to. Has anyone yet gotten the htc drivers to work under vista?
I had this same issue with ADB..all I did was, while connected via usb, uncheck debugging and then recheck. Clicked root again and it worked.
Sigh, there was a adb update. Install the new version from the sdk, delete the one in shiftrr, copy the new one in, close adb with task manager, then run as you were trying to do before. That fixed it for me.
And make sure when you install the recovery, not to use the one it comes with, it doesn't support the newer roms we have on the shift now. If you want to flash current ones, use clockwork 5.0.2.0, our twrp (recommended)
Ok so i downloaded adb already along with android sdk. But every time I click on the adb application it just opens and closes immediately after a bunch of words show up but I can't read it because it closes too fast. Is there something I'm missing?
Sent from my SGH-I777 using XDA Premium App
fcb1 said:
Ok so i downloaded adb already along with android sdk. But every time I click on the adb application it just opens and closes immediately after a bunch of words show up but I can't read it because it closes too fast. Is there something I'm missing?
Sent from my SGH-I777 using XDA Premium App
Click to expand...
Click to collapse
You cannot open adb like that.. You need open command prompt where adb exist and then use commands, for example
If you installed sdk in c:/android then you need to open command prompt and type
cd c:/android/platform-tools
Then start using adb commands like
adb push
adb pull
Sent from my HTC One X using xda premium
This incorporates the ideas of http://forum.xda-developers.com/showthread.php?t=2144709, so if you want to see how this was resolved for the Nexus 4, check out that thread.
Okay. So you've flashed a spanking new 4.2.2 ROM and ADB no longer talks to your Sensation. What happened?
Well, the fact is that 4.2.2 is significantly more secure, in the good sense. It enforces RSA authentication via ADB. However, RSA authentication is supported only in recent versions of ADB.
What to do?
First, make sure you have the latest version of ADB on your PC.
On Windows you can quickly find out if you your version of ADB is up to date. Check your ".android" folder and see if it holds a file called "adbkey".
On any platform type "adb version" to verify that you have the latest version of ADB. Versions 1.0.31+ support RSA authentication.
-- So now, if you have ADB 1.0.31 or higher. You can skip directly to step 2, then.
-- If you do not have ADB 1.0.31 or higher, and you have the full Android SDK installed, open the SDK manager and update it. If you only have ADB and fastboot installed in a folder on your PC, overwrite files in the folder with those in the corresponding zip file attached (windows or linux -- sorry! I don't have Mac versions at this time). These come from version 16.01 of the android platform-tools package, if you are curious.
-- if you have never installed the SDK or ADB or fastboot, now is the time to do that. I recommend going to http://developer.android.com/sdk/index.html to get started.
[*]Enable USB debugging on your phone
USB debugging is now enabled by selecting Android Debugging in System Settings > Developer Options.
"I don't have the Developer Options items in System Settings!!"
In Android 4.2.x, you need to go to System Settings > About Phone and tap the Build Number item about 6 or 8 times, and Developer Options will reappear.
[*]Plug in the USB cable. Securely.
Dismiss the USB mass storage window.
"I connected the cable, but nothing happened!!"
Okay, chill. You won't get a response until ADB tries to connect to your Sensation. So go ahead and start ADB on your PC. Suggested command:
Code:
adb devices
"Now ADB started, but nothing's happening on my computer!!!"
Uh, didn't I just advise you to chill ? Take a look at your phone...
"What's this pop-up that just popped up??"
(See image below)
Congratulations, that is Android asking your permission to store an RSA key on your Sensation for ADB interaction with your PC.
Fearlessly accept it.
Hint: check the "Always allow from this computer" box to save time later on.
The RSA authentication key you just accepted will be stored on your phone in the file /data/misc/adb/adb_keys.
You are now good to go. Just 3 easy steps with a minimum of panic.
Questions? Problems? Ask away!
Many thanks to XDA member skipjacks for the idea for this post
Hi,
Nice! :good:
People should also not use USB 3.0 slots or USB hubs.
Try several slots if the front ones do not work.
Windows 7 & 8 drivers are HERE in case anyone needs them...
malybru said:
People should also not use USB 3.0 slots or USB hubs.
Click to expand...
Click to collapse
I understand about the hubs, but why not USB 3.0?
Skipjacks said:
I understand about the hubs, but why not USB 3.0?
Click to expand...
Click to collapse
Hi,
I have read a lot of instances of "Device not recognized" when using 3.0 slots.
I am not saying it will never work.
But ,if you use one,and it does not work,then,try it on a 2.0 slot.
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
onemanshow85 said:
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
Click to expand...
Click to collapse
Hi,
I think there is one solution that will address both issues. Before I mention it, let me ask: are you sure you enabled USB debugging on your Sensation? This is confirmed if, when you plug in the cable to your PC, you immediately get a USB debugging icon in the Notification Bar.
Glad we got that out of the way!
Unplug your device from the PC.
Anyhow, since you already have the SDK installed, the recommended way to update is to use the SDK Manager.
--in Windows, I think this is an executable in the tools sub-folder of your main android SDK folder. Double clock on it.
--in Linux, start up a terminal and type
Code:
android
if that doesn't do it, CD to the /tools directory in android-sdk-linux, or wherever you put the SDK, first. Then type "android".
The window that opens when you start SDK Manager should show that you need an update to (at least) platform-tools. Go ahead and do the update. You will have to accept some license(s) - accept it or them.
Once the install is complete, close SDK Manager.
Now plug your USB cable back in, and try out the "adb devices" command. It should work.
Suppose you still get "device not found", though. Try the following: again unplug.
Type the command:
Code:
adb kill-server
Now plug the phone back in, verify that you have USB debugging, and try "adb devices".
If no go, let me know what platform you are running, etc. I've heard it could be the cable, but I think that you just need to make sure it is plugged in securely.
BTW, the reason you probably won't have to do the adb kill-server step is that the SDK Manager kills running adb processes during the install.
Let me know how it goes!
Yrs,
dkephart
Sent from my HTC Sensation using xda premium
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
onemanshow85 said:
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
Click to expand...
Click to collapse
Yeah... my random selection doesn't have this problem. But I once seemed to have it with the official cable. You might want to try rebooting both the phone and the PC.
Sent from my HTC Sensation using xda premium
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
onemanshow85 said:
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
Click to expand...
Click to collapse
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
dkephart said:
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Some really cheap cables only have 2 wires in them and can only be used for charging. You need the other wires for data transfer.
But some companies only put the charging wires in to save money on the copper.
It must be a REALLY low quality cable though. I mean I get all my cables on Monoprice for like $1-$2 and they all work great for data.
Or, the cable does have all the internal wires and one is just broken inside.
Sent from my HTC Sensation using xda app-developers app
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
nemovich said:
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
Click to expand...
Click to collapse
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
dkephart said:
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
no just the serial number
nemovich said:
no just the serial number
Click to expand...
Click to collapse
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
dkephart said:
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
with adb shell I get $ and with su I get #.
nemovich said:
with adb shell I get $ and with su I get #.
Click to expand...
Click to collapse
Cool! Then you have adb working. To confirm, in the shell, "ls" should come back with a listing of the files on your device. If you do "cd sdcard" and "ls" you get the files on the SD card.
You're good to go.
Sent from my HTC Sensation using xda premium
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Sent from my HTC Sensation using xda premium
nemovich said:
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Click to expand...
Click to collapse
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
dkephart said:
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
when I cd to the sdk folder ( C:\Users\Documents\adt-bundle-windows-x86-20130219), it gives me command not recognized. I can run sdk manager from the folder and everything is up to date.
I run adb from platform-tools and it gives me the same thing as before.
one thing though, I don't see the "adbkey" file in platform-tools but it is there in ".android" folder. so I run it from the later folder too but the still the same thing, no pop-up.
it's not just android commander, a lot of other apps give the same thing.
Title says it all... I'm trying to unlock my Nexus 5 boot loader, but I can't get USB debugging to work. Any ideas? I've tried two different computers
Sent from my Nexus 5 using XDA Premium 4 mobile app
thatguy97 said:
Title says it all... I'm trying to unlock my Nexus 5 boot loader, but I can't get USB debugging to work. Any ideas? I've tried two different computers
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There should be a prompt on your phone when you connect to a computer. If it doesn't show up, then try using the "Revoke usb authorisations" option and try again.
Accidental thanks. Enjoy.
thatguy97 said:
Title says it all... I'm trying to unlock my Nexus 5 boot loader, but I can't get USB debugging to work. Any ideas? I've tried two different computers
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Had the same issue. Solved it by enabling PTP in Settings - Storage - (menu button in the upper right) - USB-Connection.
After enabling PTP the Popup with RSA key appeared.
Hope I could help.
djcreature said:
Had the same issue. Solved it by enabling PTP in Settings - Storage - (menu button in the upper right) - USB-Connection.
After enabling PTP the Popup with RSA key appeared.
Hope I could help.
Click to expand...
Click to collapse
I did sort of the same. I disabled MTP and didn't enable MTP and that worked. You might need to do a fresh install of the drivers.
You won't get the pop-up by just plugging it in and toggling USB Debug, etc. You need to open up a program that uses ADB (Like WugFresh) or a command prompt in the adb/fastboot folder and typing -> adb devices (or fastboot devices if in fastboot mode). I just revoked computer permissions and tried ticking and unticking everything, and I couldn't get the auth pop-up. As soon as I started WugFresh, the pop-up appeared on the phone to authorize.
Still no popup
I tried everything in this topic and I still don't get popup RSA key.. working with nexus5 4.4.2 and windows8 and WugFresh toolkit
Any idea?
gcej said:
I tried everything in this topic and I still don't get popup RSA key.. working with nexus5 4.4.2 and windows8 and WugFresh toolkit
Any idea?
Click to expand...
Click to collapse
First of all, don't use toolkits... Please.
Make sure you have installed the correct drivers... Download Android sdk and make sure you have downloaded the usb_driver...
Go to developer options and revoke permissions, enable adb debugging... Now again connect your n5 to the PC and the a message should popup...
I had this problem because I was using an old version of adb
Sent from my Nexus 5 using Tapatalk
Try using different drivers
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
Use the third option in the driver installation window. Forgot what it was called but that was the only one that worked for me
Sent from my Nexus 5 using xda app-developers app
Universal Naked Drivers for Windows 8(8.1) - had the same issue myself. Was the only drivers I could get working on a Lenovo machine.
Help!!
I have tried everything with this, I reinstalled the usb google drivers countless times. I have redownloaded the SDK and have gotten no where, I even changed the connection to PTP. Someone please help!:crying:
Pure_Android said:
I have tried everything with this, I reinstalled the usb google drivers countless times. I have redownloaded the SDK and have gotten no where, I even changed the connection to PTP. Someone please help!:crying:
Click to expand...
Click to collapse
Do you get the yellow exclamation mark in device manager on the port not working? I had a device where no matter what I couldn't get the pc to recognize it. What worked for me was to go to update drivers, then right below the area where you can browes for drivers is an area where you can choose drivers from a list on your computer. Go there and look for the android adb interface driver
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
Do you get the yellow exclamation mark in device manager on the port not working? I had a device where no matter what I couldn't get the pc to recognize it. What worked for me was to go to update drivers, then right below the area where you can browes for drivers is an area where you can choose drivers from a list on your computer. Go there and look for the android adb interface driver
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No, It shows as
Android Device > Android Composite ADB Interface.
Pure_Android said:
No, It shows as
Android Device > Android Composite ADB Interface.
Click to expand...
Click to collapse
Your drivers are set up correctly then. Have you authorized adb debugging in developer options?
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
Your drivers are set up correctly then. Have you authorized adb debugging in developer options?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I have USB Debugging enabled, I have unknown sources enabled, I even tried revoking the permissions to try and get the RSA certification but no luck
Pure_Android said:
Yes, I have USB Debugging enabled, I have unknown sources enabled, I even tried revoking the permissions to try and get the RSA certification but no luck
Click to expand...
Click to collapse
Can you access the files on your phone from the pc? Are you on a custom Rom that may default to accepting the rsa?
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
Can you access the files on your phone from the pc? Are you on a custom Rom that may default to accepting the rsa?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I can access files, and no I am on stock, I'm attemting to root but this is whats blocking me from doing so
Pure_Android said:
Yes, I can access files, and no I am on stock, I'm attemting to root but this is whats blocking me from doing so
Click to expand...
Click to collapse
If you can copy files to the phone from the pc, just copy the super su zip to your phone. Then flash it in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
If you can copy files to the phone from the pc, just copy the super su zip to your phone. Then flash it in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The problem is, I have no root access, therefore it is till normal android. I need adb to root
Pure_Android said:
The problem is, I have no root access, therefore it is till normal android. I need adb to root
Click to expand...
Click to collapse
You don't need adb to root. Can you copy files to your phone? If so, copy supers.zip to /sdcard/download. Then get a twrp.img file and you'll flash that in fastboot.
See this http://forum.xda-developers.com/showthread.php?p=47025283
Sent from my Nexus 5 using XDA Free mobile app
Here is a way to install adb'fastboot on win8 or win8.1 for your htcm8 in less then 10 mins. only 1 Fully working m8 driver an 1 program needed to install an then your up an running adb/fastboot on win8.1 with nothing else to install no SDK no nothing
You simpley just launch program an start entrering adb an fastboot commands
DIRECTIONS
download the need files below
extract them [myself I did it to my desktop]
then to get driver to work always[no more waitng for device]
scroll to settings tab in bottom right screen
pick change pc settings an click update an recovery
next pick recovery
Then pick advanvced set up
REBOOT IS REQUIRED it should auto do this or prompt you do
then pick troubleshoot>Advance options>startup settings>click restart
once it reboots you need to disable driver signature enforcement by selecting number 7
Reboot once last time it will boot right to OS
Plug phone in>navigate to device manager I tested with a 2.0usb an stock cord
You should see your phone under other devices>click on it an select update driver software
pick find file yourself then navagte to file you extracted of driver>click ok an install driver.
Then simply install the minimal adb/fastboot program I would add desdktop icon
open program an type adb devices an yours will show up...[ if it shows offline check your phone for a prompt[it will be there if you get offline] check allow this pc an click ok
again type
adb devices an yours will show up an your good to go.
now you can reboot bootloader an try some fastboot commands
DOWNLOADS
download program from this thread
http://forum.xda-developers.com/showthread.php?p=53230508
driver
https://www.dropbox.com/s/toezcicvf9bm08v/drivers32_64bit.zip
CREDIT FOR MAKING THIS POSSIABLE
adb/fastboot program @shimp208
be sure to thank his thread for this
Reserved for later..
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Awesome can't wait to try them out
Sent from my HTC6500LVW using XDA Premium 4 mobile app
almania6 said:
Awesome can't wait to try them out
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It takes longer to read my OP then to actually do the process if you knew where to go already lol.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Link dead
Hello can you or anyone that still have that driver backup? Because the file no longer exist. Thanks