[Q]Wifi stuck on 'turning on'

Search This thread
By:
Advanced…
S

Skincho

New member
Sep 13, 2010
3
0
I have this problem since 6 months now.
I have tried everything without success (flashing kernels and many custom roms) and finally buy a new phone.

Yesterday, i started my Nexus 5 (witch was not used and with no battery since 2-3 months) and miracle, Wifi and bluetooth were functionnal !
I have played with it 4-5 hours without any problem

Informations :
- It was on cynogenmod 12
- Before launch it i have booted on download mode (volume up + connecting usb cable)

Very strange for an hardware problem no ?
 
T

timbck2

Senior Member
Jun 17, 2010
433
78
Santa Fe, NM
This problem just started for me. I've tried all the "fixes" mentioned here and elsewhere on the web, including airplane mode, re-flashing Lollipop 5.1.0, factory reset, flashing another ROM (Cyanogenmod) - nothing has worked. I'll be putting in a call to Google Support in the morning, though I have a feeling they're going to tell me, "Sorry, but your phone is out of warranty."
 
T

toastgodsupreme

Guest
timbck2 said:
This problem just started for me. I've tried all the "fixes" mentioned here and elsewhere on the web, including airplane mode, re-flashing Lollipop 5.1.0, factory reset, flashing another ROM (Cyanogenmod) - nothing has worked. I'll be putting in a call to Google Support in the morning, though I have a feeling they're going to tell me, "Sorry, but your phone is out of warranty."
Click to expand...
Click to collapse

did you attempt to fix permissions?
 
T

toastgodsupreme

Guest
timbck2 said:
Isn't that more of an Apple thing? How would one do that in Android?
Click to expand...
Click to collapse

then you haven't tried everything like you said.

http://xdaforums.com/google-nexus-5...rd-reboots-t2947784/post56924944#post56924944

basically just run these commands:

chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
Click to expand...
Click to collapse

then reboot

here's the thing... when i was working on a way to modify my mac address, i managed to break my wifi. it would show turning on, but it wouldn't turn on. because i broke it, i knew what caused it, and i also fixed it by fixing my macaddr file and it's permissions. as of yet, i haven't seen anyone with this issue try this to fix their problem.
 
E

enemylisted

New member
Apr 8, 2015
1
0
Hi guys,

I am new to XDA.. but I've been a Nexus 5 owner since November 2013. My phone was running fine without any issues until Android 5.0 OTA , which I updated in Early 2015.

My wifi button grayed out/stuck turning wifi on like everyone mentioned here. It would work sometimes if I Factory Reset/Wipe - Airplane Mode , Reboot - Safemode ( sometimes work ). I got very frustrated with this issue and I decided to call LG for repair since my warranty was due. Even though LG customer service sucked really bad but they did repair my phone for free even though I am due for factory warranty. I got my phone back from LG after 2 weeks, they replaced * Motherboard * on the service paper. Guess what? IT DID NOT FIX THE PROBLEM, so I called LG again and I Re-sent back the phone to LG for deeper investigation . After another 2 weeks that I send my phone in THE SECOND TIME, My nexus came back to me. This time the service paper indicate they * Searching for SVC message due to no service, Download new software* . Bummer, the WIFI still grayed out after Two repairs. So I called LG again today and my phone is going back to Fort Worth ,TX the third time.

I just want to let you guys know my part of story, Thank for reading. ---- My phone was never rooted and I don't plan to --- I don't think its a hardware issue, I blame Google for this ---
 
T

toastgodsupreme

Guest
You guys are so boring.

So finally today I had this problem not of my own doing. Was using my phone and it rebooted on it's own. After that, wifi stuck turning on.

So I run my commands that I told you chuckle****s, and nothing. Weird. Should have worked.

I clear cache and dalvik to be on the safe side, reboot, not fixed. Weird.

I have the liveboot log enabled, I notice a few things:
E/wpa_supplicant( 2086): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 2086): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2086): wlan0: Failed to initialize driver interface

wifistatemachine failed to start driver

<4>[ 1.802222] wifi_get_mac_addr
I/rmt_storage( 179):
<3>[ 1.802285] bcm_wifi_get_mac_addr: Failed to get information from file /persist/wifi/.macaddr (-2)

