Database Users

[Q] Can't get into recovery

Hi
I have a little problem with flashing the custom recovery image to my phone. i searched the forum, googled, and nothing seems to work, either I get an error or the guides simply doesn't work.
I don't consider myself a noob, i rootet my Desire using ADB, and my new DHD, but my fathers HTC Magic is causing me some problems.
I followed this guide, and is now rootet. I tested, and rooting is OK.
http://forum.xda-developers.com/showthread.php?t=756918
When i use this command
adb push C:\roottools\6.35Radio\Recovery-RA-hero-v1.6.2.img /sdcard
to push the custom recovery image to the phone, the command repeat itself, which should mean, that all went well.
I read that the phone itself could reflash the old recovery sometimes, so I tried this as well
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mv /sdcard/recovery.img /system/recovery.img
but get the error:
failed on '/sdcard/recovery.img' - cross device link
I tried other codes I got from old replies in the same thread as well, and still no luck.
Then I decided to get ROM manager, and flash ClockWorkMod through that, but it's not available on the market (can't find it)
Then I found the rommanager.apk and copied it to sdcard and tried to install it through apk manager, but the program isn't supported.
Now, what should I try yo get into recovery?
I've run out of ideas. please help.
Here's the info i got from HBOOT:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0009 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Dec 8 2009, 17:38:48
HBOOT
EDIT: I noticed that S-ON is... ON... and I now, that this is set to off on DHD... dunno what it is, but could this be the reason?
Also... what is the correct way to get into recovery? When I press VOL DOWN + POWER BUTTON, i get into HBOOT, I press backkey to enter fastboot, and press ANSWER CALL button... screen turns black, and phone restarts... is this wrong?

SOLVED
Found out I needed to press POWER button + HOME key instead of, to get into custom recovery why can't they make it the same on all phones

[Q] 1.34 rooted and S-off.. Need to go back. How ?

So i've rooted my Desire Z with the stock rom of v. 1.34 .. I think i need to send it back for repairs since my green led is not working anymore.. But before i can do that i want to unroot the phone.. can someone here explain to me how i do it ? Im a total retard when it comes to this.. Sometimes i even wonder how the heck i managed to root the device
EDIT: Forgot to mention that i've applied a OC kernel.. !

No one ?
5char

I reckon ppl are a bit cautious in giving advice as there have been a few issues.
Lets start with which method did you use to root and s-off?

wileykat said:
I reckon ppl are a bit cautious in giving advice as there have been a few issues.
Lets start with which method did you use to root and s-off?
Click to expand...
Click to collapse
Thanks man.. Glad you want to help ..
I wanted to able to use this kernel, so i followed the suggested rooting guide from that thread.. Which i believe is this
I just want to make sure i do everything right you know

Da9L said:
So i've rooted my Desire Z with the stock rom of v. 1.34 .. I think i need to send it back for repairs since my green led is not working anymore.. But before i can do that i want to unroot the phone.. can someone here explain to me how i do it ? Im a total retard when it comes to this.. Sometimes i even wonder how the heck i managed to root the device
EDIT: Forgot to mention that i've applied a OC kernel.. !
Click to expand...
Click to collapse
Hi !
I need to know 2 things before I can help you:
1. Did you install the engineering hboot?
You can check this by booting into fastboot mode:
- Shutdown the phone
- Press and hold the touchpad-button and hold it while pressing the Power button.
-> On the screen with the surfing androids the first lines contains either SHIP or ENG. If you have ENG then you installed the engineering hboot.
2. Did you use gfree to achive radio S-OFF
You can check this by using the gfree_verify procedure - see http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#VERIFY_.28using_.22gfree_verify.22.29
if you have @secu_flag = 0 then you are radio S-OFF if @secu_flag = 1 you are radio S-ON.
Please check this and post your results, then i can post your way to go.
have fun - Guhl

