• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

All In One Recovery Thread

Status
Not open for further replies.
Jamdat1243 said:
A quick question.
Your new link for 3.06 contains a flash_image file but it isn't zipped. The old link for 2.2.1 contains a flash_image.zip file. Since your instructions indicate that the zip file must be unzipped, I'm a bit confused as there is no zip file for 3.06.
I compared the MD5 checksums for the 3.06 and 2.2.1 flash_image files and they are different.
Has the flash_image been updated for 3.06? Is there something wrong with the download?
Click to expand...

What phone have you?...Maybe you can use Fastboot for flashing the *.img file :], you need only a "fastboot flash recovery recovery-ra-thunderg-3.06-gnm.img", then ENTER in your computer.
 
Has there been any luck with the testing on the Casio C771 running Gingerbread 2.3.3 OTA? I bricked my last one, not being able to create a Nandroid Backup.

Thanks for all your hard work

Twisted
 
can someone help me out i soft bricked my phone im new to rooting like i started yesturday so therefor i skipped some steps i didnt know about on top of that i downloaded a rom for a different phone because mine wasnt on the list ok heres what i did i rooted my phone with ginger break backed it up with with titainium downloaded rom manager and like an idiot thought i was ready for a rom so now my phone is stuck on the lg screen and i get no response from manual recovery or the plugging it in with no batt trick i would really appreciate some help here thanks
 
You didn't mention what kind of phone you have. That would be a great place to start. it's one thing to fix a phone where something happened while following a procedure, but what you did is completely wrong and will be hard to undo.
 
Hey, GNM. I used your recovery on my OptM since I had the phone and recently switched to the LG Esteem. I was looking over the files in your MediaFire and noticed a recovery named Bryce which is the code name for the Esteem/Revolution. I don't see anything in the OP about this particular recovery so I was wondering if this has been tested or what's going on or is it even for my phone. We still don't have a recovery for my phone and would love to use something that you put together. Please let me know if it can be used or not.
Thank you.
 
Aplus said:
Hey, GNM. I used your recovery on my OptM since I had the phone and recently switched to the LG Esteem. I was looking over the files in your MediaFire and noticed a recovery named Bryce which is the code name for the Esteem/Revolution. I don't see anything in the OP about this particular recovery so I was wondering if this has been tested or what's going on or is it even for my phone. We still don't have a recovery for my phone and would love to use something that you put together. Please let me know if it can be used or not.
Thank you.
Click to expand...

That ones a wip for revolution vs910. It works except for usb mass storage afaik. I could use a tester to talk with in irc to finish that one and also to be able to support revution in current ones as Ive added many changes since 3.06.
 
getitnowmarketing said:
That ones a wip for revolution vs910. It works except for usb mass storage afaik. I could use a tester to talk with in irc to finish that one and also to be able to support revution in current ones as Ive added many changes since 3.06.
Click to expand...

Yeah, that's what I thought. The weird thing is that even though the Esteem and Revolution are nearly identical, the CWR they have doesn't work with our phone. I'm not sure what the problem is but we are dying for a custom recovery. Also, when I input the commands you put up for submitting a phone for recovery the headers (dev: size erasesize name) show up but there is nothing below so I can't get the mtd# for recovery. I'm sure there would be a lot of people willing to donate if we could get a recovery for this phone.
Whether you can get a recovery for this phone or not I'm going to drop you some funds around the beginning of Dec. Like I said, I used your recovery for the Optimus M since the very beginning when you were the only one working on that phone.
Thanks for all you've done so far!
 
Aplus said:
Yeah, that's what I thought. The weird thing is that even though the Esteem and Revolution are nearly identical, the CWR they have doesn't work with our phone. I'm not sure what the problem is but we are dying for a custom recovery. Also, when I input the commands you put up for submitting a phone for recovery the headers (dev: size erasesize name) show up but there is nothing below so I can't get the mtd# for recovery. I'm sure there would be a lot of people willing to donate if we could get a recovery for this phone.
Whether you can get a recovery for this phone or not I'm going to drop you some funds around the beginning of Dec. Like I said, I used your recovery for the Optimus M since the very beginning when you were the only one working on that phone.
Thanks for all you've done so far!
Click to expand...

Yeah those directions were meant for nand flash devices not emmc based like revolution. Dump the stock recovery with dd if=/dev/block/mmcblk0pX of=/sdcard/recovery-dump.img bs=4096 and submit it with the partition mapping please. Swap the X above with correct partition #.
 
getitnowmarketing said:
Yeah those directions were meant for nand flash devices not emmc based like revolution. Dump the stock recovery with dd if=/dev/block/mmcblk0pX of=/sdcard/recovery-dump.img bs=4096 and submit it with the partition mapping please. Swap the X above with correct partition #.
Click to expand...

Thanks for the response. How do I know which partition is recovery?

Here is what I got for partitions:

cat /proc/partitions
major minor #blocks name

7 0 3150 loop0
7 1 3150 loop1
253 0 71680 ramzswap0
179 0 7573504 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 36864 mmcblk0p5
179 6 204800 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 1007616 mmcblk0p12
179 13 1572864 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 4194304 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 32 15855616 mmcblk1
179 33 15854592 mmcblk1p1
254 0 3150 dm-0
254 1 3150 dm-1
Click to expand...
 
Aplus can you get me a froyo boot.img or froyo recovery.img for esteem? The 2.6.35 lge kernel is a pain to get usb mass storage working in recovery and I have it working now on revolution with froyo kernel. Also I need the output of cat /proc/mounts pastbin'ed also.
 
getitnowmarketing said:
Aplus can you get me a froyo boot.img or froyo recovery.img for esteem? The 2.6.35 lge kernel is a pain to get usb mass storage working in recovery and I have it working now on revolution with froyo kernel. Also I need the output of cat /proc/mounts pastbin'ed also.
Click to expand...


The Esteem shipped with Gingerbread. As for the mounts, I'll get you that tonight when I get to my comp.
 
Aplus said:
The Esteem shipped with Gingerbread. As for the mounts, I'll get you that tonight when I get to my comp.
Click to expand...

Ill need you to also find the mass storage path. Look in the subdirectories of /sys/devices/platform for a directory /lun0/file. Please give me full path to it.
 
Aplus said:
No problem.

Okay, here is the pastebin.
And here is the lun0 file path.

/sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...

There is also a lun1, not sure if you need to know that.
I also have the Android and kernel source if you need anything from that.
 
I put the recovery on my commando and it works great flawless. Thanks alot. I could really use some new ROMS any would be good can't find anyone who has made them for Commando.
 
getitnowmarketing said:
Please someone else confirm on an optimus device for 3.06.
Click to expand...

I can confirm the new 3.0.6 recovery works on an LG Optimus P500. Successfully made and restored a couple of nandroid backups, did a number of wipes, flashed some kernels and a custom rom.

Thanks for the good work, particularly for the much appreciated new colors (the color scheme of 2.2.1 was awful imho)!
 
Hey im a noob that has been reading up on this and felt confident enough to give it a try but upon me typing all the pertinent info into terminal emulator. my device reboots and went back to stock can someone tell me where i went wrong?
 
Status
Not open for further replies.
Back
Top Bottom