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
Related
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
[Solved] Thank you all for helping me through, I finally, I can made it. See the last post of the actually summary of my own journey.
Without all of your value input, I will never made it.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
At the first place, why and how did you flash an HTC HD rom to Desire S without even knowing it?! You should have know from the start that you should have taken precautions, and known that its an HTC HD. It should be PORTED first.
To answer,
Try flashing the recovery again on fastboot. Check my guides on how to on my sig (preferrably the second one). Then see if it works. If it did, flash the CORRECT rom.
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
imkr said:
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
Click to expand...
Click to collapse
What I'm trying to say is to flash the recovery again. 4ext recovery recommended. And start from there. Clear instructions were given on that thread on how to flash a recovery image via fastboot, and I believe I can't simplify it much further.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
Mate don't worry, it happened to me many times.see this thread to know how I got a solution.forum.xda-developers.com/showthread.php?t=1281688
I used nandroid backup but you can flash another ROM
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
After you get the phone in FASTBOOT mode, open the cmd window and type:
FASTBOOT FLASH RECOVERY c:\recovery.img
I find it very worrying that some one who can claim to have made this mistake many times is prepared to offer advice!
nandroid backups, you now see the importance of taking them
Swyped from my Desire S using XDA Premium
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Rapier said:
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Click to expand...
Click to collapse
It's working for me now, thanks for your clear instructions:
I've type up the exact process that I experienced here
1. Get 4EXT
2. Extract to C:
3. Find android-win-tools
4. SHIFT + Right click to open cmd from here
5. Type 'fastboot flash recovery C:\recovery.img', then appeared:
sending 'recovery'... OKAY (keep looking around 10mn), another command appeared
writing 'recovery'...OKAY
6. fastboot reboot-bootloader
DONE!
I am new to the ASUS family of tablets, and j just can't figure out how to root. I have rooted many tablets and installed custom roms before but the i cannot follow the how tos listed here. For one fastboot doesnt work on my computer. It opens and closes immediately. What i would like is a detailed step by step guide with a trouble shooting guide. I mean now i reading about downgrading, blob files and a few other things i never dealt with on my galaxy. Someone help......would love to root this thing. Email me if u want [email protected]
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Check this thread, it has videos about rooting and whatnot, hope it helps:
http://forum.xda-developers.com/showthread.php?t=1663244
Northern-Loop said:
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Click to expand...
Click to collapse
Yes, Bootloader is unlocked. Ok, so I tried the flashboot command, so now what? I typed the command from the walkthru "fastboot -i 0x0B05 flash recovery recovery.img " but get an errorcannot load recovery.img. So what am I missing. I have the recovery image on my desktop.....
Put the recovery image in the same folder as your fastboot application and it should work.
xAshxMoneyx said:
Put the recovery image in the same folder as your fastboot application and it should work.
Click to expand...
Click to collapse
....what fastboot folder? I installed the ADK per the instructions, I downloaded the root and recovery image. I looked in the system for a fastboot folder and do not see it. Plus when I try to type in the fastboot command now, it says it is not a recognized command. I am sure this is something simple, but I am just not getting it. Is there a more detailed step by step somewhere that will actually walk you thru the steps without assuming you know what they are talking about? I can root my phone, my galaxy tab all day long and install and change ROMS, but this one has me upside down.
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
xAshxMoneyx said:
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
Click to expand...
Click to collapse
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
xAshxMoneyx said:
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
Click to expand...
Click to collapse
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
tccc143 said:
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
Click to expand...
Click to collapse
Ok, so reinstalled everything.....did a quick refresher on CMD directions and had it rooted with CWM in 10 minutes. I have been working in Android so long without the use of a PC that I forgot how to use the PC. Thanks for the help....now we wait for some nice roms.
Sweet, glad you got it, I've done this stuff a few times but I always have to refresh myself and take it slow on each different device.
tccc143 said:
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
Click to expand...
Click to collapse
You should not move the folder. This can cause all kinds of problems. in the cmd prompt just type
cd \folder\folder\etc.
The cd means change directory and you start off with a backslash to set the initial path to the root of your drive. if folder names include spaces then wrap the path with quotes, cd "\folder one\folder two\etc". the prompt should change from C:\windows or whatever to what you typed in.
if you've installed on a drive other than C: then first change to that drive by typing the drive letter followed by a colon, ie D:
Good old DOS will never die.
Sent from my SCH-I510 using XDA
Well I am trying to Flash the latest fagyi NAND for Blackstone - http://forum.xda-developers.com/showthread.php?t=1914723
So I did everything, but when I reached the fastboot thingy, I did this:
After ROM flashed, took batter out and restarted device.
Blue screen showed up, forced fastboot, ready USB state, so I connected to PC
Then I opened a command prompt, so now what should I enter in the command prompt! I am using fagyi's fastboot!
Thanks, in advance!
Sorry for double posting, but please someone answer me, or atleast give me a tip/advice!
Do you mean this part?
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
Click to expand...
Click to collapse
post-mortem said:
Do you mean this part?
Click to expand...
Click to collapse
Yeah that exactly!
Step 2 says
2. Extract the 'adb files & fastboot.exe' files to a folder
Click to expand...
Click to collapse
so the 1st question is, do you know what folder you put those files in? Note that we're talking about your computer, not your phone. On your computer, open a command prompt by doing Start -> Run... -> cmd (This is Step 13). Navigate to the folder from Step 2 This is Step 14). Then, type the appropriate commands from Steps 15 & 16.
Still don't get it? Ask away!
Um the files are placed in C:
And when I enter the commands, it says 'File too big to fit in memory"? What do I do now?
So your step 14 should be to type cd c:\, then 15 fastboot flash recovery recovery.img
Is that when you get the error?
Yes, exactly then!
Ok, try redownloading the fastboot program, or install the Android SDK to get the newest version directly from Google.
I've redowloaded it alot of times! And I already have the Android SDK and am using the latest one!
Are you sure that you're using the correct version of all relevant programs? By that, I mean 32 vs 64-bit.
I am not sure about that, how should I know?
Do you get the same error if you type fastboot devices ?
I havent typed that yet!
EDIT: No I get this - "RH104393397 fastboot"
Please Admin/Moderator, lock this thread, my problem is now fixed!
Angat said:
Please Admin/Moderator, lock this thread, my problem is now fixed!
Click to expand...
Click to collapse
Can you tell me how do you fix the problem ? I have the same problem
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.
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error. Screenshot of cmd would be very helpful too please
Sent from my Nexus 5 using Tapatalk
rootSU said:
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What I did is to check if the boot loader is unlocked.
And yes. It is unlocked.
So I carried onto checking if fastboot detects my devices by doing "fastboot devices". And my nexus5 gets detected.
Then I moved on to trying to flash recovery using " fastboot flash recovery recovery.img ".
But the error appears at this point. And I'm stuck.
Is this sufficient?
Do note that I did change the file name to recovery and not recovery.img as most files do not include the file type in the file name.
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
You would be better served setting windows not to hide known file types to be honest.
A screenshot of your fastboot flash attempt and error would be most useful please
Sent from my Nexus 5 using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:28 PM ----------
chblg said:
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
Click to expand...
Click to collapse
He hasn't got root. Fastboot is his only option
Sent from my Nexus 5 using Tapatalk
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Nukyi said:
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
Click to expand...
Click to collapse
rootSU said:
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Click to expand...
Click to collapse
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Nukyi said:
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Click to expand...
Click to collapse
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Nukyi said:
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Click to expand...
Click to collapse
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
rootSU said:
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
Click to expand...
Click to collapse
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Nukyi said:
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Click to expand...
Click to collapse
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
Alright. I'll do it and get back to you shortly.
Thank you.
Really hope this fixes the problem.
rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
jj14 said:
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
Click to expand...
Click to collapse
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
Now try and run cmd as an administrator if you are not doing
Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
no. the recovery.img is not in c:\users\username\
put that file there, then retry your command
OR
fastboot flash recovery c:\entire\path\to\recovery.img
Nukyi said:
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Click to expand...
Click to collapse
are you sure you downloaded the image and not the zip??
samersh72 said:
are you sure you downloaded the image and not the zip??
Click to expand...
Click to collapse
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Nukyi said:
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Click to expand...
Click to collapse
Ah. It just worked suddenly. No idea why. But I guess @rootSU 's suggestion works well.
And maybe also @Zepius 's suggestion.
Here's what I did to help others who have the same problem.
I did what rootSU asked me to do (changing the "path" part).
Then took Zepius suggestion and duplicated the recovery img in a few folders (the original folder i'm using, on desktop, on C drive root folder)