Wifi and bluetooth are not turning on - OnePlus 3T Questions & Answers

hello everyone, i have a problem with the wifi and bluetooth. My wifi mac address was shown as 02:00:00:00:00:00. wifi and bluetooth are not turning on. then i saw the files on the persist partition. some file was corrupted. so i wiped the persist partition (mke2fs command) and flashed 9.0.5 fw+modem and 9.0.5 full rom and now the corrupted files gone ( there is no file like wlan_mac.bin). mac address is shown as unknown.
can you help me for my problem? thank you and have nice day.

hajking said:
hello everyone, i have a problem with the wifi and bluetooth. My wifi mac address was shown as 02:00:00:00:00:00. wifi and bluetooth are not turning on. then i saw the files on the persist partition. some file was corrupted.
Click to expand...
Click to collapse
Which file was corrupted? What do you mean by corrupted? How did you tell?
hajking said:
so i wiped the persist partition (mke2fs command) and flashed 9.0.5 fw+modem and 9.0.5 full rom and now the corrupted files gone ( there is no file like wlan_mac.bin). mac address is shown as unknown.
can you help me for my problem? thank you and have nice day.
Click to expand...
Click to collapse
You need wlan_mac.bin in order to use wifi and bluetooth/.bt_nv.bin in order to run bt. If you don't have a backup of the persist partition, I'd give a try to the unbrick tool, though I'm not really sure if persist is restored...

nvertigo67 said:
Which file was corrupted? What do you mean by corrupted? How did you tell?
You need wlan_mac.bin in order to use wifi and bluetooth/.bt_nv.bin in order to run bt. If you don't have a backup of the persist partition, I'd give a try to the unbrick tool, though I'm not really sure if persist is restored...
Click to expand...
Click to collapse
i looked at the vendor and persist partitions and i saw that half of the data was writen in some files ( if normaly must be writen "bla bla bla", i saw "bla b"). i flash nougat via unbrick tool but no luck. may you send vendor and persist partitions backup? if you do, ill be happiest person.

hajking said:
i looked at the vendor and persist partitions and i saw that half of the data was writen in some files ( if normaly must be writen "bla bla bla", i saw "bla b"). i flash nougat via unbrick tool but no luck. may you send vendor and persist partitions backup? if you do, ill be happiest person.
Click to expand...
Click to collapse
Sent you a pm.
If you have an image file of the persist partition, eg /sdcard/sda2.img then you can write it using this command:
Code:
dd if=/sdcard/sda2.img of=/dev/block/sda2
Sent from my OnePlus 3T using XDA Labs

hajking said:
i looked at the vendor and persist partitions and i saw that half of the data was writen in some files ( if normaly must be writen "bla bla bla", i saw "bla b"). i flash nougat via unbrick tool but no luck. may you send vendor and persist partitions backup? if you do, ill be happiest person.
Click to expand...
Click to collapse
If the unbrick tool doesn't restore the persist partition, it's most probably because it's individualy (like efs) and not interchangeble between devices (makes sense for hw addresses!).
BTW: op3/t does not ship with vendor partion. /vendor is a symlink to /system/vendor. If you say files on the vendor partition were corrupted, the system partition is corrupted. Since system is mounted rw, there's a probability the hw is broken.
Perhaps, the best choice is to get your device RMAed to omeplus.
@BillGoss: this
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "cat /mnt/vendor/persist/wlan_mac.bin"
Intf0MacAddress=C0EEFBEF26C0
Intf1MacAddress=C2EEFBEF26C0
Intf3MacAddress=000AF58989FD
Intf4MacAddress=000AF58989FC
END
[email protected] /usr/local/src/oxygenos $
is my device's wlan_mac.bin. Is it different from yours? If not, I maybe wrong, and it is possible to interchange persist partitions.

nvertigo67 said:
@BillGoss: this
is my device's wlan_mac.bin. Is it different from yours? If not, I maybe wrong, and it is possible to interchange persist partitions.
Click to expand...
Click to collapse
Oops!
I didn't know you could do that. The cat command shows my phone's MAC address. I did a search of the persist partition for the address but searched for the hex value instead of the string, so I didn't see it.
My bad!
Sorry, @hajking, so don't use the file I shared with you.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Oops!
I didn't know you could do that. The cat command shows my phone's MAC address. I did a search of the persist partition for the address but searched for the hex value instead of the string, so I didn't see it.
My bad!
Sorry, @hajking, so don't use the file I shared with you.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I was surprised, too. I havn't expected this from a file ending on .bin:
Code:
adb shell su -c "file /mnt/vendor/persist/wlan_mac.bin"
/mnt/vendor/persist/wlan_mac.bin: ASCII text
Anyway, comparing the content of wlan_mac.bin seemed the easiest way to me to check weather persist is unique (like efs), or not.
Lesson learned: always keep a bakup of efs and persist partion - efs alone isn't sufficient...

