Database Users

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.

you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.

when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.

unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

[Q] MT3G bad recovery flash, stuck

Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.

truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?

I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?

Do you have fastboot. If so you can flash recovery from there.

kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.

truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.

Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.

truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.

Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.

truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.

Problem recovery flashing htc magic

I tried flashing amon ra 1.7 on my 32a htc magic which is rooted using androot using terminal emulayor app.But now when I try to go to recovery pressing home and power I m stuck on a screen showing a phone and a triangle next to it with a !.
Anybody else facing this problem?

it looks like you're back to the old days method...
I tried this on my Desire, and i needed to get "rooting tools"/"root-tools"
within this folder is several files. locate win-recovery.bat and click it.
This pushes you to the custom recovery menu
There's probably a command you can type in the command prompt of your computer, but Im a bit unsure if what it is... but its probably
fsatboot boot "recoveryimage.img" (recoveryimg being the name of the img-file)
you need sdk tools for that, and put the recovery image in the tools folder.
when in command prompt you need to be located in that tools folder to, as you write the commands

shaheemadrid said:
I tried flashing amon ra 1.7 on my 32a htc magic which is rooted using androot using terminal emulayor app.But now when I try to go to recovery pressing home and power I m stuck on a screen showing a phone and a triangle next to it with a !.
Anybody else facing this problem?
Click to expand...
Click to collapse
What you see is stock recovery.
You attempt to flash custom recovery did not succeed!
Try it once more...
Maybe follow my guide (check my signature) and do step 5/7 only.

larsn84 said:
fsatboot boot "recoveryimage.img" (recoveryimg being the name of the img-file)
Click to expand...
Click to collapse
That is a fastboot command and not an "internal" command.
For this to work you have to be in fastboot mode!
That command will actually try too boot the recovery image and not to flash it!
It is also disallowed from all newer perfected spls.
The guy wants to flash the recovery using an terminal emulator and hence must use internal commands.
The "flash_image" binary combined with the right recovery image is what he have to use.
larsn84 said:
I tried this on my Desire, and i needed to get "rooting tools"/"root-tools"
within this folder is several files. locate win-recovery.bat and click it.
Click to expand...
Click to collapse
Never do the above unless you are sure that the bat file only does what you say it will.
It also for the Desire device which has a completely different layout and procedure.(Nand-lock and all that!)

Flashboot or recovery?

Hello everybody!
Sorry to be the noob, but one must start somewhere before being a decent user!
I give you quickly the background: First I flashed the phone with the European version rom with flashboot in it.
Then I installed Froyo by Ankuch and Quarx through flashboot
And after this I installed Gingerbread by Mur4ik thanks to the exe made by eoghan2t7 in flashboot mode.
I read many times about clockwork recovery, however I do not have the impression to have came accross a specific version of the firmware such as the European version rom. Would it be by any chance included in Cyanogene Android by Mur4ik? I don't think so unfortunately!
Other question: What is best, recovery or flashboot? Apparently recovery is safer, and it would not be a bad thing given my computer savviness level ahah!
Thanks in advance!

Nevermind, I figured it out, if somebody needs help and I can be useful I would be more than happy to explain how I did it despite my weak level in computers.

Or I can explain it here for you, Fastboot is apparently more easier, if you had a usb connector from your phone to comp, because, you're gonna connect it to the PC anyway, so why not just do it on the comp?

Frandroido said:
Hello everybody!
Sorry to be the noob, but one must start somewhere before being a decent user!
I give you quickly the background: First I flashed the phone with the European version rom with flashboot in it.
Then I installed Froyo by Ankuch and Quarx through flashboot
And after this I installed Gingerbread by Mur4ik thanks to the exe made by eoghan2t7 in flashboot mode.
I read many times about clockwork recovery, however I do not have the impression to have came accross a specific version of the firmware such as the European version rom. Would it be by any chance included in Cyanogene Android by Mur4ik? I don't think so unfortunately!
Other question: What is best, recovery or flashboot? Apparently recovery is safer, and it would not be a bad thing given my computer savviness level ahah!
Thanks in advance!
Click to expand...
Click to collapse
I know it's offtopic, but can you send a backup from your recovery image to me (or have you flashed one with clockworkmod already)? Cause i haven't fastboot AND clockworkmod anymore after a little expiriment
Sent from my GT540 using XDA App

