[HTC EVO 3D] Lanaka:
Ok, I'll give it a try next after the ones I've already downloaded. I'm a methodical type of guy (don't like leaving thing left undone).

That's what I'm figuring. I start reading the original set of posts, then randomly check out a few posts in the middle, and then read the last 10%. The roms i've picked mostly had either minor issues caused by misflashing or other user errors. A few actually said had an issue or two but nothing that'd stop me from giving the rom a try.

Yup, that's the MO I've been using as instructed in the following thread:

http://xdaforums.com/showthread.php?t=1239821

I'll go thru the step-by-step process I used and you can nitpick where I went wrong, :)

I've placed a copy of adb.exe, AdbWinApi.dll, fastboot.exe and TWRP's recovery.img into folder c:\adb\

A little tip here, as I play with windoze XP a lot, a trick I used to eliminate the need to cd so much with cmd.exe. I did this after the 3rd ROM!

I place a shortcut link to cmd.exe into this same folder with the above files and exes. Next I open the Properties window for this shortcut, I made the following changes:

Start In: c:\adb

Comment: Starts cmd.exe in adb folder.

What happen is that cmd will open its window with the c-prompt already IN the same directory as my android files. Also, when i mouse-over the shortcut icon, it will popup a message reminding me that this link starts cmd.exe in adb folder.

Then I do the following:

I connect the phone to the laptop using the usb cable, set the phone to disk drive mode. Once Windows recognizes the volume and mounts it, I type the following:

c:\adb>adb reboot bootloader

After the e3d reboots into hboot, I then type the following:

c:\adb>fastboot boot recovery.img

downloading 'boot.img'... OKAY [ 1.250s]

booting... OKAY [ 0.000s]

finished. total time: 1.250s

Once TWRP loads, I then switch to the phone (WITHOUT disconnecting the phone from the laptop). Here on, I use the keys on the phone to navigate to the necessary functions. The proceedure I used mirrors what Steel25 suggested in the following thread:

http://xdaforums.com/showthread.php?t=1269610

I initially thought it was an overkill, but figured probably wouldnt hurt to be safe than sorry.

If the installed rom is something I liked, I nand it first...

I then enter the Wipe Menu proceed to hitting each of the following:

Wipe Cache

Wipe Dalvik Cache

Wipe Everything (Data Factory Reset)

Wipe Battery Stats

Then I go to Advanced/Format Menu and hit each of the following:

Format SYSTEM (/system)

Format DATA (/data)

Format CACHE (/cache)

Format SD-EXT (/sd-ext)

Then I go back to top menu and enter Install Zip Menu, and first I hit:

Wipe Cache and Dalvik Cache

Then I enable:

Reboot After Successful Flash

THEN I:

Choose Zip To Flash

(Navigate to where the rom or app zip is located and select it.) Here I take a break and let TWRP does it thingy and check back on the phone in 5 minutes or so.

After recovery reboots the phone back into system, I let the phone sit on the lockscreen for 10 minutes to let the rom complete it's init process. Then I skip thru the entire initial setup prompts (altho I enter NO for Tell HTC). I reboot phone back into system, let it sit for another 5 minutes on the lockscreen before I hit the Android Market app to trigger the process of linking the phone to my google account. I then let my account sync. Once my new email icon pops up on the notification bar, I check out the camera. By the time I've hit the 3rd rom, I've had read about the camera problem possibly being a kernel level issue, I've since then added this step....

Menu/Settings/About Phone/Software information/More

Here I took note on whether the Kernel version info has changed as well. (And for the most part, yes, the kernel information DOES change with each rom).

K, now ye can start thrashing me... ;)

-Lan