Related
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
My phone recently lost its ROM, and is now stuck on the 'HTC quietly beautiful screen', i did manage to get it into clock work mode recovery and have a backup of my old rom on a usb, however, when i plug in the USB before starting the phone it doesn't show up, meaning i cannot restore. Please help! Any help or feedback is much appreciated! :good:
When you're in recovery, you have to use the command:
Code:
adb devices
for see your phone.
After use adb command like push or sideload for put a rom into the phone
Guich said:
When you're in recovery, you have to use the command:
Code:
adb devices
for see your phone.
After use adb command like push or sideload for put a rom into the phone
Click to expand...
Click to collapse
Thanks, but how would i do that on a mac?
That's why I have parallels!
I had this problem the other day and I fixed it by going to data/media in recovery and installing an old Rom that was downloaded. I could then restore afterwards.
Sent from the one and only HTC One
Shadow Samurai said:
That's why I have parallels!
I had this problem the other day and I fixed it by going to data/media in recovery and installing an old Rom that was downloaded. I could then restore afterwards.
Sent from the one and only HTC One
Click to expand...
Click to collapse
Yes, but i cannot copy anything to my device, and when i attempt to use adb, it says "error: device not found"
Check the thread in my signature
Sent from my HTC One using xda app-developers app
MacHackz said:
Check the thread in my signature
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i have tried following your help, but when i type ./adb devices it says
"adb server is out of date. killing...
* daemon started successfully *
List of devices attached
"
it doesn't show the serial code
g4slyness said:
i have tried following your help, but when i type ./adb devices it says
"adb server is out of date. killing...
* daemon started successfully *
List of devices attached
"
it doesn't show the serial code
Click to expand...
Click to collapse
Is it turned on booted into Android, or in recovery?
MacHackz said:
Is it turned on booted into Android, or in recovery?
Click to expand...
Click to collapse
Yes
You have the latest adb binaries installed??
Sent from One with Tapa4 Beta
Guich said:
You have the latest adb binaries installed??
Sent from One with Tapa4 Beta
Click to expand...
Click to collapse
I am not sure what a binary is (HTC One is my first android phone so I'm new) but if it is the recovery mode, i only installed it about a week ago
Do you have the folder containing the adb and fastboot files on your Desktop? And do you have HTC Sync installed? It will load the proper drivers, even though I heard it may not be necessary anyway.
This method worked for me on my Mac. It is very simple using Terminal.
You don't actually have to download the whole SDK, just download the file attached in the threat, which is this http://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941
Place it on your Desktop, and follow the instructions. After ADB successfully lists your device, move the ROM file to your android folder and use the following command: adb sideload rom.zip of course replacing 'rom.zip' with whatever your rom's name is. You can also use adb push if you want to move your Nandroid backup to your device, but I am not sure where it will be located on the device itself afterwards.
Oh and you should be in TWRP > Advanced > ADB Sideload mode if you want to sideload the ROM. I am not sure how it works on CWM but it should be the same way.
TarekElsakka said:
Do you have the folder containing the adb and fastboot files on your Desktop? And do you have HTC Sync installed? It will load the proper drivers, even though I heard it may not be necessary anyway.
This method worked for me on my Mac. It is very simple using Terminal.
You don't actually have to download the whole SDK, just download the file attached in the threat, which is this http://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941
Place it on your Desktop, and follow the instructions. After ADB successfully lists your device, move the ROM file to your android folder and use the following command: adb sideload rom.zip of course replacing 'rom.zip' with whatever your rom's name is. You can also use adb push if you want to move your Nandroid backup to your device, but I am not sure where it will be located on the device itself afterwards.
Oh and you should be in TWRP > Advanced > ADB Sideload mode if you want to sideload the ROM. I am not sure how it works on CWM but it should be the same way.
Click to expand...
Click to collapse
Thanks, i have tried this method already and am in Clockworkmod recovery, i don't have TWRP
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
adb sideload
b0gd4n said:
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
Click to expand...
Click to collapse
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
rpmccormick said:
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
Click to expand...
Click to collapse
clsA said:
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
Click to expand...
Click to collapse
BenPope said:
adb sideload
Click to expand...
Click to collapse
thank you all!!!
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
b0gd4n said:
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
Click to expand...
Click to collapse
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
b0gd4n said:
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
Click to expand...
Click to collapse
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
b0gd4n said:
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
Click to expand...
Click to collapse
yup.
BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
Same Problem here. No Solution?
b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
BlockABoots said:
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
Click to expand...
Click to collapse
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
b0gd4n said:
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
Click to expand...
Click to collapse
Hmmm, maybe try uninstalling all HTC drivers on the PC and then reinstalling.....
HTCDriver_4.2.0.001.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi (or x86 version if on win 32)
SyncManager_2.0.61.0.exe
found here, http://forum.xda-developers.com/showthread.php?t=2217396
http://www.mediafire.com/?o10b16j5b3r3o
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
I deleted os
Hello brother pls help me . I am sorry but i deleted is of htc one. Now can't anything . Here is the details
Twrp - yes
Hboot- unlocked tampered.
S-off
T-mobile htc one 4.4.2
Please help me . Here I saw many many expert so brother pls help me how to solve it & I can use my htc one .
Pls brother........
If someone can mail me in [email protected]
The details what to do. As I am really new & don't know what to do.
So again brother pls help.
windieboss said:
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
Click to expand...
Click to collapse
Whooo this worked!! Finally!!!
So I uninstalled all HTC stuff I had installed (drivers, sync manager, everything), then installed the stuff in the link.
Plugged in the HTC One in sideload mode and did
Code:
adb sideload filename.zip
and it worked!! Thanks again mate!
My device is Moto X (XT1060). I wiped my Internal storage, Cache, Data, System entirely.
I went to my TWRP v2.6.3.1 recovery and tried to sideload cm12.zip via adb.exe but it failed to recognize the device.
I tried
Code:
adb sideload cmfile.zip
but it show's
Code:
error: device not found
I installed Motorola Device manager.. but no luck so far.
I think I need drivers or something for XT1060.. Please help me.
You should search for twrp 2.8.4.0 for Moto X 2013. Also, make sure you have the latest android SDK and ADB files installed. You'll need to search for threads that help get your phone connected to a pc.
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
nhizzat said:
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
Click to expand...
Click to collapse
or you can boot your phone into bootloader if you can and flash the device back to stock and start over.
nhizzat said:
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
Click to expand...
Click to collapse
That is basically all the sideload command does isn't it? I seemed to notice when I side loaded I was left with the zip I installed on my device... I could swear I deleted it manually, which would mean that sideload just pushes and installs for you in once nice package.
Either way, the issue he is having is that ADB won't find his devices... read the error message its not having trouble with the sideload or the zip... He just doesn't know how to use ADB and make it recognize his device...
Pushing doesn't always work when ADB doesn't recognize your device....
I was able to install MM using Sideload with MAC.
Procedure is the same as Windows the difference is that you NEED the most recent ADB.
https://developer.android.com/studio/index.html
Check using ./adb version that it is running at least 1.0.32
Davids-MacBook-Air:tools David$ ./adb devices
List of devices attached
XXXXXX sideload
Davids-MacBook-Air:tools David$ ./adb sideload update.zip
Total xfer: 2.07x
abcdavidefg said:
So I try to install sideload using my MAC but no luck.
I made sure the reactivation lock is "off"
I installed the ADB in my MAC.
I test:
./adb devices (and it shows my devices)
./adb reboot (and it reboots my phone)
I'm assuming that the ADB is working.
When I go into recovery mode and the "update ADB" this is what happened
Davids-MacBook-Air:mac David$ ./adb devices
List of devices attached
06157df643132f18 sideload
Davids-MacBook-Air:mac David$ ./adb sideload update.zip
error: protocol fault (no status)
Davids-MacBook-Air:mac David$
Phone wipes everything.
In the screen shows something like installing Hash tree
Hash tree successful
Phone reboots but it turns on regularly with everything wipe but no MM update.
Help!! anyone
Click to expand...
Click to collapse
Does this page help you?
http://forum.xda-developers.com/showthread.php?t=2720846
Jimmyvb98 said:
Does this page help you?
http://forum.xda-developers.com/showthread.php?t=2720846
Click to expand...
Click to collapse
No luck yet.
I try to transfer the file using
./adb push update.zip /sdcard (didn't work).... I'm assuming because I don't have a "/sdcard" directory.
Then I manually created a file called "sdcard" in the root of my memory.
Then copied the file from my computer to the memory of my phone.
Then reboot (power+home+volup) choosed update from external but I get an error saying no .../sdcard (file or directory)
I think the problem is that I can't move the file to the root of the phone. I guess I need root access (which I can't get)
I was able to sideload the file using MAC.
In general is relative the same method. Just make sure you have the most recent version of ADB for MAC.
Most of the "easy" installs of ADB for MAC are old version.
I'll post a more detail explanation. Step by Step if anyone ask for it