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

Search This thread

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,760
mpls
When in telnet you type this exactly
flash_image recovery /sdcard/recovery.img
Notice the space before and after recovery
Also make sure the .img is placed on the root of your SD card (not in any folders) and named recovery.img (not recovery.img.img)


Sent from my Nexus 7 using xda premium
 

maclick245

Senior Member
Feb 3, 2010
68
12
can't go into recovery!

When in telnet you type this exactly
flash_image recovery /sdcard/recovery.img
Notice the space before and after recovery
Also make sure the .img is placed on the root of your SD card (not in any folders) and named recovery.img (not recovery.img.img)


Sent from my Nexus 7 using xda premium

i did exactly so but still the recovery would work well. could it be that the dreaming.nbh used for downgrading is faulty? but then i see alot of people hav used the same file without sweat! Awful luck i guess.
 

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,760
mpls
well I'm thinking there's just something missing, it seems you are on the proper version of android so that's good, you have telnet, I find it easier to put the icon of the app on the home screen.
now press home. slide open keyboard and hit <enter> twice
now type
telnetd
now press home
hit the telnet icon
hit ok
type
flash_image recovery /sdcard/recovery.img
wait a couple of seconds and you will see ##
if something else then something was done wrong
remember if you use windows the file extension may be put there for you so name amonra just
recovery
not recovery.img

Sent from my HTC Vision using xda premium
 
i did exactly so but still the recovery would work well. could it be that the dreaming.nbh used for downgrading is faulty? but then i see alot of people hav used the same file without sweat! Awful luck i guess.

First off, it's DREAIMG.nbh, is it not? If you misspell it here (you typed "dreaming.nbh" ), we can assume you misspell it in telnet too.

Second, do the instructions say to use DREAIMG.nbh and rename it, or to use something else? Been a while since I've done this and I'm on my phone, not a PC, so I can't easily go look for myself.

