Just sideloaded the Mashmallow update from 5.1.1 to 6.0 (downloaded from Google) and the update seemed to go normally - most things work as normal. But the WiFi wouldn't turn on, and it's mac address reports as 02:00:00:00:00:00. That address I know was an issue in the M Preview as a fake address.
I didn't want to hard reset it but in the end relented and loaded a clean new version of 6.0 from Google. When it restarts the second thing it wants to do, after selecting a language, is start the WiFi so it can log on. Of course WiFI won't start, and I can't "skip" so it's stuck. I tried Bad_Boyz fromXDA, and then going back to 5.1.1, and now forward again to 6.0 - same result. I suspect the WiFi mac address has been cleared. I found a little help that if I shell into the tablet, and write the mac address into /persist/wifi/.macaddr I might move forward. I know how to do this, but I can't shell in with adb. I can talk over USB, and run fastboot. When I connect via USB the Nexus mounts (sort of - the storage folder isn't shown when the tablet is at the "Select WiFi network" stage of setup)
When I run "adb devices" - I can't see any, even though I can "fastboot reboot recovery" and the like. I'm sure bluetooth (mac address) is broken too, but I"ll fix that later.
Does anyone have any idea how I can encourage adb to talk, so that I can "adb shell"?
I didn't want to hard reset it but in the end relented and loaded a clean new version of 6.0 from Google. When it restarts the second thing it wants to do, after selecting a language, is start the WiFi so it can log on. Of course WiFI won't start, and I can't "skip" so it's stuck. I tried Bad_Boyz fromXDA, and then going back to 5.1.1, and now forward again to 6.0 - same result. I suspect the WiFi mac address has been cleared. I found a little help that if I shell into the tablet, and write the mac address into /persist/wifi/.macaddr I might move forward. I know how to do this, but I can't shell in with adb. I can talk over USB, and run fastboot. When I connect via USB the Nexus mounts (sort of - the storage folder isn't shown when the tablet is at the "Select WiFi network" stage of setup)
When I run "adb devices" - I can't see any, even though I can "fastboot reboot recovery" and the like. I'm sure bluetooth (mac address) is broken too, but I"ll fix that later.
Does anyone have any idea how I can encourage adb to talk, so that I can "adb shell"?
No comments:
Post a Comment