[Recovery] [15-May-2010] RA-dream-v1.7.0 (also for the Rogers Dream)

Search This thread
By:
Advanced…
D

drewdown227

Senior Member
Dec 5, 2007
112
0
CO
Yeah i just triead again like 6 more times and i cannot get it to flash. Im in terminal emulator and everytime i type this:

flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img

it just says flash_image: not found

I checked my sdcard like 5 times and the file is on the root so i cant figure out why i cannot flash it. Its probably something real simple that im missing. I am using The TMO OTA DRC83 US (Donut Inside) - NEW! 1.9.1 and have the expansion installed i dont know if this has something to do with the problem?

I also tried:

mount -a
mount sdcard
mount system

that someone posted a while back and that didnt fix the problem.

Any help with this would be greatly appreciated. Thanks.
 
JROC27

JROC27

Member
Oct 2, 2009
17
0
what i did was unroot then root putting RA-dream-v1.2.2
i am still new at this rooting stuff so not if u want to do all that
i use the one click root so didn't take long. :eek:
 
B

bkmo

Senior Member
Jun 25, 2008
1,890
226
10° 5' 59" North, 84° 16' 84" West
drewdown227 said:
Yeah i just triead again like 6 more times and i cannot get it to flash. Im in terminal emulator and everytime i type this:

flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img

it just says flash_image: not found
Click to expand...
Click to collapse
Looks like flash_image is not in the search path of the rom you are on. You will have to find it and use the full path as in /sbin/flash_image flash recovery etc., or use fastboot to flash it.
 
J

jda1977

Member
Aug 3, 2009
21
1
for those on mytouch. Rename recovery img without the .v1.2.2.img portion and it works in terminal emulator for me. Since I could type everything with the keyboard but the numbers.
 
skrki

skrki

Senior Member
Sep 1, 2009
416
2
Canberra
Amon_RA,
Awesome work once again, thanks a lot :cool: I have got to buy you, and other significant ones, some redbull, or beer or something..
I particularly like the fact that you can mount/umount SD card in recovery :D

Guys&Gals,
I see lots of people getting "errors" using mount -a. This command tried to mount ALL the file systems in file system table, so it may fail on some (for various reasons, not important here), hence you see some errors.

