[Recovery ROM] [15-August-2010] RA-hero-v1.7.0.1

[xPreSiDenT]

Where did you see that? on the Magic RA-Recovery thread?!
If you look at the first post of this thread, you should find the version for the Hero GSM (if you don't have the hero GSM please look elsewhere):


Also if you have a working recovery, it might be simpler to use the flashable update I prepared:

great we're already talking on the subject. I just bought a used htc hero gsm, which had already been rooted(at least looked like it, rom was 1.5 sense but it had the su permissions app and it had an old version of amon ra recovery, but no root apps worked). Anyway I started going through the motions, updating everything, so i flashed the latest radio (update-hero-radio-63.18.55.06JU_6.35.09.26-signed), then moved to this recovery. i flashed RA-hero-v1.7.0.1 by the first method in 1st post but it didnt boot into recovery after that. I was able to get into RA-hero-v1.7.0.1 via fastboot but then adb wont recognize the device. then I saw the line talking about 32A sapphires. in bootloader my device shows the following:

HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.09.26

so i went for recovery-RA-hero-v1.6.2.img and flashed that with method2, and it worked. I dont know if my phones 32A or what, but for whatever its worth that flashrec program said it was 32A. I'm on CM6.1 now, and btw have plenty of reasonable experience with adb, recoveries, fastboot, flashing etc.

as far as i can see, and my search results here and elsewhere have shown, 1.7.0.1 should work on gsm heros. sapphire is obviously a different phone. so my question is, am i doing anything wrong?

 

[erasmux]

great we're already talking on the subject. I just bought a used htc hero gsm, which had already been rooted(at least looked like it, rom was 1.5 sense but it had the su permissions app and it had an old version of amon ra recovery, but no root apps worked). Anyway I started going through the motions, updating everything, so i flashed the latest radio (update-hero-radio-63.18.55.06JU_6.35.09.26-signed), then moved to this recovery. i flashed RA-hero-v1.7.0.1 by the first method in 1st post but it didnt boot into recovery after that. I was able to get into RA-hero-v1.7.0.1 via fastboot but then adb wont recognize the device. then I saw the line talking about 32A sapphires. in bootloader my device shows the following:

HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.09.26

so i went for recovery-RA-hero-v1.6.2.img and flashed that with method2, and it worked. I dont know if my phones 32A or what, but for whatever its worth that flashrec program said it was 32A. I'm on CM6.1 now, and btw have plenty of reasonable experience with adb, recoveries, fastboot, flashing etc.

as far as i can see, and my search results here and elsewhere have shown, 1.7.0.1 should work on gsm heros. sapphire is obviously a different phone. so my question is, am i doing anything wrong?

If you have a previous recovery version working, try this:

To the request of rtorbs and hopefully to the joy of many, I have prepared a recovery update zip for recovery 1.7.0.1:
recovery-RA-hero-v1.7.0.1-update.zip

I have tested this for going from recovery 1.6.2 to 1.7.0.1 and it works

USE AT YOUR OWN RISK AND ONLY ON HERO GSM

 

[AdmcPL]

Hello, I flashed recovery via better terminal emulator pro. And I can enter recovery only once, after rebooting phone recovery restores to stock android recovery.

HEVO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP=o1of
TOUCH PANEL-SYN0104
RADIO-6.35.15.11

I have stock Hero Eclair ROM (3.32.405.2), I rooted phone using Universal Androot 1.6.2 beta 5

 

[erasmux]

Hello, I flashed recovery via better terminal emulator pro. And I can enter recovery only once, after rebooting phone recovery restores to stock android recovery.

HEVO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP=o1of
TOUCH PANEL-SYN0104
RADIO-6.35.15.11

I have stock Hero Eclair ROM (3.32.405.2), I rooted phone using Universal Androot 1.6.2 beta 5

I think the stock ROM restores the recovery on boot or somehow.
The easiest way to avoid this, is boot into recovery this way, then backup your current ROM (nandroid backup), then flash a custom ROM, and only then reboot.

EDIT: now that I think of it, maybe I am wrong above. I am sure I heard of this problem before but don't remember what was the cause/solution. You can try digging in this thread, it should be buried somewhere here.
From my vage memory, I would first try the following:
Boot into recovery using the way you use above (flashing through terminal emulator and booting into it), then from recovery use my update from the above post to reflash recovery from within it. And only then reboot. This makes no sense (at least to me), but I think this was the solution.
If this doesn't work, try what I said before the "EDIT" part.

 

[treesurf]

I think the stock ROM restores the recovery on boot or somehow.
The easiest way to avoid this, is boot into recovery this way, then backup your current ROM (nandroid backup), then flash a custom ROM, and only then reboot.

Actually, I had this same problem. I could flash recovery, but then only reboot into it once before the stock ROM replaced/removed it. Just make sure to be ready to nandroid backup and flash a new ROM immediately after flashing the recovery image and you should be fine. Since flashing a custom ROM I haven't had any problems booting into recovery.

 

[gene83]

Can I flash using the flash zip in the RA-recovery 1.6.2?Please advice

 

[erasmux]

can i flash using the flash zip in the ra-recovery 1.6.2?please advice

to the request of rtorbs and hopefully to the joy of many, i have prepared a recovery update zip for recovery 1.7.0.1:
recovery-ra-hero-v1.7.0.1-update.zip

i have tested this for going from recovery 1.6.2 to 1.7.0.1 and it works :d

use at your own risk and only on hero gsm

: )

 

[gene83]

recovery-ra-hero-v1.7.0.1-update.zip works well.
thanks ya.

 

[varazir]

Hello, Is there way to like password protect the recovery ?

 

[tomekk_nt]

I think not on this one.

 

[slkdk]

Delete please

 

[SilverZero]

Quick question: Can I delete the .img from the SDcard after flashing the new recovery, or is it loading from that .img every time?

 

[erasmux]

Quick question: Can I delete the .img from the SDcard after flashing the new recovery, or is it loading from that .img every time?

You can delete it. It is loaded from a special part in your internal memory - hence the need to flash it....

 

[wapz]

Just flashed a virgin hero with basic 2.1 on it with 1.7.0.1 and it went perfectly from the OS itself using terminal emulator. Thanks a lot for this!

I am still using 1.6.2 myself, would there be any risk in flashing this since there is already an updated recovery on it?

 

[mainstreamer]

Hey Erasmux,

I'm getting error message when wiping;

Can't erase at bad block x????
Does this means my internal storage card is corrupted somehow?

Thanks in regards

 

[CatmanBCN]

I had a hard time moving from 1.6.2 to 1.7.0.1 with the new SDK but I finally made it.
thanks!

 

[mainstreamer]

Hey Erasmux,

I'm getting error message when wiping;

Can't erase at bad block x????
Does this means my internal storage card is corrupted somehow?

Thanks in regards

Nobody can help me with this?

 

[swatsbiz]

Sounds like it is, try formatting it in your PC first.

Sent from my HTC Hero using XDA App

 

[Shizophren]

Why the Volume keys for navigation through the menu does't work? I can't navigate with my trackball because its absolutely not reacting to my gestures.

 

[ferraripassion]

Device : HTC Hero GSM

I am unable to get to the recovery screen (home+power), the phone is stuck in the HERO screen.
The phone boots normally, if it on without holding the home button.

I tried the fastboot+adb

I get into the Fastboot use
<vol down> Hboot mode
<menu> reset device

But the further adb commands do not work,

fastboot boot recovery-RA-hero-v1.7.0.1.img , when I put in this command it says fastboot is not recognized as an internal or external command