I had problems with sensors (accidently deleted sensors dir from persist partition), its different issue then yours but it has one in common, the persist partition - it contains sensors calibration, wifi and bt hw address.
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.

nvertigo67 said:
If the unbrick tool doesn't restore the persist partition, it's most probably because it's individualy (like efs) and not interchangeble between devices (makes sense for hw addresses!).
BTW: op3/t does not ship with vendor partion. /vendor is a symlink to /system/vendor. If you say files on the vendor partition were corrupted, the system partition is corrupted. Since system is mounted rw, there's a probability the hw is broken.
Perhaps, the best choice is to get your device RMAed to omeplus.
@BillGoss: this
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "cat /mnt/vendor/persist/wlan_mac.bin"
Intf0MacAddress=C0EEFBEF26C0
Intf1MacAddress=C2EEFBEF26C0
Intf3MacAddress=000AF58989FD
Intf4MacAddress=000AF58989FC
END
[email protected] /usr/local/src/oxygenos $
is my device's wlan_mac.bin. Is it different from yours? If not, I maybe wrong, and it is possible to interchange persist partitions.
Click to expand...
Click to collapse
dude im sorry but there is no wlan_mac.bin now. i wiped the partition using mke2fs and it gone. thats why i need a backup of persist. i you send me via pm ill change the address after restore.

ppajdek said:
I had problems with sensors (accidently deleted sensors dir from persist partition), its different issue then yours but it has one in common, the persist partition - it contains sensors calibration, wifi and bt hw address.
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.
Click to expand...
Click to collapse
thanx dude ill try tonight. ?

hajking said:
dude im sorry but there is no wlan_mac.bin now. i wiped the partition using mke2fs and it gone. thats why i need a backup of persist. i you send me via pm ill change the address after restore.
Click to expand...
Click to collapse
No.
We've just proofed by the wifi mac addresses, that the persist partitions are unique for each device. We havn't proofed, that the wlan mac address is the only difference. In deed I'm pretty sure, that bluetooth/.bt_nv.bin is different, too.
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "file /mnt/vendor/persist/bluetooth/.bt_nv.bin"
/mnt/vendor/persist/bluetooth/.bt_nv.bin: data
[email protected] /usr/local/src/oxygenos $ adb shell su -c "strings /mnt/vendor/persist/bluetooth/.bt_nv.bin"
[email protected] /usr/local/src/oxygenos $
As you can see, bluetooth/.bt_nv.bin is really a binary file, and you can't change the address like in wlan_mac.bin.
If https://forum.xda-developers.com/showpost.php?p=80704325&postcount=8 isn't working for you, either, your last resort is rmaing the device.

nvertigo67 said:
No.
We've just proofed by the wifi mac addresses, that the persist partitions are unique for each device. We havn't proofed, that the wlan mac address is the only difference. In deed I'm pretty sure, that bluetooth/.bt_nv.bin is different, too.
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "file /mnt/vendor/persist/bluetooth/.bt_nv.bin"
/mnt/vendor/persist/bluetooth/.bt_nv.bin: data
[email protected] /usr/local/src/oxygenos $ adb shell su -c "strings /mnt/vendor/persist/bluetooth/.bt_nv.bin"
[email protected] /usr/local/src/oxygenos $
As you can see, bluetooth/.bt_nv.bin is really a binary file, and you can't change the address like in wlan_mac.bin.
If https://forum.xda-developers.com/showpost.php?p=80704325&postcount=8 isn't working for you, either, your last resort is rmaing the device.
Click to expand...
Click to collapse
so it seems unbrick tool is the only way. thanx guys.

hajking said:
so it seems unbrick tool is the only way. thanx guys.
Click to expand...
Click to collapse
No. If that fails you can rma the device. As already stated, I strongly recommend to rma the device, because broken hw is the most probable reason for the coruppted files.

hajking said:
...
@BillGoss: this
dude im sorry but there is no wlan_mac.bin now. i wiped the partition using mke2fs and it gone. thats why i need a backup of persist. i you send me via pm ill change the address after restore.
Click to expand...
Click to collapse
Sent you another pm
Sent from my OnePlus 3T using XDA Labs

nvertigo67 said:
No. If that fails you can rma the device. As already stated, I strongly recommend to rma the device, because broken hw is the most probable reason for the coruppted files.
Click to expand...
Click to collapse
i beg your indulgence. what is rma?
oh i understand but i cannot rma the device because ive bought a used op3t and the seller is not answering to my calls. so i have to fix that issue.

hajking said:
i beg your indulgence. what is rma?
oh i understand but i cannot rma the device because ive bought a used op3t and the seller is not answering to my calls. so i have to fix that issue.
Click to expand...
Click to collapse
Crossing my fingers you can fix it. Crossing my fingers you havn't been sold a broken, stolen or otherwise compromised device!!!
A friend of mine has bought (without his knowledge) a stolen and broken device on ebay. When rmaing it, some days later the prosecuting attorney wants to talk... If buying used devices, always get the original shipping, warranty and invoice documents! As always: easy to claim - afterwards!
Good luck!