The fact is (besides the fact that you haven't searched ENOUGH ;)) all you need to mount here is your /sdcard and /system (which should be mounted automatically anyways). If you get errors "Can't find RA_recovery.img", that means probably your SD card is not mounted. So, before using files on your SD card, type mount in the shell, and check which file systems are mounted. If you don't see your SD card (/dev/block/mmcblk0p* on /sdcard), then you're gonna have to mount it. (asterisk represents a number, could be 1, could be 2, depends on the number of partitions on your card.)
Type this in the shell:
Code: 
mount /sdcard 
[I]Abbreviated form[/I]

To see what mount can do, check it's help:
Code: 
mount --help


Second thing:
Why not try out/flash this recovery image in bootloader? Once in fastboot, open Windows command prompt and type:
Code: 
[B]fastboot devices[/B] 
[I]Makes sure your device is in fastboot mode, you should see it in the output[/I]

[B]fastboot boot RA_recovery.img [/B]
[I]Only BOOT the recovery, this does not make a premanent change[/I]

When you're sure you want to flash it, while still in boot loader, type:
Code: 
[B]fastboot erase recovery[/B]
then,
[B]fastboot flash recovery RA_recovery.img[/B]

There you go, good luck!

P.S. Solutions like "I renamed this file to blah.img and it worked" or "Tried this a couple of times and it worked", are not solutions :p

P.S.S. My apologies to experienced users, with hope that this little guide will finally stop the clogging of this thread with questions that do not belong here in the first place... And clear things up for the new users, just cos I know how hard it is in the beginning.
 
Last edited:
M

makethetick

Senior Member
Jan 29, 2009
74
1
England
Great improvement over cm's recovery, only one thing that stands out so far though, when flashing it asks to confirm with the 'GREEN' key, not sure about anyone else but my G1 has all black and white keys on the front so that may confuse people. Most other phones have the green call answer key but ours don't! IMO it would be best leaving it how it was before by comfirming with the HOME key.

Apart from that, well done :cool:
 
B

bkmo

Senior Member
Jun 25, 2008
1,890
226
10° 5' 59" North, 84° 16' 84" West
uansari1 said:
Any chance the next version of this could also include MikeTaylor's script to fix the auto rotate function? It would be nice if it was an item in the upcoming Recovery in a submenu somewhere. His script and other info is at the link below:

http://xdaforums.com/showpost.php?p=4424396&postcount=1481
Click to expand...
Click to collapse

This is one I modded with a second menu option run from terminal. Type u at console prompt and you will get a menu with other options including the rotate fix.

http://www.4shared.com/file/137752446/7d5c3290/recovery-RA-dream-v122_BKMOd_2.html
 
C

clevetbs

Member
Jul 9, 2008
26
0
On the moon
this is nice.... i installed it and it works great... i have one question can there be a menu be added for view existing partitions as well.... but to top it off awesome!!!!
 
U

uansari1

Senior Member
Jul 27, 2008
3,545
92
Karachi
drewdown227 said:
so i have typed this
# flash image recovery /sdcard/recovery-RA-dream-v1.2.2.img

in terminal emulator it keeps saying image not found but the image is on the root of my SD

do i need to type the underscore here " flash_image " if so how do i type an underscore in the terminal emulator?
Click to expand...
Click to collapse

bkmo said:
This is one I modded with a second menu option run from terminal. Type u at console prompt and you will get a menu with other options including the rotate fix.

http://www.4shared.com/file/137752446/7d5c3290/recovery-RA-dream-v122_BKMOd_2.html
Click to expand...
Click to collapse

Outstanding!!! Thanks bro!
 
here.david

here.david

Senior Member
Jan 6, 2009
423
29
Sonoma, CA
M

Maxy6

Guest
This had been working great for me, then, strangely enough, my track ball stopped working in recovery mode (though keyboard shortcuts continue to work). I reflashed but the track ball still doesn't work in recovery. It works fine one the system is loaded. Unless I'm imagining that the track ball was working in recovery mode?
 
T

temporizer

Senior Member
Aug 17, 2006
617
0
40
Vancouver
suggestion...

I love what you have done! Great work!

One suggestion: it bothered me when cyan first incorporated nandroid backup/restore into his recovery, when you go to do a nandroid backup, it doesn't ask you to confirm, it just performs a backup. when doing a nandroid restore, it does ask you to confirm.

it sucks because the trackball is so sensitive, if you go to do a restore you might accidently scroll and hit backup (it's happened to me twice).

Just a thought to make something great even better. IMO
 
Last edited:
innerspace

innerspace

Senior Member
Jun 23, 2009
392
7
Very nice!

I'm digging this a lot, thanks for putting all these tools together in one spot!
 
You must log in or register to reply here.

Similar threads

cyanogen
[ROM][BBQ] CyanogenMod-6.1 for Dream & Magic :: V6.1.0 (12/05/2010)
Replies
5K
Views
2M
A
alpha-tester
K
How-to- Root, Hack, and Flashing your G1/Dream Read first!!
Replies
2K
Views
3M
LucidREM
LucidREM
J
[ROM] JACxHEROSkiv2.2- JAC/CC (JAC-SKI HTC KERNEL BFS-240) Dream/Mytouch 9/30/09
Replies
11K
Views
2M
D
Digi2k
ezterry
[ROM] EzGingerbread (Dream and Sapphire) stable-v1.0 2011-12-04
Replies
3K
Views
817K
HTCDreamOn
HTCDreamOn
cyanogen
[ROM] Cyanogenmod-5 For Dream/Magic - Mean Lean Pastry Machine - V5.0.8 (06/19/2010)
Replies
2K
Views
609K
gee one
gee one

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 7
    Amon_RA
    Amon_RA
    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 Dream/G1 only, if you have an :
    - HTC Magic/MT3G 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
    • 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):
      • [HOME+Back] Reboot system now :: reboot your phone
      • [Alt+X] Go to console :: bring up the console
      • [Alt+T] USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
      • [Alt+B] Backup/Restore (recovery partition not included!)
        • [Alt+0] Nand backup :: Make a Nand backup
        • [Alt+1] Nand + ext backup :: Make a Nand + ext backup
        • [Alt+2] Nand restore :: Restore a Nand backup
        • [Alt+3] BART backup :: Make a BART backup (Nand + ext)
        • [Alt+4] BART restore :: Restore latest BART backup
        • [Alt+5] Bck Google files :: Makes a backup of the Google proprietary system files in /cache/google
        • [Alt+6] Rst Google files :: Restores the Google proprietary system files from /cache/google
      • [Alt+F] Flash zip from sdcard :: Flash a zip update file from your sdcard
      • [Alt+W] Wipe
        • [Alt+0] Wipe data/factory reset :: Wipe /data and /cache
        • [Alt+1] Wipe cache :: Wipe /cache only
        • [Alt+2] Wipe Dalvik-cache :: Wipe /cache/dalvik-cache
        • [Alt+2] Wipe SD:ext partition : Wipe the ext partition on your sdcard
        • [Alt+4] Wipe battery stats : Wipe the battery stats in /data
        • [Alt+5] Wipe rotate settings : Wipe the sensor settings in /data
      • [Alt+P] Partition sdcard
        • [Alt+0] Partition SD :: Interactive SD partitioning
        • [Alt+1] Repair SD:ext :: Repair the ext partition
        • [Alt+2] SD:ext2 to ext3 :: Convert ext2 to ext3
        • [Alt+3] SD:ext3 to ext4 :: Convert ext3 to ext4
      • [Alt+O] Other
        • [Alt+0] Fix apk uid mismatches :: Does extacly that
        • [Alt+1] Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
      • [ALT+Q]Power off :: Powers off your phone
    • Scripts available from console :

    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.

    via fastboot :
    • Requires engineerings SPL!
    Code: 
    Copy recovery-RA-dream-v1.7.0.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-dream-v1.7.0.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-dream-v1.7.0.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-dream-v1.7.0.img

    via console :
    • Requires root
    • 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-dream-v1.7.0.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
#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-dream-v1.7.0.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-dream-v1.7.0.img to the root of your sdcard
start the terminal app
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img

    Download

    ALWAYS check the md5sum to make sure the zip isn't corrupted.
    Download the R version if you have a Rogers Dream EBI1 phone!

    v1.7.0

    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
    View
    1
    B
    billquinn1
    ERamseth said:
    Exactly what stats are wiped by wipe battery stats? Is it the status of what is using the battery? Does this undo or re-do "battery conditioning" (full drain, then full recharge as is often suggested by various people/sources)?

    (searched the forum and this thread and didn't find any real answers)
    Click to expand...
    Click to collapse

    It removes /data/system/batterystats.bin After that you should leave it charging until it reaches 100%.
    View
    1
    Firerat
    Firerat
    Duke3d said:
    OK so looking to upgrade from CM 4.2.0.15 to the newest and greatest (6.x) and I apparently need Danger SPL, which needs Amon Ra's recovery.

    The problem I'm having with running the recovery .img is it just sits in the console and doesn't do squat. I tried changing the file name to a non-existent one and it gives me a file not found error, so the file is indeed there but it's just not flashing.

    I have tried the recovery screen, as well as the terminal app. I type su - and hit allow/remember when asked for the permissions prompt screen (I'm assuming this is "rooting").

    When I type the flash_recovery recovery /sdcard/recovery-RA-dream-v1.7.0.img and hit enter, nothing happens. Tried a different console app, same thing.

    Please advise.

    Or can I just go ahead and install Danger SPL with the stock CM4.2.0.15 recovery?

    Thanks!
    Click to expand...
    Click to collapse

    try doing

    Code: 
    su
erase_image recovery

    first

    but, tbh it probably worked the first time, its just a little shy and keeps quiet
    View
    1
    Firerat
    Firerat
    mahroze said:
    hi i am a noob i flash it but it gives the following prompt
    Microsoft Windows XP [Version 5.1.2600]

    List of devices attached
    HT849GZ05795 recovery


    C:\android-sdk-windows\tools>adb shell
    / # flash_image recovery/sdcard/recovery-RA-dream-v1.7.0.img
    flash_image recovery/sdcard/recovery-RA-dream-v1.7.0.img
    usage: flash_image [-d] partition file.img
    options:
    -d delete the image file after a successful flash
    / #

    help
    Click to expand...
    Click to collapse

    flash_image<space>recovery<space>/sdcard/recovery-RA-dream-v1.7.0.img
    View
    1
    robuser007
    robuser007
    http://www.multiupload.com/U9YEZQ6276
    View

New posts