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

Search This thread

xPreSiDenT

Senior Member
Aug 14, 2007
384
11
Boston
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:

Code:
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

Retired Recognized Developer
May 22, 2010
1,437
455
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:

Code:
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 :D

USE AT YOUR OWN RISK AND ONLY ON HERO GSM
 

AdmcPL

Senior Member
Oct 14, 2010
82
1
Oława
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

Retired Recognized Developer
May 22, 2010
1,437
455
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.
 
Last edited:

treesurf

Senior Member
Sep 8, 2010
685
153
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.
 

erasmux

Retired Recognized Developer
May 22, 2010
1,437
455
  • Like
Reactions: gene83

SilverZero

Senior Member
May 18, 2010
1,549
409
Quick question: Can I delete the .img from the SDcard after flashing the new recovery, or is it loading from that .img every time?
 

wapz

Senior Member
Jan 20, 2008
1,089
170
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

Senior Member
Jul 20, 2010
209
7
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
 

Shizophren

Senior Member
May 13, 2009
262
12
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

Senior Member
Jun 19, 2008
547
212
www.htccode.com
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Or flash this in an older AmonRA or CWM

    Flashable 1.7.0.1 Thanks to Desean and Erasmux
    1
    This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.

    All source code is available at github.

    This recovery if for the HTC Hero only, so NOT the Sprint Hero!!!, if you have an :
    - HTC Dream/G1 you should go here.
    - HTC Magic/MT3G you should go here.
    - HTC Sprint Hero you should go here.
    - HTC Eris you should go here.
    - HTC Tattoo you should go here.
    - HTC Nexus One you should go here.
    - HTC Evo 4G you should go here.

    Important notes
    • Make sure your battery is at least 30% before using nandroid!!
    • Always check recovery.log before posting your issues!
      You can do this by doing :
      • "cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
      • Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.

    How-to Navigate
    Use the trackball (up+down) to navigate through the menu, press the trackball to select items.
    You can also use the volume keys (vol-up + vol-down) to navigate, and the CALL-ANSWER key to select items (in case your trackball is broken).

    Features
    • full ADB access in recovery mode
    • Busybox v1.15.3
    • HW-Key navigation (volume keys + CALL-ANSWER) option
    • Extended menu (with keyboard-shortcuts):
      • Reboot system now :: reboot your phone
      • USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
      • Backup/Restore (recovery partition not included!)
        • Nand backup :: Make a Nand backup
        • Nand + ext backup :: Make a Nand + ext backup
        • Nand restore :: Restore a Nand backup
        • BART backup :: Make a BART backup (Nand + ext)
        • BART restore :: Restore latest BART backup
        • Bck Google files :: Makes a backup of the Google proprietary system files in /cache/google
        • Rst Google files :: Restores the Google proprietary system files from /cache/google
      • Flash zip from sdcard :: Flash a zip update file from your sdcard
      • Wipe
        • Wipe data/factory reset :: Wipe /data and /cache
        • Wipe cache :: Wipe /cache only
        • Wipe Dalvik-cache :: Wipe /cache/dalvik-cache
        • Wipe SD:ext partition : Wipe the ext partition on your sdcard
        • Wipe battery stats : Wipe the battery stats in /data
        • Wipe rotate settings : Wipe the sensor settings in /data
      • Partition sdcard
        • Partition SD :: Interactive SD partitioning
        • Repair SD:ext :: Repair the ext partition
        • SD:ext2 to ext3 :: Convert ext2 to ext3
        • SD:ext3 to ext4 :: Convert ext3 to ext4
      • Other
        • Fix apk uid mismatches :: Does extacly that
        • Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
      • Power off :: Powers off your phone
    • Scripts available via adb :

    Install

    There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).

    via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
    Code:
    Copy recovery-RA-hero-v1.7.0.1.img to the root of your sdcard
    Boot into your current custom recovery (boot while holding HOME)
    Connect your Hero via usb to your pc/mac/...
    adb shell
    $su (not required if you have root already)
    #mount -a
    #flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img

    via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
    Code:
    adb shell reboot bootloader
    fastboot boot recovery-RA-hero-v1.7.0.1.img
    adb shell mount /sdcard
    adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
    adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
    adb shell reboot

    Download

    • ALWAYS check the md5sum to make sure the zip isn't corrupted.

    Only flash recovery-RA-hero-v1.6.2.img if you have a 32A Sapphire with 6.35.x.x radio and 1.76.x SPL, recovery-RA-hero-v1.7.0.1.img will NOT boot! I'll create a new Sapphire version soon.


    Change-log :

    v1.7.0.1
    Code:
    - Fixed some minor bugs
    - Recovery and scripts use /sd-ext instead of /system/sd as mountpoint to support the new apps2sd method (implemented mostly by Chris Soyars)
    - Added an option to backup/restore Google proprietary Android system files (backuptool.sh written by Cyanogen)
    - Removed "move apps2sd"-option as it's not needed anymore with the new apps2sd method
    - Updated BART to v1.3.1 (updated by Dumfuq to support /sd-ext)
    - Added a wipe cache only option
    - Nandroid now backups/restores /cache again by default
    - Dalvik-cache wipes /cache/dalvik-cache now
    - Removed SDCARD: prefix in output when chosing zip to flash
    - Updated kernel to fully support ext4

    v1.6.2
    Code:
    - Added power off menu item
    - New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore
    - New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue.
    [COLOR="Red"][B](This will not fix old corrupted Nandroid backups! Please make new backups!!)[/B][/COLOR]
    - New mkyaffs2image binary
    - New flash_image binary
    - Updated busybox to v1.5.3
    - Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues)
    - Fixed wipe option not wiping when ext was not present
    - Created carebear versions after the idea of packetlss
    - Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)

    Special thanks to :
    • packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
    • Koushik Dutta for the unyaffs binary code fix and help ^^
    • pensive for adding awesome features to Nandroid :)
    • Bkmo for his utility script!
    • Devsk for his switchrom script!
    • 51dusty for his sdparted script!
    • k4str0 for his fix_permissions v2.03 update.
    • Devsk, Dumfuq, Overground for creating BART :D
    • Androidappcritics for the reboot idea in BART :p
    • rikupw for the ideas and toggle_ums script.
    • MLIGN for the idea to port my recovery to the Dream.
    • http://theunlockr.com for all the awesome video’s ^^
    • JesusFreke for his awesome JFv1.43's recovery , donate
    1
    How do we revert back to the original hboot in case we flash this to over the current hboot?

    In case someone will say "just flash the backed up hboot image", i also would like to ask how do you backup the current (original, never flashed anything before) hboot?

    Thank you!
    You can get the orginal HBOOT from the old RUU package.

    If you want to flash it back here's an update package to flash it (I'm not responsible for any bricks, make sure you know what you are doing, have the right HW etc).

    This is "original" 1.76.0004 hboot, that came shipped with the Hero.
    1
    i have tried everything and nothing is working here..i am still getting this annoying e:can't read misc message.

    Try : fastboot erase misc
    1
    don't seem to differ that much? what is the difference?