Ally Recovery.img is Here!!! Custom Roms!!!


  1. getitnowmarketing

    getitnowmarketing Well-Known Member

    If you flash the recovery from the fastboot boot recovery-RA_GNM_1.13.img flash_image is built into recovery so its not needed. If you do it the other way with root shell not in recovery root shell its needed. Updated instructions for it.
    zacwhite15 likes this.
  2. getitnowmarketing

    getitnowmarketing Well-Known Member

    Pm me I was thinking of doing this too.
  3. The application is ready to go.
    When ever drellisdee wants people to test it out. I can post it.
  4. Btw with this tool you shouldnt need to have the SDK installed.
  5. getitnowmarketing

    getitnowmarketing Well-Known Member

    go ahead and post it. Is it flash_image based?
  6. Robo1007

    Robo1007 Well-Known Member

    Thanks for the hard work from everyone who is doing this your great, I would ove sometime to try and make a rom with a little help! With the root and recovery tool does this mean that even flashing to a bad rom we can recover the phone so it can't be bricked? Also with the root is it just v8 upgrade with superuser access? My wife and I both have ally's and I plan on rooting them and then adding a custom rom when available. Just had those questions thanks guys!
  7. dossa002

    dossa002 Member

    OK, I just wanted to make sure I wasn't crazy. The reason that key combo "didn't work before" was because the stock recovery loads and wipes the data, then checks for an update.zip file. If the file isn't there, it exits immediately. (hence, the quick logo popup)

    Anyway, now I'm kinda bricked due to not flashing the ROM per the suggestion above. Really, I don't know what would have bricked it. (not my ally -- incredible user here) But the thing is, I can't get past the Verizon logo. Since I don't have the custom recovery flashed, I can't use the keypress to get into recovery and stay there. Also, I'm really not sure on the keypress for fastboot. Anyone wanna help me out now? :)

    UPDATE: My bad. So, I'm stuck at the end of the Verizon bootup animation but for whatever reason, I can still get adb running. I should be up and going here shortly.

    UPDATE: So, yes, apparently I got stuck somewhere after the Verizon Wireless animation. Apparently, this far into it you can do ADB and reboot to fastboot if you don't have the recovery flashed. I also restored a Nandroid backup where I hadn't flashed the custom recovery and had to re-flash it.
  8. savoxis

    savoxis Well-Known Member

    Beautiful...

    I wanted to see if this recovery console boot would work, but was too impatient so I tried it at work from my phone... Worked like a charm! Just emailed myself the recov img and the flash_image.bin, moved them with astro and used betterterm to:
    su
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
    mv /sdcard/download/flash_image.bin /sdcard/flash_image
    mv /sdcard/download/recovery-RA_GNM_1.13.img /sdcard/recovery-RA_GNM_1.13.img
    cat /sdcard/flash_image > /system/bin/flash_image
    chmod 755 /system/bin/flash_image
    flash_image recovery /sdcard/recovery-RA_GNM_1.13.img
    reboot

    And like magic I can boot to the recov from my phone.

    Thanks to everyone!
    This is amazing!
    (its lost on my co workers though, I just get blank stares)
    4hed517 likes this.
  9. john122675

    john122675 New Member

    everything seemed to work until flash_image recovery /sdcard/recovery-RA_GNM_1.13.img i got an error then it went everything worked until i tried to hold down send+menu+power it tried to boot into recovery then boots up normal.
  10. getitnowmarketing

    getitnowmarketing Well-Known Member

    If you used flash_image and that still happens use this from recovery adb shell:
    Code:
    / # mount system
     
    / # cd system/etc
     
    / # mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh
    .bak
     
    / # umount system
     
    / # mount /sdcard
     
    / # flash_image recovery /sdcard/recovery-RA_GNM_1.13.img
     
    / # umount /sdcard
     
    / # reboot
    
  11. savoxis

    savoxis Well-Known Member



    Verify that you have recovery-RA_GNM_1.13.img in the root of your SD card by doing a ls /sdcard/recovery* before callling flash_image, also check the md5 if available to make sure the file integrity is good. BTW what is the error?
  12. dots

    dots Well-Known Member

    Not sure if its just me or i did something wrong. But after i turn on my phone holding SEND+MENU+PWR to make sure it worked. Which it did then i rebooted. While booting up my phones LED kept flashing a blue light until the phone booted to the lock screen. Also my SD card was not able to be read by any file browser. Under Settings > SD card and phone settings it showed the amount of free space and total space.

    Anyone else experience this? I've backed up the stuff on my SD card onto my computer and reformated to see if that works.

    UPDATE:

    After reformating the SD card and placing all my contents back on the SD card the file browsers were able to see it. Was it somehow possible i corrupted the card along this process?
  13. getitnowmarketing

    getitnowmarketing Well-Known Member

    yeah did you unmount it? with umount /sdcard in recovery before rebooting?
  14. woodsxdragon

    woodsxdragon New Member

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Woods>cd c:\android\sdk\tools

    c:\android\sdk\tools>adb shell
    $ su
    su
    # mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
    # cat /sdcard/flash_image > /system/bin/flash_image
    cat /sdcard/flash_image > /system/bin/flash_image
    # chmod 755 /system/bin/flash_image
    chmod 755 /system/bin/flash_image
    # mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
    mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
    # flash_image recovery /sdcard/recovery-RA_GNM_1.13.img
    flash_image recovery /sdcard/recovery-RA_GNM_1.13.img
    mtd: read error at 0x00000000 (Out of memory)
    mtd: read error at 0x00020000 (Out of memory)
    mtd: read error at 0x00040000 (Out of memory)
    mtd: read error at 0x00060000 (Out of memory)
    mtd: read error at 0x00080000 (Out of memory)
    mtd: read error at 0x000a0000 (Out of memory)
    mtd: read error at 0x000c0000 (Out of memory)
    mtd: read error at 0x000e0000 (Out of memory)
    mtd: read error at 0x00100000 (Out of memory)
    mtd: read error at 0x00120000 (Out of memory)
    mtd: read error at 0x00140000 (Out of memory)
    mtd: read error at 0x00160000 (Out of memory)
    mtd: read error at 0x00180000 (Out of memory)
    mtd: read error at 0x001a0000 (Out of memory)
    mtd: read error at 0x001c0000 (Out of memory)
    mtd: read error at 0x001e0000 (Out of memory)
    mtd: read error at 0x00200000 (Out of memory)
    mtd: read error at 0x00220000 (Out of memory)
    mtd: read error at 0x00240000 (Out of memory)
    mtd: read error at 0x00260000 (Out of memory)
    mtd: read error at 0x00280000 (Out of memory)
    mtd: read error at 0x002a0000 (Out of memory)
    mtd: read error at 0x002c0000 (Out of memory)
    mtd: read error at 0x002e0000 (Out of memory)
    mtd: read error at 0x00300000 (Out of memory)
    mtd: read error at 0x00320000 (Out of memory)
    mtd: read error at 0x00340000 (Out of memory)
    mtd: read error at 0x00360000 (Out of memory)
    mtd: read error at 0x00380000 (Out of memory)
    mtd: read error at 0x003a0000 (Out of memory)
    mtd: read error at 0x003c0000 (Out of memory)
    mtd: read error at 0x003e0000 (Out of memory)
    mtd: read error at 0x00400000 (Out of memory)
    mtd: read error at 0x00420000 (Out of memory)
    mtd: read error at 0x00440000 (Out of memory)
    mtd: read error at 0x00460000 (Out of memory)
    mtd: read error at 0x00480000 (Out of memory)
    mtd: read error at 0x004a0000 (Out of memory)
    mtd: read error at 0x004c0000 (Out of memory)
    mtd: read error at 0x004e0000 (Out of memory)
    mtd: write error at 0x00000000 (Out of memory)
    mtd: re-read error at 0x00000000 (Out of memory)
    mtd: write error at 0x00000000 (Out of memory)
    mtd: re-read error at 0x00000000 (Out of memory)
    mtd: skipping write block at 0x00000000
    mtd: write error at 0x00020000 (Out of memory)
    mtd: re-read error at 0x00020000 (Out of memory)
    mtd: write error at 0x00020000 (Out of memory)
    mtd: re-read error at 0x00020000 (Out of memory)
    mtd: skipping write block at 0x00020000
    mtd: write error at 0x00040000 (Out of memory)
    mtd: re-read error at 0x00040000 (Out of memory)
    mtd: write error at 0x00040000 (Out of memory)
    mtd: re-read error at 0x00040000 (Out of memory)
    mtd: skipping write block at 0x00040000
    mtd: write error at 0x00060000 (Out of memory)
    mtd: re-read error at 0x00060000 (Out of memory)
    mtd: write error at 0x00060000 (Out of memory)
    mtd: re-read error at 0x00060000 (Out of memory)
    mtd: skipping write block at 0x00060000


    yea i know this is my first post and it's pretty big but i got this error... any thoughts?
    *edit*
    after going for like prolly 15min:
    error writing recovery: No space left on device
    so....?
  15. getitnowmarketing

    getitnowmarketing Well-Known Member

    What firmware version are you on?
  16. woodsxdragon

    woodsxdragon New Member

    2.1-update1 firmware... or is it the SW version? if thats it... VS740ZV8
    i tried it again... it went like this:
    mtd: read error at 0x00000000 (Out of memory)
    mtd: read error at 0x00020000 (Out of memory)
    mtd: read error at 0x00040000 (Out of memory)
    mtd: read error at 0x00060000 (Out of memory)
    mtd: read error at 0x00080000 (Out of memory)
    mtd: read error at 0x000a0000 (Out of memory)
    mtd: read error at 0x000c0000 (Out of memory)
    mtd: read error at 0x000e0000 (Out of memory)
    mtd: read error at 0x00100000 (Out of memory)
    mtd: read error at 0x00120000 (Out of memory)
    mtd: read error at 0x00140000 (Out of memory)
    mtd: read error at 0x00160000 (Out of memory)
    mtd: read error at 0x00180000 (Out of memory)
    mtd: read error at 0x001a0000 (Out of memory)
    mtd: read error at 0x001c0000 (Out of memory)
    mtd: read error at 0x001e0000 (Out of memory)
    # reboot
    reboot

    so i tried to start it using the three keys and it came up with is the yellow !.
    i'm kinda stuck... am i on the wrong sw?
    *edit*
    thanks to amoamare and his awesome program. worked like a charm.
  17. getitnowmarketing

    getitnowmarketing Well-Known Member

    Try rebooting and closing apps with taskiller. If that fails use fasboot way.
  18. Desync

    Desync Well-Known Member

    I'm lost on where he says they go in 2 places. X86 Up Top and AMD Lower part...

    Anyone give me a hint on what that means?
  19. Can anyone explain why i get this error?



    Code:
    C:\users\administrator>cd c:\android\sdk\tool
     
    c:\android\sdk\tools>adb shell
    # su
    su
    # mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
    # cat /sdcard/flash_image > /system/bin/flash_image
    cat /sdcard/flash_image > /system/bin/flash_image
    /sdcard/flash_image: No such file or directory

    One more question...do the flash_image and, recovery-RA_GNM_1.13, go in as zip files?
  20. savoxis

    savoxis Well-Known Member


    I had the same error, the flash_image extracts to flash_image.bin in my case and I had to issue
    Code:
    mv /sdcard/flash_image.bin /sdcard/flash_image
    
    before running.
    orangecrushx526 likes this.
  21. ok thatnks but now when i hold send+menu+pwr i get to recovery for a fracture of a second then the phone boots back up to normal...any idea?
  22. damanddd

    damanddd New Member

    download the new su 2.3 and load it on your sdcard. Then reflash the recovery and apply su .zip before you reboot.
  23. getitnowmarketing

    getitnowmarketing Well-Known Member

    Please read part # 8 in the how to.
  24. k got it working
  25. so if i got everything working and i made a nandroid backup, is there any reason to flash the new su2.2.2?

Share This Page