Thank you AntonJrL for your support! Now I thing I got it though.
The line between fastboot and recovery was blurry for me, I thought it was a different firmware than the one I installed for fastboot.
Now I figured out that the recovery mod was inside the pack with the 2.3.3 rom and I flashed it on my phone. Now I can reboot in recovery mod so I will have to worry less about bricking my phone
Jasper580, do you want the file for flashing recovery in your phone?

Hi, i prefer fastboot because is easier. You just have to download the ROM in your puter then plug your phone in fastboot mode,copy the .img files into /tools folder then open the cmd type few codes and voila you have flashed your phone.
cheers!

I too prefer fastboot over recovery,
I've never had a problem with fastboot but in recovery I get MD5 mismatch.
Sent from my GT540 using XDA Premium App

Recovery is easier, but in fastboot you dont have problems like old recovery, md5 mismatch etc
Sorry for my english

@partyk95juve
i also think so, but i've never done the fastboot yet
so i will try it the next week .... and i hope i will not crash my phone

hey mimm.m nice to see you here
it's me michabilbang.de
back2topic:
i've done both ways, via recovery mod at my first time with swiftdroid 1.8.
If you restart your phone in recovery mod or fastboot, it's not much difference, at recovery you do it with your phone, at fastboot via pc.
But i prefer fastboot, i just have to run a bat file and it puts all on my phone.

i use fastboot but i dont like it, ive bricked my phone a few times with it.

recovery is very easy! and not need a computer with full driver

Hello,
anybody can tell how to install the recovery in GT540?

tubekeeper said:
Hello,
anybody can tell how to install the recovery in GT540?
Click to expand...
Click to collapse
Fastboot.exe flash recovery nameofthefile.img
In cmd ofcourse!
Sent from my GT540 using XDA App

Recovery Doesn't delete files or apps.
Fastboot Does But theres a way to make it not to delete which I didn't Try yet.

Fastboot VS Recovery
Fastboot is easy but i needs the computer everytime you want to change ROM.
Recovery on the other hand also needs your computer to install clockwork however once installed you have the convenience of changing your ROM as often and anywhere you like as long as you have the .zip file on your SD card.

can anybody tell me from where i can get clockwork mod image which can i use with rom manager.
Sent from my GT540 using XDA App

recowery. i tried with fastboot and all time i ger too many links error.

http://forum.xda-developers.com/showthread.php?t=1032888
fastboot tool...much easier

[Q] clockworkmode ... where is?

i have new problem. this time,i try to change clockwork mode. unsuccessfully. things go like this ...try to flash some but no luck. than i try fastboot commander and problem is there appeared.whenever I try to get in rocovery,transferred me to fastboot. cant geat clockworkmode. rom manager shows that i use clockworkmode 3.0.0.6 but i just cant get to it ... some advice what to do?

The recovery from ROM manager is a temporary one, just stored on your sdcard. But you cannoy access it without rom manager.
I think you have corrupt or missing recovery. You can try to flash a new one with fastboot:
1. Go to the developpers subforum, there is a sticky that gives you the possible recovery's for our wildfire. Pick one and download it. If it is a zip file, extract is so that you have the .img
2. Put that .img in the same folder on your computer where adb.exe and fastboot.exe are. Rename that .img to 'recovery.img' (without ' ofcourse)
3. Reboot your phone in bootloader. Change to fastboot and connect it with your pc
4. Open the command prompt on your computer and browse to the location of fastboot.exe
5. Type "fastboot devices". Your device should be listed now
6. Type "fastboot flash recovery recovery.img" and hit enter. You should now see the process continuing.
7. When done, type "fastboot reboot recovery". Your phone should reboot know, and you should be in recovery!
Good luck,
Erwin.

i try what ypu write ... read a lot from forum. do all what you write but i suppose make some msitake and this dont work. than i combinate recoveryimg. from folder where is ad nad fastboot whit fastboot comader 1.0 and "rebiit succesful". all work fine ... and solve whit this version offmode charging problem. "every day in every way more and more advance!" tnx for help

Markoleti said:
i try what ypu write ... read a lot from forum. do all what you write but i suppose make some msitake and this dont work. than i combinate recoveryimg. from folder where is ad nad fastboot whit fastboot comader 1.0 and "rebiit succesful". all work fine ... and solve whit this version offmode charging problem. "every day in every way more and more advance!" tnx for help
Click to expand...
Click to collapse
I realy do not understand what you say
but I think you got it all working now? I'm glad for you, and hope that I was of any use
Cheers,
Erwin

Haha all work fine. Tnx a lot ervin!
Sent from my HTC Wildfire using XDA App