Database Develop

[Q] WiFi suddenly stopped working (error state)

Hi, I have been using a stable early version of CM5 on my T-Mobile G1 for about 5 months and one day (about 1 week ago) the WiFi failed while connecting to my home network, and since then, the WiFi has been in an error state; not being able to bee off or on. On the Power Widget, the WiFi indicator has a faded blue bar and even trying to enable it within the Android settings fails and says "error" as the state (as opposed to "Connected" or "Off").
I have tried rebooting, shutting down, removing the battery for a minute, and even wiping completely and re-flashing with CM 6.0 DS stable, yet the issue persists.
Oddly, when I do "netcgf" in the terminal emulator, I don't see a eth0 or wlan0 to tiwlan0 as a device. I only get this:
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
So I though my wlan hardware was not initialized properly, so I went through dmesg and the driver seems to have loaded and encountered an error and then uloaded as seen by the following:
<6>[ 364.669433] TIWLAN: Driver loading
<4>[ 364.669952] wifi_probe
<4>[ 364.672363] trout_wifi_power: 1
<4>[ 364.859588] trout_wifi_reset: 0
<4>[ 364.902343] trout_wifi_set_carddetect: 1
<7>[ 364.902770] mmc0: card_present 1
<6>[ 364.902984] mmc0: Slot status change detected (0 -> 1)
<4>[ 367.466888] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 367.473815] mmc0: new SDIO card at address 0001
<6>[ 367.481750] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 367.495544] TIWLAN: Driver initialized (rc 0)
<4>[ 367.497406] TIWLAN: 1251 PG 1.2
<6>[ 367.497924] TIWLAN: Driver loaded
<4>[ 367.916229] select 611 (android.protips), adj 9, size 3310, to kill
<4>[ 367.916900] send sigkill to 611 (android.protips), adj 9, size 3310
<3>[ 370.497741] mmc0: Data timeout
<3>[ 370.497863] SDIO_SyncRead: failed (-110)
<3>[ 370.498382] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 387.593353] TIWLAN: Driver unloading
<6>[ 389.263336] TIWLAN: 4241.654203: sdio_reset_comm():
<4>[ 389.286865] mmc0: Error resetting SDIO communications (-110)
<7>[ 389.554901] TIWLAN: Releasing SDIO resources
<7>[ 389.557556] TIWLAN: SDIO resources released
<4>[ 389.560882] wifi_remove
<4>[ 389.561370] trout_wifi_set_carddetect: 0
This repeats a few times before the phone just gives up trying to load the driver.
Another instance later on of afailed attempt to load the driver is shown here:
TIWLAN: Driver loading
<4>[ 482.536315] wifi_probe
<4>[ 482.536773] trout_wifi_power: 1
<4>[ 482.767944] trout_wifi_reset: 0
<4>[ 482.815704] trout_wifi_set_carddetect: 1
<7>[ 482.815948] mmc0: card_present 1
<6>[ 482.816345] mmc0: Slot status change detected (0 -> 1)
<4>[ 485.376586] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 485.380371] mmc0: new SDIO card at address 0001
<6>[ 485.387268] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 485.397033] TIWLAN: Driver initialized (rc 0)
<4>[ 485.398773] TIWLAN: 1251 PG 1.2
<6>[ 485.399230] TIWLAN: Driver loaded
<3>[ 487.699493] mmc0: Data timeout
<3>[ 487.699829] SDIO_SyncRead: failed (-110)
<3>[ 487.701110] TIWLAN: TIWLAN: Failed to start config manager
<4>[ 489.264953] select 704 (android.vending), adj 7, size 3865, to kill
<4>[ 489.265380] send sigkill to 704 (android.vending), adj 7, size 3865
<6>[ 505.471527] TIWLAN: Driver unloading
<6>[ 507.093597] TIWLAN: 64.402242: sdio_reset_comm():
<4>[ 507.117187] mmc0: Error resetting SDIO communications (-110)
<7>[ 507.379547] TIWLAN: Releasing SDIO resources
<7>[ 507.382232] TIWLAN: SDIO resources released
<4>[ 507.385589] wifi_remove
<4>[ 507.386077] trout_wifi_set_carddetect: 0
<7>[ 507.386901] mmc0: card_present 0
<6>[ 507.387359] mmc0: Slot status change detected (1 -> 0)
<6>[ 507.388397] mmc0: card 0001 removed
Has anyone experienced this and/or have a fix? It seems like I need to replace a file or two for the TIWLAN driver.
I have attached the entire dmesg from first boot of CM6 to now, which is about 5 minutes worth (not much).
Thanks a lot,
Mike

Sorry to bump this, but I would like some sort of guidance if I can fix this so I don't have to buy a new phone I love my G1. No keyboard compares.
I made some fixes, change some permissions and now I get one and only one error cosistenly in dmesg when trying to start the WiFi, and hence the TIWLAN driver.
<6>[31876.845947] TIWLAN: Driver loading
<4>[31876.846466] wifi_probe
<4>[31876.846832] trout_wifi_power: 1
<4>[31877.008209] trout_wifi_reset: 0
<4>[31877.049407] trout_wifi_set_carddetect: 1
<7>[31877.049682] mmc0: card_present 1
<6>[31877.049896] mmc0: Slot status change detected (0 -> 1)
<4>[31879.608001] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<6>[31879.611785] mmc0: new SDIO card at address 0001
<6>[31879.623321] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[31879.637817] TIWLAN: Driver initialized (rc 0)
<4>[31879.638366] TIWLAN: 1251 PG 1.2
<6>[31879.638610] TIWLAN: Driver loaded
<3>[31880.067932] config_partition: Error writing size
<3>[31880.068664] TIWLAN: TIWLAN: Failed to start config manager
<6>[31899.710571] TIWLAN: Driver unloading
<6>[31901.334014] TIWLAN: 3652.788872: sdio_reset_comm():
<4>[31901.357391] mmc0: Error resetting SDIO communications (-110)
<7>[31901.620971] TIWLAN: Releasing SDIO resources
<7>[31901.627258] TIWLAN: SDIO resources released
<4>[31901.630523] wifi_remove
<4>[31901.631561] trout_wifi_set_carddetect: 0
<7>[31901.632049] mmc0: card_present 0
<6>[31901.632507] mmc0: Slot status change detected (1 -> 0)
<6>[31901.633911] mmc0: card 0001 removed
<4>[31901.639007] trout_wifi_reset: 1
<4>[31901.682708] trout_wifi_power: 0
<6>[31901.848754] TIWLAN: Driver unloaded
The culprits are
<3>[31880.067932] config_partition: Error writing size
<3>[31880.068664] TIWLAN: TIWLAN: Failed to start config manager
I have no idea why the partition size is trying to be written (or perhaps the file size of the config file?) but that is preventing what would otherwise be a smooth loading of the WiFi driver.
If anyone has any suggestions or can provide any help, I would greatly appreciate it!
Thanks in advance,
Mike