guhl99 said:
Hi !
I need to know 2 things before I can help you:
1. Did you install the engineering hboot?
You can check this by booting into fastboot mode:
- Shutdown the phone
- Press and hold the touchpad-button and hold it while pressing the Power button.
-> On the screen with the surfing androids the first lines contains either SHIP or ENG. If you have ENG then you installed the engineering hboot.
2. Did you use gfree to achive radio S-OFF
You can check this by using the gfree_verify procedure - see http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#VERIFY_.28using_.22gfree_verify.22.29
if you have @secu_flag = 0 then you are radio S-OFF if @secu_flag = 1 you are radio S-ON.
Please check this and post your results, then i can post your way to go.
have fun - Guhl
Click to expand...
Click to collapse
1. Nope it shows SHIP
2. Gave me this output (My phone has allways been sim unlocked however.. Bought it without contract!)
Code:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK

Da9L said:
1. Nope it shows SHIP
2. Gave me this output :...
gfree verify_secu_flag returned:
@secu_flag: 0
Click to expand...
Click to collapse
!!! WARNING FOR OTHERS - DO NOT DO THIS IF YOU ARE NOT RADIO S-OFF AND HAVE THE ENGINEERING HBOOT INSTALLED !!!
OK this is good because as you don't have the eng-hboot installed we can safely flash the full stock rom and i assume that you have a custom kernel and a custom recovery installed that we need to get rid off.
Before i go into details of commands i would like to give you the principle procedure:
1. reinstall the stock firmware by copying a PC10IMG.zip to /sdcard and then boot into hboot and let it install the complete stock rom.
2. temproot again using psneuter
3. restore the backup of your partition 7 using gfree 0.4
So what we need is:
- a stock rom from here http://www.multiupload.com/GH26HXLLES
- psneuter from here http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/psneuter/psneuter.zip
- gfree 0.4 from here http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_04.zip
You need to make sure that this PC10IMG.zip really is your stock version (maybe find yours somewhere else)
1. Installing the stock rom:
connect the phone to usb.
download the file and rename it to PC10IMG.zip and put it to the root of your sdcard using:
Code:
adb push PCIMG10.zip /sdcard/
shutdown your phone.
boot into hboot by holding the <Vol-Down> key while you press <Power> to boot.
hboot (white screen with surfing androids and the word HBOOT in blue) will scan for the file PCIMG10.img and load it.
Then you can use <Vol-Up> to start the process. In the middle of the process the screen will get dark for some seconds and then it will start again -> don't panic wait until it is completely finished.
When done - reboot
2. Temp-root using psneuter:
On the phone go to Settings - Applications - Development and enable USB debugging again.
Unzip the psneuter.zip, install and execute psneuter on your phone:
Code:
adb push psneuter /data/local/
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
3. use gfree to restore your partition 7 backup
Unzip gfree_04.zip and install it on the phone
Code:
adb push gfree /data/local/
adb shell chmod 777 /data/local/gfree
3.a When you used gfree to get radio s-off it created a backup of the partition named /sdcard/part7backup-<time>.bin (replace <time> with the time number). We will restore this file now.
Get a root shell:
Code:
adb shell
The prompt should be # now
Execute gfree to restore the backup (in the root shell) - replace <time> with your time number in the following command.
Code:
/data/local/gfree -r /sdcard/part7backup-<time>.bin
3.b Alternative: (if you don't have your partition 7 backup anymore - don't do if you did 3.a):
You need to know the CID that your phone had originaly, it could be HTC__001
Excecute gfree to set S-ON and CID:
Code:
/data/local/gfree -s on -c HTC__001
4. clean up (still in the root shell):
Code:
rm /data/local/psneuter
rm /data/local/gfree
rm /sdcard/PC10IMG.zip
So now you are back to stock.
You might want to boot to hboot again and use "FACTORY RESET" to wipe data and cache.
And you might format the micro-sd card before you return the phone.
I hope this is it (written without a phone so there might be typos)
have fun - Guhl

Wow guhl99 that is really really helpfull ! I appriciate it so much! Im gonna try it later today ..
However i dont think i got the backup of that partition.. Must have deleted by mistake for some reason
Is there anyway i can find out what CID my phone had originaly ?
EDIT: Another question.. What would happen if i just acceptet the OTA upgrade ? Wouldn't that unroot and s-on my phone ?

