Having an issue flashing a custom recovery via fastboot. Everything is set up properly, fastboot commands work, but it keeps telling me that it cant open the recovery.img. Here is the error I am getting:
Daniels-MacBook-Pro:~ danielmasterson$ fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
error: cannot open 'openrecovery-twrp-2.6.3.2-hammerhead.img'
I am at a loss. I have had this set up this way since the Galaxy Nexus and it's never not worked. Any ideas?
if it's showing up when you search for fastboot devices, it may be the file. have you tried re-downloading it, renaming it, or even grabbing the 6.0.4.4 cwm img and flashing that? i'm curious.
xBeerdroiDx said:
if it's showing up when you search for fastboot devices, it may be the file. have you tried re-downloading it, renaming it, or even grabbing the 6.0.4.4 cwm img and flashing that? i'm curious.
Click to expand...
Click to collapse
Yes, I've redownloaded, renamed, tried CWM, etc. I'm totally buffaloed...
Sent from my Nexus 5 using Tapatalk
Hell, I unlocked the bootloader via fastboot so...
Sent from my Nexus 5 using Tapatalk
what is the ls -l of the .img file? Maybe a permission issue?
Typically I always rename my recovery images to 'recovery.img' thats the only thing I do differently than you on my mac. Second, where are you storing your recovery file before you flash it? External HDD? Check the permissions on the file/ the source drive.
also, did you update your SDK/adb?
Thanks for the replies guys. I'm still not sure what was going on, I nuked my whole ADB setup and started over again and all is well. Liking the N5 so far, it's really nice stock. May not eben jack with it too much, but I know I'll get the itch sooner or later...
A couple of things to try...
1) Make sure the recovery image is in the same directory where you installed fastboot and you are executing the terminal commands from that directory
2) Try adding ./ in front of the command so it would be ./fastboot flash recovery nameofrecovery.img
Sent from my Nexus 5 using xda app-developers app
chef_christoph said:
A couple of things to try...
1) Make sure the recovery image is in the same directory where you installed fastboot and you are executing the terminal commands from that directory
2) Try adding ./ in front of the command so it would be ./fastboot flash recovery nameofrecovery.img
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
0dBu said:
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
Click to expand...
Click to collapse
I would think then you didn't update to the latest SDK/adb for N5.
0dBu said:
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
Click to expand...
Click to collapse
Sorry, missed your post while I was typing mine. Glad to hear you got it working. Cheers!
Sent from my Nexus 5 using xda app-developers app
Related
Please delete this thread.
The updated version is here
http://forum.xda-developers.com/showthread.php?t=1167819
you could always post the links as text and then after 10 posts then you can convert to urls again
www.filefactory.com/file/cb882b4/n/Flash_Recovery.zip
www.filefactory.com/file/cb88370/n/Full_recovery.zip
filefactory.com/file/cb882b4/n/Flash_Recovery.zip link 1
filefactory.com/file/cb88370/n/Full_recovery.zip link 2
PM Sent.....
Its telling me that fastboot is not a internal or external command. I'm going into the cmd and typing cd filepath then the fastboot instructions. Am I missing something?
Fixed! Thanks so much!
cloo24 said:
Its telling me that fastboot is not a internal or external command. I'm going into the cmd and typing cd filepath then the fastboot instructions. Am I missing something?
Fixed! Thanks so much!
Click to expand...
Click to collapse
Your welcome and so everyone else knows you have to hold ctrl and shift in the folder and then click on open command prompt.
ok i made it simpiler to follow. I decided to do this because the ota is coming and many people want stock back.
Anyone have any issues getting stock recovery back on their nexus? I have ran odin a few times with stock files and I end up with no recovery, just that triangle exclamation thing. I have tried fastboot flashing stock recovery as well as custom ones with no luck. The only thing that has saved me is shabby's one click...for some reason its fastboot flash of recovery works while doing it manually doesn't...but that doesn't put on stock recovery...
Thanks I really needed these instructions.
Sent from my Nexus S 4G using XDA Premium App
raiderep said:
Anyone have any issues getting stock recovery back on their nexus? I have ran odin a few times with stock files and I end up with no recovery, just that triangle exclamation thing. I have tried fastboot flashing stock recovery as well as custom ones with no luck. The only thing that has saved me is shabby's one click...for some reason its fastboot flash of recovery works while doing it manually doesn't...but that doesn't put on stock recovery...
Click to expand...
Click to collapse
When I was on stock (when I first got the phone) I remember not having a recovery at all ( just the triangle) .
Sent from my Nexus S 4G using XDA Premium App
ok i used odin put those files in the right spot but its not doing anything. It says all threads comp succeed 0 failed 0 any ideas
ok will i treid this method and it dosent work i follow the directions just like it says put the tar files in the right spot hit start and nothing happens. it gives me the mess suceed 0 failed 0. put it download more and it just sits there. i do have adb set up for the device
Petes method is better than this method guys. Use fastboot, just copy and paste the commands into the terminal. Much better than this.
mikeyinid said:
Petes method is better than this method guys. Use fastboot, just copy and paste the commands into the terminal. Much better than this.
Click to expand...
Click to collapse
Hey mike would you mind a pm on how to, cause I'm a little lost.
Sent from my Nexus S 4G using XDA Premium App
info[]box1 said:
Hey mike would you mind a pm on how to, cause I'm a little lost.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK. You obviously have fastboot drivers installed cus your rooted. Download THESE, courtesy of Pete. Extract that zip to a folder on your desktop. Open that folder, hold shift and right click in the folder and choose open command window here. Then run these commands, hitting enter at the end of each line:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
That is all, takes like a minute or 2 and your back to stock. I can do it with my eyes closed
Thanks Mike
Sent from my Nexus S 4G using XDA Premium App
windows can not recognize my phone can someone help me !
damnn said:
windows can not recognize my phone can someone help me !
Click to expand...
Click to collapse
can't recognize it at all, or can't recognize it in fasboot mode?
cant recognize it in fast boot mood.. my phone is on like normally and usb debugging is on and when i type in the cmd it doesnt go through it says "adb" is not regnozied as an internal or external command operable program or batch file
gonna try this since ive got a replacement phone on the way, what would happen if it sent the phone back unlocked and rooted anyway?
So, basically ever since I've had my phone rooted and had ROM Manager on it, it has had trouble flashing Clockwork Recovery for me. I'll select for it to flash, it will appear to do so, but when I try to boot into recovery, either manually or from ROM Manager, it will just go to the default bootloader. When I attempt to choose Recovery from there, nothing will happen, and I'll have to reboot my phone and attempt to flash CWM again, and again, until it finally boots into it.
This always used to work after about 3 tries though, but now suddenly, it's just not even going anymore.
Is there anything I can do to make this process easier (or actually work)?
Set cwm to erase before flashing.
Sent from my Nexus S using xda premium
Or just use the fastboot command and flash recovery that way.
krohnjw said:
Set cwm to erase before flashing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Just tried doing this, didn't work.
NYYFan325 said:
Or just use the fastboot command and flash recovery that way.
Click to expand...
Click to collapse
What command would that be? /noob
The command is called fastboot. You run it from a command prompt. You need to download the recovery image, then from the command prompt type:
fastboot flash recovery nameofrecoveryimage.img
There are multiple guides on here that explain it step by step
NYYFan325 said:
The command is called fastboot. You run it from a command prompt. You need to download the recovery image, then from the command prompt type:
fastboot flash recovery nameofrecoveryimage.img
There are multiple guides on here that explain it step by step
Click to expand...
Click to collapse
First off, sorry for taking so long to reply.
That was extremely noobish of me, I had completely forgotten about fastboot.
Turned out that solved it. I'm not sure what was going on, but all seems to be well now.
Thank you for your help!
use qbking77 guide in rooting ns/s 4g it is superb tutorial... go to youtube and type qbking77 ^_^
There was a file you have to delete. Look around Q&A, It's in there
Sent from my Nexus S 4G using XDA App
Ok so either delete these two files below or change the permissions so it has none (000)
"Install-recovery.sh" located in /system/etc
"Recovery-from-boot.sh" located in /system
I know this is not a new subject. but i feel i wont get a response in another thread that is pretty outdated. so im trying to flash cwm recovery thru fastboot but i get an error. I've tried typing the directory path c:\android-sdk\platform-tools\recovery.img. i get "cannot load recovery.img". this is what im typing
fastboot flash recovery c:\android-sdk\platform-tools\recovery.img
and i still get the error. I've even tried moving the recovery.img to c:\recovery.img
but no matter where or how i call it. it wont load. please help guys. I had android sdk install before but i had to wipe my pc clean and i just recieved a replacement nexus s 4g.
Have you tried navigating to the folder where recovery.img is located and typing "fastboot flash recovery recovery.img"
Sent from my Nexus S using XDA App
What do mean navigating? Typing the directory path?
Sent from my Nexus S 4G using Tapatalk
I think he means typing this first:
cd c:\android-sdk\platform-tools\
So how would I type this? I don't I am... please elaborate. Thank
Sent from my Nexus S 4G using Tapatalk
What operating system are you using? Windows?
Sent from my Nexus S using XDA App
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Harbb said:
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
wow. i did everything mentioned. i even redownloaded the recovery image. and i still get cannot load error. i even did it where i renamed it and left it alone the way it was typed
Is your bootloader unlocked? Also, fastboot devices shows a serial number right?
Harbb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
yup its unlocked.
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
let me give this a tried
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow this did it for me... i dont understand bc i typed
fastboot flash recovery rec(tab)
fastboot flash recovery recovery.img.img and i hit enter and it flashed. weird. but thanks dude i greatly appreciate it for sticking it out with me.
Wonderful. You probably have "hide file extensions for known file types" checked. So when you downloaded the original, it ACTUALLY had a .img on the end of it already (which windows hid from you). Windows, unlike unix, cannot differentiate files based on their header, but instead relies on a useless extension in the file name of all places (ie, .img, .mp3 and .jpg at the end of the filename).
And noo problem mate, happy to help.
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Techno Droid said:
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Click to expand...
Click to collapse
weird. i downloaded superuser from the their website and flashed. it didnt show. so i downloaded it from the market and tried running an app that requires su permission and it worked. am i missing something here? why did this work that way?
Flash this su.zip file. There was an older su version that automatically accepted any su access because it wasn't compatible with ICS yet.
thanks. it feels good to finally be rooted. i was stock for 2 days.. lol thanks
cannot load recovery.img
Thanks. the TAB autocomplete worked. I had forgotten about the additional file extension. gotta change that setting. Thanks again
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow, thanks man, you made my day, was about to throw the phone from anger. thanks a million man thank you.
Removed all my Dropbox links because they disabled my account due to too much traffic, if you guys want them back please consider donating a buck or two for a Mediafire Pro account...I didn't develop this, just getting the word out that's it's officially available for the Nexus 7. You can either install the "normal" version or touch version from ROM Manager
UPDATE 11/16 new version posted by Koush 6.0.1.9
CWM Regular
CWM Touch
Here is the CWM ZIP by osm0sis:
Touch 6.0.1.9
Regualr 6.0.1.9
You NEED an unlocked bootloader in order to flash this check this thread on how-to unlock/root etc Nexus 7 Toolkit
If you just want to apply an OTA update and you haven't got it, you can do so by booting into CWM without installing it or having root.
first download and save OTA files from OTA 4.1.1 files and save to your /sdcard
then use
./adb reboot bootloader
./fastboot boot recovery-clockwork-touch-6.0.1.9-grouper.img
select install zip from sdcard
toggle signature verification and make sure it's disabled
select the file you downloaded earlier and install
reboot and you will be updated
Click to expand...
Click to collapse
If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p
now use
./adb reboot bootloader
./fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
./adb reboot
Click to expand...
Click to collapse
You now have CWM installed.
I'm not responsible if you brick your tablet, it blows up mid flash etc
Make sure you know how to use ADB and have the SDK installed, you need that in order to do all of the above steps
Also make sure you have the recovery files saved to /sdk/platform-tools and also fastboot.exe has to be there also
Any commands that start with ./ are for linux/osx...just remove those when using windows
Click to expand...
Click to collapse
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
** edit 7/21/12**
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf
Feel free to mirror!
Sent from my Nexus 7 using xda app-developers app
Flashing when I get home thanks.
Sent from my Galaxy Nexus using xda app-developers app
I flashed this from rom manager and so far have not had any of the problems I have had in some of the interim CWM's like inability to delete back ups or mounting system.
hey dude it's 6.0.0.6 not 6.0.6
mrich137 said:
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Shano56 said:
hey dude it's 6.0.0.6 not 6.0.6
Click to expand...
Click to collapse
oops, typo...thanks, I will fix it now
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
It works as long as you're connected to a computer, so you can access recovery from bootloader you just need to be hooked to a computer.
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
JoeM01 said:
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
camblue said:
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
Click to expand...
Click to collapse
Flashed fine here also. Works without flaw so far.
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
Did you install the ota after you rooted and installed the recovery? I soft bricked too and I think that was the reason why. Something about the ota overwrote the recovery partition. Best thing to do is download ROM manager and click the first option to flash cwm. Then click the next button to boot into recovery. Then just flash the zip I posted to upgrade to touch.
**edit** just tried to boot into recovery from the boot loader and got stuck at the Google screen too. Holding all three buttons rebooted and started up as normal. Maybe the boot loader boot into recovery is pointing to a different partition for some reason?
Booting into recovery from ROM manager works though. That's how I've been getting in.
Sent from my Galaxy Nexus using xda app-developers app
thanks for the heads up
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
What did you try?
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
BennyJr said:
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
Click to expand...
Click to collapse
camblue said:
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
Click to expand...
Click to collapse
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Bootloader = fastboot. Any adb commands wont work
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
Sent from my Galaxy Nexus using xda app-developers app
Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
Sent from my Nexus 7 using xda premium
So today i decided to update my version of twrp to the latest:
so i entered fastboot -i 0x0B05 flash recovery twrp.blob and wanted to change twrp to something else but cmd decided to start flashing it without pressing enter (it just started flashing when i pasted the code) i was like holy poop and closed the cmd window when it said sending recovery (i was trying to flash a htc desire c twrp) so i thought yeah... i just bricked my tablet and i typed fastboot reboot-bootloader it came back into the bootloader and: no unrecoverable bootloader error so i flashed the good twrp and everything is working (my tablet didn't even mind the wrong recovery)
is this normal or am i just lucky?
Very Lucky!
Sent from my GT-I9300 using Tapatalk 4
Sounds like the command you copied and pasted had a line feed on the end of it so it also pasted the "enter" character. Easy to do.
sbdags said:
Sounds like the command you copied and pasted had a line feed on the end of it so it also pasted the "enter" character. Easy to do.
Click to expand...
Click to collapse
Agreed.
And for everyone else, next time you flash something wrong in fastboot. You can easily override it by flashing the proper file WITHOUT rebooting. Once you reboot it applies the stuff you just flashed. But as long as you don't leave the bootloader, you're gonna be OK
Sent from my SGH-M919 using xda premium
No I rebooted my tab after the bad flash!
Sent from my HTC Desire C using xda app-developers app
noahvt said:
No I rebooted my tab after the bad flash!
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
since it only was a broken recovery, fastboot option should not be broken. (flashing wrong recoveries during a nighttime session - A700 twrp2 flashed on tf300 and so on - wondering why the heck nothing worked is easily remedied once your brain catches up and you flash the correct twrp2 again )
cheers
-Buster