OH LOOK, FAILED TO GET MAC ADDRESS FROM FILE.

So I go in with root explorer, delete .macaddr file, and run these commands (the first line is my mac address being set, because I know what it is already; obviously you'll need SU to do this):
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > /persist/wifi/.macaddr
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr

**Reboot, wifi works again.**

My guess is something got corrupted with the area where that file existed. Deleting it entirely and recreating it means it was created in a new area on the chip. **** if I know for certain though. What I do know is what I've been telling you guys for a while works and none of you are bothering with doing the easiest fix. But keep flashing custom roms and sending your phones in.

Most of you don't know what your wifi mac address is, have no motivation or way to find out, and will end up using mine, so I've modified mine in the first line to not be mine. Because I don't want you all out there cloning my ****ing mac addy since you can't be bothered to change it in the script.

Edit: I have not checked if a broken btaddr file affects wifi, possible but not likely, but that may need to be repaired too in a similar manner.
 
Last edited:
D

DarkAura

Member
Dec 10, 2006
6
0
IMEI number change on wifi repair

Hey all,
Its been 2 months I am facing the same issue with my Nexus 5. After looking at logs, I am convinced its a hardware issue. I have sent my phone twice to the LG repair center to change the logic board. Here is my question, If LG changes the logic board, should the IMEI number change?
 
T

toastgodsupreme

Guest
DarkAura said:
Hey all,
Its been 2 months I am facing the same issue with my Nexus 5. After looking at logs, I am convinced its a hardware issue. I have sent my phone twice to the LG repair center to change the logic board. Here is my question, If LG changes the logic board, should the IMEI number change?
Click to expand...
Click to collapse

And what did your logs say?
 
D

DarkAura

Member
Dec 10, 2006
6
0
Here is what i see just after bootup. I am running stock 5.0 without root.
04-10 09:43:21.255: E/wpa_supplicant(877): Could not set interface wlan0 flags (UP): Operation not permitted
04-10 09:43:21.255: E/wpa_supplicant(877): nl80211: Could not set interface 'wlan0' UP
04-10 09:43:21.256: E/wpa_supplicant(877): wlan0: Failed to initialize driver interface

Also is there a way to power reset the wifi chip? some equivalent to disconnecting the battery?
 
T

toastgodsupreme

Guest
DarkAura said:
Here is what i see just after bootup. I am running stock 5.0 without root.
04-10 09:43:21.255: E/wpa_supplicant(877): Could not set interface wlan0 flags (UP): Operation not permitted
04-10 09:43:21.255: E/wpa_supplicant(877): nl80211: Could not set interface 'wlan0' UP
04-10 09:43:21.256: E/wpa_supplicant(877): wlan0: Failed to initialize driver interface

Also is there a way to power reset the wifi chip? some equivalent to disconnecting the battery?
Click to expand...
Click to collapse

Did you even read my post RIGHT ABOVE YOURS where I posted the same log message AND fixed the issue? ?
 
D

DarkAura

Member
Dec 10, 2006
6
0
That worked once. Wifi started and the phone froze during accessing wifi settings. On reboot I saw the following:

<6>[ 0.469266] wifi: bcm_init_wlan_mem: WIFI MEM Allocated
<6>[ 0.469401] bcm_wifi_init_gpio_mem: wifi gpio and mem initialized
<6>[ 1.430818] wcf_status: wifi_detect = 0
<4>[ 1.474627] wifi_set_power = 1
<6>[ 1.630446] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 1.840182] wifi_set_carddetect = 1
<6>[ 1.840223] wcf_status: wifi_detect = 1
<4>[ 3.840200] failed to power up wifi chip, retry again (4 left) **
<4>[ 3.840382] ## wifi_remove
<4>[ 3.840423] wifi_set_power = 0
<6>[ 3.940531] bcm_wifi_set_power: wifi power successed to pull down
<4>[ 3.940604] wifi_set_carddetect = 0
<6>[ 3.940644] wcf_status: wifi_detect = 0
<4>[ 3.941222] wifi_set_power = 1
<6>[ 4.091316] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 4.300177] wifi_set_carddetect = 1
<6>[ 4.300250] wcf_status: wifi_detect = 1
<4>[ 6.300191] failed to power up wifi chip, retry again (3 left) **
<4>[ 6.300333] ## wifi_remove
<6>[ 6.400442] bcm_wifi_set_power: wifi power successed to pull down
<6>[ 6.400484] wcf_status: wifi_detect = 0
<6>[ 6.550949] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 6.760227] wifi_set_carddetect = 1
<6>[ 6.760266] wcf_status: wifi_detect = 1
<4>[ 8.760188] failed to power up wifi chip, retry again (2 left) **
<4>[ 8.760367] ## wifi_remove
<4>[ 8.760406] wifi_set_power = 0
<6>[ 8.860513] bcm_wifi_set_power: wifi power successed to pull down
<4>[ 8.860585] wifi_set_carddetect = 0
<6>[ 8.860626] wcf_status: wifi_detect = 0
<4>[ 8.861030] wifi_set_power = 1
<6>[ 9.011125] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 9.220187] wifi_set_carddetect = 1
<6>[ 9.220259] wcf_status: wifi_detect = 1
<4>[ 11.220187] failed to power up wifi chip, retry again (1 left) **
<4>[ 11.220360] ## wifi_remove
<4>[ 11.220399] wifi_set_power = 0
<6>[ 11.320481] bcm_wifi_set_power: wifi power successed to pull down
<6>[ 11.320554] wcf_status: wifi_detect = 0
 
