Database Users

How To Flash an HBOOT image? (yes, i'm rooted)

I'm wondering how to flash back to the stock 1.56 hboot. I was one of those who ran the test-keys RUU about two months ago and have the newer hboot...

You can't, HBOOT's can't be downgraded.

Kcarpenter said:
You can't, HBOOT's can't be downgraded.
Click to expand...
Click to collapse
Not true. As long as you have root you can restore your hboot from 1.47 back to 1.41.
Tested and confirmed that this works on my own phone. I am attaching a .zip that you need to run in recovery. You will be prompted to reboot your phone after this runs, then your hboot will be restored to 1.41.
Props to another user here that put individual pieces of the stock .ruu into flashable zip files.

danknee said:
Not true. As long as you have root you can restore your hboot from 1.47 back to 1.41.
Tested and confirmed that this works on my own phone. I am attaching a .zip that you need to run in recovery. You will be prompted to reboot your phone after this runs, then your hboot will be restored to 1.41.
Props to another user here that put individual pieces of the stock .ruu into flashable zip files.
Click to expand...
Click to collapse
Thank you SO much

That's from the RUU,
now in the newer RUU's the hboot is not a .img file... its a .nb0 or something, so you can't just directly flash it

regaw_leinad said:
That's from the RUU,
now in the newer RUU's the hboot is not a .img file... its a .nb0 or something, so you can't just directly flash it
Click to expand...
Click to collapse
If you had a custom recovery and root (still impossible on official 2.1 ruu build) you could simply flash the older hboot.

danknee said:
If you had a custom recovery and root (still impossible on official 2.1 ruu build) you could simply flash the older hboot.
Click to expand...
Click to collapse
Oh i know, I was just saying that if we theoretically wanted to upgrade our hboot lol

I flashed the hboot update.zip above and tried to RUU back to 1.56 and I got an error.
Error 180 said:
The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse

HeroMeng said:
I flashed the hboot update.zip above and tried to RUU back to 1.56 and I got an error.
Click to expand...
Click to collapse
Are you on a custom rom?
Please post you're build prop in a pastebin link. I'll help you out.

Now that you have stock hboot use method one here >> http://forum.xda-developers.com/showthread.php?t=657086.
Otherwise, use method two from that same thread.
For your sake I hope you don't end up with an official 2.1 ROM phone, if you are ruu'ing to send the phone in for your battery issue.

danknee said:
Now that you have stock hboot use method one here >> http://forum.xda-developers.com/showthread.php?t=657086.
Otherwise, use method two from that same thread.
For your sake I hope you don't end up with an official 2.1 ROM phone, if you are ruu'ing to send the phone in for your battery issue.
Click to expand...
Click to collapse
Same here... If I do end up with a 2.1 phone, I'll be stuck unrooted till October.

regaw_leinad said:
Are you on a custom rom?
Please post you're build prop in a pastebin link. I'll help you out.
Click to expand...
Click to collapse
http://pastebin.com/8i65vXCL
Thanks!
Evidenced by the build.prop, I'm on DarchDroid.

HeroMeng said:
http://pastebin.com/8i65vXCL
Thanks!
Evidenced by the build.prop, I'm on DarchDroid.
Click to expand...
Click to collapse
rename the attchment to build.prop then
Code:
adb remount
adb push build.prop /system
adb sync
adb reboot
then try running the RUU again. This is worth a try.

regaw_leinad said:
rename the attchment to build.prop then
Code:
adb remount
adb push build.prop /system
adb sync
adb reboot
then try running the RUU again. This is worth a try.
Click to expand...
Click to collapse
Ok... thanks for your help. Will try again... after a nandroid /facepalm

HeroMeng said:
Ok... thanks for your help. Will try again... after a nandroid /facepalm
Click to expand...
Click to collapse
All i did was change your build.prop version # down to that of the RUU, since it compares number's w/ the zip it flashes.

regaw_leinad said:
All i did was change your build.prop version # down to that of the RUU, since it compares number's w/ the zip it flashes.
Click to expand...
Click to collapse
Makes sense. If this works, going in for a replacement... might join the fight for rooted 2.1 with you
EDIT: I mean I might HAVE to join the fight for rooted 2.1. Not a choice I want to choose

Same error with your build.prop.

HeroMeng said:
Same error with your build.prop.
Click to expand...
Click to collapse
ok, you know how to get the rom.zip from that ruu?
grab the rom.zip and run the commands like the RUU does. It should give a better error message.... well hopefully lol
grab the rom.zip. put it in your tools folder of your sdk. open a cmd window there.
then type (with your phone plugged in)
Code:
adb shell reboot oem-78
this will boot to a HTC screen
then type
Code:
fastboot flash zip rom.zip
now it should start the sending of the zip to your phone, and it will display everything in the console of the status.
then when it finishes, type
Code:
fastboot reboot
that is the exact same thing as running the RUU. try that and see what error it gives you.

regaw_leinad said:
ok, you know how to get the rom.zip from that ruu?
grab the rom.zip and run the commands like the RUU does. It should give a better error message.... well hopefully lol
grab the rom.zip. put it in your tools folder of your sdk. open a cmd window there.
then type (with your phone plugged in)
Code:
adb shell reboot oem-78
this will boot to a HTC screen
then type
Code:
fastboot flash zip rom.zip
now it should start the sending of the zip to your phone, and it will display everything in the console of the status.
then when it finishes, type
Code:
fastboot reboot
that is the exact same thing as running the RUU. try that and see what error it gives you.
Click to expand...
Click to collapse
Ok... doing it now.

Got an error again... here's what it gave me.
Code:
Kevin-2:tools kevinsimac$ ./fastboot flash zip ./rom.zip
sending 'zip' (104813 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
Kevin-2:tools kevinsimac$ ./fastboot reboot
rebooting...
Kevin-2:tools kevinsimac$

Pre-Rooted HTC, flashed new custom recovery. Cannot boot into.

Hi Guys,
A while ago I used the flashrec app to flash a custom recovery on my unlocked hero which worked well. I'd been using this for ages to flash custom rooted roms etc onto my device.
Today I decided to update the recovery rom to recovery-ra-hero-v1.6.2.img by terminal emulator. (su, flash_image recovery /sdcard/recovery-ra-hero-v1.6.2.img). This didn't work! When I try and enter recovery mode (hold down HOME whilst booting), it freezes.
I can still get into my rooted rom, and it still appears via adb, but I cannot flash any custom recoveries! When I try to flash via adb I get the wonderful 'downloading 'boot.img'... FAILED (remote: not allow)' error.
Any idea how I can flash the recovery?
Cheers,
Matt

Have you tried using Flashrec again?
btdag said:
5. Download this APK and recovery image and save it to your computer:
http://zenthought.org/content/project/flashrec - FlashRec.apk
http://forum.xda-developers.com/showthread.php?t=561124 - Amon_Ra’s Hero Recovery Image
6. Copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
7. Unplug the phone from the computer once they are downloaded to the SD card.
8. Go to the Market and download ASTRO File Manager or any file manager program if you do not already have one.
9. Open the file manager and find the FlashRec apk file and click it and choose open app manager and then install it.
10. When it is installed click Open. Click on Backup Recovery Image and wait for it to finish. If you get "backup failed" response see the text on the right for more details, if the backup is a success carry on to step 11.
a. Installing the correct HTC ROM
Orange UK Users - Please downgrade your ROM version to 2.73.61.5
Generic Hero Users - Please downgrade to 2.73.405.5, or follow the goldcard method if this doesn't work
T-Mobile UK Users – Please follow the "Goldcard" method below
All Other Users - Please follow the "Goldcard" method below​
11. Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-hero-v1.6.2.img
(replace exact name as new versions come out)
Then click on the Flash Recovery Image button and wait for it to finish.
Click to expand...
Click to collapse

I have yes, forgot to say in OP - sorry! It gives the generic 'flashing failed' message.
I think I've narrowed it down to my running hboot 1.76.0007. Am I right in thinking this version doesn't allow non-htc images to be booted?

I wouldn't know about the hboot stuff sorry...
... But I did once read that an older version of Flashrec worked where the latest did not,... worth a try?
http://code.google.com/p/flashrec/downloads/detail?name=flashrec-1.1.2-20090909.apk

Same error - backup failed: could not run command.
I have a android backup which should include the previous recovery image. Is there any way of restoring that from a terminal in the rom or via adb?

I don't think a Nandroid backup covers the recovery... and I wouldn't know about restoring it through adb.
Only other things I can think of are,...
1... Find out how to update recovery through fastboot? ( I once looked into this but dint get v-far)
2... Run a HTC RUU .exe and start from scratch.
I'd go option 2 for ease, 1 if you want to educate yourself.

I think I've already tried number 1 - "fastboot flash recovery recovery-ra-hero-v1.6.2.img" and got an error: "remote does not allow".
Looks like I'm going to have to go down the RUU route. Hopefully I'll be able to restore a recent nandroid backup once it's complete!
Thanks for your help!

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD

hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance

Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery

ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.

WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.

lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is

lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support

Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.

Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.

behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be

ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)

hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?

try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd

ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?

breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.

AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho

I am hanging at booting while trying to do this any ideas?

Can I install Custom ROM on my Legend that already has S-OFF

So here's the thing. I've been trying to downgrade and root my Android 2.2 Legend for many hours now and have been failing as the adb could not push the flash_image and misc1-2.img files for reasons unknown to me (said adb: not found despite the files being there).
Anyways, I rebooted into the Fastboot mode and found that my phone's NAND is unlocked as the fastboot says S-OFF. I thought of giving another try by temp rooting with Visionary+ and then trying to Perm Root it. To my surprise, after rebooting and even uninstalling Visionary+, apps requiring root access function properly. Does this mean Legend 2.2 with HBOOT 1.01 has been permanently rooted?
I also installed the ROM Manager and it did manage to install the ClockworkMod. However, whenever I try to back up my current firmware, it says backup cache could not be found.
Also, I wanted to know since its showing that my phone is rooted and has ClockworkMod, will I be able to install ROM without any issues?

If it says adb: not found then you probably don't have problems with the files to be flashed not found but with the adb binary not found.
In older versions of the Android SDK it was in tools directory but since r09 it is in platform-tools instead.
Many of the guides found in the internet refer to the old directory names.
From your HBOOT Screenshot you can perfectly see that your phone is S-OFF.
Did you install Clockworkmod permanently already? (e.g. when you reboot your phone into recovery mode from hboot screen you have clockworkmod recovery and not the default Attention sign)
If yes, then you should be fine installing a custom rom from the rom manager or by hand.
The problems with backuping your current firmware using the nandroid backup that comes with clockworkmod fails here too, though I don't know why.
Maybe you want to just backup your settings with Titanium Backup instead of the whole rom.

Could his hboot be used to s-off the phones which have the vodafone ota hboot 1.0?

ThauExodus said:
Could his hboot be used to s-off the phones which have the vodafone ota hboot 1.0?
Click to expand...
Click to collapse
Yeah i wonder the same??
Sent from my Legend using XDA App

IIRC, The S-OFF dev did ask for 24 hours access to an HBOOT1.01 phone to pull off everything he needed and have a play then he'd look at S-OFF for 1.01. See the original S-OFF thread.

I can boot into recovery mode from hboot screen but I have to enter by pressing Vol Up + Power button to enter as clockworkmod shows an exclamation mark in a triangle.
When I enter the recovery mode, it shows E:can't open /cache/recovery/command.
Also, can anyone tell me what will wipe cache partition do in recovery?
I'm willing to help if any Legend dev wants to know more about my phone's Hboot 1.01 with S-off.

I think this message is normal E:can't open /cache/recovery/command
Can you try to backup your hboot and your radio?

sorry for being a n00b. how do i do that?

I tried installing a custom firmware but I can't as the Legend reboots and shows an icon of installing from the microSD and stopping mid-way with a question mark.
I was trying to install Blayo's latest ROM

Hboot 1.01.s-off. Now, that's a new thing. It'll be good if you can help devs on the hboot side with your s-off.
Sent from my Legend using XDA App

psyionx said:
Hboot 1.01.s-off. Now, that's a new thing. It'll be good if you can help devs on the hboot side with your s-off.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
As I said, I'm willing to. Only if someone would direct me on how to do it.

@legendusr
Would you try to backup your hboot, and posting it here?
Maybe this could work:
(instructions by XDA user OzJD)
Power off phone, Connect your phone to PC, Hold back button while turning phone on (to get to fastboot mode)
On the PC:
Code:
fastboot oem saveprt2sd hboot -n hboot.bin

Or you can maybe try to make nandroid backup....

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