Database Develop

broken wifi- logcat included

1. did clean wipe out
2. installed kingorama 1.0
3. installed lastest pershoot's kernel
4. reboot
5. skip all the steps selected launcher pro, went to setting turn on wifi (scanning, but says unable to find any networks and turns off)
6.clear proxy setting, save , turn on wifi = same result
7.clear proxy setting, uncheck the "use proxy only on wifi" save, turn on wifi= same result
8. airplane mode on, turn on wifi = same result
Logcat
D/WifiSerivce( 134): ACTION_BATTERY_CHANGED PluggedType: 2
E/WifiHw ( 134): Unable to open connetion to supplicant on "eth0": No such file or directory
D/WifiStateTracker ( 134): Reset connections and stopping DHCP
D/WifiService ( 134): acquireWifiLocked: WifiLock{NetworkLocationProvider type =2 [email protected]
I/wpa_supplicant ( 1035): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
E/wpa_supplicant ( 1035): Failed to disable WPA in the driver
D/WifiStateTracker( 134) disabling interface
E/WifiHW ( 134): Supplicant not running, cannot connect
D/LocationMasfClient ( 134): getNetworkLocation(): Location not found in chace, making network request
D/ProtorequestListener (134): requestFailed()
E/WifiHW ( 134): Supplicant not running, cannot connect
V/WifiStateTracker( 134): Supplicant died unexpectedly
D/WifiStateTracker( 134):Reset connections and stopping DHCP
Right now what i have in System/lib/Module
2.6.34.7-cyanogenmod
2.6.35.9-cyanogenmod+
bcm4329.ko
i have Gateway 3800HGV router.
Router setting
Default: 2WIREXXX <-- x'ed it out just in case
SSID Broadcast : Enabled
Wirelesschannel is set to Auto
Current Channel is 11
Authentication Type : WPA-PSK (TKIP)
MAC filtering is OFF
Wireless Mode is set to 802.11 b/g
my mac address starts with 00
i posted it in Kang-o-rama thread but i wanted to see if i can get any more help from the Q&A
sorry for posting lots of question about broken wifi lately

Are you sure the correct wifi module is present that was built against the kernel?

evilkorn said:
Are you sure the correct wifi module is present that was built against the kernel?
Click to expand...
Click to collapse
yes. im 100% positive as i have relfahsed many roms many kernels.

Just to be clear, you did wipe after all those?
Also it never hurts to go back to stock as a test. If wifi fails under stock conditions it's a hardware problem and should be covered under the warranty.

evilkorn said:
Just to be clear, you did wipe after all those?
Click to expand...
Click to collapse
i wipe out everything b4 i flash anything. and yes i wiped out data, cache dalvik cache after i flashed to see if it makes any differences.
i am thinking about sending it for replacement idk..
i know mine is unlocked but..oh well..
did anyone expereinced this weird wifi issue?

eunkipark92 said:
i wipe out everything b4 i flash anything. and yes i wiped out data, cache dalvik cache after i flashed to see if it makes any differences.
i am thinking about sending it for replacement idk..
i know mine is unlocked but..oh well..
did anyone expereinced this weird wifi issue?
Click to expand...
Click to collapse
try going back to stock

andy2na said:
try going back to stock
Click to expand...
Click to collapse
yae im trying it again and having bit of a problem in a proper way .
is there a chat or anything ?

[Q] [Problem] Force close on dialler

Background:
I updated to JVB though Kies when it became available (code: XEE). Before that I was on Voodoo, but on RFS.
After the update, it ran for some time but suddenly a week or so ago I got quite a number of problems with the phone acting up (not wanting to hang up after calls -the green status bar would remain, I could not even hang up it in the notification area). Generally the phone was also using a lot of RAM.
I thought, let's do a factory reset. When I did this all my user apps did not seem to get deleted although I did get the "New phone" startup sequence. I
Finally, I booted into CWM recovery but trying to do the reset there, I got some errors
Code:
Formatting /data…
E:format_volume: rfs format failed on /dev/block/mmblk0p2
Formatting /dbdata…
E:format_volume: rfs format failed on /dev/block/stl10
Deleting Meta Data
Formatting /cache…
E:format_volume: rfs format failed on /dev/block/stl11
When this failed to work a reflashed the firmware (Code: NEE) with repartition and everything and everything was clean. I rooted via CF-Root and restored all users apps + data for these. I also restored some "system" data such as call logs, smses, etc.
After a day I started getting force closes when I used the dialler. I.e. I start typing e.g. "253" and the phone tries to match this against contacts and after 1 sec, I get a force close. OK I thought, maybe I should not have restored system data.
I restored from a Nadroid backup (that had root) and started all over with user apps. I did not touch any system data this time.
I still get the force closes often when I try to find a contact using the key pad.
From aLogCat:
Code:
5-06 16:15:51.855 E/JavaBinder( 482): !!! FAILED BINDER TRANSACTION !!!
05-06 16:15:51.859 E/InputDispatcher( 482): channel '40c41cb8 com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
05-06 16:15:51.859 E/InputDispatcher( 482): channel '40c41cb8 com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-06 16:15:51.878 E/JavaBinder( 482): !!! FAILED BINDER TRANSACTION !!!
05-06 16:15:52.871 E/libBlurEffect(23357): AndroidBitmap_getInfo() failed ! error=-1
05-06 16:15:54.562 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:15:58.742 E/InputDispatcher( 482): channel '40dcbd58 com.sec.android.app.dialertab/com.sec.android.app.dialertab.DialerTabActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
05-06 16:15:58.742 E/InputDispatcher( 482): channel '40dcbd58 com.sec.android.app.dialertab/com.sec.android.app.dialertab.DialerTabActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-06 16:15:59.574 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:16:04.617 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:16:05.898 W/InputMethodManager(23566): Ignoring onBind: cur seq=987, given seq=986
05-06 16:16:09.644 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
Does anybody have any idea what may be the cause of this?
BTW I use e-mail and Nitrodesk Touchdown to get contacts on my phone.

you should install another rom.. easiest solution. have you tried customs?

Well, no, but should I not be able to use the standard Samsung Rom fit for my device and area?

No clever people can help out here?
If at all prossible, I'd like to prevent sending in the phone for service since this will take at least 2 weeks.

FINALLY I have found someone having the same problem as me.
I have a Samsung Exhibit 4G and have this same issue with the contact list closing when I don't want it to. I sometimes (not always) get kicked back to the home screen when viewing a contact list, call logs, or when starting to dial a number via the keypad. The "force quitting" or whatever you call it seems to happen in relation to an activity that searches the contacts in some way.
I recently discovered aLogcat and immediately after this happening I saw the same "DialerTabActivity" error that fjelsten was seeing.
My phone was finally rooted recently, and I can't wait for a custom rom to come out so I can be rid of this B.S. stock ROM.

Cell signal lost

Some people (like me) loosing the signal to the provider. WiFi is ok, but to get back the mobile connection I had to reboot the phone (1-2 times a working day. I never had this problem over the weekend).
I could pin down this behavior to a fast switching between mobile connection and no mobile connection. If the connection is just reestablished and in the next moment it is lost again the phone hangs. I take the underground to reach the office. That is the reason why I only have this issue on working days
So the solution is clear: Stop working. Enjoy the free time
I used "How to get useful logs" from tonyp with the App: SysLog and found in the modem.log the following error: (full log attached)
( 98): dlc[12] atchannel: at_send_command_full() at handshake fails, err - 12. Restarting rild
( 98): lge-ril: handle Cp Reset (CP Reset Cause - 1, RIL recovery activated flag - 0, dlc - 12)
( 98): [0485]< DEACTIVATE_DATA_CALL fails by E_RAIDO_NOT_AVAILABLE
( 98): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 22231000. s_dlc_handler_create_tracker - 0x6013f
( 759): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
( 759): Unrecognized RIL errno 16
Click to expand...
Click to collapse
I tried a lot of different basebands but could not fix the problem. The only difference was the RIL errno changed from 16 to 14 ???
The basebands I tried are: V30b, V30a, V30c (SU660 - because the sticker under the battery says: Made in Korea), V20m, V20s. In the end I tried different RILs but that only made the problem worse. Now I am back on the original cm10.1 RIL.
Losing the IMEI in the phone is not the problem. I already checked this.
I am pretty sure it is not ROM related because I experienced the same thing on cm7.2 and now on cm10.1 from tonyp on the old and new Boot loader
Regards
Fidi

Possible solution
Hi,
it looks like I found a solution for the loosing signal problem.
After trying all kinds of differnt basebands I switched to an old not recommended baseband. No signal lost for 4 working days in a row :fingers-crossed:
I am now on Baseband 0823-V21b and using ROM tonyp cm10.1 (04)
For the baseband have a look at the P990 Complete Baseband Overview Thread from tonyp: http://forum.xda-developers.com/showthread.php?t=1658047
Cheers
Fidi

Thanks for your informations, i think i have the same problem. Please respond if you have further informations!

I keep you updated:
Over the weekend: Everything worked fine and stable. I used the phone "normal" over the last three days. Including running with Endomondo Sports Tracker and some other parts. The phone is still stable. No reboot since the downgrade to Baseband 0823-V21b.
If I don't get any issues over the week I think that's the solution.
trampi did you downgrade your baseband too? I hope it's a working solution for you too.
Cheers
Fidi

Thank you Fidi!
I have the same logs when my data connection drops, currently with tonyp's T-Build 4 and Kowalski 125 and baseband 0725-V10d.
I will try this out, and report back.

Well I had this data drop issue but when using tonyp's T-Build I started having drops in the whole mobile connection (no voice as well). So I followed his recommendation and flashed BB V30a but that did nothing. Then I tried his Paranoid Android and it's working great!

Bad news here:
7 hours after flashing the baseband 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp), I got the same error again, and no data, no voice. And only reboot will fix it.
As soon as I see
## AT COMMAND TIMEOUT ##
in the radio log, I'm in the same situation again.
then at the moment of the connection blackout, always followed by:
E/RILJ ( 584): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
and
D/RIL ( 98): dlc[5]: lge-ril - requestInterface: Exiting DLC handler, thread - 7126560. s_dlc_handler_create_tracker - 0x611df
Only with this baseband I don't see this anymore:
E/GSM ( 593): Unrecognized RIL errno 16

