Related
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
oceanisbleu said:
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
Click to expand...
Click to collapse
Double check your path...
"Now type cd\AndroidSDK\tools\"
My path is c:\android-sdk-windows\tools\
I've renamed the file to AndroidSDK & placed it directly in C:/ so for me it's C:/ AndroidSDK/tools/
doesn't work...
-I plug the phone in and it's recognized as "Android ADB Interface" in device manager
-I open easy tether on the phone then right click on the pc & click connect then it says connection established via Android ADB.....
-I open CMD
-I type cd\
-then cd\AndroidSDK\tools\
-then adb devices & this is where I want to break everything because I can never get past this part and all I see is 'adb' is not recognized as an internal or external command.......
I hate this phone lol & wish I had the money to get the evo so I can put this thing in the trash, I just want to setup firerat's and that's the main reason why I want to establish ADB, is there any way it can be done without ADB????
thanks for trying to help, I hope someone can still figure this out for me
If you downloaded the newest SDK, then the problem might be that you are looking for adb in the wrong directory. It is no longer located in \tools. It was moved to the \platform-tools directory
Sent from my HERO CDMA using xda premium
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
I have just added this exact directory to the end of my PATH
;C:\AndroidSDK\platform-tools\
rebooted, opened cmd, typed adb devices and still I get ADB is not a recognized command.
I went to HTC's site & downloaded the latest hero sync software (new version just came out 2 days ago) when I plugged my phone in it re-installed the drivers, tried it again and nothing!!
I did notice that after the HTC Sync installation in device manager the phone is no longer Android ADB Device, now it says MY HTC, did Sync ruin my ADB drivers?
Ok. So were you at with this???
Shoot me a pm if you still need assistance.
Edit: From reading your post I think your not changing the directory first.
So open up the cmd window. And type cd\ "then hit enter"
Thenn type.
cd\AndroidSDK\platform-tools\
And hit enter.
Then type. "adb devices" without the quotes. And see if that will show your serial number.
If that yeilds no results then try
cd\android\SDK\tools\
And hit enter.
Then type "adb devices" without the quotes. And hit enter and see if that will return your serial number.
Locked & Loaded
" Shooter on Deck"
Thanks guys for all the help you have provided, I have finally figured it out using this guide;
http://forum.xda-developers.com/showthread.php?t=532719
slightly different than the first guide I followed, instead of editing the PATH a new Environment Variable was created also a slightly different CMD code to get to ADB;
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
I hope this helps anyone else who might have the same issue.
Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....
xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this
Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message
ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)
nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think
Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key
Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed
KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.
http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app
Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:
mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood
Hello,
My nexus 6 was rooted and with TWRP. However, while trying to update to 5.0.2 using this ROM (http://forum.xda-developers.com/nexus-6/development/rom-pure-shamu-beta-2-0-t2952604), I ended up with no OS on it. I can boot into TWRP just fine.
So I am trying to sideload the ROM and rest of the files, however, my Win 8.1 shows "device not found". The command "adb devices" show no devices as well.
Win 8.1 device manager shows the phone as "Google Nexus ADB Interface" with driver ClockworkMod 8/27/12 7.0.0.4.
Any ideas?
Reinstalling and selecting from list did the trick, the device is listed as "Android Composite ADB Interface".
However, I must be missing something too obvious that I just cannot see...
I go into TWRP
go into advanced
go into ADB sideload and enable it
on PC, "adb device" will list it "recovery"
on PC, "adb sideload filename.zip" give me "error: Protocol fault (no status)"
then found out I had to stop the process "adb", which I do now.
Now when sideloading the zip I get "error: closed"
Ok, who knows why it was not working, but ended up doing a push instead, then I just installed via TWRP the ROM, gapps and SU.
Command I used: adb push rom.zip /data/media/rom.zip
this thread sounds like what I do when my mom has a question about something. Leave her alone for awhile and she finds the answer her self.
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
ioakimakos93 said:
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
Click to expand...
Click to collapse
Danny201281 said:
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
Click to expand...
Click to collapse
Ok I read your post again and think I misunderstood your problem. Your drivers are working as adb see's the device so what exactly is the problem? The sideload does not complete?
You should uninstall HTC Sync for starters it will do you no favours while using adb/fastboot commands it has the potential to cause hangs. if
Code:
adb sideload name-of-zip
is not working for you.
Try adb push instead with the one on the TWRP home screen (Not in Sideload mode)
Code:
adb push name-of-zip.zip /sdcard
The command window will appear unresponsive until the push completes. (several minutes) When it's done select Install from the TWRP menu and select the rom zip file.
If you still get problems copy and paste the error from your command window here :good:
Or flash TWRP 2.8.5.0 it has the ability to use MTP in recovery so you can see your phones Internal Storage while in recovery and just drag and drop the rom to your phone :good:
Hello guys,
I hope you can help me.
I wanted to delete all my private files on the sdcard and accidentlty deleted "system" in TWRP...
Now I cannot access my phone anymore
ADB devices is showing me an empty list.
Only on fastboot and when entering sideload through TWRP my HTC One is listed.
Unfortunately when I try "adb sideload rom.zip" I get "* cannot read 'sideload' *"
When I try "adb push rom.zip /sdcard/" in sideload mode, I get "error: closed"
Does anybody have an idea how to get my HTC One working again?
Thank you very much in advance!
Greets kally
kally said:
ADB devices is showing me an empty list.
Only on fastboot and when entering sideload through TWRP my HTC One is listed.
Click to expand...
Click to collapse
Its completely normal, ADB only works in custom recovery or in a booted rom with "usb debug" turned on, ADB doesn't work in bootloader, only fastboot will work in bootloader.
Unfortunately when I try "adb sideload rom.zip" I get "* cannot read 'sideload' *"
Click to expand...
Click to collapse
What is your adb version? You can find the version using the command "adb version"
What is your twrp version?
What rom are you trying to push?
When I try "adb push rom.zip /sdcard/" in sideload mode, I get "error: closed"
Click to expand...
Click to collapse
You can't adb push in sideload mode, sideload mode is only for.... sideloading...
To use adb push, just boot in twrp main menu with sideload turned off.
Does anybody have an idea how to get my HTC One working again?
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" remove imei and serialno.
Hello alray,
thank you for your reply!
My adb version is "Android Debug Bridge version 1.0.31"
TWRP Version: 2.6.3.4
I'm trying to push ARHD 92.0.
Luckily, while typing my answer, I was somehow able to push the rom with adb in the recovery.
Now everything works like a charm.
Thank you very much for your help!
Greets kally