Related

P970 Noob Flash with No Backup and now no IMEI & Network

I am really hoping someone can help me sort this problem. I recently bought a LG P970, and after long await from customs, i received it! On day 1 before even purchasing a simcard i rooted and changed roms. I went through all sorts of roms from nightly cm7 to cm10, nove, aokp etc.. I finally decided i like AOKP Rom and day 2 bought my sim card. SUPRIZE!! no network! IMEI unknown. Unfortunately i was to ignorant to do a backup and i have been searching for +- 40hours now to try resolve this issue.
I have tried the tutty/Hyperterminal.. Does not work! If i dial 3845#*970# and access the hidden menu. as soon as i select CP USB, the pc just makes the insert/ takeout sound constantly and does not install driver, but on AP USB, the sd card can be accessed, my device shows on system and everything is 100%. I have tried this on 2 windows 7 computers. So that option is out.
Does anyone know another way to restore the IMEI? I dont have any fancy box tools, just my pc.
jugz54 said:
I am really hoping someone can help me sort this problem. I recently bought a LG P970, and after long await from customs, i received it! On day 1 before even purchasing a simcard i rooted and changed roms. I went through all sorts of roms from nightly cm7 to cm10, nove, aokp etc.. I finally decided i like AOKP Rom and day 2 bought my sim card. SUPRIZE!! no network! IMEI unknown. Unfortunately i was to ignorant to do a backup and i have been searching for +- 40hours now to try resolve this issue.
I have tried the tutty/Hyperterminal.. Does not work! If i dial 3845#*970# and access the hidden menu. as soon as i select CP USB, the pc just makes the insert/ takeout sound constantly and does not install driver, but on AP USB, the sd card can be accessed, my device shows on system and everything is 100%. I have tried this on 2 windows 7 computers. So that option is out.
Does anyone know another way to restore the IMEI? I dont have any fancy box tools, just my pc.
Click to expand...
Click to collapse
The AOKP hasn't been updated in a while and has more bugs than CM10 and V30 repacks.
When did this start? You can only wipe IMEI if you select "Wipe Entire AP" or something like that on SFT. Does the problem persist on other ROMs? Also no network connection isn't related to IMEI, more likely ROM related.
If your really desperate you can extract your nv partition and hex edit your IMEI in and push back to device. All you need is microusb to usb cable and computer (and a hex editor, but thats free to download ), but I will only do this as a last resort.
xonar_ said:
The AOKP hasn't been updated in a while and has more bugs than CM10 and V30 repacks.
When did this start? You can only wipe IMEI if you select "Wipe Entire AP" or something like that on SFT. Does the problem persist on other ROMs? Also no network connection isn't related to IMEI, more likely ROM related.
If your really desperate you can extract your nv partition and hex edit your IMEI in and push back to device. All you need is microusb to usb cable and computer (and a hex editor, but thats free to download ), but I will only do this as a last resort.
Click to expand...
Click to collapse
Thanks for you reply,
When i bought the phone, before i put in a simcard, i ended up flashing and changing roms, so the next day i bought a sim and there was no network, did research and found out that my IMEI is missing. if i type *#06# then is just says IMEI and no number. I have flashed back to original rom but still no luck. I have tried many things on youtube but nothing works, i tried the tutty to try restore an IMEI but doesn't work,
What do you suggest i do? and is there a step by step guide to resolving this?
jugz54 said:
Thanks for you reply,
When i bought the phone, before i put in a simcard, i ended up flashing and changing roms, so the next day i bought a sim and there was no network, did research and found out that my IMEI is missing. if i type *#06# then is just says IMEI and no number. I have flashed back to original rom but still no luck. I have tried many things on youtube but nothing works, i tried the tutty to try restore an IMEI but doesn't work,
What do you suggest i do? and is there a step by step guide to resolving this?
Click to expand...
Click to collapse
This will only work with the P970
Use adb shell from your computer or use a app like terminal emulator.
Code:
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
where $IMEI is you IMEI
The large bold print is for people that can't read headings that might run this and brick their devices.
Something I learned that isn't mentioned on the forum is that its important to backup your nv partition since that contains info that can't be retrieved after damaging it and nothing backs it up for you. Like MAC addresses, your IMEI etc.
On you computor
Backup using
Code:
adb pull /dev/block/mmcblk0p11 nv.img
Restore using
Code:
adb push nv.img /dev/block/mmcblk0p11
EDIT: Added notrunc to not truncate the rest of the partition
xonar_ said:
Use adb shell from your computer or use a app like terminal emulator.
Code:
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
where $IMEI is you IMEI
Click to expand...
Click to collapse
Hey, Thanks for getting back to me. I tried the command on Terminal Emulator and it says IMEI not found and conv disabled. Any suggestion?
Did you try the official LG Mobile Update Tool?
There is emergancy and recovery mod where you can fix it.
sbdemir said:
Did you try the official LG Mobile Update Tool?
There is emergancy and recovery mod where you can fix it.
Click to expand...
Click to collapse
I tried the LGMobile Support Tool various times. The recovery module does not work, if i type IMEI adn select check phone, nothing happens. The strange thing is the support tool picks up my phone model as LGKU5900 version V10I. That could have happened with me trying to repair the phone with various programs and youtube videos.
I have tried uninstalling and reinstalling the support tool as well as the drivers but still no luck.... I reflashed the original rom V10F with no patch etc.. but still the Support tool picks up the model as LGKU5900, and when i select update phone, it downloads the update and during installing of update it stays on 6% for roughly 20 minutes then just stops. I have tried this numerous times and same things happens everytime.
If this is of interest to you to, you can take control of my system and check it out via team viewer.
jugz54 said:
Hey, Thanks for getting back to me. I tried the command on Terminal Emulator and it says IMEI not found and conv disabled. Any suggestion?
Click to expand...
Click to collapse
rather try this. included dd might not be up to standard
Code:
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
and replace $IMEI with your IMEI.
EDIT: The above should repair your IMEI, but if SFT fails to update your phone then it's wrong firmware or HW problem and it will cause problems elsewhere aswel.
xonar_ said:
rather try this. included dd might not be up to standard
Code:
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
and replace $IMEI with your IMEI.
EDIT: The above should repair your IMEI, but if SFT fails to update your phone then it's wrong firmware or HW problem and it will cause problems elsewhere aswel.
Click to expand...
Click to collapse
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
jugz54 said:
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
Click to expand...
Click to collapse
dd should be included in busybox. What busybox are you using?
The conv=notrunc just tells it not to truncate the rest of the file (in this case don't truncate the rest of the nv partition)
the echo pipes the IMEI to dd which writes it to /dev/block/mmcblk0p11 (your nv partition) on two different spots. I
You need su permissions to write to /dev/block/mmcblk0p11. I forgot to mention that. Otherwise dd will fail and the included binutils dd doesn't always list error messages. Just terminates silently without doing anything most of the time.
You can also try reflashing just the baseband. (The fls file with SFT)
If all that doesn't work then you need to take it into repairs.
jugz54 said:
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
Click to expand...
Click to collapse
I don't have a solution to your problem however I am in a similar situation. I purchased my Optimus Black from an ebay seller located in Hong Kong, it was advertised as an Optimus Black P970. The software version was similar to yours, outdated, so I grabbed a stable gingerbread version patched it with root etc. and flashed.
Upon reboot I had no cellular network, tried two different sims/networks. No Joy. Further troubleshooting uncovered the loss of the imei. I came across this thread and decided to give it a try, it didn't work. I suspect I messed up the command, in my case this was lucky because I was able to see the content of the mmcblk0p11 file using a hex editor. The imei is in there, and it is also in the same location as my Optimus Black P970, I assume it is stored elsewhere as well....
Long and short of this is you and I have purchased the KU5900, the Korean version not the P970, flashing with P970 firmware is what has messed the phones up.
Note. I did try flashing with the only Korean version that was available to me, a V30 something, that bricked the device. It is now unbricked but still shows no imei. I haven't given up but wading through reams of forum posts trying to get info on this is daunting ... My seller has agreed to replace the phone, but I fear I will end up with another KU5900 which isn't any good to me unless I can upgrade the firmware.
had the same problem recently..got it fixed because of this...
http://forum.xda-developers.com/showthread.php?t=2107419
IAP001 said:
had the same problem recently..got it fixed because of this...
http://forum.xda-developers.com/showthread.php?t=2107419
Click to expand...
Click to collapse
I just fixed one P970 with unknown IMEI by flashing it with Octopus box, I think that you can solve it by flashing with original flash file using SFT.
Best Regards.
Hi....few days back, I had the same problem....After flashing my phone to V30B(CIS version) which was not available for my phone in my country India, the IMEI then got removed automatically(*#06#- shows IMEI not available), then I installed the latest version V20G which was available for my country then (through smartflash tool) and then got back the IMEI. Try installing the latest version available for your country and do let us know if that solve your problem. Best of luck
Sent from my LG-P970 using xda app-developers app
sunnygunjesh said:
Hi....few days back, I had the same problem....After flashing my phone to V30B(CIS version) which was not available for my phone in my country India, the IMEI then got removed automatically(*#06#- shows IMEI not available), then I installed the latest version V20G which was available for my country then (through smartflash tool) and then got back the IMEI. Try installing the latest version available for your country and do let us know if that solve your problem. Best of luck
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
i had similar problem when installing cm10 rom and cici rom, after flashing those roms my device had no IMEI and no network, it didnt even rcognize my contacs in sim card. the strange part is that i was able to make calls, but when i flashed back to the rom i had, everything was back and looking good.
i had marvel v9 rom thats runs pretty good.

[GUIDE][FIX] Boot loop on Lollipop 5.0 and above (fix persist partition)

What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
Can't access to internal storage.
No signal even after formating cache and fastboot flash cache.img
IMEI number is lost even after formating cache and fastboot flash cache.img
Boot loop on Lollipop 5.0 and above
You get "e: cannot mount /persist" in recovery
then your persist partition have to be fixed.
Requirements to proceed:
Ability to use adb command.
TWRP or Philz touch recovery.
Universal Naked Driver for recovery. (Windows users)
Root.
Setting up adb, rooting and installing drivers are not part of this guide. If you have to do that then please use @rootSU's great thread to find the guides you need.
Let's start!
Reboot your phone to recovery.
Connect USB cable.
Open CMD or Terminal application.
Enter following commands in CMD or Terminal application:
adb shell
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
Click to expand...
Click to collapse
You should be prompted to repair or fix errors. Keep pressing enter until the process finishes.
If you are not prompted for repair or you still have problems then follow my instructions.
Get to that point again when you entered the adb shell command then type the following command:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Click to expand...
Click to collapse
Reboot your phone.
Now all your problems should be gone now, but your wifi and bluetooth addresses should be fixed to prevent further problems or bugs.
Download this rar file.
Extract it.
(Linux users should enable show hidden files)
Open .bdaddr with a hexeditor.
You should see following:
BC F5 AC 00 00 00
Click to expand...
Click to collapse
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .bdaddr.
Open .macaddr with a hexeditor.
You should see the following:
8C 3A E3 00 00 00
Click to expand...
Click to collapse
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .macaddr.
Copy both files to your sdcard.
Enable USB debugging on the phone.
Open CMD or Terminal application. (If you closed it)
Enter following commands in CMD or Terminal application:
adb shell
su
Click to expand...
Click to collapse
Grant access on the phone.
cd /persist
mkdir bluetooth wifi
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
cp /sdcard/.bdaddr /persist/bluetooth
chown bluetooth:system ./bluetooth/.bdaddr
chmod 660 ./bluetooth/.bdaddr
chown wifi:system ./wifi
chmod 770 ./wifi
cp /sdcard/.macaddr /persist/wifi
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Click to expand...
Click to collapse
Reboot your phone. All your problems should have gone now. You can delete .bdaddr and .macaddr from your sdcard.
About the other files:
SNS.reg will be regenrated, but the DRM releated files will not. Nobody ever complained about the missing DRM files, but I still want to make it possible to restore them. If anyone could make an md5 checksum about the files on the persist partition that would be great.
Great thread @bitdomo. Thanks for adding this to the forum. I added it to the root guides section of sticky roll-up
Sent from my Nexus 5 using Tapatalk
Nice job! ?
This should be very helpful, well done!
I keep getting not found when i enter that comand in cmd.
Great thread. Didn't even know about such a partition to be honest.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Juniluis said:
I keep getting not found when i enter that comand in cmd.
Click to expand...
Click to collapse
Have you added adb to your PATH?
Sent from my Nexus 5 using Tapatalk
Man your a life saver thank you so much I just copy your and I stop typing because I was typing something bad.
One question the Mac address WiFi and Bluetooth steps in hex editor only the ones that had problem with the first qoute ta was ef2sck .....etc and needed to go to the second quote that was make ef4 ..,.etc need to do it right?
bitdomo said:
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
Can't access to internal storage.
No signal even after formating cache and fastboot flash cache.img
IMEI number is lost even after formating cache and fastboot flash cache.img
You get "e: cannot mount /persist" in recovery
then your persist partition have to be fixed.
Requirements to proceed:
Ability to use adb command.
TWRP or Philz touch recovery.
Universal Naked Driver for recovery. (Windows users)
Root.
Setting up adb, rooting and installing drivers are not part of this guide. If you have to do that then please use @rootSU's great thread to find the guides you need.
Let's start!
Reboot your phone to recovery.
Connect USB cable.
Open CMD or Terminal application.
Enter following commands in CMD or Terminal application:
You should be prompted to repair or fix errors. Keep pressing enter until the process finishes.
If you are not prompted for repair or you still have problems then follow my instructions.
Get to that point again when you entered the adb shell command then type the following command:
Reboot your phone.
Now all your problems should be gone now, but your wifi and bluetooth addresses should be fixed to prevent further problems or bugs.
Download this rar file.
Extract it.
(Linux users should enable show hidden files)
Open .bdaddr with a hexeditor.
You should see following:
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .bdaddr.
Open .macaddr with a hexeditor.
You should see the following:
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .macaddr.
Copy both files to your sdcard.
Enable USB debugging on the phone.
Open CMD or Terminal application. (If you closed it)
Enter following commands in CMD or Terminal application:
Grant access on the phone.
Reboot your phone. All your problems should have gone now. You can delete .bdaddr and .macaddr from your sdcard.
About the other files:
SNS.reg will be regenrated, but the DRM releated files will not. Nobody ever complained about the missing DRM files, but I still want to make it possible to restore them. If anyone could make an md5 checksum about the files on the persist partition that would be great.
Click to expand...
Click to collapse
I have a big problem: when I enter "e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist", it says that the journal has data and can't set superblocks, and when I enter "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist" the problem persist..:crying:
thaaaaaaaaaanks the phone is work O_O
I need a professional guy help
rootSU said:
Great thread @bitdomo. Thanks for adding this to the forum. I added it to the root guides section of sticky roll-up
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im really stuck on the starting adb and fastboot is their any guy to whom should i show this nexus 5 imei gone. storage corrupt and baseband null even camera is also not working.
i live in pak please prefer a guy who can resolve my problem
Thanks
I registered in the forum to thank you @bitdomo ! My Nexus 5 lost signal a few weeks ago and I did EVERYTHING. Started with trying to add apn stuff manually, then in-android factory reset, wipes, then stock flash, a few more flashes, and I started to go crazy. My IMEI was lost. But this got it back! Thank you very much!
The same thing here! Thanx a lot,bitdomo!
faizanfarooq86 said:
im really stuck on the starting adb and fastboot is their any guy to whom should i show this nexus 5 imei gone. storage corrupt and baseband null even camera is also not working.
i live in pak please prefer a guy who can resolve my problem
Thanks
Click to expand...
Click to collapse
Did you try any of the suggested guides/links by rootSU in the OP? The required information on getting ADB/fastboot working correctly is all there, see link http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Thank you very much! This helped me a lot.
The best way is to flash factory images.
I had this issue in the morning and solved it in no time.
Goodluck
DaGr81 said:
The best way is to flash factory images.
I had this issue in the morning and solved it in no time.
Goodluck
Click to expand...
Click to collapse
This issue won't be solved by flashing factory images. Hence the thread.
Thanks!!!!!!!!
I love my Nexus 5. This did the trick. I did have to flash-all at the end because I screwed it up too much while trying to fix it.
By the way the symptom I was experience was the phone was in a endless forever loop on the boot and I was seeing the color dots animation for a couple days.
Don't copy the whole OP page to ask a simple question please #swag
Sent from my Nexus 5
Guys can this only be done in adb? My nexus 5 is in a bootloop, tried reflashing stock. Still the same. I can get into bootloader, tried going in recovery but it just bootloops after that. Help please. Thought it was the power button. Replaced but still the same

XT1092 radio

Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
if you can tell me how to extract i will do it for you.
and, if you can help me, i need the system image of the build kxe21.187-42. should be yours as well.
i made another mistake with the messaging app, and now i have to reset all my moto x XT1092 (european)
Andariel636 said:
if you can tell me how to extract i will do it for you.
and, if you can help me, i need the system image of the build kxe21.187-42. should be yours as well.
i made another mistake with the messaging app, and now i have to reset all my moto x XT1092 (european)
Click to expand...
Click to collapse
You have to have USB Debugging enabled, then check adb for your device, type the following:
1. adb shell
2. su
2.1 Grant su permission on your phone
3. dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
4. Choose a file explorer you like and grab the modem from the sd card. its probably in /sdcard. +
If you could do that, i would be SOOOOOOOOOOOOO thankful. I dont have the System Image, i could give you a nandroid backup though
Tomorrow i try this. Is possible to do this only with titanium backup?
Otherwise i have to find a windows pc, i have only a macbook.
Radixtrator said:
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
Click to expand...
Click to collapse
Hi my friend!
Don't know if this help, but try to extract from the sbf image or reinstall the entire rom again.
Try this link:
http://sbf.droid-developers.org/phone.php?device=37
Sent from my XT1097 using XDA Premium HD app
Radixtrator said:
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
Click to expand...
Click to collapse
Here you go, had to put it in a folder (but extract, it's not flashable), hope it helps.
Andariel636 said:
Tomorrow i try this. Is possible to do this only with titanium backup?
Otherwise i have to find a windows pc, i have only a macbook.
Click to expand...
Click to collapse
If you have adb installed on your macbook, you can do this from the terminal
fnut6969 said:
Here you go, had to put it in a folder (but extract, it's not flashable), hope it helps.
Click to expand...
Click to collapse
Sadly it didnt.. Your phone was an US phone correct? It stil shows no Sim no reception.. IMEI is gone too from the info screen
Could you try doing this for me ?
su (press Return)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return)
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)
I remember my script deleted thos, and maybe that will do the trick
Radixtrator,
What exactly you flashed as wrong radio: NON-HLOS.bin ? fsg.mbn? Both ? Please explain in more details.
And how you flashed modem file, provided by fnut6969?
Radixtrator said:
You have to have USB Debugging enabled, then check adb for your device, type the following:
1. adb shell
2. su
2.1 Grant su permission on your phone
3. dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
4. Choose a file explorer you like and grab the modem from the sd card. its probably in /sdcard. +
If you could do that, i would be SOOOOOOOOOOOOO thankful. I dont have the System Image, i could give you a nandroid backup though
Click to expand...
Click to collapse
Here it is!
a nandroid backup shuld be usefull? or i can use it to extract only the messaging app?
Radixtrator said:
If you have adb installed on your macbook, you can do this from the terminal
Sadly it didnt.. Your phone was an US phone correct? It stil shows no Sim no reception.. IMEI is gone too from the info screen
Could you try doing this for me ?
su (press Return)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return)
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)
I remember my script deleted thos, and maybe that will do the trick
Click to expand...
Click to collapse
My apologies, I now notice you were looking for the XT1092 modem, I guess that shows how important it is to actually read posts thoroughly.
fnut6969 said:
My apologies, I now notice you were looking for the XT1092 modem, I guess that shows how important it is to actually read posts thoroughly.
Click to expand...
Click to collapse
No problem
Radixtrator said:
Hi Guys, I flashed a wrong radio by accident, could someone be so nice to extract his radio from a XT1092 and send it to me? Theres a beer in it for you
Click to expand...
Click to collapse
I thought the factory images where available on the motorola site but I see now that they aren't. Maybe you can tell me how to create a system dump to return to stock (I have an xt1092)
godutch said:
I thought the factory images where available on the motorola site but I see now that they aren't. Maybe you can tell me how to create a system dump to return to stock (I have an xt1092)
Click to expand...
Click to collapse
The absolutely most awesome thing you could do is give me a Full Nandroid Backup ( without data) especially including the EFS Partition, because i believe thats whats wrong with my phone... That would be incredibly awesome
I don't want to unluck just yet. I didn't even know btw moto has an efs partition too, I can't see it
godutch said:
I don't want to unluck just yet. I didn't even know btw moto has an efs partition too, I can't see it
Click to expand...
Click to collapse
In twrp you can definitely select EFS as a backup able partition
Radixtrator said:
In twrp you can definitely select EFS as a backup able partition
Click to expand...
Click to collapse
I can't boot twrp witp a locked bootloader and I am sorry but I don't want to publish my efs, my imei might get blocked but I can try to make a system dump
i did find this thread http://forum.xda-developers.com/showthread.php?t=1960918
or this one:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
godutch said:
i did find this thread http://forum.xda-developers.com/showthread.php?t=1960918
or this one:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
Click to expand...
Click to collapse
Well the fella in the first link seemed to have fixed it by flashing the Original Firmware...
The Problem is, there is no german firmware ANYwhere on the Internet.
Radixtrator said:
Well the fella in the first link seemed to have fixed it by flashing the Original Firmware...
The Problem is, there is no german firmware ANYwhere on the Internet.
Click to expand...
Click to collapse
Well one suggestion is to factory reset without the sim and set up the phone with no sim. It won't hurt to try

/sdcard problems after upgrading Android

I'm seeing a few posts and qquestions about this with the latest Lollipop release being upon us.
There are several issues here and I wanted to write a quick note aboyut them both for you
1) You cannot SEE your /sdcard data after updating to lollipop
Cause:
Some strange difference between L and KK, where /storage/emulated and /data/media are not "alligned"
Fix:
Open a terminal emulator application and enter the following 2 line command (Press enter after each line)
Code:
su
restorecon -FR /data/media/0
Reboot
2) You have lost permissions to /sdcard
Cause:
You restored all your sdcard data using adb push or MTP whilst booted into recovery. IT screws up your permissions. These methods are fine for single files or backups that you waant to flash or restore, but as soon as you start pushing folders, this issue will be seen
Fix:
In a root explorer app, browse to /data/media/0 and locate your Download folder. Set the permissions for all on Download to read / write (Long press the Download folder > permissions)
Download and flash THIS ZIP from the thread below.
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] (by @osm0sis)
You can also download the zip to a computer and adb push it / MTP via recovery
3) 32 GB device shows the storage of 16 GB version
Cause:
Unknown. This has actually been happening since the Nexus 5 was released
Fix:
Wipe cache and data
4) TWRP backups are missing
Cause:
This is really unknown. We're not even sure that this can be fixed. Some say its a TWRP bug but that cannot be proven.
Sometimes backup folder is empty....
Fix:
Multiple things you can try. Some have to use restorecon command but usually that has to be done after every backup.
Others have just flashed the factory images
Some of us have never had issues so its hard to call it a bug, but there is definitely something funky going on here.
Other times, backups shows as an unknown file type, 0bytes in size. I haven't a specific fix as I have had no feedback from anyone who has fixed it. You could try deleting that unknown file then running the fix above.
Also, please update to TWRP 2.8.3.0
5) All I see in /sdcard is 0 folder
Cause:
Well known issue on /data/media/0 devices - which is the location of the /sdcard. Unsure of the cause on Nexus 5 though
Fix:
/sdcard is in /data/media/0. If you see a 0 folder in /sdcard, you're actually seeing /data/media/0/0.
To fix, just move /data/media/0/0/* to /data/media/0
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
alen1901 said:
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
Click to expand...
Click to collapse
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
I have used always Mixplorer and now after flashing 5.0 I cant see nothing under /root. Why so? Something with root permissions? everything else is ok. ( I want to modify build.prop a little )
do I need use some other file explorer?
restorecon -FR /data/media/0 fixed a problem I had with a bad TWRP folder on my Nexus 10 - many thanks!
rootSU said:
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
Click to expand...
Click to collapse
I restored everything except data and android folders back to sdcard, i even restored obb files and no problems at all. It is the best practice for users to restore only their data, not the ones android creates itself. Im sure most people just selects everything and transfer to pc/stick, then copy everything back.
Sent from Pure Nexus 5
Thanks dude. I wish I had this information this morning - would've saved me a lot of sweat.
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
vnvman said:
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
Click to expand...
Click to collapse
Yeah that's a different but common issue.
Thank you, rootSU. This fixed my issue.
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
rizhqrd said:
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
Click to expand...
Click to collapse
Move them manually.
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
tomp100 said:
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
Click to expand...
Click to collapse
Please explain your issue.
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
~ # restorecon -FR /data/media/0/
restorecon: invalid option -- F
Click to expand...
Click to collapse
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
-F
Force reset of context to match file_context for customizable files, and the default file context, changing the user, role, range portion as well as the type.
Click to expand...
Click to collapse
RVDigital said:
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
Click to expand...
Click to collapse
Not sure but glancing at the Dev preview thread, some had success with this:
restorecon -r /data/media/0/*
Tried both, all that happened is that /sdcard is now blank. /data/media/0 still lists all of the files, but /sdcard itself is empty or unlinked or something. I unfortunately don't know which of the two steps did it.
Quick question, I'm currently on slimkat and plan on clean flashing tonight via bigxies ROM. With this method of fixing the SD card, I won't lose all my data as far as downloads, pictures, etc.?
rootSU said:
Please explain your issue.
Click to expand...
Click to collapse
Essentially, the phone doesn't think it has an SD card. When i click on SD card in root browser, it is empty. Items that were on the SD card in 4.4.4 are now located in data/media/0/0 , and I am unable to move these items to SD. Also, if I try to dowload sonething off the internet, I get a "no SD card" message.
I can confirm that my issues were caused by importing my backed up /SDCard/ data via an "adb push" while in recovery.
If doing the same while the phone is booted into system, permissions are set appropriately and no further action is required.
Thanks again for this post!

Wifi Keeps turning on but never turn on (MAC address shows 20:00:00:00:00:00)

I have problem with WIFI keeps turning on but it never turn on like usual, i tried flash stock rom neswest build and do factory reset it with no luck.
Searching around internet and found that there are some Nexus5 user can fix it by delete folder of mac address (they said it is in /persist/wifi folder) buti cant find that folder in my Marshmallow. Anyone knows how to fix this i think it is something wrong with corrupted MAC address it quite weird that my MAC Address is 20:00:00:00:00:00
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
pradipsoman said:
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
Click to expand...
Click to collapse
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Droidphilev said:
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
Click to expand...
Click to collapse
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
pradipsoman said:
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
Click to expand...
Click to collapse
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Droidphilev said:
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Click to expand...
Click to collapse
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
pradipsoman said:
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
Click to expand...
Click to collapse
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Droidphilev said:
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Click to expand...
Click to collapse
Could it be related to the /persist folder
pradipsoman said:
Could it be related to the /persist folder
Click to expand...
Click to collapse
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Droidphilev said:
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Click to expand...
Click to collapse
I was on 5.1.1 and then everything was working fine...I installed the 6.0 OTA and then this happened....
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
pradipsoman said:
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
Click to expand...
Click to collapse
the unbrick thing or the persist thing?
you guys do realize that google is using the wifi to figure out your location, right? even if you never ever turn wifi on. you have to disable scanning in the location settings for google not to use the wifi.
none
If you had a hard bricked device you would know it because your phone would have a black screen and you would have a paperweight
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
pradipsoman said:
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
Click to expand...
Click to collapse
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
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.
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...
Not working..
toastgodsupreme said:
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
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.
Click to expand...
Click to collapse
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
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?
pradipsoman said:
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
Click to expand...
Click to collapse
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...

Categories

Resources