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)
First off, Mark great program. I'e searched the tread and didn't find this question.
I have a Verizon S3 I535 4.1.1 and want to retrieve my pictures and data from the phone. Currently the screen broke so I can't unlock the phone password nor can I put the phone in USB debugging mode. Is there a way I can use this app to retrieve my data?
Thanks
Bump...Anyone?
AltecBX said:
Bump...Anyone?
Click to expand...
Click to collapse
Can't you just plug it into your USB port? I don't have mine in USB debug mode and I can just open an explorer window and navigate to the device.
Just_AGuy said:
Can't you just plug it into your USB port? I don't have mine in USB debug mode and I can just open an explorer window and navigate to the device.
Click to expand...
Click to collapse
I do have it plugged in to the USB port, I just can't access any files but the pre-loaded drivers that on it. I need to first unlock my phone to see the files in it.
I'm just trying to get important pictures off the phone.
Can someone help me out. These are my new born pics from the hospital.
Couldn't you grab the SDK tools, then use the command:
ADB pull \sdcard\DCIM
(or wherever your pictures are located, for me it's \0\SDcard\DCIM because I'm on 4.2)
Sent from my Nexus 4 using xda premium
every gavenel
I don't know how to do that. This is a screen shot I get when I open Samsung GS3 Toolkit.
Also is another screenshot of what happens when I plug the phone to the computer
AltecBX said:
First off, Mark great program. I'e searched the tread and didn't find this question.
I have a Verizon S3 I535 4.1.1 and want to retrieve my pictures and data from the phone. Currently the screen broke so I can't unlock the phone password nor can I put the phone in USB debugging mode. Is there a way I can use this app to retrieve my data?
Thanks
Click to expand...
Click to collapse
open back cover, take out sd card, plug in sd card reader, profit. its in dcim
dragon1357 said:
open back cover, take out sd card, plug in sd card reader, profit. its in dcim
Click to expand...
Click to collapse
it doesn't have a SD card. The baby pictures are in the internal memory.
bump!!
Can Anyone please help me out with this...
AltecBX said:
Can Anyone please help me out with this...
Click to expand...
Click to collapse
Dude. Learn how to use adb. Problem solved. You're not going to get a simpler or easier answer than that.
Sent from my SCH-I535 using xda app-developers app
Did you try to reinstall the USB drives?
I had an issue recently that when I plugged my S3 into my computer noting came up. Reinstalling the drives fixed it for me.
If you haven't already tried, you could installing Kies. You can get to your phones from that.
---------- Post added at 10:15 AM ---------- Previous post was at 10:01 AM ----------
thebeastglasser said:
Couldn't you grab the SDK tools, then use the command:
ADB pull \sdcard\DCIM
(or wherever your pictures are located, for me it's \0\SDcard\DCIM because I'm on 4.2)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
^^^ This
You only need to know a few linux commands id you don't know where your files are located.
adb help will give you a list of commands.
to test if your are able to connect, type adb devices
it will return you phone device number if attached properly.
Use adb shell
This will open a shell so you can cd to directories to find that files and path you need.
Then use as stated above adb pull <location> <remote>
Guys, I don't have my phone is USB debug mode. My phone was locked when the screen cracked. I've installed Samsung Kies for the Samsung drivers, I installed the Samsung drivers from their website, I've also installed the drivers from the phone when plugged in through USB, which is the only thing I see.
-Ajrty33 - I've tried using ADB, but it doesn't recognize a phone connected in the computer. Keeps coming up with nothing found. My understanding is that you need USB Debugging enabled to have it detect the phone, no?
-Just_AGuy - I've tried using the ADB Linux commands to detect the phone. it comes up with nothing. What else can I try?
--Thanks for the help people...I'm really appreciating it
AltecBX said:
-Just_AGuy - I've tried using the ADB Linux commands to detect the phone. it comes up with nothing. What else can I try?
Click to expand...
Click to collapse
When you type adb devices, does it just come back with "List of devices attached" then nothing under that?
If it doesn't list any devices, you have bigger problems.
Have you tried different USB port too? I've seen issues with USB3 port not working with odin and the Motorola equivalent RSD lite.
It still could be drivers. I had issue with mine a while ago. I tried reinstalling them and it appeared to install but didn't properly. I had to reboot the computer a couple times and reboot the phone.
As a last resort you might bring it to Verizon and see if they can get the files off for you.
It comes up with no device found. I tried another USB port and nothing. I've tried connecting my wife's phone and it works on all USB ports.
It did install new drivers when I connected her phone and it's the same model.
That's too bad. It sounds like you have hardware issues. Take it to the techs at the Verizon store, I don't think even they can screw it up more.
I just tried installing Kies on my work computer. After doing so, the computer didn't recognize my phone. I rebooted both the computer and the phone. The computer still didn't see the phone.
I shut off the phone and did a battery pull. Then restarted the phone and plugged in the USB cable. The computer recognized the phone and reinstalled the drivers.
Try it.
Just_AGuy said:
I just tried installing Kies on my work computer. After doing so, the computer didn't recognize my phone. I rebooted both the computer and the phone. The computer still didn't see the phone.
I shut off the phone and did a battery pull. Then restarted the phone and plugged in the USB cable. The computer recognized the phone and reinstalled the drivers.
Try it.
Click to expand...
Click to collapse
I tried that. I then installed in other computer running Windows 7 64bit, same issue.
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.
Wow the threads make it look so easy but here are my steps so far and I'm a couple hours into S-Off but had to go through all this stuff (The basics I guess but this is my first time on android 4.4 so I was pretty lost.
1) First I found the XDA Developer link here which has a QR code to scan to download the file.
2) Realized I did not have a QR Scanner installed so I installed google goggles.
3) Scanned the code and realized it did not work and simply takes me to the xda developers forum
4) Searched for another link and found this one http://dottech.org/156395/how-to-roo...verizon-guide/ (This QR code works)
5) downloaded and installed the weaksauce exploit.
6) Decided I will backup my data on the phone before continuing .
7) Installed titanium backup
8) Was told to enable USB debugging
9) Found this can only be enabled if your phone has development mode enabled.
10) Searched for how to do that on this newest version of android and found this link. http://www.pcadvisor.co.uk/how-to/go...formance-mode/ which I was able to figure out the exact steps for the M* on my own.
11) In the newly unlocked developer options from the enabled USB debugging.
12) Titanium backup reminded me I do not have the paid version (but I do own a licesnse!) Need to copy the license file to the SD card.
13) Realized I don't have an external SD card installed.
14) Searched the house for a paperclip to pop out the SD card slot, no dice... Found a needle and trimmed the head off it with wire cutters, and popped out the door.
15) Installed the SD card!
16) Titanium backup says it cannot write to the external SD card (Well this is where I like to keep my backups not on the internal Card....)
So Starting from 18 how do I:
1) Use titanium backup to backup to my external SD card (No write permission). I have tried the SDFix application and that did not work. How do i get write permission to backup with titanium backup?
2) Where do I download the HTC M8 Drivers?
Ok so I guess I cannot backup the phone, lets say I will just skip the backup.
I'm trying to S-Off using the weaksauce method. I go to the folder where I downloaded firewater and type adb reboot and I get a message that my device is unauthorized..
What now?
Did you look here ? http://forum.xda-developers.com/showthread.php?t=2708628
Works great.
You can just use internal storage for your backup, once you get the phone s offed . Then do a backup to the external sd card. You need root access and a kernel without write protection. Take your time, it'll work.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I would recommend watching some of these videos, they are very helpful.
http://forum.xda-developers.com/showthread.php?t=2697957
+1 on the videos well worth watching!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Did you get it figured out? If you didn't and still need some help, send me a PM and I'll walk you through step by step and help you get it done. I've walked three people through the S-OFF method now (using Teamviewer and chat) and am getting pretty efficient at it. Shoot me a PM if your still stuck.
Watch this...
https://www.youtube.com/watch?v=sLtmwN1UyUU
I'm having the exact same problem. I rooted the phone thinking that's all I'd need to do. But with TiBu I can't backup to my SD card. So now I'm trying to do the S-Off so I can solve that problem. But I can't get the adb to work either.
I installed the HTC Sync Manager "package" from HTC, which allegedly comes with the driver. But, when I plug the phone into the computer it doesn't even see an adb device for my phone. I'm familiar with adb devices because I used it on my Droid Bionic.
Then I downloaded what has been nicknamed the "HTC One Toolkit M8" and installed the "Universal Adb Driver" from that. Still, no adb device is detected. Frankly, I'm laughing and disgusted with this phone. I'm laughing because someone with my prior skills with android should have no problem with this. But disgusted because this phone has been the most counter-intuitive phone I've ever owned. Just trying to disable the lock screen took almost 30 minutes.
Anyone know what I'm doing wrong? When I plug the phone in right now it shows up under "Portable Devices" and that's it. My Bionic would pop up 3 devices(CD-ROM, media device or something of that sort and the adb device).
I've literally spent the last hour searching with Google trying to figure out what I'm doing wrong. I thought it was a driver problem, but now that I'm not seeing any "unknown" devices nor am I seeing the adb device I'm convinced I've screwed this up somehow.
Yay me. I can't find my old account info, so 1 post for me.
Edit: Also, after installing the "Minimal ADB and Fastboot" as well as the Android SDK, the command "adb devices" has never found my phone. LOL
Just an FYI...the tool to open the SD card slot comes with the phone. It's the metal piece with the HTC logo in the packaging that the manuals come in. You'll have to pull that part of the box apart to get it out.
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Pauls57 said:
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Also, if you have any other type of phone software such as pdanet installed on your computer, either uninstall it or close it before trying to run the exploit.
Pauls57 said:
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Click to expand...
Click to collapse
Yeah, I did that already. I'm convinced this isn't a driver issue since I never actually see the adb device(or an unknown device) in my device manager.
robocuff said:
Also, if you have any other type of phone software such as pdanet installed on your computer, either uninstall it or close it before trying to run the exploit.
Click to expand...
Click to collapse
I don't. I haven't gotten that far since I haven't gotten s-off done.
Are you using a USB 2.0 port on your computer. USB 3.0 will cause problems with ADB. What operating system does your computer have on it? Windows 8 doesn't seem to get along well with ADB either. Seems to work for some, and not for others.
Joshy8 said:
Yeah, I did that already. I'm convinced this isn't a driver issue since I never actually see the adb device(or an unknown device) in my device manager.
I don't. I haven't gotten that far since I haven't gotten s-off done.
Click to expand...
Click to collapse
That just seems to me that it IS more likely a driver issue. You should see your device name or at least unknown device. Open up your device manager, then unplug your phone and replug it in. See what it shows when it refreshes. It will be under portable devices or Android USB devices or both. Mine shows both. If you still need help shoot me a PM and I can walk you through.
robocuff said:
Are you using a USB 2.0 port on your computer. USB 3.0 will cause problems with ADB. What operating system does your computer have on it? Windows 8 doesn't seem to get along well with ADB either. Seems to work for some, and not for others.
Click to expand...
Click to collapse
Windows 8 doesn't have any problems with adb. I've used it flawlessly on several computers. USB 3.0 neither. USB 3.0 can however cause problems with Firewater running correctly.
nicholi2789 said:
That just seems to me that it IS more likely a driver issue. You should see your device name or at least unknown device. Open up your device manager, then unplug your phone and replug it in. See what it shows when it refreshes. It will be under portable devices or Android USB devices or both. Mine shows both. If you still need help shoot me a PM and I can walk you through.
Click to expand...
Click to collapse
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Joshy8 said:
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Click to expand...
Click to collapse
I don't know, I have had lots of driver issues on lots of devices and had to sort it out many times. Most notably was my Nexus 7 that thing was the hardest device to get drivers installed for, it took me hours. I've gotten pretty dang efficient at installing drivers nowadays though. I need more specific information about your set-up before I can really offer good advice though. The HTC Media Cd rom that you see pop up when you plug in is the CDROM.iso. It's just stupid HTC bloatware crap, you can disable it or delete it once you have root. When you plug it in you should see the CDROM popup on your desktop then it should mount as MTP too. You should be able to browse your internal and external storage.
One thing I would suggest though and you may think i'm crazy for it.. Swap the USB cable your using for a different one and try that on a different usb port. I've messed around trying to get drivers installed for hours, only to switch the USB cord and have it work just fine. I've even had this problem with brand new USB cords.
If you do still need help tomorrow don't hesitate to shoot me a PM, I would be glad to help.
Joshy8 said:
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Click to expand...
Click to collapse
I don't know if this will help but I see you typing in adb device, it must be adb devices you must have the s.
Don't ask me how I know.
hager03 said:
I don't know if this will help but I see you typing in adb device, it must be adb devices you must have the s.
Don't ask me how I know.
Click to expand...
Click to collapse
Haha. I wont' ask. Thanks for the tip, but I am doing adb devices. It comes back and says something like "List of devices found" or something and then is blank. Of course, it works just fine on my Bionic.. haha. It's always listed.
This is going to be a silly question, but did you turn on USB Debugging in the developer options? Does the phone say USB debugging connected on the phone's notification tray?
You should either have unknown device or you should see it listed properly in device manager.
I would go through device manager and uninstall any devices related to the phone. When prompted I would also remove the drivers. Then follow the below guide.
http://forum.xda-developers.com/showthread.php?t=2742295
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.