Da9L said:
Wow guhl99 that is really really helpfull ! I appriciate it so much! Im gonna try it later today ..
However i dont think i got the backup of that partition.. Must have deleted by mistake for some reason
Is there anyway i can find out what CID my phone had originaly ?
Click to expand...
Click to collapse
Hi !
Welcome, i think it was time to summarize this once. And as I am constantly going back to stock to test some exploits and then reroot i have some practive.
Yes there is. The CID is also stored in the first 8 bytes of partition 17 - the misc partition - (and no one knows why).
So you can to the following (in a adb root shell)
Code:
dd if=/dev/block/mmcblk0p17 bs=8 count=1 2>/dev/null
The first 8 characters of the output should be your CID (the # behind it is the prompt for the next command as you do not receive a new-line by the command above)
have fun - Guhl

Da9L said:
EDIT: Another question.. What would happen if i just acceptet the OTA upgrade ? Wouldn't that unroot and s-on my phone ?
Click to expand...
Click to collapse
Sorry I did not see this question.
It will unroot but will NOT S-ON the phone.
But something really nasty will happen:
- It will install a radio firmware version that prevents gfree from dropping the write protection of the emmc chip for the radio configuration partition 7. And because of this you are not able to set S-ON again or set your CID back (or restore your partition 7 backup).
You would then have to downgrade the firmware again to 1.34 (using a procedure that is documented in this forum) and is even more complicated. And after the downgrade (that includes installing the stock rom as i described above) you would have to continue at point 2 of my description above.
SO DO NOT ACCEPT THE OTA (it would not brick things but needs another 2 steps).
have fun - Guhl

Guhl, could you use Gfree to restore your backup (or go S-ON) first while you were still rooted? Then with S-ON, use the PC10IMG.zip to restore back to the shipping ROM (which should work, assuming the zip to be signed).
Just wondering if that extra step of temp rooting before using gfree is necessary...

ianmcquinn said:
Guhl, could you use Gfree to restore your backup (or go S-ON) first while you were still rooted? Then with S-ON, use the PC10IMG.zip to restore back to the shipping ROM (which should work, assuming the zip to be signed).
Just wondering if that extra step of temp rooting before using gfree is necessary...
Click to expand...
Click to collapse
Hi !
You are absolutely right, you could do it this way.
The reason why i always remove s-on as the last step is just to have the system and recovery partitions write enabled till the last step.
So if anything goes wrong you still have options till the end.
But if you don't need that extra security you could do it your way.
have fun - Guhl

Old Dog, New Tricks, Need a Little Assistance

My goal: to install a CyanogenMod or custom rom, and flash a custom recovery, along with something called an "engineering SPL".
Howdy all! You may or may not know me from the Atrix forums, but I'm an avid supporter of xda and have been a member for six months. Recently, I rediscovered an old Mytouch 3g (32B) that my mom had let me have a long while back. Here's what I've got so far, and what I need help with:
Yesterday I spent 14 hours combing the forums and google searching. I am using this guide to basically wipe and start fresh. http://forum.xda-developers.com/showthread.php?t=807899 I got all that DONE, starting with the sapphire and upgrading to 1.6 then installing the SPL and finally to froyo 2.2.1. (Now keep in mind, I have no data plan on the sim card inserted into this phone, so I have to use froyo in order to skip the google account setup.) When I start my phone using back button + power, it shows:
sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP30000)
RADIO-2.22.27.00
Oct 21 2009, 22:33:27
Here's my question. I've tried multiple times to flash an engineering SPL and custom recovery. I have used SuperOneclick to root, and it worked fine. But I can't use any of the methods for flashing a custom recovery from here http://forum.xda-developers.com/showthread.php?t=530492
because I can't install an engineering SPL (from stock recovery it tells me it isn't signed), don't have access to fastboot (because no SPL), it doesn't work right when running from terminal (tells me can't find flash_image), and to use it via ADB it says I need a custom recovery, which is what i'm TRYING desperately to get lol. I'm not sure where to go from here, I've tried Clockwork Mod recovery and it flashes fine. Then I hit reboot into recovery and get rebooted into stock recovery. So....I dunno what to do at this point. I would appreciate any help I can get, I've spent a LOT of time on this already lol.

Mmm... I notice that is no manual to use flash_image, and this section is not easy to explain...
Note: Many official roms do not have binary flash_image. But it can be installed manually.
1. Download this: http://www.2shared.com/file/sfPPeA5G/flash_image.html
2. Download custom recovery according radio
- AmonRa 1.7.0 G - for radio 2.22.XX.XX
- AmonRa 1.7.0 H - for radio 3.22.XX.XX
- AmonRa 1.6.2 H patched by cursordroid - for radio 6.35.XX.XX
3. Copy flash_image and recovery to root of sdcard
4. Make sure Android SDK Tools configured and run to enter into terminal
Code:
adb shell
5. Copy flash_image into the phone
Code:
cat /sdcard/flash_image > /data/local/tmp/flash_image
6. Change permissions
Code:
chmod 755 /data/local/tmp/flash_image
7. Flash recovery
Code:
/data/local/tmp/flash_image recovery /sdcard/recovery.img
8. Turn phone off, then turn on by pressing Home + Power to check recovery (custom recoveries show their versions in bottom line)

Thank you soooo much! I was thinking "oh no one will answer me in such an old forum I'm dooomed!" But I was wrong! Thanks again this worked like a charm, I'm now running Cyanogenmod 6.1 on my mytouch 3g! I'm going to be looking around for the fastest ROM I can find since this only has 192 mb of RAM lol. Thanks again!

5[Strogino] said:
Mmm... I notice that is no manual to use flash_image, and this section is not easy to explain...
Click to expand...
Click to collapse
4th thread in the general section :0)
It's sticky also...
http://forum.xda-developers.com/showthread.php?t=756918
110000+ views....