I've found a workaround to restore the connection without rebooting:
first kill the /system/bin/rild process
then kill the com.android.phone process
They will both restart automatically.
So this looks like a problem with the ril. Is the ril not compatible with the baseband?
This is also suggested by the "Exception processing unsol response" messages: ril is not able to handle certain baseband commands, although this could also be a corruption on the baseband side...
Now creating a script to automate this workaround will at least give back the connection immediately.

Hi gios_
I am running on the same configuration: 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp)
If you could provide the script that will check for the error and kill the two services that would be gorgeous. That will solve the problem even if we don't find a "real" solution :fingers-crossed:

Here's the script to fix the connection:
Code:
#!/system/xbin/sh
ps|grep phone|cut -c10-14|xargs kill
ps|grep rild|cut -c10-14|xargs kill
To quickly execute it, you can use gscript (then leave out that first line).

do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564

antec123 said:
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
Click to expand...
Click to collapse
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.

gios_ said:
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
Click to expand...
Click to collapse
i used that solution, and with kowalski kernel exp 125 i haven't gotten any data loss. up time already 4 days. using kowalski kernel exp 124, i always get data loss and need reboot.
i use bb v30b ics, and ril (default). rom is using tony bulid 4 cm10.1 newBL. and using 2G always.

Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_

FidiS said:
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
Click to expand...
Click to collapse
yeah i think that true. I'm also confused why some people still have data loss with kowalski exp 125 and some people don't, so wierd

