yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] toastgodsupreme:
Have you tried setting a custom MAC yet?

Had this for my old N5:

cd /persist

rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr

rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr

Reboot afterwards. Of course you'll need root.

Some things to keep in mind:

1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.

2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.

3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
I have the exact same problem but with a completely stock, never-rooted Nexus 6. Marshmallow 6.0 OTA arrived a week after the 1 year Motorola warranty expired, and problems with screencasting started immediately. But yesterday, the wifi quit, and the phone rebooted itself moments later. The wifi has never come back on since. I also noticed the bogus 02:00:00:00:00:00 mac address, suggesting that something got corrupted. For reference, this phone was purchased directly from Motorola, and is using a VZW sim.

Of course there's nothing Motorola will do, since it's 2 weeks out of warranty. But I'm hopeful that the hardware is still alright since I can still turn bluetooth on and off. Can someone confirm that this phone's BT and Wifi are on the same chip? I suppose there is no reason not to root it now...

I'd like to try to set the mac address using the above code. Can anyone suggest a way to retrieve the old mac? Thanks...
[Nexus 6 Q&A, Help & Troubleshooting] pradipsoman:
Not working..

Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00
[Nexus 6 Q&A, Help & Troubleshooting] tanipat:
Thanks for all supported here, seems so many people got tge same problem as mine.

I never unlock bootloader on this device, im at 5.1.1 and it happens with my wifi shows wrong mac address so i just tried to ota to 6.0 and the issue is still there? Anybody find the cause pf problem here?
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
Did you happen to try setting it to its original mac, or to some other valid broadcom mac? Or did it fail after setting a random mac. I ask because I am about to root my wife's phone just to attempt this same procedure...
[Nexus 6 Q&A, Help & Troubleshooting] pradipsoman:
I used the same id as provided here since there is no way to retrieve my original mac id..linux/android command to find eth0 id do not work since the wifi/bluetooth is corrupt. I am pretty sure your outcome may be same as mine...as I find many having the same issue but no genuine solutions...In fact seems Moto guys think we are fools as they keep talking of "ohh sir....you should not have rooted it" and the factory reset method would repair the wifi etc....they only have such elementary suggestions suggested by non-tech people who do not understand the issue at all.....
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
Which totally blows because, 1) I never rooted this one for that very reason, and 2) the warranty expired a week before it quit working.

I was able to retrieve the original mac address by checking my home router's DHCP logs and eliminating other known macs. You might try something like that. [MENTION=3085114]toastgodsupreme[/MENTION] mentions that some worked and some didn't, so I am holding out hope.
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
sigh... It seems your prediction has proved correct. I rooted it easily enough (and in the process performed a factory reset) and later went in with ADB to try resetting the .macaddr file in the /persist folder using these commands suggested by [MENTION=3085114]toastgodsupreme[/MENTION] :

*where ?? is my actual mac address.

I tried the original wifi mac address for this phone (forwards and also in reverse order), and by changing the last number slightly. Each time, I could verify that the binary file was readable with:

cat ./wifi/.macaddr | od -c

I would restart after each attempt, and each time the wifi mac address in Settings > About Phone would come up as "02:00:00:00:00:00" and I could not turn on the wifi.

I also notice, in case this is helpful to anyone, that no matter what value I had set in the /wifi/.macaddr file, my original wifi mac address always gets returned when I run:

ip link show wlan0

which returns:

5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether ??:??:??:??:??:?? brd ff:ff:ff:ff:ff:ff

* where ?? is my actual original mac addess

This leads me to think that the mac address is not stored in the same format or location on the Nexus 6 as it was on the Nexus 5. Would someone with a working N6 be willing to investigate their /persist folder and figure out how to fix this?

For what it's worth, I also tried:

ip link set wlan0 up

but always get:

RTNETLINK answers: Operation not permitted

despite clearly having root.
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
UPDATE: Wifi started working after just removing the SIM!

