SDA using Qtek 2.6.33 ROM now has MAJOR issues - PLEASE assist!

[Guest notaliberal]

Really hope somebody can offer ANY suggestions - I really don't want to do ANOTHER hard reset. :D

A few days ago I put the new Qtek 2.6.33xxxxx ROM (don't remember the whole number string). Aside from the problems, the ROM is really nice and my phone performed considerably better with it. That being said...

Three times now, I've had the thing get stuck at the windows mobile splash screen. The first time was after I used the reboot command from facade, and no matter what I did I could not get past it and eventually had to hard reset and reflash the ROM. Not cool.

So, once I got everything back on there and running, I used the reboot in facade again, and sure enough the boot hung. This time, I pulled the battery, waited a few, and tried again, and it DID boot, but it ran REALLY slow. So, I shut it down, waited another few minutes, and it booted fine and ran great for about a day.

This morning however, when I went to lock the keypad, I accidentally hit one of the media buttons as well while holding the red phone key, so just as the keys locked TCPMP started. Apparently, that's REALLY bad. I could not unlock the keys anymore while TCPMP was in the foreground. I assume this is because I had TCPMP set to use the 9 key to increase brightness, so it wasn't passing the keycode on to windows?

So, I had to pull the battery, nothing else would work to get it to shut down. Now, of course, the boot hung completely again, and it's stuck at the windows mobile splash screen.

I've left the battery out for over a half hour, and now I've been letting the stuck splash screen sit there for slightly longer than that hoping it will eventually find itself...

So, anybody know what the heck is causing this, and more importantly how to STOP it from happening?

Has anybody found a way to recover from this hang WITHOUT having to lose all my data and hard reset again?

PLEASE, ANY ADVISE APPRECIATED > ALL SUGGESTIONS WELCOME!!!!

Jeff

[Guest notaliberal]

Considering that this is now my 5th time recovering from this, I am seriously surprised nobody else seems to have come across it, or a solution.

Two times ago, I went from the qtek to the imate ROM, both were 2.6.33 whatever...

It happened again on the imate, so I hard reset. Put everything back on except the omap + powercontrol, just in case that was the culprit. Sure enough, happened AGAIN not two hours after I got everything back the way it was.

SO FRIGGIN FRUSTRATING

The only ROM that hasn't done this is the stupid stock t-mobile one. I am, of course, putting that one on now. But that one doesn't run nearly as nicely as the 2.6 ROMS, and it doesn't have the new keypad timeout. But the t-mobile one jsut WONT even run as fast. PocketNester runs PERFECT on the 2.6 roms with omap installed, but with omap installed on the t-mobile one it is ALWAYS jumpy and sluggish.

Does ANYBODY have a solution to this? I really want to run the new ROM, apparently T-mobile [trying not to flame on t-mobile...very hard...must resist...] isn't going to support a new ROM release. SO what can I do?

I was hoping one could create custom ROMS from their phone to be able to quickly recover from that stuff and flash your phone right back to exactly the way you had it, 3rd party apps, reg edits, and all. No response on my post regarding that... :D

Hoping for some help,