Wifi password lost on shutdown/reset - General Questions and Answers

Hi,
I have been trying to troubleshoot this problem for some time. The basic problem is that every time the device is shutdown/reset the existing wifi data including known hotspots and passwords is lost.
I have tried factory resetting the tablet (Samsung Note 10.1 SM-T520), along with flashing various stock 4.4.2 Roms (i.e. different release dates and different countries). The tablet was purchased in the US and gifted to my mum in New Zealand, it originally had a stock US rom and now has the NZ rom loaded. Unfortunately Samsung's warranty required us to ship the tablet back to the US to investigate the problem (they would not look at it in NZ as it was not from NZ).
Based on some other threads, I thought it was a problem with the wpa_supplicant.conf file. So I rooted the phone using CF root through odin. I have looked at the wpa_supplicant.conf file and noticed that every time the device is shutdown/reset the
Code:
network={
}
section is removed.
When the device is turned on and I enter the network password the wpa_supplicant.conf file will be updated with the network information and as I said when shutdown this information is removed.
The wpa_supplicant has read/write privilages and user is set to system and group is set to wifi (I did not change these), this is the same for the wpa_supplicant.bak.conf which is created on reboot/shutdown (the bak file doesn't keep the network data on reset either)
In the data/misc/wifi/sockets folder (which the wpa_supplicant.conf references) are the following 4 files:
p2p0
wlan
wpa_ctrl_2719-7
wpa_ctrl_2719-8
This has been an ongoing problem for a year now and has driven me to the point of insanity.
Also, the problem was not originally solely related to the wifi data but also other common settings (i.e. app positioning on the home screen, stored settings), however, after some tinkering and flashing various stock roms some of the problems I was having before I have not been able to re-produce. I am waiting until the battery runs out to see if my home screen will return to the default factory state along with other settings which initially was part of the problem.
Any help or advice would be much appreciated I am happy to do any troubleshooting that may shed some light on the problem. The tablet is current rooted with a stock NZ room running 4.4.2.
Thanks

So an update, with some success
I read another thread that suggested the /efs/ss_data file could be causing the problem. Although this file does not exist... however as part of the troubleshooting process to see if this file might be causing the problem the following was suggested
There is most likely a problem with the phone's /efs/ss_data file. I think it's basically a key for decryption of your Wi-Fi passwords and other things in secure storage.
Root is required for this fix.
First we need to confirm it's a problem with secure storage.
Install BuildProp Editor from Play Store
Set ro.secure.storage=false
Reboot, setup Wi-Fi & reboot again
WiFi should now remember passwords if there was an issue with secure storage.
Now let's fix the secure storage issue since we know what's broken.
Set ro.secure.storage=true using BuildProp Editor
Backup EFS using TWRP/CWM recovery
Delete ss_data in /efs using ES File Explorer in root mode
Reboot, setup Wi-Fi and reboot again
Your Wi-Fi passwords should be remembered now on any ROM/kernel, non rooted and without edits to build.props
Click to expand...
Click to collapse
I didn't have the exact entry as per above but changed ro.securestorage.support to false and my wifi password seems to have saved. At least on one reset test.
As a side note, previously my apps weren't updating automatically and my gmail was not responding, now both seem to be working. Everything I have tested so far that had known problems seems to be working.
Now I have ejected the microSD and have not tested it with it in the device, I'm on 3% battery so running it dead before I do more testing.
Can someone shed any more light on how this problem has occurred and what is the permanent fix? (I cannot delete the ss_data file as the advice above suggests as the file does not exist??!!?

Related

Help with WiFi

Hello,
I own a Motorola Milestone (rooted, unlocked). Two days ago a weird thing appeared: when i try to activate the wifi, it goes into a Turning on - turning off - turning on etc. loop and i can stop it just if i activate the airplane mode, restart the phone and deactivate the airplane mode. It does not see any wireless network, i can't stop it and i can't connect to any network.
If i try to see the MAC in the wifi settings -> advanced, it writes 00:00:00:00:00:00 when it is in the loop mode. In the service menu, the MAC Address appears Unavailable.
I tried to reflash different firmwares to solve the problem, but no luck. I reflashed the original rom on it, but also: no luck. I tried everything possible with no luck.
In sys/devices/virtual/net/ i don't have any eth0 folder which i think that contains the network drivers.
I didn't drop the phone, i didn't drop anything on it. It appeared from nowhere. There aren't any other problems with the phone. The bluetooth works fine so, i don't think it's a hw problem (i found somewhere that the two hw modules are the same...it's possible that i should got it wrong).
How can i solve it?
PS: i wrote this here because i saw that this happened to different persons around the world but nobody gave an answer. So, i don't think it's phone related.
If this happened to me I would try this:
1: Nandroid backup+Titanium backup
2: Run WiFi Fixer.apk
if it won't help:
3: Try some other ROMs
btw I don't really understand how did you come up with an idea that this is "Milestone Android Development" thread...
1. I don't have any Titanium Backup or nandroid backup
2. WiFi fixer doesn't work
3. i tested CM7, FroyoMod 2.3.3, CM6, original sbf file...nothing works
I posted this here because the other Milestone threads are not read by most of you.
then RMA it.
After you try to enable wifi, paste kernel log (output from 'dmesg' or 'logcat -b kernel' commands) and main log (logcat) to pastebin.com and post links to it here for inspection.
Is your /pds/wifi/nvs_map.bin file in place?
Hello kabaldan,
I was waiting for your reply master.
The /pds/wifi/nvs_map.bin is there but i can see it only in terminal, with ls, after su. In default file explorer from CM7, the folder is empty.
Here is the output of dmesg: http://pastebin.com/Ngz9iaQU
I'm currently using CM7 RC15 (the last night build).
PS: I promise to donate as soon as i get my money from the company i'm working for.
sdiodrv_data_xfer_sync() transfer error! STAT = 0x108011
Click to expand...
Click to collapse
Sorry to say that, but this is a hardware failure. The wlan sd card does not respond to commands sent to it.
You should send your phone for repair.

Unable to remove Wi-Fi network

Hi, I would like to remove a Wi-Fi network from my list. It's listed as "not in range"
A long press then "forget" sequence returns "cannot forget".
After resetting the phone, the entry is unaffected.
How do I remove the entry (Z736563757265).
thanks nb
spice123 said:
Hi, I would like to remove a Wi-Fi network from my list. It's listed as "not in range"
A long press then "forget" sequence returns "cannot forget".
After resetting the phone, the entry is unaffected.
How do I remove the entry (Z736563757265).
thanks nb
Click to expand...
Click to collapse
Hey, I encountered the same issue (I have this exact SSID saved that cannot be forgotten, "failed to forget network" - where did this SSID come from????) and spent some time figuring out how to remove it. Well, I actually fixed it with the 'attwifi' network but I assume the following steps would apply for you too. I have an LG G2 running stock android 4.2, rooted. Note that you will need a rooted phone in order to do this. Here are the steps I took:
1.) Get a text editor capable of running as root (I used 920 text editor, there is a permissions issue with it though that I detail later).
2.) Open /data/misc/wifi/wpa_supplicant.conf using your text editor. Make a backup of this file while you're at it.
3.) Find the 'attwifi' entry and rename it (I renamed it to 'attwifi2'.) You could also probably remove the entry but I didn't try that.
4.) Turn off and turn on Wifi
* Note, I couldn't turn on wifi at first once I changed wpa_supplicant's conf file. It turned out to be a permission issue - my text editor did not save the file with the correct permissions. I had to run 'chmod 777 /data/misc/wifi/wpa_supplicant.conf' in a terminal window to give permissions back (it probably just needs chmod 666).
5.) Find 'attwifi2' in your saved wifi list and 'forget network'. It should now be forgetten. There is no more attwifi or attwifi2.
If this doesn't work for you, then you are probably using a different version of android where the conf file is in a different path. Try grepping for attwifi via a terminal window. Another thing you can try is to run 'dmesg' in a terminal window to see the system log - this could give you a clue as to what is going wrong. Best of luck!
Wifi issue on note2
I have a wifi issue, wifi I is not turning on after flashed the hd revolution on my note 2 pls help me
klaus ita said:
I have a wifi issue, wifi I is not turning on after flashed the hd revolution on my note 2 pls help me
Click to expand...
Click to collapse
I think your best bet is to ask your question in this thread: http://forum.xda-developers.com/showthread.php?t=2055736
Thanks!