T

toastgodsupreme

Guest
DarkAura said:
That worked once. Wifi started and the phone froze during accessing wifi settings. On reboot I saw the following:

<6>[ 0.469266] wifi: bcm_init_wlan_mem: WIFI MEM Allocated
<6>[ 0.469401] bcm_wifi_init_gpio_mem: wifi gpio and mem initialized
<6>[ 1.430818] wcf_status: wifi_detect = 0
<4>[ 1.474627] wifi_set_power = 1
<6>[ 1.630446] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 1.840182] wifi_set_carddetect = 1
<6>[ 1.840223] wcf_status: wifi_detect = 1
<4>[ 3.840200] failed to power up wifi chip, retry again (4 left) **
<4>[ 3.840382] ## wifi_remove
<4>[ 3.840423] wifi_set_power = 0
<6>[ 3.940531] bcm_wifi_set_power: wifi power successed to pull down
<4>[ 3.940604] wifi_set_carddetect = 0
<6>[ 3.940644] wcf_status: wifi_detect = 0
<4>[ 3.941222] wifi_set_power = 1
<6>[ 4.091316] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 4.300177] wifi_set_carddetect = 1
<6>[ 4.300250] wcf_status: wifi_detect = 1
<4>[ 6.300191] failed to power up wifi chip, retry again (3 left) **
<4>[ 6.300333] ## wifi_remove
<6>[ 6.400442] bcm_wifi_set_power: wifi power successed to pull down
<6>[ 6.400484] wcf_status: wifi_detect = 0
<6>[ 6.550949] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 6.760227] wifi_set_carddetect = 1
<6>[ 6.760266] wcf_status: wifi_detect = 1
<4>[ 8.760188] failed to power up wifi chip, retry again (2 left) **
<4>[ 8.760367] ## wifi_remove
<4>[ 8.760406] wifi_set_power = 0
<6>[ 8.860513] bcm_wifi_set_power: wifi power successed to pull down
<4>[ 8.860585] wifi_set_carddetect = 0
<6>[ 8.860626] wcf_status: wifi_detect = 0
<4>[ 8.861030] wifi_set_power = 1
<6>[ 9.011125] bcm_wifi_set_power: wifi power successed to pull up
<4>[ 9.220187] wifi_set_carddetect = 1
<6>[ 9.220259] wcf_status: wifi_detect = 1
<4>[ 11.220187] failed to power up wifi chip, retry again (1 left) **
<4>[ 11.220360] ## wifi_remove
<4>[ 11.220399] wifi_set_power = 0
<6>[ 11.320481] bcm_wifi_set_power: wifi power successed to pull down
<6>[ 11.320554] wcf_status: wifi_detect = 0
Click to expand...
Click to collapse

