Database Info

Trouble installing new recovery

Im trying to get my new XOOM from unlock to root and having a nightmare!
I have read and followed guides from the forum but still can't get the new recovery on?
I have done fastboot oem unlock and followed the instructions on the tab and at the end it says complete. Next once it reboots enabled usb debugging and rebooted into bootloader, all ok so far but when I try to run the command "fastboot flash recovery recovery-tiamat-r4c-100611-1150-cwm.img" it comes up with "cannot load"? I have tried with and without the. img at the end and also renamed the file "recovery" and "recovery.img" and still the same thing.
Has anyone had this same problem and can get me back on track please.
Sent from my MZ604 using xda premium

(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img

Ok, will give it a try when I get to my computer and will report back.
Thank you
Sent from my Desire HD using xda premium

Our Indian cricket team is in your country desperately need a win

rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
nope that didnt work, same thing error: cannot load 'recovery.img

ok now im getting someware
still not working but when i do adb devices it says list of devices attached but nothing?

Just a note usb debbuging is on
Sent from my MZ604 using xda premium

rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, it really doesn't matter if all your files that you need are in Tools or Platform tools, as long as they are all in there and your command window is operating out of that folder.
Second, you are making a good point re: the img file extension...in Windows, it sometimes is set to hide file extensions, so it is possible that someone could already have the img file extension there and not see it and add it again, making recovery.img.img which of course wouldn't work.
I don't think this is the OP's problem, but you never know.

Stuck on htc screen 'flashed wrong rom'

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!

[Q] Noob Root Walkthru

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

I'm lost installing CMW

OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?

polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
change directory to the folder the recover/fastboot is in, using the CMD on windows. So:
"cd C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools"
make sure the recovery is called "recovery.img" and that its in the "platform-tools" folder alongside the fastboot.exe, then run the commands:
"fastboot -i 0x0B05 flash recovery recovery.img"
and
"fastboot reboot"

polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.

buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
Thanks but I've already downgraded. I'll try what the guy above said thank you for the help
Sent from my SGH-I747M using Tapatalk 2

when you are in the fastboot folder, you have to press control & right click inside the folder, and you will see the option to open a terminal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Pat,
If it makes you feel any better I had a heck of a time with this myself.
Once I realized I had platform tools in a folder on my PC desktop with the command prompt
in it I was able to flash.
Gotta say it wasn't easy to figure out in bits and pieces.
Sent from the inside out...

Thanks guys, you've been REALLY helpful! I completely forgot about the shortcut to open cmd in a folder, and i'm not sure if you were wrong or its because im on windows 8 but its ctrl + shift + right click
EDIT: now i get a problem, it do all this and i get "waiting for device"
i tried different USB ports, same deal...any ideas?
EDIT: EDIT: tried all USB port but one, the last one i used did the trick, thanks for all!

I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app

mnk0ota said:
I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
try to open CMD as Administrator.

buhohitr said:
...
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2

John Kotches said:
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.

Firebrazer said:
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.
Click to expand...
Click to collapse
Thanks... if it seems too good to be true it probably is.
Sent from my MB855 using Tapatalk 2

[Q] [Problem] Cannot flash recovery

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)