Third, you unwittingly answered your own question. In telnet, you're basically using the phone's underlying Linux command shell. So, if you mistype something, you might get a one-line response telling you how to use the command. Hence, as you typed, "usage: flash_image partition filename" (going from memory, I think I mistyped something) is telling you that you got something wrong on your command line.notice the command, "flash_image", followed by a space, then the name of the partition (I don't remember the valid names, but "boot" and "recovery" come to mind), followed by another space and the path to and name of the image file you're trying to flash.

For example, "flash_image boot /mnt/sdcard/boot.img" (this of course would have to be altered to suit what you're doing).

If you're flashing amon ra, it should be as the other respondent said (sorry, forgot your name).

flash_image recovery /mnt/sdcard/recovery.img

Of course, the filename has to match exactly what's on your sd card. It does NOT have to be "recovery.img" or "amonra.img". You just have to make sure it's an img format (as opposed to an update.zip or an nbh) and you have to make sure you get the exact name. By the way, cApitALiZAtIon matters.

Hope this helps.

--
Sent from my Bulletproof_Doubleshot using xda app-developers app
 
Last edited:

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,760
mpls
thiss needs a option to remove sig verification

+1
I contacted amonra a few months back to see if he was interested in doing a final update along with some other stuff
He respectfully declined at the moment as he had other things going on, but hopefully someday he will consider it

Sent from my Nexus 7 using xda premium
 

AndDiSa

Senior Member
Dec 2, 2009
3,680
4,995
Heidelberg
HTC Desire
-1
I think AmonRa is right in not providing this feature. Why you need the possibility to flash unsigned zip files? What's the problem in providing a signed update file? The only advantage I see in that: It will be much more easy for people to brick their phones.
 

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,760
mpls
I agree mostly, the only thing is I've been trying to build, when I test these I don't always sign, so for that it would be nice. but being the real only reason I guess it does make more sense not to as others may cause damage. but then again wouldn't it only creat a soft brick at the worst? I mean isn't it very hard to truley brick flashing a rom even if its curropt in some way?

Sent from my HTC Vision using xda premium
 

AndDiSa

Senior Member
Dec 2, 2009
3,680
4,995
Heidelberg
HTC Desire
I agree mostly, the only thing is I've been trying to build, when I test these I don't always sign, so for that it would be nice. but being the real only reason I guess it does make more sense not to as others may cause damage. but then again wouldn't it only creat a soft brick at the worst? I mean isn't it very hard to truley brick flashing a rom even if its curropt in some way?

Sent from my HTC Vision using xda premium

As log as you flash only boot / system and/or data images you are right, but if you flash recovery/radio/spl within the update zip, flashing will take place while rebooting the phone and after that it will automatically reboot into recovery. If something goes wrong or if the image doesn't work it will be a hard brick ...

... when I test these I don't always sign, so for that it would be nice ...
... use a script which automatically packs and signs your update.zip or use adb to push your modified files.
 

xanda143

Senior Member
May 26, 2012
413
41
I agree mostly, the only thing is I've been trying to build, when I test these I don't always sign, so for that it would be nice. but being the real only reason I guess it does make more sense not to as others may cause damage. but then again wouldn't it only creat a soft brick at the worst? I mean isn't it very hard to truley brick flashing a rom even if its curropt in some way?

Sent from my HTC Vision using xda premium

This is the reason I need it of course I have apps ect that can sigjn them for me but it would be nice to just jave that fwature as I test and some of the zips I test aren't sighned as the devs dont bother to and I really just want amon ra with that feature

Sent from my HTC Magic using xda premium
 

AndDiSa

Senior Member
Dec 2, 2009
3,680
4,995
Heidelberg
HTC Desire
This is the reason I need it of course I have apps ect that can sigjn them for me but it would be nice to just jave that fwature as I test and some of the zips I test aren't sighned as the devs dont bother to and I really just want amon ra with that feature

Sent from my HTC Magic using xda premium

Blame the devs or use adb to install them on your phone. There is no need for flashing unsigned zips by recovery.
 

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,760
mpls
Its no vig deal but it was given in cwn the safest of recoverhies not saying your wring but the feature couldn't hurt

Sent from my HTC Magic using xda premium

not saying anyone is wrong as (like is said previously) for me it is a nice feature but after thinking about it more probably not a feture that should be there as for many others it could just prove to be harmfull
I can't agree that clockwork recovery is the safest, it actually has turned out to be the buggest and least "safe" for any phone/tablet I have used. as I appreciate koush's hard work I dislike his recoveries and more or less do my best not to use them. having said this I did purchase rom manager a long ways back to support him, but I have only used maybe once or twice just to test and I feel it was too expensive (should have just donated to his paypal)
rambling done...


Sent from my HTC Vision using xda premium
 

xanda143

Senior Member
May 26, 2012
413
41
not saying anyone is wrong as (like is said previously) for me it is a nice feature but after thinking about it more probably not a feture that should be there as for many others it could just prove to be harmfull
I can't agree that clockwork recovery is the safest, it actually has turned out to be the buggest and least "safe" for any phone/tablet I have used. as I appreciate koush's hard work I dislike his recoveries and more or less do my best not to use them. having said this I did purchase rom manager a long ways back to support him, but I have only used maybe once or twice just to test and I feel it was too expensive (should have just donated to his paypal)
rambling done...


Sent from my HTC Vision using xda premium

Poimt taken well what can I say except what the hec I would luke an amon ra with this feature buts maybe a moded one not the standerd as this is thanks for the input

Sent from my HTC Magic using xda premium
 

peschka

Senior Member
Mar 12, 2007
121
24
31
Varna
Someone still keep a copy of latest recovery-RA-dream-v1.7.0.img ? I want to revive this legendary device.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    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
    1
    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)

    It removes /data/system/batterystats.bin After that you should leave it charging until it reaches 100%.
    1
    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!

    try doing

    Code:
    su
    erase_image recovery

    first

    but, tbh it probably worked the first time, its just a little shy and keeps quiet
    1
    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

    flash_image<space>recovery<space>/sdcard/recovery-RA-dream-v1.7.0.img