[Recovery] [32A & 32B] [16-May-2010] RA-sapphire-v1.7.0

Search This thread

romis138

Member
Aug 16, 2010
43
7
I can't reboot into recovery, I think I corrupted something. When I try to reflash with recovery-RA-sapphire-v1.7.0H.img on my SD root from terminal with SU, I get

flash_image not found

I don't have a nandroid backup and I can't boot into recovery with vol- and power on, can't boot into fastboot by holding Back. I think I may have previously flashed the wrong recovery and that's why this is happening (or flashed an incompatible ROM), is there any way to get the recovery back onto this or am I too far up the wrong creek without a paddle?

I have to send this phone back, so I'd appreciate any help.
 

mark manning

Senior Moderator
Staff member
Apr 7, 2010
8,099
13,665
Nusquam et ubique
I can't reboot into recovery, I think I corrupted something. When I try to reflash with recovery-RA-sapphire-v1.7.0H.img on my SD root from terminal with SU, I get

flash_image not found

I don't have a nandroid backup and I can't boot into recovery with vol- and power on, can't boot into fastboot by holding Back. I think I may have previously flashed the wrong recovery and that's why this is happening (or flashed an incompatible ROM), is there any way to get the recovery back onto this or am I too far up the wrong creek without a paddle?

I have to send this phone back, so I'd appreciate any help.

You can't get into hboot?

What about adb reboot bootloader?

Sent from my Galaxy Nexus
 

romis138

Member
Aug 16, 2010
43
7
You can't get into hboot?

What about adb reboot bootloader?

Sent from my Galaxy Nexus

Thanks for replying, I know this is an old thread and device.

Running "adb reboot bootloader" through terminal gives me "adb: permission denied", if i do su first, it gives me "adb: not found"

Otherwise, through the adbToggle application itself, reboot into Bootloader simply reboots the phone.

Through adbToggle, "reboot into Recovery" gives me this white triangle logo and nothing happens;

4ev0F.jpg


My about reads;
Version.1.1.30.MB611.T-Mobile.en.US
MB611
Android version 2.2.2
Kernel 2.6.32.9-g40740d1

I forgot which custom ROM I'm running, but I'm uncertain that matters. It was a mod of an official one, probably.

Is running the official RUU an option? Will it risk a brick? Will it stock everything (radio, recovery, OS rom)? Again, I want to return to stock before I send this out.
 
Last edited:

mark manning

Senior Moderator
Staff member
Apr 7, 2010
8,099
13,665
Nusquam et ubique
Thanks for replying, I know this is an old thread and device.

Running "adb reboot bootloader" through terminal gives me "adb: permission denied", if i do su first, it gives me "adb: not found"

Otherwise, through the adbToggle application itself, reboot into Bootloader simply reboots the phone.

Through adbToggle, "reboot into Recovery" gives me this white triangle logo and nothing happens;

4ev0F.jpg


My about reads;
Version.1.1.30.MB611.T-Mobile.en.US
MB611
Android version 2.2.2
Kernel 2.6.32.9-g40740d1

I forgot which custom ROM I'm running, but I'm uncertain that matters. It was a mod of an official one, probably.

Is running the official RUU an option? Will it risk a brick? Will it stock everything (radio, recovery, OS rom)? Again, I want to return to stock before I send this out.

Your testing my memory hard core but adb commands are done through your computer and command prompt or terminal if your using Linux. If you don't know how to use ADB that's a whole other world.

As far as I remember there is no RUU because it is stock android. There are official Pxxxx.IMG files but those won't help you unless you can get into hboot. Make sure your booting into there right. If you cant get into either recovery or hboot I'm sorry to say it sounds like a brick.

Did you recently flash something?

Sent from my Galaxy Nexus
 

Amanoo

Senior Member
Jan 30, 2009
148
9
Twente
I can't reboot into recovery, I think I corrupted something. When I try to reflash with recovery-RA-sapphire-v1.7.0H.img on my SD root from terminal with SU, I get

flash_image not found