In desperation, I got a replacement Nexus 6, and moved the Verizon Wireless SIM card over to the new phone (which is still running 5.1.0, and I am quite hesitant to update it...). That would have let my wife use it it while I attempt to fix the broken wifi on the original. In scouring XDA I had found a ton of suggestions well beyond repairing the MAC address. (If anyone is interested, I will post that detailed list here with links to the relevant posts.) That list included things like repairing the /persist partition, altering and/or deleting the wpa_supplicant.conf file, various changes while in airplane mode or safe mode, clearing data for certain google services -- from chilling it in the fridge to baking it in the oven.

But, before I got a chance to try

any

of those suggestions, I started up the original phone without any SIM card in it, and lo and behold - wifi is functioning normally! I can toggle it on and off, change the frequency, connect to networks, and stream data, and the MAC address appears correctly in settings. So at least in my case, it was

not a hardware issue

. I suspected this when I could see bluetooth functioning normally. Now why did removing the SIM work? Will it still work when I abandon Verizon for Project Fi? I'll update when I find out.

Could this be related to Verizon rolling out wifi calling? Or do they just hate me for holding on to 2 unlimited data plans?
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
What a hell this is! :(
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Have you tried modifying this file? On my Nexus 6, it is displaying my mac address.

/sys/devices/virtual/net/wlan0
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Update first to Marshmallow
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
Thanks - The text files at that location definitely seem to be where it pulls its display info from when I run:

#ip link show wlan0

My actual mac address appears correctly there, as well as in binary file: /persist/wifi/.macaddr

I am leaning away from this issue being a corrupted /persist and more towards it being a driver issue. I was able to get wifi to turn back on by adding the line "ap_scan=1" to the /data/misc/wifi/wpa_supplicant.conf file, as suggested by this thread, but it did not survive a reboot. Like the experience of [MENTION=6088025]jpsflores[/MENTION], the line was automatically removed from the wpa_supplicant.conf, and now I can't get wifi back with or without any of these lines in the wpa_supplicant.conf file:

ap_scan=1
ctrl_interface=wlan0
disable_scan_offload=0

So, I am quite frustrated. The few times wifi appeared, it seemed to be a fluke, and lasted only about an hour or until a reboot. Now I am not sure what to do.

---------- Post added at 05:03 PM ---------- Previous post was at 04:53 PM ----------

Thank you. However, this wifi problem started after the phone took an OTA to 6.0.0 Marshmallow. It is currently running the stock MRA58R build.

I am considering flashing the 6.0.1 MMB29S factory image, hoping the wifi driver might get replaced. Does anyone know if the radio changes from 6.0.0 to 6.0.1?
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
I don't think your wifi issue is caused by the radio.

But 6.x came with a new radio.

When you want to root, consider the lite rom of Danvdh. In the thread are bootloader and radio zips to flash in recovery.

http://xdaforums.com/showthread.php?p=59561445
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
Thanks for the links. I was trying to decide which ROM to go with. To be absolutely sure, I just did a complete wipe with TWRP, and took the full factory image from google's site, which also replaces the recovery and boot images. After that, the only partition that should not have changed is the /EFS partition.

Wifi still does not turn on, and I am not surprised after so many others have tried fixing it by replacing the ROM. At this point, it could only be something amiss in the /EFS partition, or else it is actually flakey hardware that works only occasionally and just long enough to tease me.

I'll re-root it tomorrow and see what the new wpa_supplicant.conf looks like. I can't for the life of me explain why adding "ap_scan=1" got it to work immediately, but then stopped working on every reboot afterward.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Have seen the same WiFi issue as yours with a Samsung S3.

Cause was the interfering and strong wifi-signal from an accespoint of the neighbours.
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
AFAIK the wifi driver is in the kernel, not in the radio.
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
A strong wifi signal masked your mac address and prevented the wifi from even turning on? Wouldn't you at least have to be able to turn on the wifi first before being affected by such a rogue signal? Also, after seeing the behavior in more than one location (at home and at work) I could say that in my case at least, it is not environmental.

However, thanks for highlighting that the problem is not unique to the Nexus 6. In my searching, I found tons of Nexus 5 users and some Samsung users complaining of the exact same symptoms.

Strangely, unlike most others, I can toggle bluetooth on and off all day long, but I can't toggle wifi to the on state.
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
Yes - and either way, replacing both had no effect. Flashed the stock image of MMB29S, and still no wifi.

Re-rooting was easy without a build.img using SuperSU 2.6.6, and as expected, the /data/misc/wifi/wpa_supplicant.conf reverts to the template from /system/etc/wifi/wpa_supplicant.conf, and looks like this now, with the default "ap_scan=1":

update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
pmf=1

But I am curious.... how does a wpa_supplicant.conf file go from looking like the above, to looking like this, which is how mine was right after the problems started?

disable_scan_offload=1
driver_param=use_p2p_group_interface=1p2p_device=1
update_config=1
device_name=shamu
manufacturer=motorola
model_name=Nexus 6
model_number=Nexus 6
serial_number=**********
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_no_go_freq=5170-5740
pmf=1
external_sim=1
wowlan_triggers=any
p2p_search_delay=0

network={
ssid="**"
psk="************"
key_mgmt=WPA-PSK
priority=1
}

network={
ssid="******"
psk="********"
key_mgmt=WPA-PSK
priority=2
}

I mean, what process goes in and changes this file over the life of the phone?
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Then there are only setting options left to try out.

1. WiFi interval (root)

Add/set in the file build.prop --> WiFi_supplicant_scan_interval; value of your choice (mine 200 for battery life). App: build.prop editor.

2. WiFi settings - Advanced: during sleep - never; frequency - 2,4 Ghz (manual)
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
Looks different
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
I can't thank you enough for posting those permissions. The differences were minor, and all were related to me trying to fix it in the first place. I removed the extra permissions from wlan_mac_serial.bin, and the wifi folder, but could not change the owner and group to 9004. In this context, that UID doesn't exist. (I am able to chown 9004 while in recovery, however I can not mount the persist folder there to edit it) But, since both your bt and wifi folders were empty anyway, I said, "ef it" and just deleted the wifi folder entirely. While in recovery I deleted cache and dalvik, and rebooted.

So, the wifi is currently working, and if it stays that way for more than a few days, I am selling this sucker as is. I already have an unopened N6 being delivered to replace it.

Interestingly, this is the third time that wifi has re-appeared after trying various things. For all three of these times the phone had been left on, untouched, in airplane mode for more than 48 hours. The first time it disappeared a week after taking the OTA to 6.0.0. I tried many things to fix it, rooting it in the process, and ultimately frustrated, left it alone for a week, turned it on without the sim card, and there it was working again. The second time it disappeared was after unrooting using the "Full Unroot" option in SuperSU. After rebooting, wifi was gone. Many more failed attempts to restore wifi later, it sat in airplane mode for another day or two until I added "apscan=1" to the wpa_supplicant.conf file. On reboot, wifi was back! 20 minutes later, it went away without reason! Today, after tweaking the permissions in the /persist folder, I rebooted, took it out of airplane mode, and there it was again. Coincidence? Or is it only working after COMPLETELY cycling power to the wifi chip?

I am both grateful (for your help), and skeptical (that it will last).
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
Well, np. Let me tell you a story of some problem i had a while ago. I use a Samsung tablet. When the first custom roms came i was very excited. A friend of mine made a CM12.1 rom for this device. I use a Logitech case with BT keyboard. I flashed CM, set everything up and everything worked fine untill i rebooted. The pair with the keyboard was gone and BT mac of the tablet was changed. After searching for days i had the idea to compare the /EFS partition (which holds IMEI, WIFI MAC, BT MAC ETC on a Samsung) with the tablet of my kid (same model, a month younger). I turned out that the rom changed not only permissions but also user/group of the file that holds the BT MAC. I don't know much about permissions, user and groups but i do know they are most important. I hope changing the permission like you did now fixed your problem.

(If the rom couldn't read the MAC from this file it "fantasized" a mac on booting. Sorry, english is not my native language so i don't know the correct word)
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
It's interesting, because even in your persist folder, the /persist/bt and /persist/wifi folders are empty, and the file permissions I changed only made it more restrictive, not less. I really can't say why it started working.

So, wifi has been working just fine since my last post. For a full week, I carried it with me, poked at it, turned wifi on and off (and back on again), connected to many different access points, signed into my google account, used every app in the stock image (including google apps for those thinking its related to google connectivity services) and browsed the newsstand for days without a hiccup. However, I kept it powered on the whole time. I allowed it to sleep, of course, and even drained the battery slowly down to 25%, and then charged it back to 100%. Nothing in the hardware prevented it from functioning perfectly.

What it can't do, it seems, is continue working after a reboot. I'd like to sell this thing, which means I've got to wipe it, which means I eventually would have had to reboot it. Which I did. Just now. And no... wifi did not come back.

Time to test a theory: I'll leave it on in airplane mode for 48 hours without changing anything else at all. I'll report back then...
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
After 73 hours, left on, I turned off airplane mode, and no dice. Still not working.

meh.
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
unbelievable :(

What will you try next?
[Nexus 6 Q&A, Help & Troubleshooting] DefectiveRobot:
Immediately following my last post on the 21st, I put it in airplane mode, and rebooted it, leaving it untouched in airplane mode until today. I picked it up (still on) and its battery was still at 50%. Turned off airplane mode. Tried to turn on wifi - and still nothing. A minute later (after making zero changes) I rebooted it and wifi came on all by itself again.

I know it is impossible to believe. It makes no sense at all.
[Nexus 6 Q&A, Help & Troubleshooting] bigmdm:
6.01 - same problem

My Device Google Nexus 5 begin automaticle updated from Android 5.xx to 6.00, then from 6.00 to 6.01.

After the upgrade from 6.00 to 6.01 missing WiFi and bluetooth. MAC address - 02: 00: 00: 00: 00: 00 ...

-Hard reset

-Factory reset

- Switch to Fly mode

it has not helped...

The folder /sys/class/net/wlan0/ - not found.
[Nexus 6 Q&A, Help & Troubleshooting] mrfunks:
same issue with Cyanogen 13

Updated to Marshmallow, and this dreded Mac address issue has appeared :( getting the 02:00:00 :00:00 address :(

I installed the latest Cyanogen 13, with and the issue is still here..

Whilst looking at the folders my data/media/wifi folder contains what looks like a corruped entropy.bin file.. has lots of random symbols in it..

Also looking at system/etc/wifi wpa_supplicant_overlay.conf , this has a line of "no_ctrl_interfaces= ", surely something should be after the = ?

I welcome any help, as we ll do in solving this nsty bug..

thanks

D
[Nexus 6 Q&A, Help & Troubleshooting] radool:
same issue here. had this issue for a few months.

switched to using a moto x.

at some point wifi was back, and it worked fine until i inserted a sim.

nothing seems to make it work anymore, not even booting in safe mode or removing the sim.

does anyone have any sort of solution for this? even a temporary one?

also... important note: BT used to be dead, now it works, but wifi still dead.
[Nexus 6 Q&A, Help & Troubleshooting] fbarcelo:
I have had the exact same situation In my Nexus 6 with Marshmallow, sadly I've thought that a factory reset could help and I do that.

Since that moment was unable to use my phone anymore, cause during setup it tries to turn on wifi and get stuck and that step (Skip option is not available)

Later I found a possible solution on XDA forum

"i also have a same problem with you. i tried to do as follow and succeeded

- go to data/misc/wifi (required root)

-backup file wpa_supplicant.conf in this folder which contains username and password wifi

- delete all file in this folder

- turn on wifi ( if you careful, you can reboot )

- now you can connect to wifi

- recovery file wpa_supplicant.conf"

But I didn't rooted my phone, neither activate the "unlock bootloader" option in settings.

So my situation now is:

1- Phone unrooted and can't be rooted without activating "unlock bootloader" option

2- That option can't be activated as phone never ends set up process step 2

3- Motorola wash their hands arguing I've bought the phone in USA and I live in Argentina (Yes I couldn't believe either, specially cause they broke my phone with the marshmallow upgrade)

4- In a desperate attempt I've tried to apply the upgrade to Android N (using adb sideload option) but the situation is the same.

I've understand that a downgrade to lollipop could fix it, but I couldn't do that without unlocking bootloader.

Any ideas? Any way to unlock bootloader from fastboot without accessing the settings menu?
[Nexus 6 Q&A, Help & Troubleshooting] ScottIsMyName:
Have you tried the old trick of bypassing activation?

On the welcome screen:

1) Tap the top left corner of the screen

2) Tap the top right corner of the screen

3) Tap the bottom right corner of the screen

