Custom Recovery Image

Discussion in 'Droid X Roms' started by Randomocity, Dec 12, 2009.

  1. gardobus

    gardobus Silver Member

    Joined:
    Nov 1, 2009
    Messages:
    1,965
    Likes Received:
    0
    Trophy Points:
    101
    Location:
    Arizona
    Ratings:
    +0
    I don't know if its a program or another command or what. Others have reported it working fine so I wonder what we're not doing. I thought maybe the commands should be run via adb but it says to run it on the phone so I don't know.
     
  2. gardobus

    gardobus Silver Member

    Joined:
    Nov 1, 2009
    Messages:
    1,965
    Likes Received:
    0
    Trophy Points:
    101
    Location:
    Arizona
    Ratings:
    +0
    I even tried chmod-ing flash_image to 777
     
  3. toka

    toka New Member

    Joined:
    Dec 12, 2009
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    @gardobus : sdcard is noexec - you need to copy the binary elsewhere in order to run it. do an ls -l to verify the permissions
     
  4. brianr0131

    brianr0131 Member

    Joined:
    Nov 10, 2009
    Messages:
    407
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cherry Hill, NJ
    Ratings:
    +0
    type ls /sdcard and you'll see a list of the files on your sd card

    When i do this I see both the recovery-0.08.img and the flash_image files. Do you?

    This is frustrating
     
  5. boostdscoob

    boostdscoob Member

    Joined:
    Dec 11, 2009
    Messages:
    273
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    ohio
    Ratings:
    +0
    would it affect anything if we rename the recovery? maybe its an issue with the 0's.. idk.. im lost.
     
  6. gardobus

    gardobus Silver Member

    Joined:
    Nov 1, 2009
    Messages:
    1,965
    Likes Received:
    0
    Trophy Points:
    101
    Location:
    Arizona
    Ratings:
    +0
    Damn seriously? Then why would the instructions not have you move it?

    Is there a temporary area or something where I can put it without just randomly throwing it somewhere?
     
  7. toka

    toka New Member

    Joined:
    Dec 12, 2009
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    yep... seriously =)

    personally, I had copied it into my /system/xbin (where I had also placed busybox) - figured it was probably a tool I wanted to keep on the phone... we'll ignore the fact that i somehow managed to wind up with a brick later on... (yep even with the custom recovery image (0.07))
     
  8. brianr0131

    brianr0131 Member

    Joined:
    Nov 10, 2009
    Messages:
    407
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cherry Hill, NJ
    Ratings:
    +0
    Do we need busybox to run this?
     
  9. boostdscoob

    boostdscoob Member

    Joined:
    Dec 11, 2009
    Messages:
    273
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    ohio
    Ratings:
    +0
    i reckon, i'll just wait for the one with nandroid, and a little more stable.
     
  10. gardobus

    gardobus Silver Member

    Joined:
    Nov 1, 2009
    Messages:
    1,965
    Likes Received:
    0
    Trophy Points:
    101
    Location:
    Arizona
    Ratings:
    +0
    Just to be sure, copying flash_image to /system/xbin and flashing the recovery image had nothing to do with the bricking right? LOL
     
  11. Brian7

    Brian7 Member

    Joined:
    Nov 25, 2009
    Messages:
    70
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    if flash_image is in the root of the sdcard, you'll have to run
    '/sdcard/flash_image recovery /sdcard/recovery.img' since flash_image is not in your $PATH
     
  12. toka

    toka New Member

    Joined:
    Dec 12, 2009
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    i don't believe it's a dependency for this tool... but i'm not sure

    the base os is pretty difficult to navigate without the builtin applets busybox has (which, uptime, uname, ifconfig, less, etc...) - so you may want to consider placing it in your/system/xbin (which is in your PATH) - to get into the busybox shell, simply type busybox sh (sh is still /system/bin/sh) - you'll have a PS1 set and get some better tab completion (and all those useful commands) - just my $.02 on that though =)
     
  13. Bear in NM

    Bear in NM Active Member

    Joined:
    Nov 12, 2009
    Messages:
    1,389
    Likes Received:
    1
    Trophy Points:
    38
    Ratings:
    +1
    I tried many of the steps posted above, and I get no further than "image not found".

    Perhaps this will help us. When I unzip the Flash_Image, I get a 26 kb file that has no extension. My recovery-0.08.img file is 3116 kb in size. I am using winXP, and have been using terminal emulater with SU. The files LS fine on the SD root/home directory. I also tried copying the Flash_Image folder with the Flash_image extensionless file onto the SD. No luck.

    Gotta be a missing something, or perhaps those of us with problems have a common denominator that we need to link.


    Craig

    I posted this while the path post was being typed. Makes sense, but the brick comment has me a little concerned.
     
    Last edited: Dec 12, 2009
  14. gardobus

    gardobus Silver Member

    Joined:
    Nov 1, 2009
    Messages:
    1,965
    Likes Received:
    0
    Trophy Points:
    101
    Location:
    Arizona
    Ratings:
    +0


    didn't work :icon_eek:
     
  15. toka

    toka New Member

    Joined:
    Dec 12, 2009
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    HAHA - think it was more with what i did after getting the recovery image installed =) - went through a couple reboots (install recovery-0.07, boot to recovery to validate, reboot to android, reboot to recovery to validate roll-back, boot to android, reinstall recovery-0.07, disable auto-reflash of recovery - then i had a whole serious of reboots as i planned to replace the animation.zip, and only then bricked)

    for anybody curious, brick symptoms included inability to enter recovery image - so it's possible even with this software to have a shiny new paperweight.
     
Search tags for this page

custom recovery image for droid x

,

verizon droid x recovery.img downloads