[G2 and Desire Z Q&A, Help & Troubleshooting] DRSdroid:
I'm running my htc vision with Pyromod v2.0 (2.3.3 gb ROM) with the pyro kernel, which i believe is an altered version of pershoots latest kernel. Fantastic ROM, i've been using it since sunday morning with no problems, it's fast, slick, and incredibly small and responsive...

but, last night i ran the phone, with gps on, and streaming over amazonmp3 app, got to my location, sent a text, closed the keyboard, and hit the power button to put the screen to sleep. I got out of my car, walked up to the front door and was about to call to be let in, take out my phone, screen won't turn on, buttons on the bottom the screen light up and respond as normal. I have it set so i can hit the back button to unlock, so i hit back, and adjust the volume.. i hear the tone, so i knew i was on the main screen and past the lockscreen. After i get into the apt after being noticed, i do a battery pull. The phone reboots, i heard the vibrate that comes on right when the htc boot logo comes up, but STILL NOTHING on the screen! I try this a few more times.. let it boot, and have my girlfriend call me, she does, phone rings and i can answer it, touchscreen is responsive to slide to answer, but NOTHING on screen! phone functions, but the screen won't turn on. i leave the battery out overnight, in the morning my gf puts the battery in while i'm in the bathroom, unknown to me.. i come back and she holds up my phone, booting up, screen on.. needless to say i was thrilled! Flash forward, i'm at work during the day, screen and phone have been working fine.. around 3.. i turn the screen off.. and it doesn't turn back on again, same as before!

Now that i'm home i have messed with it a bit, if i leave the "blank" screen on while the phone is charging, eventually it times out.. but when i hit to power it on again for a 2nd time, the screen returns to life... but if i turn it off i have to do that again.

I've tried changed the cpu scaling, removing software.. but deep down i don't think that it's a problem with the software, does anyone think it could be the rom?

I guess my questions are

-does anyone know how i can test the unit via adb to see what's wrong?

-has anyone experienced anything like this before?

-anyone know where i can find the stock rom in case i have to return this thing?

EDIT: UPDATE: Here is the Logcat from my device

https://rapidshare.com/files/2442882484/logcat.txt

Pretty much this is what happens when i tried to turn the screen on and got nothing

I/power ( 1340): *** set_screen_state 0

W/IInputConnectionWrapper( 3292): getExtractedText on inactive InputConnection

W/IInputConnectionWrapper( 3292): getExtractedText on inactive InputConnection

D/SurfaceFlinger( 1340): About to give-up screen, flinger = 0x93b98

D/TEST] ( 2419): There are 0 instances of Clock

I/com.dropbox.android.activity.lock.LockReceiver( 3322): Received action: android.intent.action.SCREEN_OFF

D/AK8975 ( 1234): Compass CLOSE

D/dalvikvm( 3322): GC_EXPLICIT freed 293K, 51% free 3343K/6791K, external 1K/513K, paused 79ms

D/dalvikvm( 3153): GC_EXPLICIT freed <1K, 51% free 2750K/5511K, external 0K/0K, paused 86ms

I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/H7CTransparentBlack_base_small_95.png

I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png

I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png

I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png

I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_chancestorm.png

I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlycloudy.png

I/power ( 1340): *** set_screen_state 1

D/SurfaceFlinger( 1340): Screen about to return, flinger = 0x93b98

D/AK8975 ( 1234): Compass Start

D/TEST] ( 2419): There are 0 instances of Clock

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 334K, 53% free 2881K/6023K, external 1331K/1444K, paused 42ms

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 316K, 53% free 2846K/6023K, external 932K/1163K, paused 35ms

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 53K, 49% free 3127K/6023K, external 1524K/1725K, paused 35ms

D/dalvikvm( 1340): GC_EXTERNAL_ALLOC freed 169K, 53% free 6663K/14151K, external 4375K/4478K, paused 72ms

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 349K, 53% free 2881K/6023K, external 1314K/1381K, paused 28ms

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 317K, 53% free 2845K/6023K, external 932K/1163K, paused 34ms

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 46K, 53% free 2879K/6023K, external 1612K/1725K, paused 35ms

D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 316K, 53% free 2844K/6023K, external 932K/1163K, paused 26ms

D/dalvikvm( 1340): GC_EXTERNAL_ALLOC freed 25K, 53% free 6658K/14151K, external 4405K/4478K, paused 69ms

D/GoogleVoice( 3139): MASFUpdateSettingsRpc.createRequestPayload: ENT

D/GoogleVoice( 3139): MASFUpdateSettingsRpc.createRequestPayload: RET

I/System.out( 3139): [INFO:5970349]: LogSource: Running flush

I/System.out( 3139): [INFO:5970352]: LogSource: Sending payload [bytes=660]