I don't have a nandroid backup and I can't boot into recovery with vol- and power on, can't boot into fastboot by holding Back. I think I may have previously flashed the wrong recovery and that's why this is happening (or flashed an incompatible ROM), is there any way to get the recovery back onto this or am I too far up the wrong creek without a paddle?

I have to send this phone back, so I'd appreciate any help.

If you have the 32b model, you need recovery-RA-sapphire-v1.7.0G.img. Not the H version. Beats me how you would flash that.
 

mark manning

Senior Moderator
Staff member
Apr 7, 2010
8,099
13,665
Nusquam et ubique
I haven't been able to figure out how to flash the G version either.

Can you boot up, if so have you done this?


Download Amon_Ra 1.7.0G md5: 8846b53e3184d688e3e8a628ad81074f

Rename Amon_Ra's Recovery Image to recovery.img.

Copy the recovery.img to the root of the SD card (NOT in any folders).

Disconnect the HTC Magic from the computer.


Open Android Telnet Client and type found here

flash_image recovery /sdcard/recovery.img

Once the Amon_Ra's Recovery is finished installing, you will see # # on the screen below the line you've just typed.

Amon_Ra's Recovery should now be installed on the HTC Magic.
 

mark manning

Senior Moderator
Staff member
Apr 7, 2010
8,099
13,665
Nusquam et ubique
Are you sure your using a magic and not the Motorola Cliq 2

---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------

I google'd the version you listed and that is a Motorola rom
 

mark manning

Senior Moderator
Staff member
Apr 7, 2010
8,099
13,665
Nusquam et ubique

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    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 Magic/MT3G only, if you have an :
    - HTC Dream/G1 you should go here.
    - HTC Hero 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.

    Important notes
    • 32A users with SPL 1.76.x should flash the Hero version! (Will be updated to v1.7.0 soon!!)
    • 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.

    Features

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

    • 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).
    • You don't need to enter "mount -a" if your partitions are already mounted.
    • Use the H/G version if your Magic is HTC branded (PVT 32A board)/Google branded (PVT 32B board).

    via fastboot :
    • Requires engineerings SPL!
    Code:
    Copy recovery-RA-sapphire-v1.7.0G.img to a location where fastboot can find it.
    Boot your G1 into fastboot mode (boot while holding BACK)
    Connect your G1 via usb to your pc/mac/...
    fastboot devices (to make sure that fastboot "sees" your device)
    fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img

    via adb :
    • Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
    • Do NOT follow these steps from a terminal application on the phone, make sure that you've booted into a custom recovery first!!!
    Code:
    Copy recovery-RA-sapphire-v1.7.0G.img to the root of your sdcard
    Boot into your current custom recovery (boot while holding HOME)
    Connect your G1 via usb to your pc/mac/...
    adb shell
    #mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
    #flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img

    via terminal application installed on the phone :
    • Requires root
      [*]DO NOT use this method with CM5.0.7, there are currently some memory issues while flashing, use the above methods (preferably the fastboot method) instead until the issue is fixed in CM5.0.7!
    Code:
    Copy recovery-RA-sapphire-v1.7.0G.img to the root of your sdcard
    start the terminal app
    #flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img



    Download

    • ALWAYS check the md5sum to make sure the zip isn't corrupted.
    • Click on the Mirror-link if you don't like rapidshare
    • Use the H/G version if your Magic is HTC branded (PVT 32A board)/Google branded (PVT 32B board).


    Change-log :

    v1.7.0
    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
    - Added Cyan version (There's no difference with the normal version, only the wallpaper and textcolor changed)

    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
    7
    Links in OP for 1.7.0 recoveries have been updated.
    1
    I think its because the stock spl has signiture checking on. Change the spl though and...
    1
    But there says "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."
    Thanks.
    1
    Hello! Anyone who wants to get this recovery in 2022(and beyond) go here: 1pwn.ixmoe.com/websites/android.vslinux.net/downloads/recoveries/index.html
    There are H and G versions, as well as many interesting (e.g. CyanogenMod 6.1.1 for HTC Desire A8181)