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

getitnowmarketing · August 10th, 2010, 12:26 AM

Outdated : New thread All In One Recovery Thread

Trident · August 10th, 2010, 07:05 AM

I could be missing something since I'm attempting to read this with my Droid, but is there a download link for the recovery.img itself?

By the way, awesome job! Glad you finally got it going!

getitnowmarketing · August 10th, 2010, 08:39 AM

Quote:

Originally Posted by Trident

I could be missing something since I'm attempting to read this with my Droid, but is there a download link for the recovery.img itself?

By the way, awesome job! Glad you finally got it going!

\

Changed the download link to make it stickout more.

Vmanisme · August 10th, 2010, 09:30 AM

Do you have any idea if this will fix the 50% bug? If I got it right this is technically an image from your phone, so if you dont have the bug and I push this to my phone it will replace the OS and no bug?

getitnowmarketing · August 10th, 2010, 10:59 AM

Quote:

Originally Posted by Vmanisme

Do you have any idea if this will fix the 50% bug? If I got it right this is technically an image from your phone, so if you dont have the bug and I push this to my phone it will replace the OS and no bug?

No its a custom recovery that will make rooting very easy and allow you to nandroid backup and allow installing custom roms ie updates.zip. This doesn't touch the OS unless you install a custom rom.

Vmanisme · August 10th, 2010, 11:01 AM

Quote:

Originally Posted by drellisdee

No its a custom recovery that will make rooting very easy and allow you to nandroid backup and allow installing custom roms ie updates.zip. This doesn't touch the OS unless you install a custom rom.

Well dang it... guess I gotta wait for Froyo now =/

getitnowmarketing · August 10th, 2010, 11:13 AM

Quote:

Originally Posted by Vmanisme

Well dang it... guess I gotta wait for Froyo now =/

Well if someone wants to build froyo from AOSP we now have the means to test it and flash it.

Trident · August 10th, 2010, 11:17 AM

Quote:

Originally Posted by drellisdee

Well if someone wants to build froyo from AOSP we now have the means to test it and flash it.

We could technically make a Froyo port from another device. I'm going to chat with Peter Alfonso to see if he feels like it..

Vmanisme · August 10th, 2010, 11:29 AM

Well it would be great to beat LG at their own job lol. I think LG is gonna take their time releasing Froyo, we'll be lucky if we get it before the year is over

Trident · August 10th, 2010, 11:39 AM

Pete said that he is not that experienced at porting but will be in the coming months.

savoxis · August 10th, 2010, 04:16 PM

Incredible! Drellisdee, you are my new hero

zacwhite15 · August 10th, 2010, 09:01 PM

hey guys i am going nuts here. i cannot seem to get my phone to boot into bootloader, i send the command adb reboot-bootloader and it just restarts the phone and loads back into the OS. i am running the V9 build ( i was an idiot and installed the update before realizing that it would break my root) can anyone help me? if you can IM me its zacwhite01 at gmail dot com

****Edit****
hey guys i was able to reflash my phone back to v6, so now i will hopefully get this applied

zacwhite15 · August 10th, 2010, 11:24 PM

hey guys whats the chance of actually flashing this too the rom and configuring a key combination to the kb?

getitnowmarketing · August 11th, 2010, 12:03 AM

Quote:

Originally Posted by zacwhite15

hey guys whats the chance of actually flashing this too the rom and configuring a key combination to the kb?

To permanantly flash it copy recovery-RA_GNM_1.13.img to root of sdcard. Once booted into my temp recovery (fastboot boot recovery-RA_GNM_1.13.img) use command adb shell

Code:

mount /sdcard

 flash_image recovery /sdcard/recovery-RA_GNM_1.13.img

dossa002 · August 11th, 2010, 02:11 AM

I may be wrong, but isn't SEND+MENU+PWR on boot for recovery?

getitnowmarketing · August 11th, 2010, 10:40 AM

Quote:

Originally Posted by dossa002

I may be wrong, but isn't SEND+MENU+PWR on boot for recovery?

I'll be damned that worked when custom recovery was flashed. Didn't work on stock. Updating instructions and thats awesome because now a bad boot.img will not brick phone as you can boot recovery with those keys.

savoxis · August 11th, 2010, 10:42 AM

Quote:

Originally Posted by drellisdee

You can flash it just fine but ally has no kb command to launch fastboot or recovery that we know of. It requires a boot halfway past vzw splash and command adb reboot recovery to launch. To permanantly flash it copy recovery-RA_GNM_1.13.img to root of sdcard. Once booted into my temp recovery (fastboot boot recovery-RA_GNM_1.13.img) use command adb shell

Code:

mount /sdcard

 flash_image recovery /sdcard/recovery-RA_GNM_1.13.img

then still in adb shell type reboot then after reboot do adb reboot recovery to test

Would it be possible to then use something like the quick boot app to force restart to recovery from SW?

ED: Well if SEND+MENU+PWR works after it has been flashed then I guess there is no point

Mitchell4500 · August 11th, 2010, 11:11 AM

