Guyz as soon as i reboot folders created in /persist namely bluetooth n wifi gets deleted again n again .
what's the matter?
what's the matter?
Changed the name of the thread to draw more attention to those who facing this problem on lollipop
Reboot to Sytem.@bitdomo
During the procedure, you advise to "reboot your phone". Do we reboot phone into recovery mode like noted in the first instruction or just reboot letting it go to the standard homescreen?
I appreciate it! In hindsight, one can only execute that su command and "grant access on phone" from the system.....Reboot to Sytem.
avc: denied { read } for name="wpa_supplicant.conf" dev="mmcblk0p28" ino=318356 scontext=u:r:wpa:s0 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=1
----------- it's related with selinux . For a moment Wifi started working, HW addr for wlan0 was detected ( i had wlan0 and p2p in "ip link show" terminal command ). Will investigate more related with that.
I/wpa_supplicant( 3427): type=1400 audit(0.0:13): avc: denied { read } for name="wpa_supplicant.conf" dev="mmcblk0p28" ino=318356 scontext=u:r:wpa:s0 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=1
I/wpa_supplicant( 3427): type=1400 audit(0.0:14): avc: denied { open } for name="wpa_supplicant.conf" dev="mmcblk0p28" ino=318356 scontext=u:r:wpa:s0 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=1
I/wpa_supplicant( 3427): type=1400 audit(0.0:15): avc: denied { getattr } for path="/data/misc/wifi/wpa_supplicant.conf" dev="mmcblk0p28" ino=318356 scontext=u:r:wpa:s0 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=1
D/SoftapController( 190): Softap fwReload - Ok
W/CommandListener( 190): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 190): Setting iface cfg
E/WifiStateMachine( 770): Unable to change interface settings: java.lang.IllegalStateException: command '29 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 29 Failed to set address (No such device)'
E/WifiMonitor( 770): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
E/WifiMonitor( 770): startMonitor called with unknown iface=wlan0
The "wifi turning on" issue is not related to the persist partition. People who have corrupted persist can turn on the wifi and bluetooth just fine, but their mac address become random.I have Clockwork Recovery Touch on my Nexus 5. Will this work with that, or do I need to switch to TWRP or Philz recovery?
Also, what does the universal naked driver do? I can run commands from Windows through command prompt no problem.
The only issue I have is that after flying once and using airplane mode, WiFi is stuck turning on. I've tried just deleting the wifi folder, remaking it and adding the .macaddr file, but no success. I might go ahead and do the whole /persist fix this thread details, but I'd like to know if I need TWRP and universal naked driver. Any help would be awesome!
Oh okay. How do I fix the wifi turning on issue?The "wifi turning on" issue is not related to the persist partition. People who have corrupted persist can turn on the wifi and bluetooth just fine, but their mac address become random.
I wish I knew, but I dont any soultion for that.Oh okay. How do I fix the wifi turning on issue?
hey bitdomo, i just need some help i got stuck because when i typed the adb shell command instead the next line starting with ~# mine is ~#[6N so when i type e2fsck command it says not found, im using the TWRP recovery installed.. do you know how to fix this? thanksWhat 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:
then your persist partition have to be fixed.
- 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
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.