Hi. Me and many other people are experimenting issues with wifi/bluetooth.
I've upgraded/downloaded to almost any possible rom and the problem is still here
Looking on forums found that is a very common issue since marshmallow in many devices (Specially Nexus)
Most people couldn't fix it but some could.
the problem is with devices macaddress that shown 02:00:00:00:00:00 and get stuck turning on
there are solutions in forums that seems to be a little bizarre like drain battery to 0 and full recharge (This one works for me once)
and others.
But I found one for nexus 5 who replaces the full /persist partition with a dump and edit the files and permissions with macaddress information.
This seems to have logic and provides an explanation about why the problem persist after, factory reset or rom changing so I want to try it in nexus 6.
Could someone provide me a dump of it?
There is an app: http://ift.tt/1E4nTO5, that makes the process of making a partition backup easy. The persist partition is on /dev/block/mmcblk0p26
Thanks in advance
I've upgraded/downloaded to almost any possible rom and the problem is still here
Looking on forums found that is a very common issue since marshmallow in many devices (Specially Nexus)
Most people couldn't fix it but some could.
the problem is with devices macaddress that shown 02:00:00:00:00:00 and get stuck turning on
there are solutions in forums that seems to be a little bizarre like drain battery to 0 and full recharge (This one works for me once)
and others.
But I found one for nexus 5 who replaces the full /persist partition with a dump and edit the files and permissions with macaddress information.
This seems to have logic and provides an explanation about why the problem persist after, factory reset or rom changing so I want to try it in nexus 6.
Could someone provide me a dump of it?
There is an app: http://ift.tt/1E4nTO5, that makes the process of making a partition backup easy. The persist partition is on /dev/block/mmcblk0p26
Thanks in advance
from xda-developers http://ift.tt/1pZLzx0
via IFTTT
Aucun commentaire:
Enregistrer un commentaire