Same here
gtabmx said:
Hi, I have been using a stable early version of CM5 on my T-Mobile G1 for about 5 months and one day (about 1 week ago) the WiFi failed while connecting to my home network, and since then, the WiFi has been in an error state; not being able to bee off or on. On the Power Widget, the WiFi indicator has a faded blue bar and even trying to enable it within the Android settings fails and says "error" as the state (as opposed to "Connected" or "Off").
I have tried rebooting, shutting down, removing the battery for a minute, and even wiping completely and re-flashing with CM 6.0 DS stable, yet the issue persists.
Oddly, when I do "netcgf" in the terminal emulator, I don't see a eth0 or wlan0 to tiwlan0 as a device. I only get this:
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
So I though my wlan hardware was not initialized properly, so I went through dmesg and the driver seems to have loaded and encountered an error and then uloaded as seen by the following:
<6>[ 364.669433] TIWLAN: Driver loading
<4>[ 364.669952] wifi_probe
<4>[ 364.672363] trout_wifi_power: 1
<4>[ 364.859588] trout_wifi_reset: 0
<4>[ 364.902343] trout_wifi_set_carddetect: 1
<7>[ 364.902770] mmc0: card_present 1
<6>[ 364.902984] mmc0: Slot status change detected (0 -> 1)
<4>[ 367.466888] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 367.473815] mmc0: new SDIO card at address 0001
<6>[ 367.481750] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 367.495544] TIWLAN: Driver initialized (rc 0)
<4>[ 367.497406] TIWLAN: 1251 PG 1.2
<6>[ 367.497924] TIWLAN: Driver loaded
<4>[ 367.916229] select 611 (android.protips), adj 9, size 3310, to kill
<4>[ 367.916900] send sigkill to 611 (android.protips), adj 9, size 3310
<3>[ 370.497741] mmc0: Data timeout
<3>[ 370.497863] SDIO_SyncRead: failed (-110)
<3>[ 370.498382] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 387.593353] TIWLAN: Driver unloading
<6>[ 389.263336] TIWLAN: 4241.654203: sdio_reset_comm():
<4>[ 389.286865] mmc0: Error resetting SDIO communications (-110)
<7>[ 389.554901] TIWLAN: Releasing SDIO resources
<7>[ 389.557556] TIWLAN: SDIO resources released
<4>[ 389.560882] wifi_remove
<4>[ 389.561370] trout_wifi_set_carddetect: 0
This repeats a few times before the phone just gives up trying to load the driver.
Another instance later on of afailed attempt to load the driver is shown here:
TIWLAN: Driver loading
<4>[ 482.536315] wifi_probe
<4>[ 482.536773] trout_wifi_power: 1
<4>[ 482.767944] trout_wifi_reset: 0
<4>[ 482.815704] trout_wifi_set_carddetect: 1
<7>[ 482.815948] mmc0: card_present 1
<6>[ 482.816345] mmc0: Slot status change detected (0 -> 1)
<4>[ 485.376586] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 485.380371] mmc0: new SDIO card at address 0001
<6>[ 485.387268] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 485.397033] TIWLAN: Driver initialized (rc 0)
<4>[ 485.398773] TIWLAN: 1251 PG 1.2
<6>[ 485.399230] TIWLAN: Driver loaded
<3>[ 487.699493] mmc0: Data timeout
<3>[ 487.699829] SDIO_SyncRead: failed (-110)
<3>[ 487.701110] TIWLAN: TIWLAN: Failed to start config manager
<4>[ 489.264953] select 704 (android.vending), adj 7, size 3865, to kill
<4>[ 489.265380] send sigkill to 704 (android.vending), adj 7, size 3865
<6>[ 505.471527] TIWLAN: Driver unloading
<6>[ 507.093597] TIWLAN: 64.402242: sdio_reset_comm():
<4>[ 507.117187] mmc0: Error resetting SDIO communications (-110)
<7>[ 507.379547] TIWLAN: Releasing SDIO resources
<7>[ 507.382232] TIWLAN: SDIO resources released
<4>[ 507.385589] wifi_remove
<4>[ 507.386077] trout_wifi_set_carddetect: 0
<7>[ 507.386901] mmc0: card_present 0
<6>[ 507.387359] mmc0: Slot status change detected (1 -> 0)
<6>[ 507.388397] mmc0: card 0001 removed
Has anyone experienced this and/or have a fix? It seems like I need to replace a file or two for the TIWLAN driver.
I have attached the entire dmesg from first boot of CM6 to now, which is about 5 minutes worth (not much).
Thanks a lot,
Mike
Click to expand...
Click to collapse
I'm having the same problem. I've done a factory reset and went to wifi settings. As soon as I tried to turn on the wifi again the word "error" came back.
Someone please help

Same here. mine started this sh*t 2 days ago. been runnin cm6.1.1 for bout 3 weeks now.

Hi,
I face the same issue with my developer phone 2..

Okay.. it resumed after factory data reset!
A more detailed survey of this error can be found on the android-tether developer website.. I cannot post links as i am a new member here... But it can be found as the first google link for the search string "google code issue 1124"

WiFi connection problems

Hey guys,
i'm having really bad wifi issues on various roms (KoR 1.1 + MiuiMod) and kernels (WM, Pershoot, Intersect) right now.
What happens is, i switch on wifi and it scans and finds the registered router, but when i try to connect it somehow stays stuck scanning or it says getting ip and then switches itself off again.
i pulled a log from OSMonitor and quite a lot of stuff seems to be going bad
10/30/2010 16:01:29 [INFORMATION] samsung_oled_panel_unblank: -()
10/30/2010 16:01:30 [WARNING] wifi_set_power = 1
10/30/2010 16:01:30 [WARNING] mahimahi_wifi_power: 1
10/30/2010 16:01:30 [WARNING] wifi_set_carddetect =
10/30/2010 16:01:30 [INFORMATION] mahimahi_wifi_set_carddetect: 1
10/30/2010 16:01:30 [DEBUG] mmc0: card_present 1
10/30/2010 16:01:30 [INFORMATION] mmc0: Slot status change detected (0 -> 1)
10/30/2010 16:01:30 [WARNING]
10/30/2010 16:01:30 [WARNING] Dongle Host Driver, version 4.218.248.10
10/30/2010 16:01:30 [WARNING] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
10/30/2010 16:01:30 [INFORMATION] mmc0: new high speed SDIO card at address 0001
10/30/2010 16:01:30 [WARNING] DHD: dongle ram size is set to 294912(orig 294912)
10/30/2010 16:01:31 [WARNING] wifi_get_mac_addr
10/30/2010 16:01:31 [WARNING] Firmware version = wl0: Apr 22 2010 10:02:12 version 4.218.223.0
10/30/2010 16:01:31 [WARNING] eth0: Broadcom Dongle Host Driver mac=00:23:76:b1:01:df
10/30/2010 16:01:32 [WARNING] STA connect received 1
10/30/2010 16:01:41 [DEBUG] eth0: no IPv6 routers present
10/30/2010 16:01:58 [WARNING] wifi_set_power = 0
10/30/2010 16:01:58 [WARNING] mahimahi_wifi_power: 0
10/30/2010 16:01:59 [WARNING] wifi_set_carddetect =
10/30/2010 16:01:59 [INFORMATION] mahimahi_wifi_set_carddetect: 0
10/30/2010 16:01:59 [DEBUG] mmc0: card_present 0
10/30/2010 16:01:59 [INFORMATION] mmc0: Slot status change detected (1 -> 0)
10/30/2010 16:01:59 [INFORMATION] mmc0: card 0001 removed
10/30/2010 16:02:35 [INFORMATION] batt: 89%, 4021 mV, -120 mA (-199 avg), 22.1 C, 1182 mAh
Click to expand...
Click to collapse
also check out this really long error log here:
http://pastebin.com/Si5dB9WH
this keeps going on until it just magically connects (or i give up). a reboot also solves the problem and gets me a direct connection
any idea whats going on please help me?

