I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Ironcheeks said:
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Click to expand...
Click to collapse
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Lgrootnoob said:
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Click to expand...
Click to collapse
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Ironcheeks said:
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Click to expand...
Click to collapse
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Lgrootnoob said:
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Click to expand...
Click to collapse
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Ironcheeks said:
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Click to expand...
Click to collapse
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Ironcheeks said:
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Click to expand...
Click to collapse
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Lgrootnoob said:
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Click to expand...
Click to collapse
Thank you for all your help!
I can run adb devices, adb reboot. but when I go to. adb wait-for-device push firewater /data/local/tmp, I get a response, cannot stat 'firewater': No such file or directory. I have deleted and redownloaded the firewater file, and yes i have it in the right folder. Also, when the phone reboots, I get a driver message stating device driver not successfully installed, removed, redownladed the htc drivers, installed them, same error message
do you have temproot?
Stews X said:
I can run adb devices, adb reboot. but when I go to. adb wait-for-device push firewater /data/local/tmp, I get a response, cannot stat 'firewater': No such file or directory. I have deleted and redownloaded the firewater file, and yes i have it in the right folder. Also, when the phone reboots, I get a driver message stating device driver not successfully installed, removed, redownladed the htc drivers, installed them, same error message
Click to expand...
Click to collapse
Did you uninstall HTC Sync right after install?
Just to humor us, what folder is the firewater file located in (please paste the path)?
sorry I didnt get back, been crazy around here lately. Here is where I have firewater located
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools
Have you temp root?
andrewnelson said:
Have you temp root?
Click to expand...
Click to collapse
Yup
did you do any other commands before "adb wait-for-device push firewater /data/local/tmp"?
26463446
Karl said:
did you do any other commands before "adb wait-for-device push firewater /data/local/tmp"?
Click to expand...
Click to collapse
yes, adb reboot
I tried factory reset, did the temp root, checked with root checker, all good. But I still can not achieve root, keep getting the same response, can not find firewater. Do I need to have fast boot enabled?? Frustrating
Stews X said:
I tried factory reset, did the temp root, checked with root checker, all good. But I still can not achieve root, keep getting the same response, can not find firewater. Do I need to have fast boot enabled?? Frustrating
Click to expand...
Click to collapse
Wait, are you trying to get root, or to get S-Off?
I'm going to assume you're actually trying to S-Off based on the rest of your posts. Now, when you first connected your phone to your PC while you had debugging on, did you hit the "Always allow" option that popped up when it asked? If you don't hit "Always allow", I noticed that it doesn't pop up on each successive connection attempt, it just seemed to auto-deny it. You would need to go back into Developer Options, disable USB Debugging, then re-enable it and reconnect your phone to your PC. It should then prompt to allow USB debugging again, and this time hit the checkbox to "Always allow".
sfreemanoh said:
Wait, are you trying to get root, or to get S-Off?
I'm going to assume you're actually trying to S-Off based on the rest of your posts. Now, when you first connected your phone to your PC while you had debugging on, did you hit the "Always allow" option that popped up when it asked? If you don't hit "Always allow", I noticed that it doesn't pop up on each successive connection attempt, it just seemed to auto-deny it. You would need to go back into Developer Options, disable USB Debugging, then re-enable it and reconnect your phone to your PC. It should then prompt to allow USB debugging again, and this time hit the checkbox to "Always allow".
Click to expand...
Click to collapse
I did mean s-off sorry for the confusion, I believe I did, but I will try your suggestion, thanks
and to answer your earlier question, you do not want fast boot on.
Stews X said:
I did mean s-off sorry for the confusion, I believe I did, but I will try your suggestion, thanks
Click to expand...
Click to collapse
Also, are you still getting the driver error when you connect your phone? If so, that's a problem. And, when you're running the ADB command, what directory is CMD pointed to? As long as all the ADB files and the firewater file are in the same directory, it should be:
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
sfreemanoh said:
Also, are you still getting the driver error when you connect your phone? If so, that's a problem. And, when you're running the ADB command, what directory is CMD pointed to? As long as all the ADB files and the firewater file are in the same directory, it should be:
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
Click to expand...
Click to collapse
still wont go, now I am getting ," is not recongnized as an internal or external command, operable program or batch file
Stews X said:
I can run adb devices, adb reboot. but when I go to. adb wait-for-device push firewater /data/local/tmp, I get a response, cannot stat 'firewater': No such file or directory. I have deleted and redownloaded the firewater file, and yes i have it in the right folder. Also, when the phone reboots, I get a driver message stating device driver not successfully installed, removed, redownladed the htc drivers, installed them, same error message
Click to expand...
Click to collapse
the problem you're having is exactly what the error message says. "Cannot stat" means it does not see the file you are trying to push. I see you're using Windows to do this. Are you sure when you downloaded firewater your browser did not automatically append an extension (ie; .bin). Your problem is with the firewater file itself, either its not in the directory you say its in or its not called "firewater" for some reason. When you're in the CMD window look at the directory you're in and confirm the firewater file is in fact there with adb.exe.
billard412 said:
the problem you're having is exactly what the error message says. "Cannot stat" means it does not see the file you are trying to push. I see you're using Windows to do this. Are you sure when you downloaded firewater your browser did not automatically append an extension (ie; .bin). Your problem is with the firewater file itself, either its not in the directory you say its in or its not called "firewater" for some reason. When you're in the CMD window look at the directory you're in and confirm the firewater file is in fact there with adb.exe.
Click to expand...
Click to collapse
Here is a screenshot as to where I have firewater etc. what should be the next command after adb reboot, this is what I am pasting in the cmd window after the adb reboot as stated on firewaters webpage for instruction,"adb wait-for-device push firewater /data/local/tmp" is this correct?
Thanks again for all the help guys
Stews X said:
Here is a screenshot as to where I have firewater etc. what should be the next command after adb reboot, this is what I am pasting in the cmd window after the adb reboot as stated on firewaters webpage for instruction,"adb wait-for-device push firewater /data/local/tmp" is this correct?
Thanks again for all the help guys
Click to expand...
Click to collapse
Definitely looks right to me... now I'm scratchin my head a little lol
Stews X said:
still wont go, now I am getting ," is not recongnized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
billard412 said:
the problem you're having is exactly what the error message says. "Cannot stat" means it does not see the file you are trying to push. I see you're using Windows to do this. Are you sure when you downloaded firewater your browser did not automatically append an extension (ie; .bin). Your problem is with the firewater file itself, either its not in the directory you say its in or its not called "firewater" for some reason. When you're in the CMD window look at the directory you're in and confirm the firewater file is in fact there with adb.exe.
Click to expand...
Click to collapse
Possibly incorrect, it means part of the command he's trying to run isn't being found, but it could be referring to any part of the command string (or he may have made a typo when he entered the command). But more than likely, your CMD prompt is pointed to the wrong directory. But since you didn't answer my earlier question, I can't be sure about that, so try this:
- From the Platform-tools folder, hold down Shift, then press your right mouse button
- From the menu that comes up select Open Command Window Here.
- Run through the instructions again from the beginning: http://firewater-soff.com/instructions/
If you see something at any point that looks different from what the instructions say you should be seeing, don't just keep going, try to fix it. Here's a How To guide someone wrote up that may also be able to help. http://forum.xda-developers.com/showthread.php?t=2708628
sfreemanoh said:
Possibly incorrect, it means part of the command he's trying to run isn't being found, but it could be referring to any part of the command string (or he may have made a typo when he entered the command). But more than likely, your CMD prompt is pointed to the wrong directory. But since you didn't answer my earlier question, I can't be sure about that, so try this:
- From the Platform-tools folder, hold down Shift, then press your right mouse button
- From the menu that comes up select Open Command Window Here.
- Run through the instructions again from the beginning: http://firewater-soff.com/instructions/
If you see something at any point that looks different from what the instructions say you should be seeing, don't just keep going, try to fix it. Here's a How To guide someone wrote up that may also be able to help. http://forum.xda-developers.com/showthread.php?t=2708628
Click to expand...
Click to collapse
My sincerest apologies. I was starting the command window from the run button, instead of shift and right clicking from the directory. Thanks for your help and patience
Stews X said:
My sincerest apologies. I was starting the command window from the run button, instead of shift and right clicking from the directory. Thanks for your help and patience
Click to expand...
Click to collapse
No problem. Running from Start would have worked as well, you just would have had to type cd "c:\<full path to ADB folder>" before running any commands.
Is the S-Off working now for you or are you getting any other errors?
I want to start off saying that I'm a complete noob to this and I now realize I was stupid for biting of waaay more than I can chew.
I turned s-off and rooted using firewater exploit. I installed ViperOne with TWRP and all was well, until I decided I wanted to try Android Revolution HD (here) I stupidly decided that in addition to wiping the normal stuff, I would just format. I backed up to my pc just by copying everything into a folder (downloads, pictures, etc) and I wiped it. Now I've got the ROM on my computer and I'm trying to put it on the phone. I've tried using adb sideloader, and adb push but neither are working (I'm fairly certain I typed everything in correctly in cmd.)
How can I install ANY rom so that I can download with the phone and install from TWRP without formatting?
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
jova33 said:
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
Click to expand...
Click to collapse
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
chobungus said:
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
Click to expand...
Click to collapse
You probably didn't have USB debugging enabled, do you have access to a micro SD card?
If you do, load the rom onto that and flash from there.
Sent from my HTC6525LVW using Tapatalk
Well I was able to get it working, but as usual, I don't really know how. I redownloaded adb and the rom and restarted my computer. Tried the exact same sideload command and it worked.
Hi All, I hope someone can help.
I got this phone in December, and unlocked it, flashed TWRP and rooted.
My phone automaticly updated and was on version 7.1.2. But Super SU wasnt working anymore.
I tried to boot into TWRP but it was saying somthing like "No command given" when I tried.
I used Skipsoft toolkit to flash the recovery again (What I originally used) and when the phone rebooted, it gets to the Google logo and instantly reboots.
I can get to bootloader, but if I select recovery, it reboots.
Is there anything I can do here?
I did a backup in TWRP before I flashed, its stored on the phone.
Thanks in advance
I would use the tool to go back to stock. Just pick the last Google is the app I believe its V. Either update to the lastest software or I just flashed a rom with the newest vender
Hi, Thanks for your reply.
How can I do this though, I cant get the phone to boot, or into recovery
Is there a way I can use adb to push a TMRP so I can restore my backup?
My PC makes the noise as if something is attached by USB, but when I do adb devices, nothing shows.
Hi all,
I managed to sort it out and restore to original as advised above with fastboot. Never used it before, but I followed this guide and it worked great.
http://www.droidviews.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/
Thanks again
You can get TWRP and root on the May update.
https://forum.xda-developers.com/showthread.php?t=3600606
Anthony2oo5 said:
Hi all,
I managed to sort it out and restore to original as advised above with fastboot. Never used it before, but I followed this guide and it worked great.
http://www.droidviews.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/
Thanks again
Click to expand...
Click to collapse
This didn't work for me. I got as far as:
7. Now type the following command in the command window and hit the Enter key.
flash-all.bat
When doing that, I got the following returned in the CMD prompt:
'flash-all.bat' is not recognized as an internal or external command, operable program or batch file.
In the CMD prompt, make sure you're in the folder where you extracted the contents of the zip file.
graymoment said:
This didn't work for me. I got as far as:
7. Now type the following command in the command window and hit the Enter key.
flash-all.bat
When doing that, I got the following returned in the CMD prompt:
'flash-all.bat' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
X04D said:
In the CMD prompt, make sure you're in the folder where you extracted the contents of the zip file.
Click to expand...
Click to collapse
As X04D states you need to be in the correct directory. Hold shift and richt click in the folder where the files are located and press "Open command prompt here" then try again.
Anthony2oo5 said:
As X04D states you need to be in the correct directory. Hold shift and richt click in the folder where the files are located and press "Open command prompt here" then try again.
Click to expand...
Click to collapse
I probably should have clarified, but by quoting step 7 as the point it failed, I meant to imply that I had performed steps 1-6. Step 6 is the "open command prompt here" step.
graymoment said:
I probably should have clarified, but by quoting step 7 as the point it failed, I meant to imply that I had performed steps 1-6. Step 6 is the "open command prompt here" step.
Click to expand...
Click to collapse
That error means flash-all.bat is not in the same directory as the command prompt you opened. You unzipped it elsewhere, didn't unzip it or you opened the command prompt in the wrong place.
Flash this file after flash other files
VerifiedBootSigner