[HTC EVO 3D] Lanaka:
Update: Back to work on problem...

Been a while guys. Unfortunately, work becons (or more accurately, intruded). Had to deal with a bunch of sht from my job. Things gone to the dumps there. Well, enuff of that.

In meantime, with my phone being activated and in use, I tried to tether (teeether, ;) hehe) my e4g to my e3d and noticed I'm also having wifi issues. What rang a bell is when I noticed my wifi tether issues disappeared after I turned off 3G. It's like, heeeeey, didn't I read something like this in xda??? After doing some researching (on xda, of course :D ) I've learned that this is also a kernel issue, most often because the new kernel was not properly flashed in conjunction to having the correct matched kernel modules (wifi, CAMERA, 3g/4g, etc.) installed as well. On reading these, I went 'hmmm...' Looks like all of these issues others and I that have been experiencing are all kernel/module misflashes (no thanks to hboot 1.50). Where I think I hit pay dirt is when I found a xda thread that actually explains in depth Flash Image GUI, which was also mentioned earlier in THIS thread (thanks, il Duce).

So, I have downloaded the apk, installed it. Downloaded a new ROM (Olympus Trinity XE Version IV) STRAIGHT to phone...

Oh, just remembered. I've noticed another possible cause of problems. I've originally downloaded the various files from xda and then either push it to phone or more often just enable hardrive mode and drag/dropped it into the phones sdcard directly. Normally, I check the md5 hash on download, but yesterday, I ALSO checked the md5 hash again after moving it to the phone. Meaning, I downloaded ROM to pc, then checked md5 hash, all good. Copied ROM to phone and then checked md5 hash again. NOT good. Somehow, it changed during the copy process. What prompted me to check was I also downloaded Flash Image GUI to pc and copied it to phone and then had phone try install it. It failed to "parse" file correctly, which tells me that the file may have been corrupted. I downloaded Flash Image directly to phone and tried again, and success! Suspicious now, I checked the md5 hash of all three copies of the apk. The laptop downloaded and the phone downloaded copies matched the source's md5, while the COPIED version did NOT match! Whaaa Daaaa FFF(bleep!)!!! I then checked the two copies of the ROM (pc downloaded and phone copied) and they DON'T match!

Sigh. I'm in a area that has poor 3G connection, while ironically, my laptop's 4G was good.

So, I bit the bullet and endured the nearly hour long download of the ROM directly to phone and double checked the hash (which matched the pc downloaded copy, the source didn't provide a hash). THEN I used the Flash Image GUI app to pull the kernel and modules and pop it into phone. Immediately rebooted phone into recovery. Well, tried. Wished Flash Image GUI gave the option to reboot directly into recovery or bootloader, like those 4-/5-/6-1 Reboot options offered in the various ROMs. Because it just simple did a reboot back into System.

I didn't want to take chance with problems with mismatched ROM/kernels (I was on Android Revolution 1.1.1 at the time), so I quickly turned to adb on my laptop and had it reboot phone into recovery.

Once in recovery, I immediately started doing my usual ROM change process. Wiped using every wipe option (except for sdcard) in TWRP (oh btw, I also updated it to 1.1.1 earlier) in both the standard wipe and advanced wipe menus. Once I did so, I then thought, hey where did Flash Image GUI dump the kernels into? Couldn't remember whether it was DATA or SYSTEM. But decided that with Flash Image GUI it's ain't no hassle to reflash the kernel again after the ROM is installed. Besides, read somewhere that some issues was resolved after reflashing the kernel again after the ROM, so wouldn't hurt to try anyway.

Will let ye know how it goes, TWRP is installing Trinity XE as I type this. Gonna continue the SOP by letting it sit for 7-10 minutes. Skip thru init setup. Reboot. Let sit for another 7-10 minutes. Relink my google account. Let first Sync finish. (Basically let it sit again for another 7 minutes). Reboot. Hit Market and download Flash Image GUI, and pay for it, it's well worth IT!!! Flash the ROM's kernel/modules again. Reboot. And hopefully it should be a-ok!

(cross fingers ...on both hands)!

-Lance

PS: Assuming it's fixed, I'm gonna edit the second post and reflag this thread as resolved. Will put what I did to get it fixed, including all necessary links and credits as expected. I know it's premature, but THANKS, I wouldn't have gotten even this far without you guys (and gals) on XDA!

PPS: Also chris.goodman's AnthraX Kernel thread was also quite informative. Mebbe I'll try a ROM that features AnthraX. Somehow, the thought of being over-clocked to ~1.52G sounds appealing! :)