bump! please i still havent solved this

Nexus One Reboot Freezes what could be the problem?

So i have two nexus's one is perfect. However I also have my old one (before htc sent me the new one) it has a major problem were the phone will usually not boot and if it does after a few minutes of use will reboot and vibrate a bunch of times.
So what do you guys think could be the problem??? I'm thinking the logic board?
I'm asking because i am thinking about fixing it myself

Do an ADB logcat.
The phone doesn't have to completely boot to start it. This is the best way to determine at what point the phone stops. I use these when I get a boot loop.

K I will try that and post back
Sent from my Nexus One using XDA App

Search the forum using "vibrations" keyword.

Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around. It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Code:
E/CameraInput < 59>: Recording is not ready <iPeer 0x1fc94 iState 2 iWriteState
1 iClockState 0>, frame dropped
I/AudioHardwareQSD< 59>: AudioHardware pcm playback is going to standby.
And that's it thats last thing before it crashed and turned off... Any ideas what means in english? something about audio but i don't know if that is realated
EDIT: And yes it is the seven vibrations problem

What radio are you using?

Jack_R1 said:
What radio are you using?
Click to expand...
Click to collapse
5.12 right now but i have tried all of them. Same problem. Almost all the kernels and roms too. from stock to cyanogen to miui.
Non make a difference. The phone clearly has a hardware problem i just want to identify which piece of hardware

"adb bugreport" will help much more.
Also, "cat /proc/kmsg" and "cat /proc/last_kmsg", too.

Clear cache
Sent from my Nexus One using XDA App

I have cleared cache a hundred times...
I am going to try the other adb commands

Tech_Boy said:
Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around.
It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Click to expand...
Click to collapse
Right click anywhere in the window itself and select: edit, then select all
After everything is highlighted again right click on anywhere on the window and select: edit, then copy
You can then paste this into a notepad to edit it, or whatever.
Also as mentioned, try adb bugreport as well that could help.