I dont understand. How do you do the Send+Menu+Pwr thing. I Hold the buttons down when its off and nothing happens..... (Noob)

savoxis · August 11th, 2010, 11:40 AM

Quote:

Originally Posted by Mitchell4500

I dont understand. How do you do the Send+Menu+Pwr thing. I Hold the buttons down when its off and nothing happens..... (Noob)

I haven't had a chance to test it yet as I haven't flashed the recovery image. If someone could test this that would be great, because ATM there is no way to recover from a bad flash. If we can verify that flashing the recovery image and using send+menu+pwr keypress at boot it will be much "safer" to go forward

zacwhite15 · August 11th, 2010, 11:48 AM

Quote:

Originally Posted by Mitchell4500

I dont understand. How do you do the Send+Menu+Pwr thing. I Hold the buttons down when its off and nothing happens..... (Noob)

lol, first you have to flash the recovery image too your sdcard. after doing that you can access the recovery menu by holding Send+Menu+Power.

if your wondering how to flash to your sdcard, the instructions are a couple posts up from drellisdee.

zacwhite15 · August 11th, 2010, 11:50 AM

Quote:

Originally Posted by savoxis

I haven't had a chance to test it yet as I haven't flashed the recovery image. If someone could test this that would be great, because ATM there is no way to recover from a bad flash. If we can verify that flashing the recovery image and using send+menu+pwr keypress at boot it will be much "safer" to go forward

i can verify that it works, i tested it 5 times just too be sure

now all we need is someone to release a 2.2 image and they will be worshipped by the ally community :P

getitnowmarketing · August 11th, 2010, 12:24 PM

Quote:

Originally Posted by zacwhite15

lol, first you have to flash the recovery image too your sdcard. after doing that you can access the recovery menu by holding Send+Menu+Power.

if your wondering how to flash to your sdcard, the instructions are a couple posts up from drellisdee.

Close its not flashed to your sd card but to the nand flash on your device. The img is copied to your sdcard per my instructions and is flashed to nand using the flash_image.

zacwhite15 · August 11th, 2010, 12:36 PM

Quote:

Originally Posted by drellisdee

Close its not flashed to your sd card but to the nand flash on your device. The img is copied to your sdcard per my instructions and is flashed to nand using the flash_image.

lol ok, i feel blonde now :P

~~amoamare~~ · August 11th, 2010, 01:15 PM

If you dont mind have a application that does this all self automatically.

zacwhite15 · August 11th, 2010, 01:24 PM

hey drellisdee what is that flash_image file thats attached to your first post?

getitnowmarketing · August 11th, 2010, 01:43 PM

Quote:

Originally Posted by zacwhite15

hey drellisdee what is that flash_image file thats attached to your first post?

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.

getitnowmarketing · August 11th, 2010, 01:44 PM

Quote:

Originally Posted by amoamare

If you dont mind have a application that does this all self automatically.

Pm me I was thinking of doing this too.

~~amoamare~~ · August 11th, 2010, 03:36 PM

The application is ready to go.
When ever drellisdee wants people to test it out. I can post it.

~~amoamare~~ · August 11th, 2010, 03:54 PM

Btw with this tool you shouldnt need to have the SDK installed.

getitnowmarketing · August 11th, 2010, 04:18 PM

go ahead and post it. Is it flash_image based?

Robo1007 · August 11th, 2010, 05:26 PM

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!

dossa002 · August 11th, 2010, 06:06 PM

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.

savoxis · August 11th, 2010, 06:26 PM

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)

john122675 · August 11th, 2010, 07:00 PM

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.

getitnowmarketing · August 11th, 2010, 10:23 PM

Quote:

Originally Posted by john122675

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.

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

savoxis · August 11th, 2010, 10:30 PM

Quote:

Originally Posted by john122675

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.

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?

dots · August 12th, 2010, 11:51 AM

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?

getitnowmarketing · August 12th, 2010, 03:00 PM

Quote:

Originally Posted by dots

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?

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

woodsxdragon · August 12th, 2010, 05:28 PM

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

getitnowmarketing · August 12th, 2010, 05:37 PM

What firmware version are you on?

woodsxdragon · August 12th, 2010, 05:46 PM

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.

getitnowmarketing · August 12th, 2010, 05:56 PM

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

Desync · August 15th, 2010, 02:16 PM

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?

orangecrushx526 · August 15th, 2010, 11:45 PM

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?

savoxis · August 16th, 2010, 12:08 AM

Quote:

Originally Posted by orangecrushx526

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?

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 · August 16th, 2010, 01:14 AM

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?

damanddd · August 16th, 2010, 07:59 AM

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

getitnowmarketing · August 16th, 2010, 09:44 AM

Quote:

Originally Posted by orangecrushx526

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?

Please read part # 8 in the how to.

orangecrushx526 · August 16th, 2010, 12:37 PM

k got it working

orangecrushx526 · August 16th, 2010, 12:46 PM

so if i got everything working and i made a nandroid backup, is there any reason to flash the new su2.2.2?