I will stick with baseband 0823-V21b. Still there is no real issue.
There is only remaining thing. In the situations when I formerly lost my connection now the phone rarely heats up for a short time with can drain the battery about 3%. After that the connection is reestablished and everything works as it should
Cheers Fidi

NFC Firmware for HTC Desire C ROMs with NFC Enabled

Hi everybody !
In the attachment you will find nfc.golfu.so which is the firmware for HTC Desire C with NFC (phone model PL01110). I get it from RUU_GOLF_U_ICS_40A_H3G_UK_1.45.771.3_Radio_10.11.98.09H_1.06.98.13M2_release_266089_signed.exe that you can find on the net.
I upload firmware here because I have spend 3 weeks to get it working with [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3.
On this rom, we see the NFC option but it can not enable it and we get the error hw_get_module() failed with logcat and the option stick unchecked.
With the attachement to this post, NFC is working (at least with JZO54K CM10 build#3), see logcat :
I/NfcService( 477): Enabling NFC
D/NFCJNI ( 477): Start Initialization
I/dalvikvm( 315): Jit: resizing JitTable from 4096 to 8192
D/NFCJNI ( 477): NFC capabilities: HAL = 8150100, FW = a76d0c, HW = 620003, Model = 10, HCI = 1, Full_FW = 109, Rev = 12, FW Update Info = 0
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 477):
D/NFCJNI ( 477): > Number of Secure Element(s) : 1
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 477): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 477): NFC Initialized​
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)