Ok this is what i got. I don't understand much of it, so i don't know what i am looking for.
I ran the first two the third gave a file no found error... Also I notice cmd didn't copy the whole thing, like when it reaches a certain amount of lines it cuts off the top stuff
Code:
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #2 Window{44ac0690 SurfaceView paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,38)(480x762) gr=#33 ty=1000 fl=#24218 fmt=-3}
mAttachedWindow=Window{44b7ce48 com.android.launcher/com.android.launcher2.L
auncher paused=false} mLayoutAttached=true
mBaseLayer=21000 mSubLayer=1 mAnimLayer=21010+0=21010 mLastLayer=21010
mToken=WindowToken{44ac0630 [email protected]}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
mPolicyVisibility=true mPolicyVisibilityAfterAnim=true mAttachedHidden=true
Requested w=480 h=762 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,38][480,800] last=[0,38][480,800]
mFrame=[0,38][480,800] last=[0,38][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #1 Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) sim=#20 ty=1 fl=#110100 fmt=-2 wanim
=0x1030001}
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21005+0=21005 mLastLayer=21005
mToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.laun
cher/com.android.launcher2.Launcher}}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=480 h=800 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
Window #0 Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=fa
lse}:
mSession=Session{44a8e370 uid 10029} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) gr=#33 ty=2013 fl=#318 fmt=-1 wanim=
0x1030075}
mIsImWindow=false mIsWallpaper=true mIsFloatingLayer=true mWallpaperVisible=
false
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21000+0=21000 mLastLayer=21000
mSurface=Surface(name=com.android.wallpaper.nexus.NexusWallpaper, identity=4
)
Surface: shown=false layer=21000 alpha=1.0 rect=(0,0) 480 x 800
mToken=WindowToken{449909f0 [email protected]}
mRootToken=WindowToken{449909f0 [email protected]}
mViewVisibility=0x0 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=-1 h=-1 mLayoutSeq=318
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,0][480,800] mVisibleFrame=[0,0][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mAnimating=false mLocalAnimating=false mAnimationIsEntrance=true mAnimation=
null
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
All active sessions:
Session Session{44bcab88 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4a1cd90
Session Session{44b399c8 uid 10028}:
mNumWindow=2 mClientDead=false [email protected]
49a1ed8
Session Session{44a8e370 uid 10029}:
mNumWindow=1 mClientDead=false [email protected]
4960760
Session Session{44ac1528 uid 10018}:
mNumWindow=0 mClientDead=false [email protected]
49c5ee0
Session Session{44af3498 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4af4eb8
All tokens:
Token null:
token=null
windows=[Window{44af4960 StatusBar paused=false}, Window{44b24fa0 TrackingVi
ew paused=false}, Window{44af8488 StatusBarExpanded paused=false}]
windowType=-1 hidden=false hasVisible=true
Token [email protected]:
[email protected]
windows=[]
windowType=2011 hidden=false hasVisible=false
Token HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Launch
er}:
token=HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Laun
cher}
windows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.La
uncher paused=false}, Window{44ac0690 SurfaceView paused=false}]
groupId=5 appFullscreen=true requestedOrientation=5
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=3 numDrawnWindows=3 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Token HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}:
token=HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}
windows=[Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}]
windowType=2 hidden=false hasVisible=true
app=true
allAppWindows=[Window{44b4d8a0 com.android.settings/com.android.settings.Dev
elopmentSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=false clientHidden=false willBeHidden=false reportedVisible=
false
numInterestingWindows=2 numDrawnWindows=2 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44ac0690 SurfaceView paused=false}]
windowType=-1 hidden=false hasVisible=true
Token HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}:
token=HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}
windows=[]
windowType=2 hidden=true hasVisible=true
app=true
groupId=2 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
Token HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}:
token=HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}
windows=[Window{44b446f8 com.android.settings/com.android.settings.Applicati
onSettings paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b446f8 com.android.settings/com.android.settings.App
licationSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token HistoryRecord{44beca80 com.android.settings/.Settings}:
token=HistoryRecord{44beca80 com.android.settings/.Settings}
windows=[Window{44b2c1d8 com.android.settings/com.android.settings.Settings
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b2c1d8 com.android.settings/com.android.settings.Set
tings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
startingWindow=null startingView=null startingDisplayed=true startingMovedfa
lse
Window token list:
#0: WindowToken{44af47b0 token=null}
#1: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setupwiza
rd/.SetupWizardActivity}}
#2: WindowToken{449909f0 [email protected]}
#3: WindowToken{44ae24d0 [email protected]}
#4: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launcher/
com.android.launcher2.Launcher}}
#5: WindowToken{44ac0630 [email protected]}
#6: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.settings/
.Settings}}
#7: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.settings/
.ApplicationSettings}}
#8: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.settings/
.DevelopmentSettings}}
Wallpaper tokens:
Wallpaper #0 WindowToken{449909f0 [email protected]}:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Application tokens in Z order:
App #4: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.setti
ngs/.DevelopmentSettings}}
App #3: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.setti
ngs/.ApplicationSettings}}
App #2: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.setti
ngs/.Settings}}
App #1: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launc
her/com.android.launcher2.Launcher}}
App #0: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setup
wizard/.SetupWizardActivity}}
mCurrentFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Develo
pmentSettings paused=false}
mLastFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}
mFocusedApp=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.s
ettings/.DevelopmentSettings}}
mInputMethodTarget=null
mInputMethodWindow=null
mWallpaperTarget=null
mCurConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 or
ien=1 layout=34 uiMode=17 seq=4}
mInTouchMode=true mLayoutSeq=345
mSystemBooted=true mDisplayEnabled=true
mLayoutNeeded=false mBlurShown=false
mDimShown=true current=0.0 target=0.0 delta=-0.004 lastAnimTime=0
mInputMethodAnimLayerAdjustment=0 mWallpaperAnimLayerAdjustment=0
mLastWallpaperX=0.5 mLastWallpaperY=0.0
mDisplayFrozen=false mWindowsFreezingScreen=false mAppsFreezingScreen=0 mWaiti
ngForConfig=false
mRotation=0, mForcedAppOrientation=-1, mRequestedRotation=0
mAnimationPending=false mWindowAnimationScale=1.0 mTransitionWindowAnimationSc
ale=1.0
mNextAppTransition=0xffffffff, mAppTransitionReady=false, mAppTransitionRunnin
g=false, mAppTransitionTimeout=false
mStartingIconInTransition=false, mSkipAppTransitionAnimation=false
mLastEnterAnimToken=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.a
ndroid.settings/.DevelopmentSettings}}, mLastEnterAnimParams=WM.LayoutParams{(0,
0)(fillxfill) sim=#110 ty=1 fl=#10100 fmt=-1 wanim=0x1030001}
DisplayWidth=480 DisplayHeight=800
KeyWaiter state:
mLastWin=null mLastBinder=null
mFinished=true mGotFirstWindow=true mEventDispatching=true mTimeToSwitch=0
[dumpsys: 3.3s elapsed]
C:\android-sdk-windows\tools>
Code:
<6>[ 5.608520] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.608764] mmc0: Slot eject status = 1
<6>[ 5.608886] mmc0: Power save feature enable = 1
<6>[ 5.609039] mmc0: DM non-cached buffer at ffa04000, dma_addr 0x279bd000
<6>[ 5.609283] mmc0: DM cmd busaddr 0x279bd000, cmdptr busaddr 0x279bd300
<6>[ 5.610229] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
<6>[ 5.610443] mmc1: 4 bit data mode enabled
<6>[ 5.610595] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.610839] mmc1: Slot eject status = 0
<6>[ 5.610961] mmc1: Power save feature enable = 1
<6>[ 5.611206] mmc1: DM non-cached buffer at ffa05000, dma_addr 0x279be000
<6>[ 5.611328] mmc1: DM cmd busaddr 0x279be000, cmdptr busaddr 0x279be300
<6>[ 5.612396] logger: created 64K log 'log_main'
<6>[ 5.612640] logger: created 256K log 'log_events'
<6>[ 5.612945] logger: created 64K log 'log_radio'
<6>[ 5.613128] logger: created 64K log 'log_system'
<4>[ 5.613586] GACT probability NOT on
<4>[ 5.613800] Mirror/redirect action on
<4>[ 5.613952] u32 classifier
<4>[ 5.614074] Actions configured
<4>[ 5.614318] Netfilter messages via NETLINK v0.30.
<4>[ 5.614501] nf_conntrack version 0.5.0 (6171 buckets, 24684 max)
<4>[ 5.614929] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plea
se use
<4>[ 5.615081] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack modu
le option or
<4>[ 5.615295] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<4>[ 5.615570] ctnetlink v0.93: registering with nfnetlink.
<6>[ 5.616058] xt_time: kernel timezone is -0000
<6>[ 5.616394] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 5.616729] arp_tables: (C) 2002 David S. Miller
<6>[ 5.616943] TCP cubic registered
<6>[ 5.617279] NET: Registered protocol family 10
<6>[ 5.617980] lo: Disabled Privacy Extensions
<6>[ 5.618896] Mobile IPv6
<6>[ 5.619049] IPv6 over IPv4 tunneling driver
<6>[ 5.619720] sit0: Disabled Privacy Extensions
<6>[ 5.620330] ip6tnl0: Disabled Privacy Extensions
<6>[ 5.620666] NET: Registered protocol family 17
<6>[ 5.620819] NET: Registered protocol family 15
<6>[ 5.620971] Bluetooth: L2CAP ver 2.14
<6>[ 5.621215] Bluetooth: L2CAP socket layer initialized
<6>[ 5.621337] Bluetooth: SCO (Voice Link) ver 0.6
<6>[ 5.621582] Bluetooth: SCO socket layer initialized
<6>[ 5.621917] Bluetooth: RFCOMM TTY layer initialized
<6>[ 5.622070] Bluetooth: RFCOMM socket layer initialized
<6>[ 5.622314] Bluetooth: RFCOMM ver 1.11
<6>[ 5.622436] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 5.622680] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 5.622894] ThumbEE CPU extension supported.
<6>[ 5.623596] clock_late_init() disabled 18 unused clocks
<4>[ 5.623809] mahimahi_wifi_init: start
<6>[ 5.624206] VFP support v0.3: implementor 51 architecture 0 part 0f varian
t 0 rev 1
<4>[ 5.652435] regulator_init_complete: incomplete constraints, leaving ldo2
on
<4>[ 5.653320] regulator_init_complete: incomplete constraints, leaving ldo1
on
<4>[ 5.654083] regulator_init_complete: incomplete constraints, leaving dcdc3
on
<4>[ 5.654968] regulator_init_complete: incomplete constraints, leaving dcdc2
on
<4>[ 5.655853] regulator_init_complete: incomplete constraints, leaving dcdc1
on
<6>[ 5.657379] rs30000048:00010000 rs30000048:00010000: setting system clock
to 2010-11-23 19:51:55 UTC (1290541915)
<6>[ 5.657714] Freeing init memory: 120K
<4>[ 5.657867] Warning: unable to open an initial console.
<6>[ 5.745422] keychord: using input dev h2w headset for fevent
<6>[ 5.745574] keychord: using input dev mahimahi-keypad for fevent
<6>[ 5.745971] keychord: using input dev mahimahi-nav for fevent
<6>[ 5.748168] yaffs: dev is 32505859 name is "mtdblock3"
<6>[ 5.748443] yaffs: passed flags ""
<4>[ 5.748565] yaffs: Attempting MTD mount on 31.3, "mtdblock3"
<4>[ 5.915313] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 5.915496] mmc1: new high speed SDHC card at address aaaa
<6>[ 5.916229] mmcblk0: mmc1:aaaa SU04G 3.69 GiB
<6>[ 5.916625] mmcblk0: p1
<4>[ 5.956512] yaffs: restored from checkpoint
<4>[ 5.956970] yaffs_read_super: isCheckpointed 1
<6>[ 5.996093] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 5.996337] yaffs: passed flags ""
<4>[ 5.996459] yaffs: Attempting MTD mount on 31.5, "mtdblock5"
<6>[ 6.100860] batt: 83%, 4030 mV, -237 mA (0 avg), 27.0 C, 1128 mAh
<6>[ 6.108581] batt: charging OFF
<4>[ 6.298553] block 164 is bad
<4>[ 6.373718] block 410 is bad
<4>[ 6.429870] block 594 is bad
<4>[ 6.436859] block 617 is bad
<4>[ 6.514953] block 873 is bad
<4>[ 6.581939] block 1092 is bad
<4>[ 6.585266] block 1103 is bad
<4>[ 6.612121] block 1191 is bad
<4>[ 6.626129] block 1237 is bad
<4>[ 7.622741] yaffs_read_super: isCheckpointed 0
<6>[ 7.628631] yaffs: dev is 32505860 name is "mtdblock4"
<6>[ 7.628753] yaffs: passed flags ""
<4>[ 7.628997] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<4>[ 7.773559] block 93 is bad
<4>[ 7.794616] block 162 is bad
<4>[ 7.836578] block 299 is bad
<4>[ 7.836853] block 300 is bad
<4>[ 7.903015] block 519 is bad
<4>[ 7.987426] yaffs_read_super: isCheckpointed 0
<3>[ 8.017700] init: service 'console' requires console
<3>[ 8.062011] init: cannot execve('/system/etc/install-recovery.sh'): Permis
sion denied
<3>[ 8.110382] init: cannot find '/system/bin/dspcrashd', disabling 'dspcrash
d'
<6>[ 8.125823] acpuclk_set_vdd_level got regulator
<6>[ 8.545745] warning: `rild' uses 32-bit capabilities (legacy support in us
e)
<6>[ 8.679840] SMD: ch 0 1 -> 2
<6>[ 8.681640] qmi: smd closed
<6>[ 8.682006] SMD: ch 50 1 -> 2
<6>[ 8.682312] qmi: smd opened
<6>[ 8.683135] qmi: smd closed
<6>[ 8.683471] SMD: ch 51 1 -> 2
<6>[ 8.683807] qmi: smd opened
<6>[ 8.684265] qmi: ctl: wds use client_id 0x01
<6>[ 8.684936] qmi: ctl: wds use client_id 0x01
<6>[ 8.685455] qmi: smd closed
<6>[ 8.685913] SMD: ch 52 1 -> 2
<6>[ 8.686523] qmi: smd opened
<6>[ 8.687438] qmi: ctl: wds use client_id 0x01
<6>[ 9.907592] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 12.805664] a1026_bootup_init: firmware loaded successfully
<6>[ 12.966003] a1026_bootup_init: initialized!
<6>[ 12.968688] htc-acoustic: open
<3>[ 12.969726] smd_alloc_channel() cid 41 does not exist
<3>[ 12.969848] smd_alloc_channel() cid 47 does not exist
<6>[ 12.973327] htc-acoustic: mmap
<6>[ 12.973541] htc-acoustic: ioctl
<6>[ 12.973632] htc-acoustic: ioctl: ACOUSTIC_UPDATE_ADIE called 59.
<6>[ 12.976440] htc-acoustic: ioctl: ONCRPC_UPDATE_ADIE_PROC success.
<6>[ 12.977264] htc-acoustic: release
<6>[ 12.997161] audio: init: codecs
<6>[ 12.997375] SMD: ch 43 1 -> 2
<6>[ 13.109802] dal_attach: status = 0, name = 'DAL_AQ_AUD'
<6>[ 13.109985] audio: init: INIT
<6>[ 13.110290] audio: init: OPEN control
<6>[ 13.495880] audio: init: attach ACDB
<6>[ 13.496215] SMD: ch 48 1 -> 2
<6>[ 13.606018] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 13.606140] audio: init: attach ADIE
<6>[ 13.606628] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 17.041503] lcdc_unblank: ()
<6>[ 17.041748] samsung_oled_panel_unblank: +()
<6>[ 17.256103] msm_kgsl: initilized dev=1 mmu=on
<6>[ 17.256561] misc kgsl: firmware: requesting yamato_pm4.fw
<6>[ 17.263732] misc kgsl: firmware: requesting yamato_pfp.fw
<3>[ 17.265991] init: untracked pid 87 exited
<3>[ 17.271881] init: untracked pid 88 exited
<6>[ 17.325988] samsung_oled_panel_unblank: -()
<6>[ 25.646606] capella_cm3602_open
<6>[ 25.647003] capella_cm3602_ioctl cmd 2
<6>[ 25.647918] capella_cm3602_disable
<6>[ 25.648040] capella_cm3602_disable: already disabled
<6>[ 25.648162] capella_cm3602_ioctl cmd 1
<6>[ 25.655303] request_suspend_state: wakeup (3->0) at 21809722976 (2010-11-2
3 19:52:15.497955355 UTC)
<6>[ 25.672088] capella_cm3602_ioctl cmd 1
<6>[ 32.422729] request_suspend_state: sleep (0->3) at 28577117998 (2010-11-23
19:52:22.265350377 UTC)
<6>[ 32.422851] capella_cm3602_ioctl cmd 1
<7>[ 32.423767] flashlight_control: mode 0 -> 0
<6>[ 32.423767] flashlight_control: off
<6>[ 32.426666] capella_cm3602_ioctl cmd 1
<6>[ 32.439849] lcdc_blank: ()
<6>[ 32.439971] samsung_oled_panel_blank: +()
<6>[ 32.645751] samsung_oled_panel_blank: -()
<6>[ 32.647949] mahimahi_ts_power: power 0
<6>[ 32.655822] lcdc_suspend: suspending
<4>[ 32.701049] save exit: isCheckpointed 1
<4>[ 32.706878] save exit: isCheckpointed 1
<4>[ 32.739654] save exit: isCheckpointed 1
<6>[ 32.763153] active wake lock kgsl
<6>[ 32.763275] active wake lock PowerManagerService
<6>[ 32.763366] wake lock mmc_delayed_work, expired
<6>[ 32.763549] wake lock qmi0, expired
<6>[ 32.763671] wake lock qmi1, expired
<6>[ 32.763763] wake lock qmi2, expired
<6>[ 32.763977] wake lock SMD_DS, expired
<6>[ 33.365203] request_suspend_state: wakeup (3->0) at 29519592363 (2010-11-2
3 19:52:23.207824742 UTC)
<6>[ 33.367401] lcdc_resume: resuming
<6>[ 33.367919] mahimahi_ts_power: power 1
<6>[ 33.369537] capella_cm3602_ioctl cmd 2
<6>[ 33.369750] capella_cm3602_disable
<6>[ 33.369842] capella_cm3602_disable: already disabled
<6>[ 33.369964] capella_cm3602_ioctl cmd 1
<6>[ 33.372253] capella_cm3602_ioctl cmd 1
<6>[ 33.415130] lcdc_unblank: ()
<6>[ 33.415252] samsung_oled_panel_unblank: +()
<6>[ 33.697570] samsung_oled_panel_unblank: -()
<6>[ 33.960021] cable_status_update: status=1
<6>[ 33.985809] msm72k_udc: OFFLINE -> ONLINE
<6>[ 33.986114] hsusb: reset controller
<6>[ 34.045654] msm_hsusb_phy_reset: success
<6>[ 34.195678] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[ 34.195861] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[ 34.195983] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 34.196166] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 34.196929] msm72k_udc: ept #0 out max:64 head:ffa02000 bit:0
<6>[ 34.197143] msm72k_udc: ept #1 out max:512 head:ffa02080 bit:1
<6>[ 34.197235] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.197448] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 34.197540] msm72k_udc: ept #4 out max:512 head:ffa02200 bit:4
<6>[ 34.197753] msm72k_udc: ept #5 out max:512 head:ffa02280 bit:5
<6>[ 34.197845] msm72k_udc: ept #6 out max:512 head:ffa02300 bit:6
<6>[ 34.198059] msm72k_udc: ept #7 out max:512 head:ffa02380 bit:7
<6>[ 34.198150] msm72k_udc: ept #8 out max:512 head:ffa02400 bit:8
<6>[ 34.198364] msm72k_udc: ept #9 out max:512 head:ffa02480 bit:9
<6>[ 34.198547] msm72k_udc: ept #10 out max:512 head:ffa02500 bit:10
<6>[ 34.198760] msm72k_udc: ept #11 out max:512 head:ffa02580 bit:11
<6>[ 34.198883] msm72k_udc: ept #12 out max:512 head:ffa02600 bit:12
<6>[ 34.200134] msm72k_udc: ept #13 out max:512 head:ffa02680 bit:13
<6>[ 34.200225] msm72k_udc: ept #14 out max:512 head:ffa02700 bit:14
<6>[ 34.200439] msm72k_udc: ept #15 out max:512 head:ffa02780 bit:15
<6>[ 34.200531] msm72k_udc: ept #0 in max:64 head:ffa02040 bit:16
<6>[ 34.200744] msm72k_udc: ept #1 in max:512 head:ffa020c0 bit:17
<6>[ 34.200836] msm72k_udc: ept #2 in max:512 head:ffa02140 bit:18
<6>[ 34.201049] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.201141] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 34.201354] msm72k_udc: ept #5 in max:512 head:ffa022c0 bit:21
<6>[ 34.201446] msm72k_udc: ept #6 in max:512 head:ffa02340 bit:22
<6>[ 34.201660] msm72k_udc: ept #7 in max:512 head:ffa023c0 bit:23
<6>[ 34.201751] msm72k_udc: ept #8 in max:512 head:ffa02440 bit:24
<6>[ 34.201965] msm72k_udc: ept #9 in max:512 head:ffa024c0 bit:25
<6>[ 34.202148] msm72k_udc: ept #10 in max:512 head:ffa02540 bit:26
<6>[ 34.202270] msm72k_udc: ept #11 in max:512 head:ffa025c0 bit:27
<6>[ 34.202453] msm72k_udc: ept #12 in max:512 head:ffa02640 bit:28
<6>[ 34.202575] msm72k_udc: ept #13 in max:512 head:ffa026c0 bit:29
<6>[ 34.202758] msm72k_udc: ept #14 in max:512 head:ffa02740 bit:30
<6>[ 34.202880] msm72k_udc: ept #15 in max:512 head:ffa027c0 bit:31
<6>[ 34.203094] usb: notify offline
<6>[ 34.203216] msm_hsusb: enable pullup
<6>[ 34.206329] msm72k_udc: msm72k_udc: suspend
<6>[ 34.226043] batt: charging SLOW
<6>[ 34.312683] msm72k_udc: msm72k_udc: reset
<6>[ 34.314941] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<6>[ 34.473693] msm72k_udc: msm72k_udc: reset
<6>[ 34.475982] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 34.696075] ### notify_usb_connected(1) ###
<6>[ 34.696228] android_usb gadget: high speed config #1: android
<6>[ 34.696716] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.696929] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.985809] binder: release 289:289 transaction 2744 out, still active
<6>[ 35.002349] binder: 79:223 transaction failed 29189, size 4-0
<6>[ 35.002593] binder: send failed reply for transaction 2744, target dead
<6>[ 55.218261] binder: 79:147 transaction failed 29189, size 52-0
<6>[ 59.133666] batt: 83%, 4060 mV, 58 mA (-68 avg), 27.1 C, 1126 mAh
<6>[ 67.028320] enabling adb
<6>[ 67.028472] msm_hsusb: disable pullup
<6>[ 67.045684] msm_hsusb: enable pullup
<6>[ 67.048828] msm72k_udc: msm72k_udc: suspend
<6>[ 67.056182] adb_open
<6>[ 67.206604] msm72k_udc: msm72k_udc: reset
<6>[ 67.206665] usb: notify offline
<6>[ 67.206878] adb_release
<6>[ 67.207946] adb_open
<6>[ 67.208740] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<3>[ 67.209564] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 67.367462] msm72k_udc: msm72k_udc: reset
<6>[ 67.369750] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 67.581878] ### notify_usb_connected(1) ###
<6>[ 67.581970] android_usb gadget: high speed config #1: android
<6>[ 67.582031] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 67.582061] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 67.582763] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 67.582824] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<3>[ 68.069061] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 115.879241] batt: 83%, 4089 mV, 251 mA (230 avg), 27.6 C, 1129 mAh
<6>[ 165.942657] batt: 84%, 4094 mV, 250 mA (254 avg), 28.0 C, 1134 mAh
cat<6>[ 216.020111] batt: 84%, 4099 mV, 248 mA (249 avg), 28.2 C, 1137 mAh
<6>[ 266.188140] batt: 84%, 4104 mV, 248 mA (249 avg), 28.5 C, 1140 mAh
<6>[ 316.250946] batt: 84%, 4104 mV, 246 mA (248 avg), 28.7 C, 1145 mAh

What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.

Ok, I'll spell it out:
ROOT. You need it to see system logs.
Then wait until it crashes with reboot.
Then run:
adb shell cat /proc/last_kmsg > c:\last_kmsg.log
adb shell cat /proc/kmsg > c:\kmsg.log
(here you'll need to stop it after 20-30 sec by Ctrl-C)
adb bugreport > c:\bugreport.log
Then you'll have 3 files in C:\, which you need. Upload here, maybe something will be better understandable from them.

ok thanks i will try to do that

GchildT said:
What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.
Click to expand...
Click to collapse
Hi to all
I didn't want to open a new thread because of the sam problem.
So I have Nexus One, and it restarts randomly after a period of use. When the phone restarts it is stuck on the "X" sign, until it reboots again, and again... and I have to remove battery and wait for a while to turn it back on.
Anybody have any idea what this could be, and could it be this conflict.
Android version: 2.3.3
Baseband version: 32.50.00.32U_5.12.00.08
Kernel version: 2.6.35.7-59423-g008607d4
[email protected]#1
Build number: GRI40
HBOOT: 0.35.0017
Radio-5.12.00.00
Current recovery: RA Recovery V2.2.1

[Q] How to verify hardware failure on Audio inout jack?

I've been using DarkyROM 10.1 for over 4 months now with no problems whatsoever.
Till a week back my headphone started not to work on the left earphone. It was time to change it. I went today to replace the headphone and when I was testing the headphone button it didn't work.
Further more I tried to test the mic on calls and it is not working. The built in mic is the only thing working.
It looks like the phone is stuck in the button pressed mode which I think mutes the mic.
I got the dmesg log and the jack info there was as the following,
/ # dmesg | grep jack
dmesg | grep jack
<6>[ 186.249633] sec_jack_set_type : jack_type = 2
<6>[ 230.395379] sec_jack_set_type : jack_type = 0
<6>[ 851.884970] sec_jack_set_type : jack_type = 2
<6>[ 908.898467] sec_jack_set_type : jack_type = 0
<6>[ 913.641106] sec_jack_set_type : jack_type = 2
<6>[ 914.764902] sec_jack_set_type : jack_type = 0
<6>[ 917.147299] active wake lock sec_jack_det, time left 1322
<6>[ 921.237020] sec_jack_set_type : jack_type = 2
<6>[ 930.587688] sec_jack_set_type : jack_type = 0
<6>[ 3053.033646] sec_jack_set_type : jack_type = 2
<6>[ 3127.994797] sec_jack_set_type : jack_type = 0
<6>[ 3139.175387] sec_jack_set_type : jack_type = 2
<6>[ 3331.251091] sec_jack_set_type : jack_type = 0
<6>[ 3334.832856] active wake lock sec_jack_det, time left 723
<6>[ 3748.558797] sec_jack_set_type : jack_type = 2
<6>[ 4256.425996] sec_jack_set_type : jack_type = 0
<6>[ 4263.752653] sec_jack_set_type : jack_type = 2
<6>[ 4273.007345] sec_jack_set_type : jack_type = 0
<6>[ 4288.558637] sec_jack_set_type : jack_type = 2
<6>[ 4294.126007] sec_jack_set_type : jack_type = 0
<6>[ 4307.354710] sec_jack_set_type : jack_type = 2
<6>[ 4307.827809] sec_jack_set_type : jack_type = 0
<6>[ 4327.778638] sec_jack_set_type : jack_type = 2
<6>[ 4329.332950] sec_jack_set_type : jack_type = 0
<6>[ 5523.733072] sec_jack_set_type : jack_type = 2
<6>[ 5568.944868] sec_jack_set_type : jack_type = 0
<6>[ 5611.345671] wakeup wake lock: sec_jack_det
<6>[ 5614.900765] sec_jack_set_type : jack_type = 2
<6>[ 5615.948397] sec_jack_set_type : jack_type = 0
<6>[ 5622.514618] wake lock sec_jack_det, expired
<6>[ 5622.719607] wakeup wake lock: sec_jack_det
<6>[ 5626.224616] sec_jack_set_type : jack_type = 2
<6>[ 5655.934294] sec_jack_set_type : jack_type = 0
<6>[ 5663.190634] sec_jack_set_type : jack_type = 2
<6>[ 5678.021070] sec_jack_set_type : jack_type = 0
Each time I plug the headphone I get nothing I remove it I get the two lines
<6>[ 5663.190634] sec_jack_set_type : jack_type = 2
<6>[ 5678.021070] sec_jack_set_type : jack_type = 0
Is it the problem that it is stuck in button pushed mode?
I tried to clear dalvik cache but it was of no use.
Would a fresh flashing do the trick? or is it a hardware damage?
P.S. When I discovered that the headphone is faulty the button was still working. it's only today that I have discovered it is not working when I tried to buy a new one.
Later on I went and installed DarkyROM 10.2.2 EE and did a date Wipe and it's the same issue, I even went further and formatted everything and went with a stock 2.3.5 and it's the same thing.
What I can think of now is a hardware failure, but I need to be 100% sure of that before sending it to the service center.
Can you guys help me with debugging this even more?
Thanks and sorry for the long thread.

[Q] Recovery gives black screen

Recently I decided to install a new ROM, so I tried booting into recovery to do a nandroid backup. However, once I click the Recovery option in the bootloader menu, I get the white HTC screen and then a blank, black screen.
It has never done this before and I have not done anything to mess with the recovery.
I've tried using 3 different recoveries, 2 from the android dev section here in xda as well as CWM 5.0.2.0 (the latest for vivo).
I also recently got my phone back from "repairs" due to a faulty eMMC chip, and I've noticed that there's a lot of lag (not framerate lag, but like I press Browser and I have to wait 5 seconds for it to open) in the ROM I'm currently using (CyanVivoX) - could it be that they replaced it with a faulty chip?
Help!

Bump?

anonymousthing said:
Recently I decided to install a new ROM, so I tried booting into recovery to do a nandroid backup. However, once I click the Recovery option in the bootloader menu, I get the white HTC screen and then a blank, black screen.
It has never done this before and I have not done anything to mess with the recovery.
I've tried using 3 different recoveries, 2 from the android dev section here in xda as well as CWM 5.0.2.0 (the latest for vivo).
I also recently got my phone back from "repairs" due to a faulty eMMC chip, and I've noticed that there's a lot of lag (not framerate lag, but like I press Browser and I have to wait 5 seconds for it to open) in the ROM I'm currently using (CyanVivoX) - could it be that they replaced it with a faulty chip?
Help!
Click to expand...
Click to collapse
So wait. HTC fixed your phone up with S-OFF and CyanVivoX. Can you show us what's in your bootloader screen? "fastboot getvar all"?

072665995 said:
So wait. HTC fixed your phone up with S-OFF and CyanVivoX. Can you show us what's in your bootloader screen? "fastboot getvar all"?
Click to expand...
Click to collapse
I can't get my output right now (phone not with me) but I had restored it to something looking like factory condition when I sent it to HTC. They then repaired it, sent it to me and then I S-OFF'd it and flashed CyanVivoX.

Here's my output from fastboot:
Code:
[email protected]:~# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.13.1002
(bootloader) version-baseband: 3805.06.03.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.405.1
(bootloader) serialno: MB243TD16593
(bootloader) imei: 358000047520257
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3771mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-8a731c6e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.003s
It also seems that it's only the screen that is blank at recovery - I can still load up adb from there and adb devices returns:
List of devices attached
MB243TD16593 recovery

update: dmesg returns a nice big list of errors:
Code:
<6>[ 401.158233] pm8058_drvx_led_brightness_set: bank 4 brightness 200
<7>[ 401.495208] vivow_mddi_init
<4>[ 401.615722] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 401.945495] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 402.335174] vivow_mddi_init
<4>[ 402.455627] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 402.784149] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<3>[ 402.795135] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<3>[ 402.797790] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<7>[ 403.165222] vivow_mddi_init
<4>[ 403.285675] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 403.614074] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 404.035278] vivow_mddi_init
<4>[ 404.155731] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 404.484161] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<3>[ 404.487915] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<3>[ 404.490570] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<7>[ 404.874114] vivow_mddi_init
<4>[ 404.994567] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 405.164398] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<6>[ 422.027282] pm8058_drvx_led_brightness_set: bank 4 brightness 200
<7>[ 422.424224] vivow_mddi_init
<4>[ 422.544708] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 422.875244] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 423.255249] vivow_mddi_init
<4>[ 423.375701] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 423.704162] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 424.084106] vivow_mddi_init
<4>[ 424.204559] [DISP]msmfb_pan_display timeout rerequest vsync
<6>[ 424.490234] batt: M2A_RPC: level_update: 70 at 420906266035 (2013-09-07 07:54:34.359736074 UTC)
<6>[ 424.490356] batt: batt:power_supply_changed: battery at 420906388105 (2013-09-07 07:54:34.359827627 UTC)
<4>[ 424.534149] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 424.914154] vivow_mddi_init
<4>[ 425.034606] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 425.365234] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 425.695281] vivow_mddi_init
<4>[ 425.815765] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 426.145202] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 426.524139] vivow_mddi_init
<4>[ 426.644592] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 426.975219] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 427.355194] vivow_mddi_init
<4>[ 427.475646] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 427.804138] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 428.185211] vivow_mddi_init
<4>[ 428.305664] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 428.635223] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 429.014160] vivow_mddi_init
<4>[ 429.134613] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 429.465209] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 429.795257] vivow_mddi_init
<4>[ 429.915740] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 430.245208] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 430.574188] vivow_mddi_init
<4>[ 430.694641] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 431.025238] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 431.405273] vivow_mddi_init
<4>[ 431.525756] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 431.854156] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 432.235137] vivow_mddi_init
<4>[ 432.355621] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 432.685241] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 433.064239] vivow_mddi_init
<4>[ 433.184692] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 433.515258] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 433.895233] vivow_mddi_init
<4>[ 434.015716] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 434.344207] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 434.725189] vivow_mddi_init
<4>[ 434.845642] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 435.175201] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 435.554229] vivow_mddi_init
<4>[ 435.674682] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 436.005249] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 436.385192] vivow_mddi_init
<4>[ 436.505645] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 436.834167] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<3>[ 436.846191] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<3>[ 436.848571] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<7>[ 437.215209] vivow_mddi_init
<4>[ 437.335662] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 437.665313] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 438.044158] vivow_mddi_init
<4>[ 438.164611] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 438.495239] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 438.875244] vivow_mddi_init
<4>[ 438.995697] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 439.324157] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 439.705200] vivow_mddi_init
<4>[ 439.825653] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 440.155242] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<3>[ 440.166046] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<3>[ 440.168670] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem
<7>[ 440.534240] vivow_mddi_init
<4>[ 440.654693] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 440.985198] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 441.365173] vivow_mddi_init
<4>[ 441.485778] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 441.814178] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 442.195159] vivow_mddi_init
<4>[ 442.315673] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 442.645233] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<7>[ 443.024200] vivow_mddi_init
<4>[ 443.144683] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 443.184448] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<3>[ 484.585388] INFO: task krmt_storagecln:495 blocked for more than 120 seconds.
<3>[ 484.586120] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 484.586822] krmt_storagecln D c0430da8 0 495 2 0x00000000
<4>[ 484.587921] Backtrace:
<4>[ 484.588989] [<c04309a8>] (schedule+0x0/0x494) from [<c00499d8>] (__msm_rpc_read+0x210/0x9d8)
<4>[ 484.589385] [<c00497c8>] (__msm_rpc_read+0x0/0x9d8) from [<c004a1bc>] (msm_rpc_read+0x1c/0x88)
<4>[ 484.590118] [<c004a1a0>] (msm_rpc_read+0x0/0x88) from [<c004cb80>] (rpc_clients_thread+0x5c/0x1dc)
<4>[ 484.590820] r6:e66e6930 r5:00000000 r4:e66e68e0
<4>[ 484.592315] [<c004cb24>] (rpc_clients_thread+0x0/0x1dc) from [<c00a44a8>] (kthread+0x84/0x8c)
<4>[ 484.593048] [<c00a4424>] (kthread+0x0/0x8c) from [<c00913a4>] (do_exit+0x0/0x6a0)
<4>[ 484.593780] r7:00000013 r6:c00913a4 r5:c00a4424 r4:e6c29df0
<3>[ 484.595611] INFO: task krmt_storagecln:496 blocked for more than 120 seconds.
<3>[ 484.596313] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 484.596679] krmt_storagecln D c0430da8 0 496 2 0x00000000
<4>[ 484.598052] Backtrace:
<4>[ 484.598815] [<c04309a8>] (schedule+0x0/0x494) from [<c004ca0c>] (rpc_clients_cb_thread+0x98/0x1b0)
<4>[ 484.599548] [<c004c974>] (rpc_clients_cb_thread+0x0/0x1b0) from [<c00a44a8>] (kthread+0x84/0x8c)
<4>[ 484.600311] [<c00a4424>] (kthread+0x0/0x8c) from [<c00913a4>] (do_exit+0x0/0x6a0)
<4>[ 484.600982] r7:00000013 r6:c00913a4 r5:c00a4424 r4:e6c29df0

I just downloaded and ran the RUU, it installed...
And now when I boot, I get the nice, white HTC screen... then...
Black screen of death! (accompanied by a nice startup sound). So it appears that the RUU system rom has the black screen issue with my phone now as well.
Their recovery mode screen isn't though, I get the pic of the phone with the green arrow/circle thing - I flashed CWM and bam, black screen as usual.
It's definitely not my actual lcd screen though - fastboot/bootloader works and I can see the white HTC boot logo fine.

anonymousthing said:
I just downloaded and ran the RUU, it installed...
And now when I boot, I get the nice, white HTC screen... then...
Black screen of death! (accompanied by a nice startup sound). So it appears that the RUU system rom has the black screen issue with my phone now as well.
Their recovery mode screen isn't though, I get the pic of the phone with the green arrow/circle thing - I flashed CWM and bam, black screen as usual.
It's definitely not my actual lcd screen though - fastboot/bootloader works and I can see the white HTC boot logo fine.
Click to expand...
Click to collapse
You cannot flash a RUU when you have Revolutionary S-Off. You need to reflash a custom recovery in FASTBOOT USB mode and then flash a new custom ROM.
Why don't you give 4EXT recovery a try instead of CWM.

tpbklake said:
You cannot flash a RUU when you have Revolutionary S-Off. You need to reflash a custom recovery in FASTBOOT USB mode and then flash a new custom ROM.
Why don't you give 4EXT recovery a try instead of CWM.
Click to expand...
Click to collapse
I had S-ON'd my device before I ran the RUU, and resulted in the symtoms of my last post (so right now I have HBOOT 1.13 S-ON), still black screen.
... and now I can't flash anything because I can't boot into the ROM (black screen), and I can't flash anything through fastboot because of signature checks.
I think I'm going to go hand it in to repair centre tomorrow (luckily warranty is still available and I'm back on stock bootloader), but if there's any more suggestions, I'm willing to try