Related
ok i know i have most things set up right but for some reason my phone isnt being recognized for adb use. i just updated my sdk and adb runs in command prompt as it should but my phone still isnt recognized, and yes i do have it in debugging mode. ive searched already to find nothing. im currently running franken-twiz (which is awesome by the way) my phone previously would work with adb when it was stock but now nothing happens and i have no clue whats going on. droid explorer never finds it and neither does the computer, but putting it into mass storage mode seems to work fine... nothing i do seems to work any ideas or solutions would be amazingly helpful. thanks in advance
I am having the same issue. Any help??
Are you sure that you have the correct drivers installed? (check TGA_Gunnman's thread)
Sent from my SGH-T959 using XDA App
Oniyuri said:
Are you sure that you have the correct drivers installed? (check TGA_Gunnman's thread)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah I'm sure like I said before it worked but now that I'm not stock Rom it doesn't seem to work I used the Samsung drivers.exe for 64 bit machines and it worked but after leaving stock Rom it seemed to quit on me Idk what the deal is
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Toggle debugging on then off.
I am in the same boat as you. A suggestion was posted in my thread in the Q&A section that PDANet solves the issue as it installs the drivers for you but it didn't work for me. Any dev's know a solution to this issue.
"fastboot devices" should work.
orangechoochoo said:
"fastboot devices" should work.
Click to expand...
Click to collapse
mine does it gives me the serial number and fastboot
but neither of our adb devices work.
I did the USB Debugging toggle multiple times and and it won't work. I saw your thread termin8tor22 and I am in the process of trying the pdanet solution. I'll post back if it works for me.
orangechoochoo said:
"fastboot devices" should work.
Click to expand...
Click to collapse
When you say that it should work, are you referring to the fact that we can run the exploit and unlock the phone even though it doesn't show in adb devices? I haven't been able to get mine to work that way. Thanks.
The pdanet didn't work either same error as previously stated. Mine doesn't even show up in fastboot devices. I am at a total loss here. I tried to override the drivers and it fails and states that the MTP USB Drivers are the most up to date and refuses to change or update it.
antnyh said:
When you say that it should work, are you referring to the fact that we can run the exploit and unlock the phone even though it doesn't show in adb devices? I haven't been able to get mine to work that way. Thanks.
Click to expand...
Click to collapse
No, the exploit will not work if your phone does not show up in adb.
Also, this thread should be in Q&A, not in Development.
antnyh said:
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Click to expand...
Click to collapse
I was able to get it to see the device after going into cwr. then i was all good
jsa11ey001 said:
I was able to get it to see the device after going into cwr. then i was all good
Click to expand...
Click to collapse
How can we get cwr whithout an unlocked bootloader or root. This isn't helpful unless we have cwr already on there which we don't as we don't have root because we don't have adb to push the exploit. I don't mean to be rude but I am getting aggravated with this ADB thing.
CastleBravo said:
No, the exploit will not work if your phone does not show up in adb.
Also, this thread should be in Q&A, not in Development.
Click to expand...
Click to collapse
The thread is where it is unless a mod wants to move it.
jsa11ey001 said:
I was able to get it to see the device after going into cwr. then i was all good
Click to expand...
Click to collapse
I am trying to unlock it so I can get CWR on it. I can't even unlock it since it refuses to show up in ADB. How did you get CWR on yours if you don't mind me asking?
antnyh said:
The thread is where it is unless a mod wants to move it.
I am trying to unlock it so I can get CWR on it. I can't even unlock it since it refuses to show up in ADB. How did you get CWR on yours if you don't mind me asking?
Click to expand...
Click to collapse
I pushed thru adb. did you uninstall htc sync and update your android sdk. sorry just trying to give any usefull info. not in any way a master dev or anything
---------- Post added at 06:43 AM ---------- Previous post was at 06:35 AM ----------
i used this method http://forum.xda-developers.com/showthread.php?t=1996389, and had to do the CIDGEN unlock because I have a verizon phone. I followed the steps exactly and had 0 problems.
see you pushed through adb, which we cant get to recognize our devices. thats all, no harm intended.
antnyh said:
The pdanet didn't work either same error as previously stated. Mine doesn't even show up in fastboot devices. I am at a total loss here. I tried to override the drivers and it fails and states that the MTP USB Drivers are the most up to date and refuses to change or update it.
Click to expand...
Click to collapse
did you change your environment variable path set to your adb/fastboot location?
As for the drivers:
HTCDriver.RAR > run the exe
HTCDriver.rar
HTC.RAR > put in C:\Program Files\ and C:\Program Files (x86)
HTC.rar
thats my setup and it worked
antnyh said:
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
I had similar issues with ADB not recognizing the DNA, I disabled HTC sync and closed out of the HTC SYNC in the task manager... You may or may not have tried this... Based on my experience this was what happened with me.. I also have windows 8 64bit. Hope this helps
:fingers-crossed:
I installed drivers listed on one of the forums here. then i installed htc sync. Then i had to download the sdk /with google drivers.
I would assume that when you have your command prompt open that you cd into the folder. platform-tools. that way the cmd can find adb?
kraziekc said:
Hello,
I had similar issues with ADB not recognizing the DNA, I disabled HTC sync and closed out of the HTC SYNC in the task manager... You may or may not have tried this... Based on my experience this was what happened with me.. I also have windows 8 64bit. Hope this helps
:fingers-crossed:
Click to expand...
Click to collapse
Hmm.. I haven't started mine yet but I'm on win8, this seems like good advice. Will be trying later and post results
Sent from my HTC6435LVW using Tapatalk 2
damagickid said:
I installed drivers listed on one of the forums here. then i installed htc sync. Then i had to download the sdk /with google drivers.
I would assume that when you have your command prompt open that you cd into the folder. platform-tools. that way the cmd can find adb?
Click to expand...
Click to collapse
If you set up adb right you don't have to CD into that folder.
Sent from my HTC6435LVW using xda app-developers app
You need to disable HTC Sync. Go in task manager and see if there is another ADB current running. That is what happened to me, HTC Sync was trying to push via ADB so when I tried to root it couldn't recognize my DNA.
ive tried every method to unlocking the bootloader and i cant get the command prompt to do anything it wont reconize my device is their an easier way into unlocking and rooting
If you can't get adb working then you shpuldnt have a rooted phone in the first place.
Sent from my HTC6435LVW using xda app-developers app
Sounds like you don't have all the drivers installed and/or don't have sdk tools installed.
And no, there is no other way to unlock it.
orangechoochoo said:
Sounds like you don't have all the drivers installed and/or don't have sdk tools installed.
And no, there is no other way to unlock it.
Click to expand...
Click to collapse
Download the latest SDK (search for 'adt- bundle -windowsx86') and extract that file into your C drive.
There will now be an 'adt-bundle-windowsx86' folder on your C drive, inside that is the SDK manager.exe
Run SDK manager-it will create the adb tools you will need AND put them in the "sdk/platform-tools folder"
after the SDK tool opens, you only need to add the 'google usb drivers' (1 item) No need to select that box
as is checked off by default anyway. All other required adb files will have installed already. Install those google drivers
and you should be ready to unlock the bootloader. I would put all the OTHER required files to unlock it in the 'platform-tools folder also.
Then go to that platform-tools folder, hold down shift key and right click in an open area, choose 'open command prompt here' then just follow the tutorial pasting in the commands.it will work...
Jduncan312 said:
ive tried every method to unlocking the bootloader and i cant get the command prompt to do anything it wont reconize my device is their an easier way into unlocking and rooting
Click to expand...
Click to collapse
This work perfectly for me http://forum.xda-developers.com/showthread.php?p=34582289
https://www.youtube.com/watch?v=glGdw2HAumg&feature=youtube_gdata_player
I followed this video to get sdk installed
Thats the same vid that i used too and it work just fine for me, did you also changed your local variable like the vid, also on your phone make sure you have usb debugging enabled
Gungrave223 said:
Thats the same vid that i used too and it work just fine for me, did you also changed your local variable like the vid, also on your phone make sure you have usb debugging enabled
Click to expand...
Click to collapse
I'm not the one with the problem, I'm already unlocked, rooted, and rommed
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
I had a issue with the drivers installing from my phone to my pc. I installed pdanet 3.5 (Google it for pc, play store for phone) on my pc and phone. Let pdanet install the drivers, once installed you can uninstall pdanet.
Once the drivers installed I was able to see my device in adb. Sorry if one of the links above were for this fix I didn't click them.
HTC DROID DNA
orangechoochoo said:
I'm not the one with the problem, I'm already unlocked, rooted, and rommed
Click to expand...
Click to collapse
Lol yea i know i was just saying that that method work for me too.
Jduncan312 said:
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
Click to expand...
Click to collapse
Well if you type the command adb device and nothing and your device doesnt show, there is 2 possible reason for the issue the first is that your phone is not in adb mode, go to the setting/developer options and make sure usb debugging is enabled
the second is that your phone adb driver weren't installed correctly i had the issue when i watch this video because when i was in sdk manger i unchecked the option to install the android 4.2 (API17) package, disconnect/reconnect phone and the adb driver install just fine after that
Sadly there is no other way to remove the verizon cid block as of right now
Jduncan312 said:
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
Click to expand...
Click to collapse
If you have sdk installed right then adb will be working...then if you follow the tutorial in the dev section (jcase) it will work. I have heard that some older versions of adb didn't support restore and that WAS an issue for me so I re installed the latest version of SDK and it then worked flawlessly. That's why I suggested getting the latest version and reinstalling. Maybe not the problem but you have had no luck with your old version so why not. You need to go slowly and read carefully. The process is really 3 sections, bootloader fix, official HTC website unlock code process and then rooting itself. It takes a while but it's how everyone got there, some easier than others.
My phone is LG Prada P940.
The problem is when I connect the phone to usb debug mode, status bar show slow charging, usb debug start completely.
But, when I try to root it in cmd, it sticks at daemon running. When I try "adb devices" command, it says "xxxxxxxxxxxxxxxxxxxxxxx offline".
Now I can't root my phone.
Anyone have had experience for this solution? Please help. Thanks in advance.
Just try the below command and post your findings..
adb kill-server
adb start-server
And make sure usb debugging is checked
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
And make sure usb debugging is checked
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
All was done, but it still didn't work. Devices still offline.
amith007 said:
Just try the below command and post your findings..
adb kill-server
adb start-server
Click to expand...
Click to collapse
All was done, but it still didn't work. Devices still offline.
Have you tried with another PC?? If not have a try..
Are you sure drivers are installed and that your pc recognizes it?
Sent from my GT-N7000 using xda app-developers app
Thank
Thatgrass said:
Are you sure drivers are installed and that your pc recognizes it?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thank you for all your help. I've tried all of those solutions: tried on the other computers, the phone could be recognized and I could even upgrade the firmware, and stuff. Unfortunately, couldn't be rooted because the devices offline issue.
Any other ways? Please!
nhthanh05 said:
Thank you for all your help. I've tried all of those solutions: tried on the other computers, the phone could be recognized and I could even upgrade the firmware, and stuff. Unfortunately, couldn't be rooted because the devices offline issue.
Any other ways? Please!
Click to expand...
Click to collapse
Are you using the latest version of ADB?
aidfarh said:
Are you using the latest version of ADB?
Click to expand...
Click to collapse
Absolutely. The main issue is that I couldn't run any root methods to root the phone, because of the ADB devices offline.
nhthanh05 said:
Absolutely. The main issue is that I couldn't run any root methods to root the phone, because of the ADB devices offline.
Click to expand...
Click to collapse
Were all the computers you tested on running Windows? How about trying running ADB on a Linux PC and see if it works?
Another thing, maybe you can try installing this driver on Windows just in case it's a driver issue:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
The above is a Universal ADB Driver for Windows newly developed by Koushik Dutta.
Need help. ADB devices offline.
aidfarh said:
Were all the computers you tested on running Windows? How about trying running ADB on a Linux PC and see if it works?
Another thing, maybe you can try installing this driver on Windows just in case it's a driver issue:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
The above is a Universal ADB Driver for Windows newly developed by Koushik Dutta.
Click to expand...
Click to collapse
Thanks a lot. I wish it could work, but it did not.
By the way, my phone used to be rooted before. One day, I did something wrong with the 'bootloader' file in the system folder, then the phone could not restart. I had to do some things such as: downgrade, upgrade the firmware, and stuff. Everything seems ok then. Just the phone could not be rooted any longer.
Have any ideas? I will try whatever. Please!
I have same problem. plz help
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Did you try closing HTC Sync Manager?
Make sure and exit completely, right click and exit in the system tray
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
TheEmpyre said:
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
Click to expand...
Click to collapse
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
jonathan413 said:
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
Click to expand...
Click to collapse
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
an0ther said:
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
Click to expand...
Click to collapse
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
TheEmpyre said:
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
Click to expand...
Click to collapse
there is no other drivers showing up other than HTC's. and ive reinstalled it at least three times. everything is working except ADB recognizing the phone.
jonathan413 said:
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
Click to expand...
Click to collapse
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
an0ther said:
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Click to expand...
Click to collapse
thats already checked. just unistalled all duplicate drivers and started fresh. now there is 3 drivers not installing. CDC serial, Android phone, and CDC serial again. not sure why that one installs twice but it failed anyway..those 3 will not install for the life of me.
TheEmpyre said:
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
Click to expand...
Click to collapse
in the toolkit it says "device not found"..when i run ADB devices it says "list of devices" but shows nothing. Now when i run the command it says in missing some .DLL extension file
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
TheEmpyre said:
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
Click to expand...
Click to collapse
ok i followed your instructions and yes all the drivers installed correctly, thank you. BUT now i run the toolkit and now it says "error: device offline".
an0ther said:
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
Click to expand...
Click to collapse
not sure. i dont keep ADB on my computer. I download it only when I need to. But i followed the instructions from the other user but now i get this message. "error: device offline".
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
TheEmpyre said:
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
Click to expand...
Click to collapse
ok so i ran the toolkit for the 3rd or 4th time and it rebooted in fastboot to obtain my token to unlock. but when i enter the token into htcdev website it keeps saying its wrong length. i checked over and over and its the right length and im copying what i see from the htc dev website instructions but three times i get wrong token length.
ok i got the code to work..now onto the next step.if i have problems ill be back here.