[Starfox]

Couple of things.

1) The sequence of events for me went like this:
Try to flash rhodimg -> Find out I didn't have HSPL on this one (I think this was the third one replaced), had to find the unlocker, then find out that it needs an internet connection to HSPL. Of course, it also needs an ActiveSync, so can't PAM while doing it (since it is my Internet). Ended up using Wi-Fi Tether to keep a connection long enough for it to HSPL.

Tri-color-flash RHODIMG. Boot into mpl. Windows throws up an unknown device error. I had the ADB set up under haret, so I freak out. NANDROID says something about a driver I needed to download. Flash into Factory, haret and download said driver. Flash mpl again. Driver doesn't take. It actually does _not_ need the driver bundle, but you need to force it to use Android devices -> HTC Dream. Fastboot seems to be working now (freaked out right after driver install, but I see it waiting after it rebooting on its own).

Fastboot recovery. Use fastboot reboot, it complains about flash errors. Try various permutations of fastboot flash recovery/fastboot erase <stuff>. Still nothing. On a whim try fastboot boot recovery.img. I get into cwm-ish screen. Apply omgb. It says successful.

mpl shows valid flash now, but any attempts to boot either results in a single-vibrate reboot (most of the time) OR a dual-vibrate and the splash screen for a second THEN a reboot (usually only once). Try going into recovery again, and flash omgb. No dice. Start from fastboot flash recovery, nothing either. Found out it still can get into tri-color by holding Vol-Dn. Re-flash mpl again, go through the same process. Nothing. Gave up for now and reflashed factory so I can get into haret.

2) Observations:
Technically it doesn't seem to require a recovery flash at all, only need mpl to load recovery via End->fastboot boot recovery.img trick. Other than the convenience factor of having a recovery handy, can you actually bypass having to flash recovery?

I see some kernel parms while mpl attempted to boot omgb. Where are these stored, and what's the procedure for changing it, i.e. overclocking, etc.

Says native tethering isn't working. Are the menu items not present/disabled, or is it just not working when you try to enable it? For me this would be a killer, since I do keep AP Mode on. I could try to figure stuff out via EasyTether to try to debug the issue.

I saw some "expert mode" in the recovery from Oct 1st recovery.img, selecting it dimmed the screen and told me to hit End to get out. It completely refused to respond to keys after that, so I had to pull battery. Was this the charging thing that was addressed in the new recovery this morning?

If I were to try to roll my own kernel, what would be the procedure to get it flashed? I assume I'd have to use anykernel-type thing and create an update.zip to flash via recovery.

And what's the best minimal "wm" rhodimg to keep handy just in case I do need to access FRX? Flashing factory takes too long and seems to unnecessarily kill flash cells just to get to haret.

-- Starfox