Database Info

Error: can not load recovery-Tiamat-R4c-100611-1150-cwm

So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.

I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798

supenova3000 said:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.

williamthegoat said:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
Click to expand...
Click to collapse
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!

So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.

Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
Sent from my MB860 using xda premium

I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys

Think you have to be stock to flash to ICS, at least that was the word yesterday.
I gave up trying to root just as I found out about the ICS update.

williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Click to expand...
Click to collapse
Two simple errors:
1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and
2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img

williamthegoat said:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
Click to expand...
Click to collapse
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...
So, cd\...\platform-tools and then flash

The simplest way I perform all of my operations for this:
I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.
For Windows 7, I use Windows PowerShell.
For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)
Once opened: I type this configuration EXACTLY as is: (Keys in <>)
Code:
cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>
This above brings me directly to:
C:\Program Files (x86)\Android\Android-sdk\Platform-tools\
Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.
to use FASTBOOT (XOOM already in fastboot mode):
Code:
./fastboot flash recovery rec<TAB><ENTER>
This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img
Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.
Auto-complete is a nice thing. "./" is added to command from the working directory.

williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys[/QUOTE
Worked for me too!!! Thanks!!!
Click to expand...
Click to collapse

Help for installation of clockwork

hi guys, i'm trying to install the clockwork touch 5.8.0.2 crespo on my Nexus S (GSM), i have create the folder in C: with in the file, i have installed the driver of my phone, but when i open the prompt for write fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo.img, he tells me "fastboot is not recognized as internal or external command, executable programm or file batch.", what can i do??
i also want to install this after: http://forum.xda-developers.com/showthread.php?t=1764119, someone can help me also for this??

DavideDroid said:
hi guys, i'm trying to install the clockwork touch 5.8.0.2 crespo on my Nexus S (GSM), i have create the folder in C: with in the file, i have installed the driver of my phone, but when i open the prompt for write fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo.img, he tells me "fastboot is not recognized as internal or external command, executable programm or file batch.", what can i do??
i also want to install this after: http://forum.xda-developers.com/showthread.php?t=1764119, someone can help me also for this??
Click to expand...
Click to collapse
You need to have AndroidSDK installed or atleast have fastboot executable.
Once you have that, you can either set the path in environment variables or just go to that path using command line and use the fastboot command.

You should follow this instruction, it's very helpful.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/

superatmos said:
You need to have AndroidSDK installed or atleast have fastboot executable.
Once you have that, you can either set the path in environment variables or just go to that path using command line and use the fastboot command.
Click to expand...
Click to collapse
I already have the SDK; the site from which i was following the tutorial have told me i miss the fastboot.exe, can you tell me where I can find it??
rubenflush said:
You should follow this instruction, it's very helpful. (i can't quote the url)
Click to expand...
Click to collapse
But that is for the 4G version, is the same thing?

I just rooted my first Android device the day before yesterday. One problem I ran into is that the Android SDK now installs to "C:\Users\USER\AppData\Local\Android\android-sdk" instead of "C:\android-sdk" like most instructions give.
These are the instructions I followed to root my phone: wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide (Sorry for the lack of a link. I just found out I'm not able to post links because I'm new )
They helped me out a lot but it took a lot of time and concentration to get it done. Just keep in mind where Android SDK installs and change the paths to the new path when you need to.

DeadBra1ns said:
I just rooted my first Android device the day before yesterday. One problem I ran into is that the Android SDK now installs to "C:\Users\USER\AppData\Local\Android\android-sdk" instead of "C:\android-sdk" like most instructions give.
These are the instructions I followed to root my phone: wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide (Sorry for the lack of a link. I just found out I'm not able to post links because I'm new )
They helped me out a lot but it took a lot of time and concentration to get it done. Just keep in mind where Android SDK installs and change the paths to the new path when you need to.
Click to expand...
Click to collapse
Thank you very much, tomorrow i try again following this tutorial

Yes same thing, sorry for late post.
Sent from my Nexus S using xda app-developers app

[Q] Blank Phone? Need Help!

Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?

vI Ragnarok Iv said:
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
Click to expand...
Click to collapse
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.

simms22 said:
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
Click to expand...
Click to collapse
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!

vI Ragnarok Iv said:
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
Click to expand...
Click to collapse
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.

exb0 said:
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
Click to expand...
Click to collapse
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/

vI Ragnarok Iv said:
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
Click to expand...
Click to collapse
Oh, that was probably a driver issue. No worries, you can always get into android, transfer the custom rom into your SD card, boot into recovery, wipe and flash if you want to try out a custom rom.

[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)

[Q] I need help with my Nexus 5 with no OS on it.

I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.

1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work

First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.

awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.

The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?

What does the terminal say as an error? And are you running Linux, Mac, or windows?

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.

So just gonna ask again, what message did you get in the terminal?

Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit

After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?

Try adb kill-server then (I'm a little rusty with windows) su adb start-server

experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device

Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)

experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.

sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish

sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..

Thread cleaned.
Let's keep it on topic guys,