Nothing there indicates a hardware issue with the wifi system. If the fix worked once then it's obviously software related. Do it again but also nuke your wpa_supplicant file. Then reboot.
 
D

DarkAura

Member
Dec 10, 2006
6
0
Tried setting the mac address and deleting wpa_supplicant. Wifi does starts up and drops. After a few drops, it reverts back to "Turning on..."
Here are the dmesg logs. I see SDCC-CORE: Register Dumps over and over again.

<3>[ 224.802934] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.803065] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.803142] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.803277] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.810734] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.810832] mmc0: SDCC PWR is ON
<3>[ 224.810884] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.810936] mmc0: SDCC irq is enabled
<3>[ 224.811028] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.811082] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.811176] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.811268] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.811321] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.811412] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.811464] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.811556] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.811606] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.811695] == SDCC Test Bus Debug ==
<3>[ 224.811747] TestBus(0) = 0x00008000
<3>[ 224.811841] TestBus(1) = 0x00000080
<3>[ 224.811932] TestBus(2) = 0x00006010
<3>[ 224.811982] TestBus(3) = 0x018001ff
<3>[ 224.812033] TestBus(4) = 0x00063fd0
<3>[ 224.812122] TestBus(5) = 0x0004c030
<3>[ 224.812172] TestBus(6) = 0x00000000
<3>[ 224.812222] TestBus(7) = 0x000003ff
<3>[ 224.812313] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.812365] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.812459] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.812552] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.817425] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.817478] mmc0: SDCC PWR is ON
<3>[ 224.817530] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.817621] mmc0: SDCC irq is enabled
<3>[ 224.817673] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.817767] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.817819] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.817873] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.817967] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.818020] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.818113] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.818218] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.818316] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.818369] == SDCC Test Bus Debug ==
<3>[ 224.818463] TestBus(0) = 0x00008000
<3>[ 224.818653] TestBus(1) = 0x00000080
<3>[ 224.818750] TestBus(2) = 0x00006010
<3>[ 224.818803] TestBus(3) = 0x018001ff
<3>[ 224.818895] TestBus(4) = 0x00063fd0
<3>[ 224.818946] TestBus(5) = 0x0004c030
<3>[ 224.818997] TestBus(6) = 0x00000000
<3>[ 224.819089] TestBus(7) = 0x000003ff
<3>[ 224.819139] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.819191] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.819299] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.819396] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.824000] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.824095] mmc0: SDCC PWR is ON
<3>[ 224.824147] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.824198] mmc0: SDCC irq is enabled
<3>[ 224.824290] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.824344] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.824437] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.824530] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.824583] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.824675] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.824728] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.824821] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.824872] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.824964] == SDCC Test Bus Debug ==
<3>[ 224.825015] TestBus(0) = 0x00008000
<3>[ 224.825111] TestBus(1) = 0x00000080
<3>[ 224.825202] TestBus(2) = 0x00006010
<3>[ 224.825253] TestBus(3) = 0x018001ff
<3>[ 224.825303] TestBus(4) = 0x00063fd0
<3>[ 224.825394] TestBus(5) = 0x0004c030
<3>[ 224.825445] TestBus(6) = 0x00000000
<3>[ 224.825496] TestBus(7) = 0x000003ff
<3>[ 224.825547] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.825638] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.825731] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.825784] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.829155] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.829208] mmc0: SDCC PWR is ON
<3>[ 224.829258] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.829348] mmc0: SDCC irq is enabled
<3>[ 224.829399] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.829493] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.829546] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.829638] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.829732] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.829784] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.829878] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.829930] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.830022] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.830072] == SDCC Test Bus Debug ==
<3>[ 224.830163] TestBus(0) = 0x00008000
<3>[ 224.830259] TestBus(1) = 0x00000080
<3>[ 224.830310] TestBus(2) = 0x00006010
<3>[ 224.830361] TestBus(3) = 0x018001ff
<3>[ 224.830454] TestBus(4) = 0x00063fd0
<3>[ 224.830504] TestBus(5) = 0x0004c030
<3>[ 224.830556] TestBus(6) = 0x00000000
<3>[ 224.830648] TestBus(7) = 0x000003ff
<3>[ 224.830698] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.830750] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.830844] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.830939] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.835352] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.835445] mmc0: SDCC PWR is ON
<3>[ 224.835495] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.835546] mmc0: SDCC irq is enabled
<3>[ 224.835637] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.835689] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.835782] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.835834] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.835926] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.836019] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.836071] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.836162] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.836212] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.836303] == SDCC Test Bus Debug ==
<3>[ 224.836353] TestBus(0) = 0x00008000
<3>[ 224.836450] TestBus(1) = 0x00000080
<3>[ 224.836540] TestBus(2) = 0x00006010
<3>[ 224.836590] TestBus(3) = 0x018001ff
<3>[ 224.836640] TestBus(4) = 0x00063fd0
<3>[ 224.836730] TestBus(5) = 0x0004c030
<3>[ 224.836781] TestBus(6) = 0x00000000
<3>[ 224.836831] TestBus(7) = 0x000003ff
<3>[ 224.836882] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.836974] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.837067] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.837121] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.841458] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.841552] mmc0: SDCC PWR is ON
<3>[ 224.841603] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.841695] mmc0: SDCC irq is enabled
<3>[ 224.841747] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.841843] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.841896] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.841989] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.842082] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.842133] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.842224] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.842276] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.842366] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.842415] == SDCC Test Bus Debug ==
<3>[ 224.842464] TestBus(0) = 0x00008000
<3>[ 224.842597] TestBus(1) = 0x00000080
<3>[ 224.842647] TestBus(2) = 0x00006010
<3>[ 224.842696] TestBus(3) = 0x018001ff
<3>[ 224.842785] TestBus(4) = 0x00063fd0
<3>[ 224.842834] TestBus(5) = 0x0004c030
<3>[ 224.842884] TestBus(6) = 0x00000000
<3>[ 224.842973] TestBus(7) = 0x000003ff
<3>[ 224.843023] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.843119] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.843212] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.843305] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<3>[ 224.846878] mmc0: msmsdcc_execute_tuning: no tuning point found
<3>[ 224.846934] mmc0: SDCC PWR is ON
<3>[ 224.847028] mmc0: SDCC clks are ON, MCLK rate=200000000
<3>[ 224.847079] mmc0: SDCC irq is enabled
<3>[ 224.847171] ===== SDCC-CORE: Register Dumps @Phys_base=0xf98a4000, @virt_base=0xf0338000 =====
<3>[ 224.847226] Reg=0x00: 0x00000001, 0x01211b00, 0x00000000, 0x00000000
<3>[ 224.847320] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.847375] Reg=0x20: 0x00000000, 0x17d78400, 0x00000000, 0x00000000
<3>[ 224.847470] Reg=0x30: 0x00000000, 0x000c0000, 0x00000000, 0x408001ff
<3>[ 224.847566] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.847620] Reg=0x50: 0x00000038, 0x00000000, 0x00000000, 0x00000000
<3>[ 224.847716] Reg=0x60: 0x07876400, 0x00000000, 0x00000040, 0x00000000
<3>[ 224.847769] mmc0: MCI_TEST_INPUT = 0x0000003e
<3>[ 224.847861] == SDCC Test Bus Debug ==
<3>[ 224.847911] TestBus(0) = 0x00008000
<3>[ 224.848007] TestBus(1) = 0x00000080
<3>[ 224.848099] TestBus(2) = 0x00006010
<3>[ 224.848150] TestBus(3) = 0x018001ff
<3>[ 224.848201] TestBus(4) = 0x00063fd0
<3>[ 224.848253] TestBus(5) = 0x0004c030
<3>[ 224.848345] TestBus(6) = 0x00000000
<3>[ 224.848395] TestBus(7) = 0x000003ff
<3>[ 224.848446] mmc0: SPS BAM reset failed: sps reset_bam=1
<3>[ 224.848539] mmc0: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=0
<3>[ 224.848633] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 224.848685] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
 
