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
Related
Hallo.
I have problem with enabling Wi-Fi.
I try lots of thing to fix it:
update radio 3 times,spl,software
backup from nandroid from 2 months ago
try with 3 difrent SD cards...
but wifi still don't work.
How to diagnose this problem,it's hardware or software?
it's copy of my issue from CM issues:
Code:
What steps will reproduce the problem?
1.Attempt to enable Wi-Fi
What do you see?
[B]Unable to start Wi-Fi[/B]
What did you expect to see?
[B]Wi-fi was enabled[/B]
Please include the following info from FASTBOOT mode
MODEL? DREA1100 PVT 32B
HBOOT? 0.95.0000
RADIO? 2.22.19.261
Which version of CyanogenMod? 4.1.6
Did you wipe before flashing? yes
Have you tried running fix_permissions? yes
Have you tried rebooting? yes
Please attach a logcat of the issue.
E/WifiService( 2004): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 2443): Received wifi state changed from Unknown to
Enabling
D/SettingsWifiEnabler( 2443): Received wifi state changed from Enabling to
Unknown
Please provide any additional information below.
Wifi Cyanogenmod normally work in 4.1.6, I was connected to a wifi
network, because I moves ,lost my coverage of this network, when I wanted
to re-connect, system wrote to me "Unable
to enable wi-fi", I came home I did wipe, CM Uploader 4.1.9.2, wifi still
does not work, update to 4.1.10.1, I did wipe, fix_permission ... wifi
doesnt work...
<6>[ 212.900848] TIWLAN: Driver loading
<4>[ 212.907043] wifi_probe
<4>[ 212.909759] trout_wifi_power: 1
<4>[ 213.118225] trout_wifi_reset: 0
<4>[ 213.171936] trout_wifi_set_carddetect: 1
<7>[ 213.176422] mmc0: card_present 1
<6>[ 213.179931] mmc0: Slot status change detected (0 -> 1)
<3>[ 215.729705] mmc0: Command timeout
<3>[ 215.740417] mmc0: Command timeout
<3>[ 215.749969] mmc0: Command timeout
<3>[ 215.759490] mmc0: Command timeout
<3>[ 215.769287] mmc0: Command timeout
<3>[ 215.779052] mmc0: Command timeout
<3>[ 215.788818] mmc0: Command timeout
<3>[ 215.798583] mmc0: Command timeout
<3>[ 215.808624] mmc0: Command timeout
<3>[ 215.818969] mmc0: Command timeout
<3>[ 223.187896] tiwlan_module_init: Timed out waiting for device detect
<4>[ 223.195373] wifi_remove
<4>[ 223.198242] trout_wifi_set_carddetect: 0
<7>[ 223.202545] mmc0: card_present 0
<6>[ 223.208404] mmc0: Slot status change detected (1 -> 0)
<4>[ 223.214935] trout_wifi_reset: 1
<4>[ 223.272033] trout_wifi_power: 0
<4>[ 237.738372] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 243.077178] wds: 0021 @ 01
<6>[ 243.080200] qmi: wds: network stopped
<6>[ 243.184936] rmnet_stop()
<4>[ 260.505035] wds: 0020 @ 01
<3>[ 260.508117] qmi: wds: network start failed (000e)
<4>[ 260.513275] wds: 0022 @ ff
<6>[ 260.524932] qmi: wds: DISCONNECTED
<6>[ 274.452270] TIWLAN: Driver loading
<4>[ 274.458374] wifi_probe
<4>[ 274.461273] trout_wifi_power: 1
<4>[ 274.669494] trout_wifi_reset: 0
<4>[ 274.723083] trout_wifi_set_carddetect: 1
<7>[ 274.727508] mmc0: card_present 1
<6>[ 274.730987] mmc0: Slot status change detected (0 -> 1)
<3>[ 277.279205] mmc0: Command timeout
<3>[ 277.288909] mmc0: Command timeout
<3>[ 277.299011] mmc0: Command timeout
<3>[ 277.308959] mmc0: Command timeout
<3>[ 277.319641] mmc0: Command timeout
<3>[ 277.330718] mmc0: Command timeout
<3>[ 277.341583] mmc0: Command timeout
<3>[ 277.352416] mmc0: Command timeout
<3>[ 277.362243] mmc0: Command timeout
<3>[ 277.371734] mmc0: Command timeout
<3>[ 284.735900] tiwlan_module_init: Timed out waiting for device detect
<4>[ 284.743316] wifi_remove
<4>[ 284.749725] trout_wifi_set_carddetect: 0
<7>[ 284.754089] mmc0: card_present 0
<6>[ 284.758148] mmc0: Slot status change detected (1 -> 0)
<4>[ 284.763793] trout_wifi_reset: 1
<4>[ 284.821655] trout_wifi_power: 0
Definitely sounds like hardware. Where did you get your G1?
in Polish operator, brand new one "Era G1"
before the last weekend Wifi work absolutly normal.
ps.
It is a good thread for technical issues??
Flash a different ROM/build... do a wipe and reformat your sd card... post back with results plx
kingklick said:
Flash a different ROM/build... do a wipe and reformat your sd card... post back with results plx
Click to expand...
Click to collapse
Don't post it here if you want to continue on XDA
dan0zone said:
Don't post it here if you want to continue on XDA
Click to expand...
Click to collapse
PM me, sorry forgot
i flashed my old nandroid backup...with difrent rom...still Wifi not work...I also try with 3 diffrent Sd card with ( 1 Fat32 or 1 Fat32 + Ext2 or Fat32 + Ext2 + Swap) stiil the same with wifi...
When i try "busybox insmod wlan.ko" i reciving "device not found"
I scared...that can be hardware problem...but this will be strange becouse , wifi before that issue work perfecly normal,phone never fall...i taking good care with it.
ps.
if i do something wrong with posting please tell me,becouse like You see..i register long time ago,but to today reading was enought to me...but now i first time need help...
Kashue said:
Hallo.
Sorry for posting the same post...in 2 places...but on Q&A wasn't any construtive answers...
I have problem with enabling Wi-Fi.
I try lots of thing to fix it:
update radio 3 times,spl,software
backup from nandroid from 2 months ago
try with 3 difrent SD cards...
but wifi still don't work.
How to diagnose this problem,it's hardware or software?
it's copy of my issue from CM issues:
Code:
What steps will reproduce the problem?
1.Attempt to enable Wi-Fi
What do you see?
[B]Unable to start Wi-Fi[/B]
What did you expect to see?
[B]Wi-fi was enabled[/B]
Please include the following info from FASTBOOT mode
MODEL? DREA1100 PVT 32B
HBOOT? 0.95.0000
RADIO? 2.22.19.261
Which version of CyanogenMod? 4.1.6
Did you wipe before flashing? yes
Have you tried running fix_permissions? yes
Have you tried rebooting? yes
Please attach a logcat of the issue.
E/WifiService( 2004): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 2443): Received wifi state changed from Unknown to
Enabling
D/SettingsWifiEnabler( 2443): Received wifi state changed from Enabling to
Unknown
Please provide any additional information below.
Wifi Cyanogenmod normally work in 4.1.6, I was connected to a wifi
network, because I moves ,lost my coverage of this network, when I wanted
to re-connect, system wrote to me "Unable
to enable wi-fi", I came home I did wipe, CM Uploader 4.1.9.2, wifi still
does not work, update to 4.1.10.1, I did wipe, fix_permission ... wifi
doesnt work...
<6>[ 212.900848] TIWLAN: Driver loading
<4>[ 212.907043] wifi_probe
<4>[ 212.909759] trout_wifi_power: 1
<4>[ 213.118225] trout_wifi_reset: 0
<4>[ 213.171936] trout_wifi_set_carddetect: 1
<7>[ 213.176422] mmc0: card_present 1
<6>[ 213.179931] mmc0: Slot status change detected (0 -> 1)
<3>[ 215.729705] mmc0: Command timeout
<3>[ 215.740417] mmc0: Command timeout
<3>[ 215.749969] mmc0: Command timeout
<3>[ 215.759490] mmc0: Command timeout
<3>[ 215.769287] mmc0: Command timeout
<3>[ 215.779052] mmc0: Command timeout
<3>[ 215.788818] mmc0: Command timeout
<3>[ 215.798583] mmc0: Command timeout
<3>[ 215.808624] mmc0: Command timeout
<3>[ 215.818969] mmc0: Command timeout
<3>[ 223.187896] tiwlan_module_init: Timed out waiting for device detect
<4>[ 223.195373] wifi_remove
<4>[ 223.198242] trout_wifi_set_carddetect: 0
<7>[ 223.202545] mmc0: card_present 0
<6>[ 223.208404] mmc0: Slot status change detected (1 -> 0)
<4>[ 223.214935] trout_wifi_reset: 1
<4>[ 223.272033] trout_wifi_power: 0
<4>[ 237.738372] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 243.077178] wds: 0021 @ 01
<6>[ 243.080200] qmi: wds: network stopped
<6>[ 243.184936] rmnet_stop()
<4>[ 260.505035] wds: 0020 @ 01
<3>[ 260.508117] qmi: wds: network start failed (000e)
<4>[ 260.513275] wds: 0022 @ ff
<6>[ 260.524932] qmi: wds: DISCONNECTED
<6>[ 274.452270] TIWLAN: Driver loading
<4>[ 274.458374] wifi_probe
<4>[ 274.461273] trout_wifi_power: 1
<4>[ 274.669494] trout_wifi_reset: 0
<4>[ 274.723083] trout_wifi_set_carddetect: 1
<7>[ 274.727508] mmc0: card_present 1
<6>[ 274.730987] mmc0: Slot status change detected (0 -> 1)
<3>[ 277.279205] mmc0: Command timeout
<3>[ 277.288909] mmc0: Command timeout
<3>[ 277.299011] mmc0: Command timeout
<3>[ 277.308959] mmc0: Command timeout
<3>[ 277.319641] mmc0: Command timeout
<3>[ 277.330718] mmc0: Command timeout
<3>[ 277.341583] mmc0: Command timeout
<3>[ 277.352416] mmc0: Command timeout
<3>[ 277.362243] mmc0: Command timeout
<3>[ 277.371734] mmc0: Command timeout
<3>[ 284.735900] tiwlan_module_init: Timed out waiting for device detect
<4>[ 284.743316] wifi_remove
<4>[ 284.749725] trout_wifi_set_carddetect: 0
<7>[ 284.754089] mmc0: card_present 0
<6>[ 284.758148] mmc0: Slot status change detected (1 -> 0)
<4>[ 284.763793] trout_wifi_reset: 1
<4>[ 284.821655] trout_wifi_power: 0
Click to expand...
Click to collapse
corp769
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Senior Member
Join Date: Feb 2009
Posts: 196
Definitely sounds like hardware. Where did you get your G1?
Someone did respond to you in a very constructive manner ???? please read the rules ..Q&A is there so therads like these don't get started here !!!!
in normal Polish operator "Era" , the phone was brand new.
if it be necessary i have a guarantee
Q&A are watching 30 people
Development over 300 it's beter chance to get answer
I recently had the same issue an posted my problem here on XDA and got the same answer. "Its probably the hardware" After flashing every rom I could think of even rc29 I decided to take my chances with returning it for a warranty exchange through my provider (T-mobile). I just called them up and acted completely dumb about it. Told them my problem and followed whatever they said they wanted me to do. After 3 calls back to them, they sent me a replacement free of charge. Just don't mention anything about flashing or root etc. Each G1 in under a 1 year warranty from the time of purchase. You should be fine
I had this problem with my phone having wiped it and pushed wpa_supplicant.conf to my phone.
Turns out the permissions of the file were incorrect which stopped the wifi from working.
chmod 777 /data/misc/wifi/wpa_supplicant.conf
fixed it temporarily, but needed to be done again after a reboot. I then tried chown system.wifi /data/misc/wifi/wpa_supplicant.conf
but by the time I rebooted I also had upgraded to the newest
CyanogenMod (4.1.11.1)
So maybe that fixed it instead...
I don't have wpa_suplicant.conf in /data/misc/wifi but i moved it from /system/etc/wifi/
Change permission to but wifi still don't work...on mondey i go to network provider about warianty.,but it's strange...how wifi broken?is fault of software or normal electronic bad manufacter part...
Network error,answer posted 2 times...sry
Kashue said:
in normal Polish operator "Era" , the phone was brand new.
if it be necessary i have a guarantee
Q&A are watching 30 people
Development over 300 it's beter chance to get answer
Click to expand...
Click to collapse
So you knowingly BROKE THE RULES OF THE FORUM?
You know that will get you banned, then you will get ZERO answers, right?
both threads have been merged
next time stick to the rules
problem solved
To bring wifi to work service use somthing like this:
"Rigid-Flex Board ASSY,Daughterboard,Dream" 51H10069-00M
There was no other way...using software...i was hardware problem,but I don't know why that happend...phone newer fall,or nothing similiar.
Mod can close topic,there will not be any more update.
I 've got the same problem with my G1.....
"Error" or "Unable to start Wifi".
It's hardware issue...
I tried to put my G1 at the freeze for about 2-3 hours.
After this, wifi worked for about 20 minutes...
I think Wifi chip on daughter board is burned and it's working only if it's cold...
(...when I mean cold, I mean an icy G1 )
The only solution is daughter's board replacement......
(...or apply some thermal grease on the chip ???????)
What do you think.....???????
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"
Very recently my phone stopped connecting to my WIFI network. Using ConnectBot i was able to run dmesg and i see an issue with the wifi. Any suggestions or help would be appreciated.
Nexus One
Android 2.3.4 not rooted, stock kernel
t-mobile carrier
here's a clip from the message:
<6>[ 751.648223] mahimahi_ts_power: power 1
<6>[ 751.700134] lcdc_unblank: ()
<6>[ 751.700317] samsung_oled_panel_unblank: +()
<6>[ 752.030548] samsung_oled_panel_unblank: -()
<4>[ 752.704711] wifi_set_power = 1
<4>[ 752.705108] mahimahi_wifi_power: 1
<4>[ 753.063629] =========== WLAN going back to live ========
<4>[ 753.063873] sdio_reset_comm():
<4>[ 753.080932] net_ratelimit: 3 callbacks suppressed
<4>[ 753.081054] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 753.191375] dhd_dev_reset: WLAN ON DONE
<4>[ 753.195159] Firmware version = wl0: Dec 20 2010 19:21:39 version 4.218.248.18
<4>[ 753.896575] STA connect received 1
<4>[ 757.292633] dhd_dev_reset: WLAN OFF DONE
<4>[ 757.293426] wifi_set_power = 0
<4>[ 757.293823] mahimahi_wifi_power: 0
<4>[ 757.598693] =========== WLAN placed in RESET ========
<4>[ 795.939636] Failed to get 'wsec'iovar
<4>[ 795.939819] wl_iw_set_wpaauth: wsec_restrict -22
<4>[ 798.292144] dhdsdio_htclk: HT Avail request error: -35
<4>[ 798.394744] dhd_bus_stop: FAILED REGISTER WRITE, LINE 2735
<4>[ 798.501403] dhd_bus_stop: Failed to force clock for F2: err -35
<4>[ 798.690643] dhd_bus_stop: FAILED REGISTER WRITE, LINE 2755
<4>[ 798.690826] ------------[ cut here ]------------
<4>[ 798.691101] WARNING: at kernel/irq/manage.c:377 set_irq_wake+0x98/0x128()
<4>[ 798.691223] Unbalanced IRQ 239 wake disable
<4>[ 798.691467] Modules linked in: bcm4329(-)
<4>[ 798.691864] Backtrace:
<4>[ 798.692138] [<c002ba30>] (dump_backtrace+0x0/0x110) from [<c03519fc>] (dump_stack+0x18/0x1c)
<4>[ 798.692413] r7:00000009 r6:00000179 r5:c00961c0 r4:c7799d60
<4>[ 798.693054] [<c03519e4>] (dump_stack+0x0/0x1c) from [<c005b864>] (warn_slowpath_common+0x54/0x6c)
<4>[ 798.693298] [<c005b810>] (warn_slowpath_common+0x0/0x6c) from [<c005b920>] (warn_slowpath_fmt+0x38/0x40)
<4>[ 798.693542] r9:c7798000 r8:00000000 r7:000000ef r6:c044da28 r5:80000013
<4>[ 798.694213] r4:00000000
<4>[ 798.694580] [<c005b8e8>] (warn_slowpath_fmt+0x0/0x40) from [<c00961c0>] (set_irq_wake+0x98/0x128)
<4>[ 798.694793] r3:000000ef r2:c03ebf08
<4>[ 798.695251] [<c0096128>] (set_irq_wake+0x0/0x128) from [<bf01f084>] (bcmsdh_unregister_oob_intr+0x20/0x50 [bcm4329])
<4>[ 798.695495] r9:c7798000 r8:00000002 r7:00000010 r6:c77888a8 r5:c74cb4a0
<4>[ 798.696044] r4:bf029134
<4>[ 798.696563] [<bf01f064>] (bcmsdh_unregister_oob_intr+0x0/0x50 [bcm4329]) from [<bf001ffc>] (dhd_bus_detach+0x38/0x4c [bcm4329])
<4>[ 798.696777] r5:c74cb4a0 r4:c7788800
<4>[ 798.697174] [<bf001fc4>] (dhd_bus_detach+0x0/0x4c [bcm4329]) from [<bf002554>] (dhd_detach+0x180/0x1e0 [bcm4329])
<4>[ 798.697418] r5:c74cb4a0 r4:c7788800
<4>[ 798.697814] [<bf0023d4>] (dhd_detach+0x0/0x1e0 [bcm4329]) from [<bf0171b8>] (dhdsdio_release+0x4c/0xb8 [bcm4329])
<4>[ 798.698028] r9:c7798000 r8:c00280c4 r7:c70be39c r6:bf029148 r5:c7d1dc60
<4>[ 798.698699] r4:c716c000
<4>[ 798.699096] [<bf01716c>] (dhdsdio_release+0x0/0xb8 [bcm4329]) from [<bf017244>] (dhdsdio_disconnect+0x20/0x24 [bcm4329])
<4>[ 798.699310] r5:c7c02c20 r4:bf029134
<4>[ 798.699737] [<bf017224>] (dhdsdio_disconnect+0x0/0x24 [bcm4329]) from [<bf01f308>] (bcmsdh_remove+0x24/0x94 [bcm4329])
<4>[ 798.700042] [<bf01f2e4>] (bcmsdh_remove+0x0/0x94 [bcm4329]) from [<bf01f508>] (bcmsdh_sdmmc_remove+0x20/0x28 [bcm4329])
<4>[ 798.700256] r7:c70be39c r6:bf02639c r5:bf02639c r4:c70be360
<4>[ 798.700988] [<bf01f4e8>] (bcmsdh_sdmmc_remove+0x0/0x28 [bcm4329]) from [<c022d36c>] (sdio_bus_remove+0x20/0x5c)
<4>[ 798.701232] [<c022d34c>] (sdio_bus_remove+0x0/0x5c) from [<c01c61bc>] (__device_release_driver+0x6c/0xac)
<4>[ 798.701354] r5:bf02639c r4:c70be368
<4>[ 798.701812] [<c01c6150>] (__device_release_driver+0x0/0xac) from [<c01c62c4>] (driver_detach+0xc8/0xf0)
<4>[ 798.702026] r5:c70be368 r4:c7798000
<4>[ 798.702362] [<c01c61fc>] (driver_detach+0x0/0xf0) from [<c01c5450>] (bus_remove_driver+0x98/0xc0)
<4>[ 798.702606] r7:a7e02ba4 r6:c04619ac r5:00000000 r4:bf02639c
<4>[ 798.703186] [<c01c53b8>] (bus_remove_driver+0x0/0xc0) from [<c01c6830>] (driver_unregister+0x68/0x74)
<4>[ 798.703399] r7:a7e02ba4 r6:00000000 r5:00000000 r4:bf02639c
<4>[ 798.703979] [<c01c67c8>] (driver_unregister+0x0/0x74) from [<c022d5e0>] (sdio_unregister_driver+0x20/0x28)
<4>[ 798.704193] r7:a7e02ba4 r6:c7799f3c r5:00000000 r4:bf029308
<4>[ 798.704925] [<c022d5c0>] (sdio_unregister_driver+0x0/0x28) from [<bf01f4c8>] (sdio_function_cleanup+0x14/0x34 [bcm4329])
<4>[ 798.705230] [<bf01f4b4>] (sdio_function_cleanup+0x0/0x34 [bcm4329]) from [<bf01f2bc>] (bcmsdh_unregister+0x10/0x14 [bcm4329])
<4>[ 798.705505] [<bf01f2ac>] (bcmsdh_unregister+0x0/0x14 [bcm4329]) from [<bf01714c>] (dhd_bus_unregister+0x10/0x14 [bcm4329])
<4>[ 798.705810] [<bf01713c>] (dhd_bus_unregister+0x0/0x14 [bcm4329]) from [<bf01f6e0>] (dhd_module_cleanup+0x10/0x20 [bcm4329])
<4>[ 798.706085] [<bf01f6d0>] (dhd_module_cleanup+0x0/0x20 [bcm4329]) from [<c008a2d8>] (sys_delete_module+0x1f0/0x264)
<4>[ 798.706298] [<c008a0e8>] (sys_delete_module+0x0/0x264) from [<c0027f40>] (ret_fast_syscall+0x0/0x30)
<4>[ 798.706542] r7:00000081 r6:a7e02ba4 r5:00000009 r4:ffffffff
<4>[ 798.707092] ---[ end trace 8fd310dfb2435e8b ]---
<4>[ 798.776214] wifi_set_power = 0
<4>[ 798.776214] mahimahi_wifi_power: 0
<4>[ 799.511962] wifi_set_carddetect = 0
<6>[ 799.512145] mahimahi_wifi_set_carddetect: 0
<7>[ 799.512420] mmc0: card_present 0
<6>[ 799.512542] mmc0: Slot status change detected (1 -> 0)
<6>[ 799.513092] mmc0: card 0001 removed
<6>[ 804.765014] batt: 54%, 3811 mV, -127 mA (-155 avg), 31.8 C, 742 mAh
<4>[ 809.108337] wifi_set_power = 1
<4>[ 809.108581] mahimahi_wifi_power: 1
<4>[ 809.467437] wifi_set_carddetect = 1
<6>[ 809.467559] mahimahi_wifi_set_carddetect: 1
<7>[ 809.467681] mmc0: card_present 1
<6>[ 809.467895] mmc0: Slot status change detected (0 -> 1)
Ok sorry for my miss comprehension but I'm not sure I understand your problem is that the wifi doesn't connect? Now I would like to tell you a bit more but I'm not that great with dmesg all I can tell you is that you have an amoled screen :/ but if you could give me a regular logcat log like from alogcat then I could be more help. The other thing is are you rooted or stock and when did the problem occur?
Almost correct, WIFI wont work
WIFI won't work, it sometimes connects and will get an IP address from the router, but the connection won't be used.
Usually the device won't even connect or it'll say the network is out of range when it's very close and always has had an "Excellent" connection in the past.
at the top of the post is says Stock 2.3.4, it happend last week, nothing I can think of changed from before to after the problem.
attached is a logcat.
Have you tried rebooting your router?
Yes
I have tried rebooting the router and it hasn't fixed the problem. This problem exists on any WIFI network i try to connect to, not just my home router.
Well if this happened right after 2.3.4 then look no further it's probably the update that somewhat badly installed so I would just passimg back and then reupdate.
It wasn't right after 2.3.4, that's been installed for a while. WIFI was still working after the install of 2.3.4, that install didn't break anything.
Hello
Have you been able to learn something about the problem?
I have a HTC Desire (same hardware) and I'm starting to have a similar problem.
It has always worked well, but lately, without notice, wifi stops working and you do not see any access point.
For now can be solved by rebooting the phone (until it happens again).
Looking at my dmesg the problem was the same SDIO bus error as in your case.
Unfortunately something similar happened to me in the past with a motorola
Milestone and ended with the wifi completely unusable and I had to buy the Desire.
Hopefully this case is different, and not hardware related, but it seems.
I find it difficult to assume that a problem apparently so rare, I come up with two totally different phones.
Greetings
When you install the offical V30C 2.6.39 kernel, sometimes there will be a BSOD bug. Espcially when you try to unplug your phone from the USB port, the system sometimes will try to enter suspend mode, tuning it's frequency to 216MHz, this bug will occure. It will take the system a very long time to wakeup, or just crash the system. So if you have a incoming call at this time, maybe the baseband will ring the Android, surely, the Android will not ring you. Then you will miss the incoming call.
By checking the dmesg log, you can found something like this:
Code:
<4>[ 1235.194084] muic_wq_func : [MUIC] Now...path retain mode, muic_mode = MUIC_AP_USB (8), charing = CHARGING_NONE (1)
<4>[ 1235.194092]
<6>[ 1235.201514] suspend: enter suspend
<6>[ 1235.201533] PM: Syncing filesystems ... done.
<7>[ 1235.208726] PM: Preparing system for mem sleep
<6>[ 1235.208750] Tegra cpufreq suspend: setting frequency to 216000 kHz
<3>[ 1235.210088] Failed to set dvfs regulator vdd_core
and a lot of this:
Code:
<6>[ 1235.607271] Switched to NOHz mode on CPU #1
<4>[ 1236.607867] ------------[ cut here ]------------
<4>[ 1236.607945] WARNING: at /home/marsgod/android/CM_JB/kernel/lge/star/drivers/i2c/busses/i2c-tegra.c:669 tegra_i2c_xfer+0x2c0/0x3b8()
<4>[ 1236.607987] Modules linked in:
<4>[ 1236.608073] [<c004c2b0>] (unwind_backtrace+0x0/0xe0) from [<c008020c>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1236.608142] [<c008020c>] (warn_slowpath_common+0x4c/0x64) from [<c008023c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 1236.608212] [<c008023c>] (warn_slowpath_null+0x18/0x1c) from [<c030eb8c>] (tegra_i2c_xfer+0x2c0/0x3b8)
<4>[ 1236.608282] [<c030eb8c>] (tegra_i2c_xfer+0x2c0/0x3b8) from [<c030b480>] (i2c_transfer+0xb0/0x104)
<4>[ 1236.608375] [<c030b480>] (i2c_transfer+0xb0/0x104) from [<c0275934>] (max8907c_i2c_read+0x54/0x98)
<4>[ 1236.608451] [<c0275934>] (max8907c_i2c_read+0x54/0x98) from [<c02759b0>] (max8907c_reg_read+0x10/0x2c)
<4>[ 1236.608548] [<c02759b0>] (max8907c_reg_read+0x10/0x2c) from [<c0244108>] (max8907c_regulator_ldo_is_enabled+0x18/0x44)
<4>[ 1236.608626] [<c0244108>] (max8907c_regulator_ldo_is_enabled+0x18/0x44) from [<c0240350>] (_regulator_is_enabled+0x1c/0x28)
<4>[ 1236.608700] [<c0240350>] (_regulator_is_enabled+0x1c/0x28) from [<c0241e88>] (_regulator_do_set_voltage+0x14/0x1f8)
<4>[ 1236.608773] [<c0241e88>] (_regulator_do_set_voltage+0x14/0x1f8) from [<c024224c>] (regulator_set_voltage+0xf8/0x100)
<4>[ 1236.608869] [<c024224c>] (regulator_set_voltage+0xf8/0x100) from [<c0064724>] (dvfs_rail_set_voltage+0x14c/0x254)
<4>[ 1236.608947] [<c0064724>] (dvfs_rail_set_voltage+0x14c/0x254) from [<c00645c4>] (dvfs_rail_update+0xec/0x100)
<4>[ 1236.609021] [<c00645c4>] (dvfs_rail_update+0xec/0x100) from [<c0064b4c>] (__tegra_dvfs_set_rate+0xb4/0xf0)
<4>[ 1236.609095] [<c0064b4c>] (__tegra_dvfs_set_rate+0xb4/0xf0) from [<c0064bb8>] (tegra_dvfs_set_rate+0x30/0x48)
<4>[ 1236.609176] [<c0064bb8>] (tegra_dvfs_set_rate+0x30/0x48) from [<c0057540>] (clk_enable_locked+0x3c/0xe4)
<4>[ 1236.609244] [<c0057540>] (clk_enable_locked+0x3c/0xe4) from [<c00578b0>] (clk_enable+0x38/0x68)
<4>[ 1236.609313] [<c00578b0>] (clk_enable+0x38/0x68) from [<c02b7130>] (tegra_otg_enable_clk+0x20/0x34)
<4>[ 1236.609377] [<c02b7130>] (tegra_otg_enable_clk+0x20/0x34) from [<c02b71b8>] (tegra_otg_resume_noirq+0x10/0x58)
<4>[ 1236.609455] [<c02b71b8>] (tegra_otg_resume_noirq+0x10/0x58) from [<c02601b0>] (platform_pm_resume_noirq+0x2c/0x40)
<4>[ 1236.609527] [<c02601b0>] (platform_pm_resume_noirq+0x2c/0x40) from [<c0262d4c>] (pm_noirq_op+0xcc/0x14c)
<4>[ 1236.609590] [<c0262d4c>] (pm_noirq_op+0xcc/0x14c) from [<c0262ea0>] (dpm_resume_noirq+0xd4/0x13c)
<4>[ 1236.609658] [<c0262ea0>] (dpm_resume_noirq+0xd4/0x13c) from [<c00af7e4>] (suspend_devices_and_enter+0x1d4/0x2e0)
<4>[ 1236.609724] [<c00af7e4>] (suspend_devices_and_enter+0x1d4/0x2e0) from [<c00af9b8>] (enter_state+0xc8/0x130)
<4>[ 1236.609789] [<c00af9b8>] (enter_state+0xc8/0x130) from [<c00b0860>] (suspend+0x60/0x124)
<4>[ 1236.609850] [<c00b0860>] (suspend+0x60/0x124) from [<c00938bc>] (process_one_work+0x200/0x370)
<4>[ 1236.609912] [<c00938bc>] (process_one_work+0x200/0x370) from [<c0093c4c>] (worker_thread+0x220/0x3c0)
<4>[ 1236.609984] [<c0093c4c>] (worker_thread+0x220/0x3c0) from [<c00976c0>] (kthread+0x7c/0x84)
<4>[ 1236.610065] [<c00976c0>] (kthread+0x7c/0x84) from [<c00471b8>] (kernel_thread_exit+0x0/0x8)
<4>[ 1236.610107] ---[ end trace c5d679c0ae895105 ]---
<3>[ 1236.610148] tegra-i2c tegra-i2c.3: i2c transfer timed out, addr 0x003c, data 0x07
<4>[ 1236.611241] max8907c_i2c_read Fail Error code(0xffffff92) retry cnt=0
<4>[ 1237.607386] ------------[ cut here ]------------
<4>[ 1237.607453] WARNING: at /home/marsgod/android/CM_JB/kernel/lge/star/drivers/i2c/busses/i2c-tegra.c:669 tegra_i2c_xfer+0x2c0/0x3b8()
<4>[ 1237.607494] Modules linked in:
<4>[ 1237.607566] [<c004c2b0>] (unwind_backtrace+0x0/0xe0) from [<c008020c>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1237.607634] [<c008020c>] (warn_slowpath_common+0x4c/0x64) from [<c008023c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 1237.607705] [<c008023c>] (warn_slowpath_null+0x18/0x1c) from [<c030eb8c>] (tegra_i2c_xfer+0x2c0/0x3b8)
<4>[ 1237.607774] [<c030eb8c>] (tegra_i2c_xfer+0x2c0/0x3b8) from [<c030b480>] (i2c_transfer+0xb0/0x104)
<4>[ 1237.607856] [<c030b480>] (i2c_transfer+0xb0/0x104) from [<c0275934>] (max8907c_i2c_read+0x54/0x98)
<4>[ 1237.607931] [<c0275934>] (max8907c_i2c_read+0x54/0x98) from [<c02759b0>] (max8907c_reg_read+0x10/0x2c)
<4>[ 1237.608017] [<c02759b0>] (max8907c_reg_read+0x10/0x2c) from [<c0244108>] (max8907c_regulator_ldo_is_enabled+0x18/0x44)
<4>[ 1237.608094] [<c0244108>] (max8907c_regulator_ldo_is_enabled+0x18/0x44) from [<c0240350>] (_regulator_is_enabled+0x1c/0x28)
<4>[ 1237.608166] [<c0240350>] (_regulator_is_enabled+0x1c/0x28) from [<c0241e88>] (_regulator_do_set_voltage+0x14/0x1f8)
<4>[ 1237.608238] [<c0241e88>] (_regulator_do_set_voltage+0x14/0x1f8) from [<c024224c>] (regulator_set_voltage+0xf8/0x100)
<4>[ 1237.608323] [<c024224c>] (regulator_set_voltage+0xf8/0x100) from [<c0064724>] (dvfs_rail_set_voltage+0x14c/0x254)
<4>[ 1237.608401] [<c0064724>] (dvfs_rail_set_voltage+0x14c/0x254) from [<c00645c4>] (dvfs_rail_update+0xec/0x100)
<4>[ 1237.608474] [<c00645c4>] (dvfs_rail_update+0xec/0x100) from [<c0064b4c>] (__tegra_dvfs_set_rate+0xb4/0xf0)
<4>[ 1237.608547] [<c0064b4c>] (__tegra_dvfs_set_rate+0xb4/0xf0) from [<c0064bb8>] (tegra_dvfs_set_rate+0x30/0x48)
<4>[ 1237.608624] [<c0064bb8>] (tegra_dvfs_set_rate+0x30/0x48) from [<c0057540>] (clk_enable_locked+0x3c/0xe4)
<4>[ 1237.608692] [<c0057540>] (clk_enable_locked+0x3c/0xe4) from [<c00578b0>] (clk_enable+0x38/0x68)
<4>[ 1237.608759] [<c00578b0>] (clk_enable+0x38/0x68) from [<c02b7130>] (tegra_otg_enable_clk+0x20/0x34)
<4>[ 1237.608823] [<c02b7130>] (tegra_otg_enable_clk+0x20/0x34) from [<c02b71b8>] (tegra_otg_resume_noirq+0x10/0x58)
<4>[ 1237.608897] [<c02b71b8>] (tegra_otg_resume_noirq+0x10/0x58) from [<c02601b0>] (platform_pm_resume_noirq+0x2c/0x40)
<4>[ 1237.608967] [<c02601b0>] (platform_pm_resume_noirq+0x2c/0x40) from [<c0262d4c>] (pm_noirq_op+0xcc/0x14c)
<4>[ 1237.609030] [<c0262d4c>] (pm_noirq_op+0xcc/0x14c) from [<c0262ea0>] (dpm_resume_noirq+0xd4/0x13c)
<4>[ 1237.609094] [<c0262ea0>] (dpm_resume_noirq+0xd4/0x13c) from [<c00af7e4>] (suspend_devices_and_enter+0x1d4/0x2e0)
<4>[ 1237.609160] [<c00af7e4>] (suspend_devices_and_enter+0x1d4/0x2e0) from [<c00af9b8>] (enter_state+0xc8/0x130)
<4>[ 1237.609223] [<c00af9b8>] (enter_state+0xc8/0x130) from [<c00b0860>] (suspend+0x60/0x124)
<4>[ 1237.609283] [<c00b0860>] (suspend+0x60/0x124) from [<c00938bc>] (process_one_work+0x200/0x370)
<4>[ 1237.609343] [<c00938bc>] (process_one_work+0x200/0x370) from [<c0093c4c>] (worker_thread+0x220/0x3c0)
<4>[ 1237.609411] [<c0093c4c>] (worker_thread+0x220/0x3c0) from [<c00976c0>] (kthread+0x7c/0x84)
<4>[ 1237.609485] [<c00976c0>] (kthread+0x7c/0x84) from [<c00471b8>] (kernel_thread_exit+0x0/0x8)
<4>[ 1237.609526] ---[ end trace c5d679c0ae895106 ]---
<3>[ 1237.609565] tegra-i2c tegra-i2c.3: i2c transfer timed out, addr 0x003c, data 0x07
<4>[ 1237.610659] max8907c_i2c_read Fail Error code(0xffffff92) retry cnt=1
When the system trying to enter into suspend mode, it first will tune the frequency to 216MHz, this will cause the dvfs.c try to low down the cpu/core voltage. When lowing down the core voltage, the regulator_check_consumers in regulator return a -EINVAL to dvfs.c set_voltage function. Which will cause the dvfs set voltage abort, so at this time , some part of CPU enter suspend mode, but others not. And this will cause a serious problem when system trying to wakeup.(a lot of I2C communicationn error)
By adding some printk into the regulator core.c, I found that there exist a "ghost consumer" which has a min_uV=0 and max_uV=0. This will cause the regulator_check_consumers always return a -EINVAL.
To workaround this , just add a fix to the drivers/regulator/core.c regulator_check_consumers function:
Code:
list_for_each_entry(regulator, &rdev->consumer_list, list) {
if (!regulator->max_uV && !regulator->min_uV)
{
// Work around for unknown 0,0 consumer bug
continue;
}
if (*max_uV > regulator->max_uV)
*max_uV = regulator->max_uV;
if (*min_uV < regulator->min_uV)
*min_uV = regulator->min_uV;
}
Please note, this bug has been fixed in 3.x kernel.
marsgod said:
When you install the offical V30C 2.6.39 kernel, sometimes there will be a BSOD bug. Espcially when you try to unplug your phone from the USB port, the system sometimes will try to enter suspend mode, tuning it's frequency to 216MHz, this bug will occure. It will take the system a very long time to wakeup, or just crash the system. So if you have a incoming call at this time, maybe the baseband will ring the Android, surely, the Android will not ring you. Then you will miss the incoming call.
To workaround this , just add a fix to the drivers/regulator/core.c regulator_check_consumers function:
Code:
list_for_each_entry(regulator, &rdev->consumer_list, list) {
if (!regulator->max_uV && !regulator->min_uV)
{
// Work around for unknown 0,0 consumer bug
continue;
}
if (*max_uV > regulator->max_uV)
*max_uV = regulator->max_uV;
if (*min_uV < regulator->min_uV)
*min_uV = regulator->min_uV;
}
Please note, this bug has been fixed in 3.x kernel.
Click to expand...
Click to collapse
Hi marsgod, there is a patch in nvidia git about it already. Here is what i cherry picked from there.
https://github.com/bhanvadia/lge-kernel-star/commit/604d675b84aaa905a675109e52b4becebded9cff
this does same as you say, just done by Nvidia already. LG forgot it in their kernel.
EDIT: And to all other xda members this is best example of having commits in GIT.... helps a lot .
Harsh said:
Hi marsgod, there is a patch in nvidia git about it already. Here is what i cherry picked from there.
https://github.com/bhanvadia/lge-kernel-star/commit/604d675b84aaa905a675109e52b4becebded9cff
this does same as you say, just done by Nvidia already. LG forgot it in their kernel.
EDIT: And to all other xda members this is best example of having commits in GIT.... helps a lot .
Click to expand...
Click to collapse
thank you....
And maybe we can revert the board-star-power.c LDO18 fix.
//LGE_CHANGE_S chen.yingchun 20120103 regulator_set_voltage of "vddio_vi" fail
//MAX8907C_REGULATOR_DEVICE(LDO18, 650000, 2225000);
MAX8907C_REGULATOR_APPLYUV_DEVICE(LDO18, 1800000, 1800000);
//LGE_CHANGE_E chen.yingchun 20120103 regulator_set_voltage of "vddio_vi" fail
Guys, why don't you push this fix into official CM kernel repo?
Reading this reminded me that the very same error and solution has been brought up by wkpark around a month ago.
See here...
Hey all,
for some reason I have a infinite boot loop on my rooted Note (the boot animation plays, but then it restarts); firmware version is stock XXLSZ with root and CWM Recovery 6.0.3.0/PhilZ Touch 4.
I have not done anything to the OS since I fixed it up the last time a month ago; and once again I have no backup of the data on the internal memory.
How can I find out what is broken, and how do I get the data off the phone with CWM recovery? adb shell works and the data in /data, /system and /emmc still appears to be there, however I can't mount /sd-ext - cwm says "can't mount /dev/block/mmcblk1p2 /sd-ext (no such file).
dmesg shows this here:
<3>[ 7.713599] c0 mmc1: cmd 17 data timeout error
<3>[ 7.713903] c0 mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
<3>[ 7.714072] c0 end_request: I/O error, dev mmcblk1, sector 5
<3>[ 9.225020] c0 mmc1: cmd 17 data timeout error
<3>[ 9.225481] c0 end_request: I/O error, dev mmcblk1, sector 7
<3>[ 9.981223] c0 mmc1: cmd 18 data timeout error
<3>[ 10.737259] c0 mmcblk1: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
<3>[ 10.737431] c0 end_request: I/O error, dev mmcblk1, sector 0
<3>[ 11.493134] c0 end_request: I/O error, dev mmcblk1, sector 1
<3>[ 12.248358] c0 mmc1: cmd 17 data timeout error
<3>[ 12.248804] c0 end_request: I/O error, dev mmcblk1, sector 2
<3>[ 13.004323] c0 mmcblk1: error -110 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
<3>[ 13.759713] c0 mmc1: cmd 17 data timeout error
<3>[ 13.759997] c0 mmcblk1: error -110 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
<3>[ 14.515904] c0 mmc1: cmd 17 data timeout error
<3>[ 15.271589] c0 mmc1: cmd 17 data timeout error
<3>[ 17.539288] c0 mmc1: cmd 17 data timeout error
<3>[ 17.539595] c0 mmcblk1: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
<3>[ 18.295005] c0 mmc1: cmd 17 data timeout error
<3>[ 18.295297] c0 mmcblk1: error -110 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
<7>[ 18.725004] c0 usb: set_config_number single config
<7>[ 18.725108] c0 usb: set_interface_count next_interface_id=2
<7>[ 18.729004] c0 usb: set_config e mass_storage[0]
<7>[ 18.729131] c0 usb: set_config e adb[1]
<7>[ 18.729239] c0 usb: SET_CON
<7>[ 18.729487] c0 usb: android_work config=c0b77704,connected=1,sw_connected=1
<7>[ 18.730247] c0 usb: android_work sent uevent USB_STATE=CONFIGURED
<7>[ 20.098554] c0 usb: set_config_number single config
<7>[ 20.100774] c0 usb: set_config_number single config
<7>[ 20.100879] c0 usb: set_interface_count next_interface_id=2
<3>[ 21.317770] c0 mmc1: cmd 17 data timeout error
<3>[ 21.318081] c0 mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
<3>[ 21.318253] c0 end_request: I/O error, dev mmcblk1, sector 5
<3>[ 22.073490] c0 mmc1: cmd 17 data timeout error
<3>[ 22.829455] c0 mmcblk1: error -110 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
<3>[ 22.829743] c0 Buffer I/O error on device mmcblk1, logical block 0
Click to expand...
Click to collapse
To me this sounds like a dead SD card (can't test though, no other SD reader), but even without the SD card the phone refuses to boot :/
Any idea how to get at least the phone booting again or where to look for errors?
When doing a dmesg|grep mmc without the SD, I get
dmesg|grep mmc
<6>[ 2.035409] c1 dw_mmc dw_mmc: clock source 0: sclk_dwmci (80000000 Hz)
<3>[ 2.035839] c1 mmc0: Version ID 0x5342230a.
<6>[ 2.036227] c1 mmc0: FIFO WMARK FOR RX 0x20 WX 0x10. ###########
<6>[ 2.036920] c1 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<6>[ 2.037542] c1 s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (8888888 Hz)
<6>[ 2.037914] c1 mmc1: vtf_2.8v regulator found
<7>[ 2.038207] c1 Registered led device: mmc1::
<6>[ 2.039448] c0 sdhci_set_ios : MMC Card ON samsung-hsmmc
<6>[ 2.039522] c0 mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>[ 2.039802] c0 mmc1: card removed.
<6>[ 2.039929] c0 s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (8888888 Hz)
<3>[ 2.040095] c0 mmc2: no vmmc regulator found
<7>[ 2.040405] c0 Registered led device: mmc2::
<6>[ 2.040749] c0 mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
<3>[ 2.065390] c0 mmc0: cmd 52 response timeout error
<3>[ 2.065799] c0 mmc0: cmd 52 response timeout error
<3>[ 2.071569] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071985] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072351] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072712] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073074] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073460] c0 mmc0: cmd 55 response timeout error
<3>[ 2.073840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.074218] c0 mmc0: cmd 55 response timeout error
<3>[ 2.074596] c0 mmc0: cmd 55 response timeout error
<6>[ 2.096913] c0 mmc0: VYL00M: 15010056594c30304d196b9c70418ed1
<4>[ 2.109437] c0 mmc0: Voltage range not supported for power class.
<3>[ 2.109486] c0 mmc0: power class selection to bus width 8 failed
<4>[ 2.109746] c0 mmc0: Voltage range not supported for power class.
<3>[ 2.109795] c0 mmc0: power class selection to bus width 8 ddr 2 failed
<6>[ 2.110081] c0 mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.110881] c0 mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.117703] c0 mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
<6>[ 2.175199] c1 sdhci_set_ios : MMC Card OFF samsung-hsmmc
<6>[ 3.776696] c1 EXT4-fs (mmcblk0p9): recovery complete
<6>[ 3.776832] c1 EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.001439] c0 EXT4-fs (mmcblk0p7): recovery complete
<6>[ 4.001574] c0 EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 5.878636] c0 EXT4-fs (mmcblk0p10): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.892909] c0 EXT4-fs (mmcblk0p10): recovery complete
<6>[ 5.892945] c0 EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts:
<6>[ 15.762233] c0 lun0: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762407] c0 lun1: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762519] c0 lun0: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762628] c0 lun1: unable to open backing file: /dev/block/mmcblk1p1
Click to expand...
Click to collapse
Boot into Philz recovery and make a nandroid backup. Make sure preload is included. Then go to wipe data factory reset. Choose clear before new rom install. Once done go to backup and restore and restore the nandroid you made. Then boot up. Check what happens.
nokiamodeln91 said:
Boot into Philz recovery and make a nandroid backup. Make sure preload is included. Then go to wipe data factory reset. Choose clear before new rom install. Once done go to backup and restore and restore the nandroid you made. Then boot up. Check what happens.
Click to expand...
Click to collapse
A nandroid backup would backup to the SD card, which is a) totally full and b) presumed dead, I'd need something that works over USB...
What can it be backed up to internal storage?
nokiamodeln91 said:
What can it be backed up to internal storage?
Click to expand...
Click to collapse
Internal storage is full to the brim, too, and I dont have any money left to buy other SD card. Also, won't the internal storage be overwritten by flashing ROM?
No. It will not be. Try cleaning the internal storage by mounting it in recovery using the mounts and storage menu and then mount usb storage. Then connect to pc. Check for drives
nokiamodeln91 said:
No. It will not be. Try cleaning the internal storage by mounting it in recovery using the mounts and storage menu and then mount usb storage. Then connect to pc. Check for drives
Click to expand...
Click to collapse
Yeah, I'm pulling the card contents now, will need two hours - lol, 2.8MB/s transfer speed! -.-
Looks like the memory has issues. I can not make a backup of /data - it always crashes somewhere. Either it locks up or it reboots without errormessage.
When doing a tar cvf /emmc/data.tar /data, it always crashes at data/log/dumpstate_ril_RESET_BY_CP_SILENTRESET_20130422194108.log; I'll just exclude data/log and try again - but is it possible that I have a defective memory chip?!
Try running a scan in recovery.
e2fsck - f - c - y /dev/block/mmcblk0p10
****. Apparently I have one of the broken ones:
/sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001 # cat name hwrev fwrev manfid oemid date type serial cid
cat name hwrev fwrev manf
id oemid date type serial cid
VYL00M
0x0
0x0
0x000015
0x0100
08/2011
MMC
0x6b9c7041
15010056594c30304d196b9c70418ed1
Click to expand...
Click to collapse
Can I somehow scan for defective blocks and "blank" them like with badblocks on a PC?