[Droid Eris Android Development] jmanley69:
Ok... Who's ready to try this.... I have absolutely no idea if this will work.

The concept I'm going to go on is that their RUU is expecting the file to pass the signature test BEFORE it actually starts the process...

Here's what we're going to do (in a nutshell). We're going to let the RUU get everything ready, unpack all its little pieces and then we're going to change the little pieces right before it puts them on the phone.

I offer no warranties or guarantees. As I see it, there are 3 possible outcomes:

The phone does not update because the zip file's md5 has changed

The phone updates, but the recovery image does not stay after a reboot

The phone updates without applying our changes (in which case you have an MR1 phone - which isn't necessarily a bad thing since we can't root the one you have anyway)

Follow these instructions carefully, and please note the ALL CAPS SECTION

Please read the entire instruction set carefully before trying the first step. If you are unsure about any of the steps, I recommend that you do not attempt this. This requires a certain degree of computer proficiency. If you don't feel comfortable doing this, or don't understand the process... PLEASE DO NOT ATTEMPT. Wait until somebody else does it and if it's successful, we can help you through it.

DO NOT CONNECT YOUR PHONE TO YOUR COMPUTER VIA THE USB CABLE

Locate your temp folder

If you're using Windows 7/Vista, it's located in c:\users\{username}\AppData\Local\Temp (AppData is hidden from you, but you can go directly to it by clicking the start "button" and typing in the path directly)

If you're using Windows XP, it's usually in c:\Document and Settings\{username}\Application Data\Temp (again, hidden, but click Start -> Run -> and type the complete path and you'll get there)

To check, go to the command prompt (doesn't matter what OS) and type set<enter> Find the entry for TEMP= and it'll tell you the path to your temp folder

Once you've found and opened the temp folder, delete everything. Yes... Everything. You will get some errors that files or folders couldn't be deleted. If you have XP, deselect those files/folders and continue to delete EVERYTHING. If you have Vista/Windows 7, it'll just say "Hey... I can't delete these, wanna skip?" - go ahead and skip

DO NOT CLOSE YOUR TEMP FOLDER

Download the RUU from the link previously in this thread.

DO NOT CONNECT YOUR PHONE TO YOUR COMPUTER VIA THE USB CABLE

unzip it to your hard drive and execute RUU_Desire_C_Verizon_WWE_1.16.605.1_release_signed_with_driver.exe

DO NOT CONNECT YOUR PHONE TO YOUR COMPUTER VIA THE USB CABLE

Watch your temp folder and you'll see some new folders that look like GUID's {#######-####-###......} Open each of those.

In one, you'll see Devcon_x86 - disregard this folder

In one, you see files including _Setup.dll and a folder Disk1 - disregard this folder

In one folder, you find another folder that looks like a GUID, coredump.ini, dotnetinstaller.exe. open the only folder in this subdirectory and you'll see a bunch of files... adb.exe... blah blah blah... rom.zip.

Copy rom.zip to someplace else (like the desktop)

Open the copy with winzip or windows, or winrar... locate and delete recovery.img

Download recovery.zip from here, unzip it, and put recovery.img into rom.zip

Replace rom.zip in your temp files with the newly modified rom.zip

Continue setup of the RUU, and connect your phone via USB when prompted by the RUU.

Like I said, there are 3 options (see above). If it works... your phone will go through the process, and try to boot. let it (because I don't know what damage interrupting this process can cause), but once it's up... turn the phone off and try to go to recovery (if it's like the Sprint Hero, hold down Vol-Down and Power until you get a white screen, then press Home). If this method did indeed put our custom recovery image on your phone, you'll be presented with the Amon-Ra recovery... from here, we can apply an update.zip which puts su on your phone and you're rooted.

If the process does not work, you will either end up with a phone that has MR1 and no custom recovery.img, or the RUU will stop because rom.zip has changed from what it's expecting.

I do not believe that this will brick your phone. The custom recovery has the kernel that is specific for this phone, and we have not changed any other files in the rom.zip.

If all else fails, you can always do the RUU again and let it put MR1'S ROM on your phone. Keep in mind, this will be a one way path. Once you've put MR1 on your phone, you cannot go back (without an RUU from HTC/Verizon).