4) Tap the bottom left corner of the screen

That’s it, should pop up the home screen shortly, if not retry. Remember not to drag your finger, simple tap top left, top right, bottom right, bottom left.
[Nexus 6 Q&A, Help & Troubleshooting] fbarcelo:
I never hear of that, will try tonight at home

And will keep you (And anyone else who could have a similar issue) informed, thanks
[Nexus 6 Q&A, Help & Troubleshooting] fbarcelo:
Sadly seems that google removed the option to skip setup in new versions :(
[Nexus 6 Q&A, Help & Troubleshooting] fbarcelo:
In desperation, I've started to try everything including change my SIM with my wife SIM

As is from another company, phone will restart it GSM-LTE settings and voila, phone boots then I was able to unlock bootloader and will try a downgrade to 5.0 this weekend, meanwhile phone works without wifi.
[Nexus 6 Q&A, Help & Troubleshooting] radool:
Did that too, tried 5.1.0 (LMY47I).

BT works now, at least when using it without a SIM, but wifi still dead. However not it doesn't say 02:00... it says unavailable.

it's strange so many people have this problem and nobody can figure out a solution.
[Nexus 6 Q&A, Help & Troubleshooting] tonio14545:
I had this problem on the March chroma ROM. My Mac address had the 2000 number and wifi wouldn't turn on. I dirty flashed the newest April one and now everything's working perfect
[Nexus 6 Q&A, Help & Troubleshooting] fbarcelo:
Downgrade, didn't fix anything, problem still the same, no wifi and no bluetoth

Now I found this

http://www.usoftsmartphone.com/t240333.html

That seems to be related.

It's for nexus 5 so the file provided does not work on nexus 6. Could you please share your /persist partition to try it?
[Nexus 6 Q&A, Help & Troubleshooting] radool:
Yes, found something like that in other forums as well.

Now we only need someone with a working Nexus 6 to share here the content of their /persist partition

Too bad noone with a GOOD nexus is looking at this thread :(
[Nexus 6 Q&A, Help & Troubleshooting] 2fas4u.kl:
Any clear updates/fixes

Hey everyone, I'm experiencing this exact same issue on a device in our household. Just wondering if anyone has come up with a clear fix, and if so, if they wouldn't mind sharing some clear step-by-step instructions. I can work my way through about anything, but don't have enough confidence/knowledge to go poking around myself.

Little background information on the device:

was previously rooted, but has been flashed back to factory using the Nexus 6 One-Click Unroot Toolkit.

I'm on a Mac, but have access to a Windows machine if needed for any tinkering.

Any help would be greatly appreciated as this issue is becoming increasingly frustrating for myself and the user.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
ok, this has been going on for a few months from my side, and my wifi only would turn on by itself(but not on) only from my home. but i finally figured it out and fixed it! now go to the main settings for the phone, choose security, smart lock.. if your smart lock is unclickable, set yourself up with a pattern or pin screen lock, then you can press smart lock. press smart lock, choose trusted places. if your address is in it(or any address), choose it then remove your address, now save. now you can remove your screen lock again if you want and that should fix the wifi turning on by itself :)

---------- Post added at 05:57 PM ---------- Previous post was at 05:57 PM ----------

just posted my "fix".
[Nexus 6 Q&A, Help & Troubleshooting] 2fas4u.kl:
unfortunately, no joy :(

just to expand, the issue on this device is the lack of or presence of an erroneous MAC address. Basically, the Wi-Fi will just never turn on.