C

cmaruan

Member
Jan 21, 2015
6
0
toastgodsupreme said:
You guys are so boring.

So finally today I had this problem not of my own doing. Was using my phone and it rebooted on it's own. After that, wifi stuck turning on.

So I run my commands that I told you chuckle****s, and nothing. Weird. Should have worked.

I clear cache and dalvik to be on the safe side, reboot, not fixed. Weird.

I have the liveboot log enabled, I notice a few things:
E/wpa_supplicant( 2086): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 2086): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2086): wlan0: Failed to initialize driver interface

wifistatemachine failed to start driver

<4>[ 1.802222] wifi_get_mac_addr
I/rmt_storage( 179):
<3>[ 1.802285] bcm_wifi_get_mac_addr: Failed to get information from file /persist/wifi/.macaddr (-2)

OH LOOK, FAILED TO GET MAC ADDRESS FROM FILE.

So I go in with root explorer, delete .macaddr file, and run these commands (the first line is my mac address being set, because I know what it is already; obviously you'll need SU to do this):
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > /persist/wifi/.macaddr
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr

**Reboot, wifi works again.**

My guess is something got corrupted with the area where that file existed. Deleting it entirely and recreating it means it was created in a new area on the chip. **** if I know for certain though. What I do know is what I've been telling you guys for a while works and none of you are bothering with doing the easiest fix. But keep flashing custom roms and sending your phones in.

Most of you don't know what your wifi mac address is, have no motivation or way to find out, and will end up using mine, so I've modified mine in the first line to not be mine. Because I don't want you all out there cloning my ****ing mac addy since you can't be bothered to change it in the script.

Edit: I have not checked if a broken btaddr file affects wifi, possible but not likely, but that may need to be repaired too in a similar manner.
Click to expand...
Click to collapse

I did the very same thing.. and nothing changed at all.
The only thing that is bothering me is that I had installed plenty of different times the android on my Nexus. And nowhere on the internet I found how to get my MAC address without connecting it first..
I typed any MAC Addr into it, but not sure if this might be the reason my wifi is not working :/
[edit] One more thing, how do I read these logs? I am using logcat.. Is there any other way to do so?
 
Last edited:
T

toastgodsupreme

Guest
cmaruan said:
I did the very same thing.. and nothing changed at all.
The only thing that is bothering me is that I had installed plenty of different times the android on my Nexus. And nowhere on the internet I found how to get my MAC address without connecting it first..
I typed any MAC Addr into it, but not sure if this might be the reason my wifi is not working :/
[edit] One more thing, how do I read these logs? I am using logcat.. Is there any other way to do so?
Click to expand...
Click to collapse

http://xdaforums.com/android/apps-games/liveboot-t2976189
 
T

tijnduck

New member
Apr 15, 2015
1
0
cmaruan said:
Already got this app.. I've been looking through these logs using adb shell .. Still cant find the mac addr of my phone :/
Click to expand...
Click to collapse

I have the same problem for two days now, cant find my mac address without connecting to wifi wich is stuck at 'turning on'.:(
Have tried everyting almost except the solution posted by toast. Is there another way to fix this?
 
L

lukasz050

Member
Jan 27, 2013
39
2
i have the same problem and I also disconected battery, motherboard, and checked all cable connections
Also I installed a few Roms

I have no warranty, and replace the motherboard will be very expensive

whether it is possible to use Wi-Fi via modem OTG on my nexus 5 ?
 
T

toastgodsupreme

Guest
cmaruan said:
Already got this app.. I've been looking through these logs using adb shell .. Still cant find the mac addr of my phone :/
Click to expand...
Click to collapse

The logs don't give you the MAC, just for finding errors.

lukasz050 said:
i have the same problem and I also disconected battery, motherboard, and checked all cable connections
Also I installed a few Roms

I have no warranty, and replace the motherboard will be very expensive

whether it is possible to use Wi-Fi via modem OTG on my nexus 5 ?
Click to expand...
Click to collapse

If it truly is hardware and you're out of warranty, the only other option without spending money right away is to try to bake the circuit board to reflow the solder points.

http://mr-mediocre.hubpages.com/hub/How-Baking-A-Motherboard-in-the-Oven-Worked-for-Me
https://www.youtube.com/watch?v=yFCFiSB2Fuk
https://www.youtube.com/watch?v=GUIi52SwUzw

Common temps are 375F at 10 minutes for a NON-CONVECTION oven (ie. normal oven).

PS1 dude did his at 425 for 8 minutes, but that's 2011.

This can possibly eat the entire circuit board, know that before doing it.
 
You must log in or register to reply here.

Similar threads

surviveland
[Guide][Flash] How to play flash video on Android 4.4 Kitkat
Replies
934
Views
3M
B
benens
E
[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4
Replies
161
Views
213K
Z
zz45
Gipjoe
What are you running on your nexus 5?
Replies
1K
Views
226K
O
ocarinaz64
L
Stuck at "erasing" when doing a factory reset?
Replies
43
Views
119K
D
DawarAhmad
T
Slow wifi on N5
Replies
216
Views
58K
Schrotty35
Schrotty35

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    H
    Humpie
    From what I have seen on the internet I'm not the only one with this problem, but as far as I know, I'm the only nexus 5 owner with this problem. See, two days ago, all of a sudden (I must confess, because the phone often forgets wifi networks, I was using the Wifi password recovery & backup app, but that can't be the problem, I use it all the time), but all of a sudden, after a reboot, my wifi is turned off. I already found that to be strange, but then it became even stranger: when I tried to turn it on, it kept on 'turning it on' but never actually turned it on! (the switch is still dark gray in the 'on' fase). I tried to figure out why it was doing this, the last apps I installed were Tasker, Autovoice and secure settings, so I uninstalled them, no difference. I tried disabeling my xposed framework, no difference. I tried wiping Cache and Dalvik cache, no difference. I accedently (swipe to wipe is dangerous!) completely wiped my phone, but still no difference. Then, using the Nexus Root Toolkit, I reverted back to stock and unrooted. Then finally, my wifi came back on :). So I slowly installed everything again (stupid me had no backup) and the wifi kept working for a day....:( And till now it's been off, not willing to turn on :(. It must be some app I installed I guess. I also tried to change kernels but again with no succes... Oh and my mac-adress is also nowhere to be found, is that normal when the wifi is turned off?
    I'm sorry for the long personal story, but I would be very grateful if someone had a working idea :)
    tnx in advance guys
    View
    2
    mhd1st
    mhd1st
    Update
    as silly as it may seems but this was a relief for me
    i got mad at it yesterday and smashed my nexus 5 into million pieces
    it was driving me crazy
    i will never buy any LG products not mobiles , dish washers or any of its products ever again.
    View
    2
    monty6630
    monty6630
    Humpie said:
    From what I have seen on the internet I'm not the only one with this problem, but as far as I know, I'm the only nexus 5 owner with this problem. See, two days ago, all of a sudden (I must confess, because the phone often forgets wifi networks, I was using the Wifi password recovery & backup app, but that can't be the problem, I use it all the time), but all of a sudden, after a reboot, my wifi is turned off. I already found that to be strange, but then it became even stranger: when I tried to turn it on, it kept on 'turning it on' but never actually turned it on! (the switch is still dark gray in the 'on' fase). I tried to figure out why it was doing this, the last apps I installed were Tasker, Autovoice and secure settings, so I uninstalled them, no difference. I tried disabeling my xposed framework, no difference. I tried wiping Cache and Dalvik cache, no difference. I accedently (swipe to wipe is dangerous!) completely wiped my phone, but still no difference. Then, using the Nexus Root Toolkit, I reverted back to stock and unrooted. Then finally, my wifi came back on :). So I slowly installed everything again (stupid me had no backup) and the wifi kept working for a day....:( And till now it's been off, not willing to turn on :(. It must be some app I installed I guess. I also tried to change kernels but again with no succes... Oh and my mac-adress is also nowhere to be found, is that normal when the wifi is turned off?
    I'm sorry for the long personal story, but I would be very grateful if someone had a working idea :)
    tnx in advance guys
    Click to expand...
    Click to collapse
    Hey all,
    After more than a week with NO WIFI, i have finally figured it out.
    Here are the detailed.
    ISSUE: After OTA update of 4.4.3 on new nexus 5, the phone was rebooted automatically and after reboot WIFI button was greyed out. It only showed "TURNING ON".
    FAILED SOLUTION ATTEMPTS: Following step DID NOT HELP
    1. Factory reset
    2. Battery drain and recharge after full drain
    3. Power off for few hours and restart
    4. Whacking the set on palm (yes, whacking, it was a recommended solution on a thread)
    5. Opened the handset and checked all the hardware link, every thing was fine
    6. Bootloader unlock, recovery installation (TWRP), downgrade to 4.4.2 (downloaded from google's web page)
    7. Downgrade to 4.4
    8. OTA update from down graded firmware
    9. Sideloading the 4.4.3 update on firmware 4.4.2
    10. Rooting, and installation of custom ROM (slimKat, Cynaogen mod)
    11. Installation of custom kernel (linaro)
    12. Flashing of 4.4.2 & 4.4 Radio/Boot images on stock rom of 4.4.3
    13. Clean install of 4.4.3 (removing everything from phone except recovery)
    14. *#*#4636#*#*, goto wifi and restart.
    15. *#*#4636#*#*, wifi state shown "UN-INITIALIZED"

    Actual Solution that worked
    ***** Install Paranoid Android ROM on rooted Nexus 5. The issue is with Kernel , which control the HW/OS communication. Apparently Kernel of this ROM removed the issue (but installation of SlimKat/CyanogenMod/Custom Kernel).
    I then restored the backup of stock 4.4.3 from recovery and did a factory reset. Wifi & every thing else works fine now *****
    View
    2
    S
    shaklee3
    Chefov01 said:
    Can you give us some details about baking the mainboard? I'd like to try this method, I don't have anything to lose! :D
    Click to expand...
    Click to collapse

    Take the phone apart and remove the main board (the large board above the battery). It has about 5 connectors plugged in. Remove your SIM. Preheat oven (I used a toaster oven) to 350 degrees, and put the board in on a crumpled piece of foil so there's plenty of airflow all around. Bake for 3 minutes. Remove it and let it cool down. Reassemble phone.
    View
    2
    F
    franksandroid
    Updated Android 6.0 solved the issue

    Humpie said:
    From what I have seen on the internet I'm not the only one with this problem, but as far as I know, I'm the only nexus 5 owner with this problem. See, two days ago, all of a sudden (I must confess, because the phone often forgets wifi networks, I was using the Wifi password recovery & backup app, but that can't be the problem, I use it all the time), but all of a sudden, after a reboot, my wifi is turned off. I already found that to be strange, but then it became even stranger: when I tried to turn it on, it kept on 'turning it on' but never actually turned it on! (the switch is still dark gray in the 'on' fase). I tried to figure out why it was doing this, the last apps I installed were Tasker, Autovoice and secure settings, so I uninstalled them, no difference. I tried disabeling my xposed framework, no difference. I tried wiping Cache and Dalvik cache, no difference. I accedently (swipe to wipe is dangerous!) completely wiped my phone, but still no difference. Then, using the Nexus Root Toolkit, I reverted back to stock and unrooted. Then finally, my wifi came back on :). So I slowly installed everything again (stupid me had no backup) and the wifi kept working for a day....:( And till now it's been off, not willing to turn on :(. It must be some app I installed I guess. I also tried to change kernels but again with no succes... Oh and my mac-adress is also nowhere to be found, is that normal when the wifi is turned off?
    I'm sorry for the long personal story, but I would be very grateful if someone had a working idea :)
    tnx in advance guys
    Click to expand...
    Click to collapse

    So I had the unfortunate experience of having my wifi go down while on vacation and for 3 weeks I spent a good chunk of time wiping and reinstalling multiple versions from Cyanogen, Paranoid android and 4.4 - 5.1 to no avail. I just did another factory wipe today and installed the new Android 6.0

    The Finger Pointing Game is OVER
    Read through 30+ pages of other android users with similar experience and some people send their units back to LG and some even managed getting a new handset. There was never any hardware issues with my unit I just couldn't turn on the WiFi but after the install WiFi works? Guess next time you push a software update to our Phones CHECK YOUR SH*T google and Maybe DON'T Take 3 months to FIX your F*CK Up.
    View

New posts