Related
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.
Im trying to unlock bootloader with the official way
however, i stucked at here,
"Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly."
I dont get any responses. Need help..
ItsNick said:
Im trying to unlock bootloader with the official way
however, i stucked at here,
"Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly."
I dont get any responses. Need help..
Click to expand...
Click to collapse
May be your adb n fastboot drivers aren't installed properly.. Read the official page of sony of unlocking the bootloader properly.. Its very clear:thumbup: and for help about installing drivers, google it or read stickies threads in neo forum..:thumbup:
Sent from my Xperia Neo V using xda premium
re install the adb driverss.. then it ll work
got the same error fr me when i first tried to unlock the bootloader
Sent from my MT11i using xda app-developers app
Cant unlock fastboot either. Actually cant install the fastboot driver, thats what the problem is. I tried a few different methods but its always the same.
Steps i taken:
Windows 8
Install JAVA and ANDROID SDK.
Updated to most recent usb drivers
Downloaded fastboot inf.
reloaded windows with the "install unsigned drivers" option enabled
And i always end up with an unrecognized device in the Devices menu.
Basically it wont "find" the driver, when i point to it.
---------- Post added at 10:11 AM ---------- Previous post was at 09:48 AM ----------
Finally i tried right clicking the driver and manually installing. After it warned me that it is not digitally signed, it installed. I went and tried to reupdate the unknown device i was getting instead of the fastboot device, chose to pick from the list and the Android Phone category was there.
Installed the device Android Bootloader Interface.
Went back to command prompt and run the "fastboot.exe -i 0x0fce getvar version", but im getting no response from the phone.
Any clues?
Any help please?
Any moderator reading the thread, willing to reply? Is it a known problem not being able to install the driver?
Is there a workaround?
BLiapis said:
Any moderator reading the thread, willing to reply? Is it a known problem not being able to install the driver?
Is there a workaround?
Click to expand...
Click to collapse
Follow these steps mentioned in this post and install adb driver.
http://talk.sonymobile.com/t5/Xperia-P/Cannot-properly-get-into-fastboot-mode/m-p/201211#M1495
AnDrOiDnEoV said:
Follow these steps mentioned in this post and install adb driver.
http://talk.sonymobile.com/t5/Xperia-P/Cannot-properly-get-into-fastboot-mode/m-p/201211#M1495
Click to expand...
Click to collapse
Thanx. Do you have a link for the package that works?
Guy graciously updated his link, but that driver still wont load. Manually updating the unknown S1boot - Fastboot device results to no go.. :crying:
[email protected]
BLiapis said:
Guy graciously updated his link, but that driver still wont load. Manually updating the unknown S1boot - Fastboot device results to no go.. :crying:
[email protected]
Click to expand...
Click to collapse
Did you switch off the phone and did you hold the menu key while plugging the phone to the computer? Could you please post the steps you are following?
AnDrOiDnEoV said:
Did you switch off the phone and did you hold the menu key while plugging the phone to the computer? Could you please post the steps you are following?
Click to expand...
Click to collapse
Sure,
Installed the JAVA/Android SDK and updated the drivers.
Turning off the device, pressing the menu button (rightmost button as facing the device) while plugging in the USB cable.
Device is found and registered in the System Manager but without drivers. S1 Boot Fastboot (or something).
Manually trying to install the drivers by pointing it to the directory of the Android usb drivers, to no avail.
Also tried installing different drivers like the ADB ones you adviced me to do, but same thing, windows searches the directory and subdirectories but cant find any compatible driver. Driver signature is turned off.
Also tried different USB ports, just to make sure im not using any USB3.0
Im using the Asus Maximus IV Gen3/Genz motherboard, on Windows8 Pro.
I hope we can get somewhere, its been months im trying to hack into the phone. Im really sick of how slow it performs
BLiapis said:
Sure,
Installed the JAVA/Android SDK and updated the drivers.
Turning off the device, pressing the menu button (rightmost button as facing the device) while plugging in the USB cable.
Device is found and registered in the System Manager but without drivers. S1 Boot Fastboot (or something).
Manually trying to install the drivers by pointing it to the directory of the Android usb drivers, to no avail.
Also tried installing different drivers like the ADB ones you adviced me to do, but same thing, windows searches the directory and subdirectories but cant find any compatible driver. Driver signature is turned off.
Also tried different USB ports, just to make sure im not using any USB3.0
Im using the Asus Maximus IV Gen3/Genz motherboard, on Windows8 Pro.
I hope we can get somewhere, its been months im trying to hack into the phone. Im really sick of how slow it performs
Click to expand...
Click to collapse
Ok. If you would like, I can help you personally on Team viewer or something. Please let me know when you are online.
AnDrOiDnEoV said:
Ok. If you would like, I can help you personally on Team viewer or something. Please let me know when you are online.
Click to expand...
Click to collapse
sure let me set the teamviewer.
would u like to contact me via skype?
vassilisfz1
AnDrOiDnEoV came and saved the day! Thank you friend!
The thing is, if windows arent able to "detect" the driver-set you are pointing at, then you need to "enforce" to use it:
1) Update Driver Software
2) Browse my computer for driver software
3) ****** LET ME PICK FROM A LIST OF DEVICE DRIVERS ON MY COMPUTER *****
use the ADB drivers for the NEO V and it should work.
I have a new S4 with baseband MK2. I am getting ready to do the root etc. but I was testing ADB first to make sure it works.
I have installed the latest USB drivers, and turned debug on in the S4
I get get adb to launch, but when I use the command "ADB devices" nothing shows up.
I have rebooted both PC and phone with the same results.
Question,
Does the phone need to be rooted before ADB will work? If so....then how to I side load "Towelroot"? or anything else for that matter.
am I missing some sdk files...or something else?
Thanks
wetwaterdog said:
I have a new S4 with baseband MK2. I am getting ready to do the root etc. but I was testing ADB first to make sure it works.
I have installed the latest USB drivers, and turned debug on in the S4
I get get adb to launch, but when I use the command "ADB devices" nothing shows up.
I have rebooted both PC and phone with the same results.
Question,
Does the phone need to be rooted before ADB will work? If so....then how to I side load "Towelroot"? or anything else for that matter.
am I missing some sdk files...or something else?
Thanks
Click to expand...
Click to collapse
Usually when nothing shows up at all it's a driver issue. What drivers did you install where did you get them. Windows right?
Edit : root not required.
jawmail said:
Usually when nothing shows up at all it's a driver issue. What drivers did you install where did you get them. Windows right?
Edit : root not required.
Click to expand...
Click to collapse
Got the drivers from samsung site...latest ver 1.5.45. phone connects to windows computer and displays directories so I know the USB driver is ok.
I did some more looking and am updating my sdk devices right now. I expect that to correct the problem.
wetwaterdog said:
Got the drivers from samsung site...latest ver 1.5.45. phone connects to windows computer and displays directories so I know the USB driver is ok.
I did some more looking and am updating my sdk devices right now. I expect that to correct the problem.
Click to expand...
Click to collapse
Drivers are good then, update your SDK like you said and try again. It should work after that, I don't have an S4 but they're all the same when it comes to ADB and fastboot. Good luck.
jawmail said:
Drivers are good then, update your SDK like you said and try again. It should work after that, I don't have an S4 but they're all the same when it comes to ADB and fastboot. Good luck.
Click to expand...
Click to collapse
Yup....sdk's installed and all is well.....
I sure wish I knew exactly which downloads to take from the SDK download manager....
I played it safe with the 4.3 and 4.4. I didn't know if the updates were progressive (included all past needed stuff) or just specific for the version.
I've been trying to get ABD working mainly so can downgrade my fire 5th gen from 5.1.3 to 5.1.2 but at all the tutorials i get stuck at the ABD. i made sure to download the android SDK for abd, i set the paths and open up command prompt ABD is still unknown command. so i figure try ubuntu and ofcourse that crashes saying "upgrade motherboard or use force" and havent seen any new mobo updates.
then ofcourse to top that all off every single tutorial that shows how to get ABD drivers working for the thing stop at the part after i install fire drivers and abd drivers. at a point it is still not done becuase now you have to go into device manager and do option where you can select "android phone" but what if you don't have "android phone" as an option? i thught that the android studio would add that but i guess not.
so what do you do when get at these problems? tutorials i fallowed are:
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
and ugh cant find other right now but as can see nothing on what to do if get at my road blocks, i have also needed ABD for other things and it used to work fine for apk transfers on older kfhd on another PC 7 but drivers for flashing rom abd mode and just NOT installing nomatter what i do tried for whole day and a half trying to figure out this nightmare.
is for only apks?
Nightmare-Rex420 said:
I've been trying to get ABD working mainly so can downgrade my fire 5th gen from 5.1.3 to 5.1.2 but at all the tutorials i get stuck at the ABD. i made sure to download the android SDK for abd, i set the paths and open up command prompt ABD is still unknown command. so i figure try ubuntu and ofcourse that crashes saying "upgrade motherboard or use force" and havent seen any new mobo updates.
then ofcourse to top that all off every single tutorial that shows how to get ABD drivers working for the thing stop at the part after i install fire drivers and abd drivers. at a point it is still not done becuase now you have to go into device manager and do option where you can select "android phone" but what if you don't have "android phone" as an option? i thught that the android studio would add that but i guess not.
so what do you do when get at these problems? tutorials i fallowed are:
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
and ugh cant find other right now but as can see nothing on what to do if get at my road blocks, i have also needed ABD for other things and it used to work fine for apk transfers on older kfhd on another PC 7 but drivers for flashing rom abd mode and just NOT installing nomatter what i do tried for whole day and a half trying to figure out this nightmare.
Click to expand...
Click to collapse
for a donwgrade there is a forum for kindle fire already why not try it?
http://forum.xda-developers.com/amazon-fire/help/downgrade-fire-os-5-1-4-to-5-1-2-t3388323
good luck:cyclops:
Note: For transfer apk you can upload to google drive or dropbox from your pc and download a install from the same apk on your device.
CharlexDe said:
for a donwgrade there is a forum for kindle fire already why not try it?
http://forum.xda-developers.com/amazon-fire/help/downgrade-fire-os-5-1-4-to-5-1-2-t3388323
good luck:cyclops:
Note: For transfer apk you can upload to google drive or dropbox from your pc and download a install from the same apk on your device.
Click to expand...
Click to collapse
uhh that pretty much says i have to load the firmware downgrade with ABD, and ABD is the problem idk how that helps?
Letme ask, did you install jdk and relate tools for adb like the one one will need for and android studio or some other developer tool? If not try to install it over Google you can find several related guidelines.
yea i got the ADB working on linux but not on windows still, also i can;t get the ABD drivers working because there is no "android phone" or "adb device" option in device manager which may have somethign to do with it.
well crap it just started working, but i still can't send adb commands because the drivers are not working due to not being able to continue tutorial over "device manager - select android phone or abd devices" step.
your problem sound like a driver problem but you can check the next forums:
http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9