Fix for mac 02:00:00:00:00. [Wi-Fi and hotspot greyed out/not working]

Important. Root required.....
Hey everyone,I saw so many posts regarding Android & iOS that the Mac address is changing to 02:00:00:00:00 and WiFi is greyed out. None of the WiFi or hotspot not turning on.I get the same problem in my Condor and I searched a lot for the solution.I go for factory reset, full reset, flashing stock, radio etc.... But nothing helped. Some strange solution was to hit the back of the phone, put it in the freezer etc...I tried many other ways and that worked only was putting a file named
WCNSS_qcom_wlan_factory_nv.bin
In to the folder / persist....... But it worked me for exactly 1 day and the problem still continued.
So I tried a new method which helped me a lot........
Steps
1.Take a back up of folders /persist and/data/misc/WiFi
2. Unzip the below attachment and put the file WCNSS_qcom_wlan_factory_nv.bin
To /Persist folder.
3.[important step].use any file manager to give full permission to the file(Use ES file explorer, I used solid explorer that provides more permission, if ES doesn't work use Solid explorer)..
4. Restart the phone
5. Now your WiFi will be back to rock............
If doesn't work try clearing the folder /data/misc/WiFi/wpa supplicant... And /persist....
If any thing goes wrong use back up's......
Don't forget to hit thanks if it worked......and don't blame me if it doesn't worked....
abhi5974 said:
Important. Root required.....
Hey everyone,I saw so many posts regarding Android & iOS that the Mac address is changing to 02:00:00:00:00 and WiFi is greyed out. None of the WiFi or hotspot not turning on.I get the same problem in my Condor and I searched a lot for the solution.I go for factory reset, full reset, flashing stock, radio etc.... But nothing helped. Some strange solution was to hit the back of the phone, put it in the freezer etc...I tried many other ways and that worked only was putting a file named
WCNSS_qcom_wlan_factory_nv.bin
In to the folder / persist....... But it worked me for exactly 1 day and the problem still continued.
So I tried a new method which helped me a lot........
Steps
1.Take a back up of folders /persist and/data/misc/WiFi
2. Unzip the below attachment and put the file WCNSS_qcom_wlan_factory_nv.bin
To /Persist folder.
3.[important step].use any file manager to give full permission to the file(Use ES file explorer, I used solid explorer that provides more permission, if ES doesn't work use Solid explorer)..
4. Restart the phone
5. Now your WiFi will be back to rock............
If doesn't work try clearing the folder /data/misc/WiFi/wpa supplicant... And /persist....
If any thing goes wrong use back up's......
Don't forget to hit thanks if it worked......and don't blame me if it doesn't worked....
Click to expand...
Click to collapse
Well this fix won't work for any device. You should probably have put this in the relevant section i think
Sent from my SM-G935F using Tapatalk
no work for me
Not working for xiaomi mi 8
hey guys
I have a xiaomi mi 8 global.
after the new miui update to 10.0.2.2 my GPS became really buggy so I rooted my phone and downgraded to miui 10.0.2.0 and that fixed my GPS issue. but just yesterday my wifi switched off and no matter how much I toggle it on it always turns back off. so I did some research and found out that other people have the same issue with other phones. apparently there is a file called WCNSS_qcom_wlan_factory_nv.bin in a folder called persist that for some reason gets deleted and doesn't come back even if you factory reset. I tried twrp restore with no luck. so I downloaded the file like suggested and placed it in the persist folder but still no luck for me where as on other phones it would work.
so my question is. I know xiaomi files and in different places then other Androids and sometimes even the names are different. where should I put the file in xiaomi mi 8 and should I rename it to something else. or what should I do

About persist partition?

Hi, I had the dreaded grey wifi bug and in my desperation tried all the fixes that are floating around, one of which was formatting the persist partition. It didn't fix it at all. What fixed it was unplugging the battery for an hour but thankfully I manually backed up the persist directory with a root file manager. Anyway my question is: is it ok to copy-paste back the old bt and wifi mac addresses files and set permissions accordingly or do I need to do something else? And is it ok to not restore the widivine and playready directories and their contents? Im asking because I don't want to break anything else as bluetooth and wifi are currently working fine again with their original addresses, dunno if those 2 directories will be needed later. Everything else like imei is unchanged.
Also is reflashing a google stock image through fastboot enough to make sure all partitions and filesystems are refreshed/fixed? My phone did this weird thing of deleting all user app data before the wifi crashed (like they were newly installed) but left the sdcard data like pictures and music intact, so I figure something made one partition/filesystem crap itself and may need to be recreated/fixed.

[SOLVED] Wi-fi "memory" reset on every disabling!

Hello,
I got a little problem with my phone (so freak... I'm explaining)
I got a router before but now I changed it, because I switched to another operator. But it feels like the Wi-fi of my phone is not agree with that.
I "forget" the now inexisting router I had and connect to the new one...
...But I do this each time I turn off then on Wi-fi, and even after switching off the device with enabled Wi-fi!
For now I just have to remember one Wi-Fi router (and, thank you Kika Keyboard developers who made an extensive clipboard where I can store my password <3) but figure out what it will be when I'll have to save more passwords! So yes it's annoying. And I also already lost at leat 8 router passwords because of this strange cr*p.
Fortunately I got a Wi-fi retriever app but this is not auto connecting and this is no longer working!
That was the last point: even the router password retriever app is acting like I didn't connect to a new router since its last analyze!
So could you help me fix this annoying bug?
For now I got an hypothesis: I got XPosed and a device ID changer app.
And it contains an useless but impossible to disable option that is "changing the SSID"
Default configuration make your phone to display your SSID. But not with the local variable where your actual SSID is displayed! No, with the SSID you got when you installed the app. So you can connect to another Wi-fi and still got the same SSID (perfectly useless)
Rest of my theory is that messing up with SSID display may cause network state not to be saved properly. But this is only a supposition. And this is hard to figure it...
So to corroborate this theory, a subquestion: What is the local Android variable where SSID is stored? Tried %WIFI, %SSID but it doesn't work. And I didn't found it after a quick search.
Thank you in advance!
Sorry for wasting your time with so much text :/
https://android.stackexchange.com/questions/124792/my-phone-stopped-remembering-wifi-passwords
There are also people conplaining this problem.
In the link pasted on the top, there is a possible fixes for some fortunate people... But actually this doesn't work for me.
-First, ro.secure.storage or ro.securestorage. thing does not exist on my device. I don't even know if it existed on my device.
-Second, there is something about /efs/ss_data, a file that also not exists on my device.
So I don't know if it's because Samsung built it differently or it has been removed. Keep checking...
After a check of my backups I saw that I got none of the file and property mentionned before.
So I'm unable to know where is the problem...
Atronid said:
After a check of my backups I saw that I got none of the file and property mentionned before.
So I'm unable to know where is the problem...
Click to expand...
Click to collapse
If you're saying that you looked in build.prop but you don't see any lines that say ro.securestorage, you can add those lines if they don't exist. Just edit build.prop and type the line in at the bottom then save build.prop and reboot the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
If you're saying that you looked in build.prop but you don't see any lines that say ro.securestorage, you can add those lines if they don't exist. Just edit build.prop and type the line in at the bottom then save build.prop and reboot the device.
Click to expand...
Click to collapse
This is what I did. Uneffective.
Why? Because I never got this prop before.
I checked my backups where the Wi-fi worked perfectly in case all of this would be due to the fact that this prop vanished because of a dark and random informatic process. And after checks I finally realized that I never had this prop...
Same thing for the file I mentionned before, located in /efs. I didn't lose it because I basically never got it.
So... This means that my device save Wi-fi informations by another way. And because I don't know this way, I cannot fix it...
(Device: Samsung Galaxy Core Prime SM-G361F AOG1 build.
Pre-rooted firmware, release date 23 February.
Latest Xposed Frameworks, Custom build by Wanam )
Atronid said:
This is what I did. Uneffective.
Why? Because I never got this prop before.
I checked my backups where the Wi-fi worked perfectly in case all of this would be due to the fact that this prop vanished because of a dark and random informatic process. And after checks I finally realized that I never had this prop...
Same thing for the file I mentionned before, located in /efs. I didn't lose it because I basically never got it.
So... This means that my device save Wi-fi informations by another way. And because I don't know this way, I cannot fix it...
(Device: Samsung Galaxy Core Prime SM-G361F AOG1 build.
Pre-rooted firmware, release date 23 February.
Latest Xposed Frameworks, Custom build by Wanam )
Click to expand...
Click to collapse
If you got a different router but kept the same network name and password and didn't change anything on your device, that might be the issue, your device is probably looking for your original router because the information you originally saved was saved while the other router was in use.
Try backing up your apps, app data and settings but don't backup your wifi settings or saved wifi information. Then boot to recovery and factory reset and wipe cache and dalvik/ART. Then reboot the device, when it boots to system, try connecting and signing into your network again and see if it saves it correctly.
If the backups you are talking about are nandroid backups created in TWRP, you can also try doing an advanced restore in TWRP, you can restore just the data from your previously working backup without restoring everything else.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Thank you, I'll try this out
Droidriven said:
Try backing up your apps, app data and settings but don't backup your wifi settings or saved wifi information. Then boot to recovery and factory reset and wipe cache and dalvik/ART. Then reboot the device, when it boots to system, try connecting and signing into your network again and see if it saves it correctly.
If the backups you are talking about are nandroid backups created in TWRP, you can also try doing an advanced restore in TWRP, you can restore just the data from your previously working backup without restoring everything else.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, tried what you told me and this didn't end well...
I used to make a factory reset of my phone. The problem was fixed. When I connected to the wifi first time, now each time I disabled and re-enabled it automatically reconnected (auto-connect is miraculous lol)
Then I flashed data back with TWRP recovery (backup by Nandroid app because I got a classical TarFork error with TWRP 2.7.0.1...)
When rebooting to Android it spammed 1M layers of various program crash message box.
Then using TWRP I reflashed this time everything I got then rebooting to Android the bootloader freezed.
I thought my phone was dead until I realized I could boot to recovery again. So I flashed an older backup and lost some data (fortunately I backed up SMS and apk).
My device is safe now, but this misadventure taught me lots of things:
-When I did a factory reset data has been erased, but system still the same and it reworked. So maybe an app is locking my Wi-fi like this. But which?
-Nandroid backup app is NOT reliable. If your device isn't clearly identified your backups are corrupt. Gotta erase all Nandroid backups I made.
Solved. Bug due to a bad TWRP backup. Made a fresh install and everything is fine now.
Thread closed.

Categories

Resources