MT3g Sapphire 2.2.1 HACK YEt?! (Recovery, rom flashing)

I have a mytouch 3g its the 1st version I'm guessing (no head phone jack)
Hboot =
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP30000)
CPLD-10
RADIO-2.22.28.25
OCT 21 2009 ,22:23:27
I tried flashing sappimg nbh and zip nbh says main is older
Zip seems as it flashes completes and go str8 back to hboot like nothing happened.
Tried to back up rec but says backup failed
And will not do anything with rom managers, says flashed recovery complete but in recovery mode shows a triangle.
Also 1 click works, su shows up in terminal..
I seen that this new update doesn't work yet
I tried searching but nothing. So if I just have to wait just say so.
But if something comes out please let me know.
And yes yes I know I shouldn't have updates now, but I didn't know before hand (obviously).
So thanks ahead for responses.
Sent from my HTC Vision using XDA App

Man, what exactly do you want? Custom recovery? There is sticked topic by mumilover. He wrote how to flash manually
http://forum.xda-developers.com/showthread.php?p=7707672
Sent from my A7-040 using Tapatalk

well that doesnt work... it just keeps saying failed when i try ... and i did root and tried to flash recovery via rom manager says flased successful but when i recovery boot it shows a triangle...
how can i get s-off on this phone.. its running stock 2.2.1

and as he says "This guide is confirmed to work with Rogers 2.1 update!
It will not work with the new 2.2.1 update" so im basically asking is ther any one that knows if a way around 2.2.1 yet?
If not thanks for trying/looking if so HELP! Plz!
=)

homeboy773 said:
well that doesnt work... it just keeps saying failed when i try ... and i did root and tried to flash recovery via rom manager says flased successful but when i recovery boot it shows a triangle...
how can i get s-off on this phone.. its running stock 2.2.1
Click to expand...
Click to collapse
Okay, I'm not going to get into why you can't flash a custom recovery, but if you have "Root" then just do this . . .
http://forum.xda-developers.com/showthread.php?t=1428838 : My Unroot/ReRoot Guide .
::----:: You might run into an issue where you can't change your recovery. . .Heres the Fix.
1.) Put Your Recovery.img on your SDCard : (CW Recovery)Click the above link..
2.) Put flash_image on your SDCard : Click the above link.
3.) Open up terminal/adb (which ever you prefer) :v:
3.a)
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
or you can do it from the terminal emulator app like i did . .
(Skip the adb shell part if you do)

