Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.

I'm using "su" binary from AOSP.. which doesn't seem to want to work with Superuser from the market. Oddly, that puts many people who can't seem to get adb to work in a bind. Hrm. Probably the best way to fix it would be to use a "su" binary from another build and load it up in recovery by mounting system (use the recovery gui to do that), then:
adb push su /system/bin
adb shell
cd /system/bin
chmod 6755 su
chown root.root su
exit

Of course you can always wait and just play with it a bit, an I'll have all of this worked out for the next build w/ working HD codecs.

Using terminal emulator I'm getting
"uid 10039 not allowed to su"
"1|u0_a39@android:/"
I can use ADB, but wondering if there's a quick way without hooking it up. (Ive got root explorer, another binary I can use, yada...)

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer? | Terms of Service