roms2000 said:
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
Click to expand...
Click to collapse
And the phone is not working, now. I tried to reboot, it's never completing the bootstrap. I can use the recovery console, I tried to fix permissions but it's always the same. How can I remove that file from recovery console?

fankool said:
And the phone is not working, now. I tried to reboot, it's never completing the bootstrap. I can use the recovery console, I tried to fix permissions but it's always the same. How can I remove that file from recovery console?
Click to expand...
Click to collapse
It doesn't work for me
Bootstrap? Is that stuck on boot animation?
If so:
You can reflash the current rom. That removes all the installed mods but not the apps or any sdcard data.
/*Worked for me, maybe not for you...*\

julian6457 said:
It doesn't work for me
Bootstrap? Is that stuck on boot animation?
If so:
You can reflash the current rom. That removes all the installed mods but not the apps or any sdcard data.
/*Worked for me, maybe not for you...*\
Click to expand...
Click to collapse
Yes, there's always the boot animation. But If I reflash the current rom I'll loose the data saved on phone and I have to reinstall the applications.

fankool said:
Yes, there's always the boot animation. But If I reflash the current rom I'll loose the data saved on phone and I have to reinstall the applications.
Click to expand...
Click to collapse
As I know flashing a new rom witout a /system wipe will not delete the applications.
You can also remove the micro SD (If you have one) there are multiple ways to cpoy the files to a pc from like micro>usb
Flasing roms only disable xposed modules and reinstall the stock apps.
Maybe a backup will come in handy the next time

julian6457 said:
As I know flashing a new rom witout a /system wipe will not delete the applications.
You can also remove the micro SD (If you have one) there are multiple ways to cpoy the files to a pc from like micro>usb
Flasing roms only disable xposed modules and reinstall the stock apps.
Maybe a backup will come in handy the next time
Click to expand...
Click to collapse
My recovery is not finishing backup for 4 months. Before it works perfectly.. so, I have only old bakcup (fbefore the last rom flashing).
I tried by adb to remove nfc.golfu.so from /system/lib/hw/ but the phone still stucks on boot, so I'll not try to copy file by memory card (it will not be useful).
I reflashed the rom without erasing anything and the phone was rebirth. Thank you!
A strange fast blinking on the screen is annoying me now, why? It's like the old crt monitor using 60Hz frequency. I restarted the phone but it's still blinking, from the white screen after switch on. Can anyone help me to understand what's happening?
---------- Post added at 11:31 AM ---------- Previous post was at 11:25 AM ----------
fankool said:
A strange fast blinking on the screen is annoying me now, why? It's like the old crt monitor using 60Hz frequency. I restarted the phone but it's still blinking, from the white screen after switch on. Can anyone help me to understand what's happening?
Click to expand...
Click to collapse
Replying to myself: I only disabled "developer options" (my phone is in italian language, I suppose this is the translation), restarted the phone and removed the battery and now works perfectly. But still I don't know why it was blinking.

Well roms2000,
thank you for your job (even if it's not working on my phone) if you are interested now I can continue the tests on my mobile phone to use NFC, I know how to quickly recover my phone (I also updated my cwm and now the backup works perfectly).
I'm wondering why it stucks (I disabled boot animation at start so I can't say exactly when it freezes) and what is the logfile I can read to understand what's happening (obviously my phone has NFC, is the O2 version).
I'm using NOPE kernel v2.6 850MHz (but at 800MHz) on miniCM v6 (a derivation of cm10). I just followed the instruction, I copied nfc.golfu.so in /system/lib/hw using x-plore and with the same application I changed the attributes to 644 (maybe, but it's difficult, I could set a wrong attributes, but in this case I think android simply ignores the library).
Also removing the file (by adb from recovery) the phone always stucks.

Sorry for long response, I did not check this post, so i couldn't received notifications.
@fankool : do you have the NFC version of HTC Desire C ? If not, you can't enable NFC, and the file won't do anything for you.
For NFC, I have simply take the module on the official rom to get it working, if your rom is base on android 4.1.2, it should work. Try to use logcat to see some message about error and NFC.
--- Edit :
I don't think MiniCM has NFC soft enabled : check on your phone : Settings / Wireless & Network (More...) / NFC
If you have a check box for NFC, rom embed NFC soft, else, it is not and I don't think firmware / module will do anything.

my desire c has NFC (it's an O2 desire c, and with stock rom and the revolution 4.0.4 it worked), but the option to enable NFC disappeared, also trying with prometheus or nope. I installed many different roms based on 4.1.1 (cm, minicm, miui..) but always NFC was not working. How can I use logcat?

Can you try this rom : JZO54K CM10 build#3, like I did ?
For logcat, it will not be useful if you do not have the option to enable NFC.

htc desire c nfc
roms2000 said:
Hi everybody !
In the attachment you will find nfc.golfu.so which is the firmware for HTC Desire C with NFC (phone model PL01110). I get it from RUU_GOLF_U_ICS_40A_H3G_UK_1.45.771.3_Radio_10.11.98.09H_1.06.98.13M2_release_266089_signed.exe that you can find on the net.
I upload firmware here because I have spend 3 weeks to get it working with [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3.
On this rom, we see the NFC option but it can not enable it and we get the error hw_get_module() failed with logcat and the option stick unchecked.
With the attachement to this post, NFC is working (at least with JZO54K CM10 build#3), see logcat :
I/NfcService( 477): Enabling NFC
D/NFCJNI ( 477): Start Initialization
I/dalvikvm( 315): Jit: resizing JitTable from 4096 to 8192
D/NFCJNI ( 477): NFC capabilities: HAL = 8150100, FW = a76d0c, HW = 620003, Model = 10, HCI = 1, Full_FW = 109, Rev = 12, FW Update Info = 0
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 477):
D/NFCJNI ( 477): > Number of Secure Element(s) : 1
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 477): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 477): NFC Initialized​
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
Click to expand...
Click to collapse
can i flash this zip file with stock rom

Stock rom should have it.
If you flash with stock I don't know if it will enable NFC.

roms2000 said:
Stock rom should have it.
If you flash with stock I don't know if it will enable NFC.
Click to expand...
Click to collapse
Well, this firmware enabled NFC on Cyanogenmod 11 - confirmed working by one of users, so thanks for this.

I've flashed Stock ROM and deodexed ROM, neither had NFC working (although it's meant to be) so it could be in boot if it works or not as my handset is 100% known to have NFC but my Bootloader is 1.31 and not 1.28
Sent from my B1-730HD using XDA Free mobile app

WiFi and Bluetooth won't turn on on any kernel and firmware (stock / custom)

Hello,
today I was working with my Xperia Z (C6603) and flashed a CM12 build. After having some problems with TWRP, I solved it in the end an TWRP and CM12 were working fine. But WiFi and Bluetooth won't turn on anymore. When I press "turn on" it takes some time and then the switch turns off again. A MAC address is not shown anymore. I tried to flash stock firmware with Flashtool, but didn't change anything.
Can someone help me to solve this? Is my phone partially bricked?
Thanks a lot!

Some update as I try to find the problem. I looked into logcat and only find this info when I try to turn on WiFi:
Code:
D/WifiService( 814): setWifiEnabled: true pid=1072, uid=10008
E/WifiStateMachine( 814): Failed to load driver
And when I try to execute wpa_suuplicant manually with "/system/bin/wpa_supplicant -Dnl80211 -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf"
Code:
I/wpa_supplicant( 9440): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): wlan0: Failed to initialize driver interface

Anyone? Just a hint to narrow down the problem?

Hi,
I have similar problem. My WiFi stopped working out of the blue.
I am quite sure I didn't changed anything. System crash occured when I was switching from Airplane mode to Normal mode (this usually turns WiFi on, if it was activated (and then deactivated) in Airplane mode). Then I got stucked in bootloop. Wiping dalvik-cache helped, but it was not the cause. At first, bluetooth was crashing too, but now it seems it works.
In *#*#INFO#*#* I can see
Code:
Supplicant state: UNINITALIZED
. LogCat issues are almost the same.
I've tried factory reset, but it didn't solved the problem. I've checked permissions, reflashed wifi-modules, tried WiFi Fixer app, reinstalled kernel, flashed another kernel, checked the wpa_supplicant.conf…but it still doesn't work.
EDIT: Oh, I forgot to mention my device: Xperi Mini St15i (Smultron), rooted, unlocked bootloader, Stock ICS ROM (only de-bloated, it worked until now) 4.0.4, build number 4.1.B.0.587. I've used kernel Kappa v1.6, but after the error occured, I tried switch to Rage kernel v2.32.
EDIT2: I've tried to restore original hosts, wpa_supplicant.conf, modules, wifi/*, etc....almost everything and nothing helped. I've flashed original stock ROM (you can find flashable stock ICS ROM for st15i here). I still don't know what happend and I'd like to know it. Hope I'll never see this problem again…