GeEazy said:
Okay, I'm not going to get into why you can't flash a custom recovery, but if you have "Root" then just do this . . .
http://forum.xda-developers.com/showthread.php?t=1428838 : My Unroot/ReRoot Guide .
::----:: You might run into an issue where you can't change your recovery. . .Heres the Fix.
1.) Put Your Recovery.img on your SDCard : (CW Recovery)Click the above link..
2.) Put flash_image on your SDCard : Click the above link.
3.) Open up terminal/adb (which ever you prefer) :v:
3.a)
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
or you can do it from the terminal emulator app like i did . .
(Skip the adb shell part if you do)
Click to expand...
Click to collapse
this is the guide for the mytouch 3g 1.2(32A). I want a guide for the 32B on 2.2.1

playerpatrick said:
this is the guide for the mytouch 3g 1.2(32A). I want a guide for the 32B on 2.2.1
Click to expand...
Click to collapse
it doesn't matter. . . it's not like your flashing a Rom, or a spl/radio .ect its a recovery its all the same steps. . .

same here
Hi
I have the same hanset, hardware, and software.
Now I happen to be going through the same problem flashing a recovery. Just wanted to know if the unroot/ reroot method worked for you?
Thank you.

is there a way to root a stock 2.2.1 mytouch 3g? ive been searching around the forums and i can only find tutorials for pre-2.2.1

iamwhoamnot said:
is there a way to root a stock 2.2.1 mytouch 3g? ive been searching around the forums and i can only find tutorials for pre-2.2.1
Click to expand...
Click to collapse
SuperOneClick can do root even if 2.2.1

can u post a link for SuperOneClick for 2.2.1?

Here at xda: http://forum.xda-developers.com/showpost.php?p=8532790&postcount=1
Before getting root and installing custom recovery it is strongly recommended do wipe data / factory reset. Make sure you have backup.
Sent from my A7-040 using Tapatalk

rooting mytouch 3g
i have a mytouch 3g with google, has stock 2.2.1 on it, i finally got the computer to recognize it and now i can get to the SD card thru my computer, but i can't find any way to root this phone at all, i keep seeing that superoneclick method works but i can't get it to work for me, i hook the phone up, push root and it gets halfway thru the steps and stops, what am i doin wrong? do i need a certain exploit set up in superoneclick?

Supeoneclick creates log on screen. Go to pastebin.com, post log there and give me link. I guess, you have problem 'no enough space'...

Cant flash recovery

Few days ago I messed the phone little bit, Magic 32A and I had to flash sappimg.nbh from fastboot.
Before that phone was S-OFF with 3.22 radio and 1.33.2010 SPL.
Right now is running Android 1.5, its rooted using UniversalAndroot and right now I cant flash recovery from Rom manager. I get error: "an error occurred while attempting to run privileged commands".
Current:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006
CPLD-12
RADIO-2.22.19.26I
What I want? Want to get on old situation with 3.22 radio, 1.33.2010 spl and if possible s-off.
Right now Im in mess cause I dont know what tutorial/source to follow. Its been two years since I have done that, besides I didnt had to do goldcard back then.
Can anyone please help cause Im really confused.
thanks

stifler05 said:
Few days ago I messed the phone little bit, Magic 32A and I had to flash sappimg.nbh from fastboot.
Before that phone was S-OFF with 3.22 radio and 1.33.2010 SPL.
Right now is running Android 1.5, its rooted using UniversalAndroot and right now I cant flash recovery from Rom manager. I get error: "an error occurred while attempting to run privileged commands".
Current:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006
CPLD-12
RADIO-2.22.19.26I
What I want? Want to get on old situation with 3.22 radio, 1.33.2010 spl and if possible s-off.
Right now Im in mess cause I dont know what tutorial/source to follow. Its been two years since I have done that, besides I didnt had to do goldcard back then.
Can anyone please help cause Im really confused.
thanks
Click to expand...
Click to collapse
ehhh, I'm kinda lost my self but my advice would be to find a way to upgrade to 2.2.1 and do superoneclick root, then use rom manager. . .
(or "something that just came to mind": Download Terminal Emulator from Android Market.)
(and manually flash a custom recovery. . . If you do have root then "su" should work flawlessly)
(Take a look at my post " http://forum.xda-developers.com/showthread.php?t=1428838 " and download the needed files to flash your recovery)

