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?
Related
I posted this in another thread but got no response, this thread (http://forum.xda-developers.com/showthread.php?t=502010&page=35)
maybe a new thread will help.
So this is my first venture into the whole ABD thing. I am trying to install the framework mod from Tazz for the HTC music player (as listed here: http://forum.xda-developers.com/show...5594&page=1277 post 12768).
Tazz mentions to “push this http://www.multiupload.com/1WWHXAUN6W
to system/ect/permissions then download and install htc music”
So, running my trusty Win7 machine I downloaded the SDK from the android development site, inserted the correct line in the path and viola, I can enter the CMD prompt and run the adb command successfully. Adb and adb shell both seem to work.
I followed the instructions from here: http://androidforums.com/developer-1...-commands.html and here: http://forum.xda-developers.com/showthread.php?t=502010 for the install.
My problem comes in when I try to push the file to the phone.
Fisrt dumb question is: what phone mode should I be in when running the adb? Standard running mode or booted to recovery? (I thought I read something about being in recovery but at that point it was all a blur).
I have the USB Debugging turned on so I think I am ok there.
I installed the SDK to my C:\Android directory.
I saved Tazz’s file to my C:\Android\Tools directory.
Here is my cmd text (maybe this is where I went wrong):
In the cmd window I CD’d to the C:\Android\Tools directory
adb push com.framework.htc.xml system/ect/permissions
After making sure that I was in the correct dir and all files were also located in the correct dir I am still getting an error, file or directory not found, or something like that.
Sorry for the long post. I figured this would be a good first step (my first adb experience) as it seems pretty benign in terms of me bricking anything but offering a good learning opportunity.
I am running a rooted Eris (KaosFroyo v36).
In looking things thru maybe I need a USB driver for the Eris?
any help is appreciated,
oh, my cmd prompt looks like sh-2# (or something like that)
Thanks
While it may be that you still need to download the appropriate drivers, it seems you are able to get root access so, this is likely not the case.
There are two things which stand out as potential issues in the steps you described. Fortunately, both are super easy.
First and foremost, make sure you have mounted the phone as "read-write."After you have cd'd to the tools folder type "adb remount" (without the quotes) and press enter. If successful, it should respond with "remount succeeded." Congrats, you have now mounted the phone as read-write.
Next, I see errors with your command. There should be a "/" before "system" and it should be "etc" not "ect." Specifically, your command should be:
adb push com.framework.htc.xml /system/etc/permissions/
[The above command of course, assumes that the name of the file you are pushing is indeed named "com.framework.htc.xml" and is in your tools folder.] You'll know it worked if the response in your command prompt indicates the speed and time it took for the push to take. For example, "1234kbps in 3.4 seconds". If you see something resembling that you should be all set. At this point you can reboot your phone and your changes should be in effect. Either unplug and reboot manually or just type "adb reboot" (without the quotes) and press enter.
In regard to your question about whether the phone can be in standard running mode or recovery... It depends on the level of root of the phone but, fully rooted and nand unlocked phones can be adb'd while in standard running mode. My EVO can and it is very likely your Eris can too.
I see
thanks OK.
typo's aside in the thread, my command was missing the / as you have described it. I also did not know about the remount thing. In my reading I thought that was just for the sd card. I will try and put all the pieces together when I get home tonight.
You are correct in that is the name of the file and I do have it in the /tools directory.
Thanks for the help, baby steps (I am learning)
No problem. We are/were all noobs at one point in our lives.
The term "mounting" has slightly different contextual meanings which can be confusing. First off, the /system/ folder is already "mounted" while using adb, however, it is mounted as read-only. So, if you are ever trying to push something to the phone and get an error back that says "mounted as read-only" you'll now know what went wrong. Simply type "adb remount"
and it puts the /system/ folder into read-write mode.
Bear in mind that upon phone reboot the /system/ folder automatically remounts into read-only mode so if you reboot and try to push another file you'll need to remember to "adb remount" again.
With regard to the sdcard "mounting" refers to whether the phone (sdcard) is mounted as a disk drive on your computer. You'll find that if this is the case many adb commands won't work because the sdcard can't be accessed by the phone while mounted on the computer. Therefore, always remember to connect your phone as "Charge Only" when adb'ing.
got it
That did the trick, worked like a charm. Thanks for the help and pointers. I have now pushed my first file...yeah for me!!
Thanks for your help and time.
glad your push worked
I am still trying to get SDK/ADB to connect to my Milestone XT720 phone. Have no idea of why they won't. Have tried all the usual suspects but nothing as of yet. NEED HELP!
All right guys, I know I should search the forum, but I have no time now, this is what's going on: I tried to install CF3D's plugin on my Transformer, but it went darn bad, I can't get past Asus' "powered by tegra" screen, and I need this by tomorrow, for my class, how do I fiz this?! I unlocked it, running TWRP v 0.2.2.3., can't remeber my rom's name but it's a mod of the CleanRom, v3.1 that's all I know. I think I can fix this by re-flashing my rom, but I don't know if I can put files into my SD only with TWRP in my hands, if not is it a real brick?? Please, help me!!!
TheBloodEagle27 said:
All right guys, I know I should search the forum, but I have no time now, this is what's going on: I tried to install CF3D's plugin on my Transformer, but it went darn bad, I can't get past Asus' "powered by tegra" screen, and I need this by tomorrow, for my class, how do I fiz this?! I unlocked it, running TWRP v 0.2.2.3., can't remeber my rom's name but it's a mod of the CleanRom, v3.1 that's all I know. I think I can fix this by re-flashing my rom, but I don't know if I can put files into my SD only with TWRP in my hands, if not is it a real brick?? Please, help me!!!
Click to expand...
Click to collapse
I don't understand "if I can put files into my SD only with TWRP in my hands", you don't have a pc where you can copy the rom to your sdcard? BTW you should be using twrp 2.3.1.0.
I actually have my PC here with me,
but like I said im not sure I can connect it to the pc since it will be on recovery, you know, like an MTP or mass storage, can TWRP do that?
Sent from my R800i using xda app-developers app
TheBloodEagle27 said:
I actually have my PC here with me,
but like I said im not sure I can connect it to the pc since it will be on recovery, you know, like an MTP or mass storage, can TWRP do that?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
You can't take the sdcard out and put it to your pc, copy the rom from pc to sdcard then put it back to your device? or you could use adb to push the file and hope adb is working on your pc.
ADB is working on my PC, but I don't see the TF700T icon under my computer
Sent from my R800i using xda app-developers app
TheBloodEagle27 said:
ADB is working on my PC, but I don't see the TF700T icon under my computer
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
buhohitr said:
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
Click to expand...
Click to collapse
Alright, I'ts getting late, so I'll try it after school after all, I was thinking of using flashtool to flash the room through fastboot, that's how I used to do on my Xperia Play, but I don't know if the program works with asus' tablets... Anyway, thanks a lot man, for trying to help me and all, If it works I'll have a lot to owe u.
TheBloodEagle27 said:
Alright, I'ts getting late, so I'll try it after school after all, I was thinking of using flashtool to flash the room through fastboot, that's how I used to do on my Xperia Play, but I don't know if the program works with asus' tablets... Anyway, thanks a lot man, for trying to help me and all, If it works I'll have a lot to owe u.
Click to expand...
Click to collapse
EDIT: I must be doing something wrong. Where is the adb.exe location? I found one in the Asus Sync folder, is it that one? Second, where do I put this command? I know, in the command prompt, but which folder is it supposed to open?
TheBloodEagle27 said:
EDIT: I must be doing something wrong. Where is the adb.exe location? I found one in the Asus Sync folder, is it that one? Second, where do I put this command? I know, in the command prompt, but which folder is it supposed to open?
Click to expand...
Click to collapse
You don't move the adb.exe, where ever the adb command located, you need to open command prompt and navigate to the adb.exe folder. Asus Sync is located in C:\Program Files\ASUS\ASUS Sync and so is the adb.exe. so open command prompt and type:
cd\ hit enter, this bring you to root Ccomputer displayed C:\>
type:
cd Program Files\ASUS\ASUS Sync hit enter, you're now in the Asus sync folder (this is where your rom.zip should be in also)
computer should displayed:
C:\Program Files\ASUS\ASUS Sync>
now type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
buhohitr said:
You don't move the adb.exe, where ever the adb command located, you need to open command prompt and navigate to the adb.exe folder. Asus Sync is located in C:\Program Files\ASUS\ASUS Sync and so is the adb.exe. so open command prompt and type:
cd\ hit enter, this bring you to root Ccomputer displayed C:\>
type:
cd Program Files\ASUS\ASUS Sync hit enter, you're now in the Asus sync folder (this is where your rom.zip should be in also)
computer should displayed:
C:\Program Files\ASUS\ASUS Sync>
now type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
Click to expand...
Click to collapse
"system could not find specified directory" Heads up ¬¬...
Do you actually have a microSD card inserted into the tablet?
MartyHulskemper said:
Do you actually have a microSD card inserted into the tablet?
Click to expand...
Click to collapse
haha!! sorry for lol! if you don't have the sdcard, you could push it to internal sd.
buhohitr said:
haha!! sorry for lol! if you don't have the sdcard, you could push it to internal sd.
Click to expand...
Click to collapse
Ok then, how do I push ut to the internal SD?
TheBloodEagle27 said:
Ok then, how do I push ut to the internal SD?
Click to expand...
Click to collapse
adb push rom.zip /sdcard/
or
adb push rom.zip /storage/sdcard0/
Edit: Is it working for you yet??
buhohitr said:
adb push rom.zip /sdcard/
or
adb push rom.zip /storage/sdcard0/
Edit: Is it working for you yet??
Click to expand...
Click to collapse
I'm not sure, i'll try it out right now. I guess if it doesn't work it could be a problem with adb, is there any tutorial on how to set it up?
buhohitr said:
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
Click to expand...
Click to collapse
I tried this, but got this message:
adb server is out of date. Killing...
ADB server didn't ACK
*failed to start daemon*
error:
what does that mean?
TheBloodEagle27 said:
I tried this, but got this message:
adb server is out of date. Killing...
ADB server didn't ACK
*failed to start daemon*
error:
what does that mean?
Click to expand...
Click to collapse
I thought that you already have adb working on your PC, but seems like you don't. You need to download Android SDK and once installed, you can use adb command from this SKD. Here is the link to how install Android SDK. It shouldn't take no more than 10 min. Just download and run the install, only select packages with the word "Android name" should be only 2. Once you done this, adb and fastboot should work fine. You also need Java, but like 99% ppl with a PC should already had Java installed.
http://forum.xda-developers.com/showthread.php?t=1616059
This tool is very important in rooting, recovery, flash stuff to your device. So I recommend you install this and get it working, it will save you a lot of time and headache in the future.
EDIT; If you think you have all the components already installed, you could download the adb/fastboot package here http://forum.xda-developers.com/attachment.php?attachmentid=1403567&d=1350299936 , unzip it to your C drive, you will have a folder called "Install recovery", in this folder there's adb and fastboot command, and then open cmd navigate to this folder and execute adb command line I provide previously see if that works.
buhohitr said:
I thought that you already have adb working on your PC, but seems like you don't. You need to download Android SDK and once installed, you can use adb command from this SKD. Here is the link to how install Android SDK. It shouldn't take no more than 10 min. Just download and run the install, only select packages with the word "Android name" should be only 2. Once you done this, adb and fastboot should work fine. You also need Java, but like 99% ppl with a PC should already had Java installed.
http://forum.xda-developers.com/showthread.php?t=1616059
This tool is very important in rooting, recovery, flash stuff to your device. So I recommend you install this and get it working, it will save you a lot of time and headache in the future.
EDIT; If you think you have all the components already installed, you could download the adb/fastboot package here http://forum.xda-developers.com/attachment.php?attachmentid=1403567&d=1350299936 , unzip it to your C drive, you will have a folder called "Install recovery", in this folder there's adb and fastboot command, and then open cmd navigate to this folder and execute adb command line I provide previously see if that works.
Click to expand...
Click to collapse
All there is in here is a .cmd file, no adb or nothing, I tried to use the command line you provided me, but all I get is:
adb server is out of date. Killing...
*daemon started succesfully*
Protocol Failure
Edit: I also downloaded the Android SDK Manager and downloaded the two tools
TheBloodEagle27 said:
All there is in here is a .cmd file, no adb or nothing, I tried to use the command line you provided me, but all I get is:
adb server is out of date. Killing...
*daemon started succesfully*
Protocol Failure
Edit: I also downloaded the Android SDK Manager and downloaded the two tools
Click to expand...
Click to collapse
If you go here http://forum.xda-developers.com/atta...7&d=1350299936 download the zip file then unzip to your drive. In this new folder you should see adb.exe and fastboot.exe and a few dll files. Do you see them??? Make sure your anti-virus doesn't strip the files.
buhohitr said:
If you go here http://forum.xda-developers.com/atta...7&d=1350299936 download the zip file then unzip to your drive. In this new folder you should see adb.exe and fastboot.exe and a few dll files. Do you see them??? Make sure your anti-virus doesn't strip the files.
Click to expand...
Click to collapse
Oh man, this sucks, it says 404 page not found, didn't you cpy the wrong link?
Hi
I have a Nexus 5 currently on KitKat 4.4, and am trying to manually update to 4.4.1 but with no success
Have read and followed all stages in posts relating to updating the firmware, have downloaded the 4.4.1 file and Android SDK.
All steps work as they should, have got as far as my PC recognising my device serial number, until I get to the step where I enter, in the command prompt opened from the platform tools folder
adb sideload KitKat.zip (KitKat.zip being the name I have given the file)
I then keep getting the error message "unable to read file KitKat.zip"
I have tried with and without .zip in the command but still no luck
Help please?? I have run out of ideas to try
The command adb sideload (filename).zip has no space between side and load.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
Also is your 4.4.1 update file in the platform tools folder? Are you opening the command prompt in the platform tools folder?
Sent from my Nexus 7 using XDA Premium HD app
Please ask questions in q&a. General is not for questions
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
nohcho said:
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
marleyfan61 said:
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
Click to expand...
Click to collapse
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
I was having the same issue. I just kept the ota name as it was when I downloaded it and added .zip to the end. It worked fine after that. Just copy and paste it in cmd
red83 said:
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
Click to expand...
Click to collapse
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
forgive me if you did this already, does your operating system display the three letter file extension like 'update.zip, adb.exe' etc.
marleyfan61 said:
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
Click to expand...
Click to collapse
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
Try my suggestion above, worked for me. I was having the same problem.
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Yes what you said works, straight into recovery no probs by putting 'adb reboot recovery in a cmd prompt window to the specific directory that the abd file is located......(in platform tools) then if I put adb devices the serial number comes up straight away with 'sideload next to it.
So then I put adb sideload update.zip, and guess what!
cannot read update.zip....
Have you tried my suggestion?
richport29 said:
Have you tried my suggestion?
Click to expand...
Click to collapse
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Should I be "de-activating/activating" anything else other than activating the developer options and selecting USB debugging....should I remove my SIM card??
Anything else I may have overlooked please?
red83 said:
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
Click to expand...
Click to collapse
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
richport29 said:
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
Click to expand...
Click to collapse
Have tried re-downloading the file from several locations, placing it directly into the platform-tools folder and only adding .zip to the file directory name.....still no joy
When you type adb devices, what comes up?
Unless you absolutely have to have the camera fix in this update right now, then I suggest you just wait til the OTA becomes available on your phone. The camera fix is the only significant thing in the update. I don't know what the issue is with what you are trying but I suspect there is something not being done right. Sounds like it's not worth the frustration tho.
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.
You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...
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