GeEazy said:
ehhh, I'm kinda lost my self but my advice would be to find a way to upgrade to 2.2.1 and do superoneclick root, then use rom manager.
Click to expand...
Click to collapse
BTW, flashing recovery will only stick if s-off is shown or engineering ROM is installed (s-on in this case is fine). Don't waste your time with superoneclick. It will be more trouble than its worth if your going through different versions.
"I didnt had to do goldcard back then."
I have never had to do a goldcard. Barely even know what it is.
You can flash recovery from any version (again provided the phone has either s-off or an engineering ROM installed):
Download and install es file explorer from marketplace (or anything that can be used to install apps)
Download and install busybox from marketplace
Copy and install Univeral Androot to phone Link -> http://bit.ly/9wAKC5 (taken from Link -> http://forum.xda-developers.com/showthread.php?t=807899 )
Install Universal Androot with es file explorer
RUN UNIVERSAL ANDROOT
It should be SET TO 1.5/1.6 already THEN
touch GO ROOT
Wait till its fully installed THEN
Install busybox by:
RUN BUSYBOX APP
Accept superuser request (If it doesn't appear reboot phone and try again OR busybox install will fail).
(Install of newest busybox version is OK)
INSTALL TO /system/bin is OK
TOUCH the X
TOUCH INSTALL
It should say successful
Download Android Dev kit
http://developer.android.com/sdk/index.html
Download JavaJDK -64bit is fine for 64bit OS
http://www.oracle.com/technetwork/java/javase/downloads/index.html
install JavaJDK THEN
install dev kit
RUN android sdk manager
install google drivers & platform tools. Unselect anything else that might be defaulted as selected.
Enable usb dev mode on phone and attach phone to PC
Run windows command prompt in admin mode
Type "CD C:\Program Files (x86)\Android\android-sdk\platform-tools"
Type "adb devices" (Device check. The phone will show up if everything is properly working OR no device is listed if not. If no device is listed then phone drivers are not working correctly OR phone is not in USB dev mode OR not attached to PC)
[FILES NEEDED:
A. Download cm 4.2.15.1 and extract flash_image from /system/bin/ ||link ->
http://goo.gl/5NPE. (Taken from link ->http://forum.xda-developers.com/showthread.php?t=807899)
B. The recovery you will be using. I recommend Amon RA. Link -> http://forum.xda-developers.com/showthread.php?t=530492 || Download the version you need! (for my t-mobile mytouch 3G 32b I use "recovery-RA-sapphire-v1.7.0G.img. You have a 32a so for you it looks like you need the "recovery-RA-sapphire-v1.7.0H.img" BUT DOUBLE/TRIPLE CHECK THAT. Not my fault if that's the wrong one. ]
rename the recovery-RA-sapphire-*.img to recovery.img
Either copy flash files directly to SDcard OR
place files on hard drive at c:\
Type "adb push c:\flash_image /sdcard/"
Type "adb push c:\recovery.img /sdcard/"
THEN Type (after each line press enter. Example: type adb shell then press enter.)
adb shell
su (if recently rooted then... touch allow on phone)
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
(taken from Link -> http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/)
(May or may not need to CLICK OK TO INSTALL ON PHONE. Or was I seeing things?)
Finally, boot phone into and enjoy the new recovery
If you need to do it again, keep the programs installed and put the files in a directory so you have easy access and know they work. Its MUCH faster the 2nd+ time.
***If you mess up your phone while trying to do any of this, that's NOT my fault.