I can't get the wifi passwords in de wpa_supplicant file to get unencrypted. I tried to change securestorage from true to false in build.prop but it still doesn't works and forgets every wifi password after a reboot.
Does someone have a solution for this?
SM-G935F, rooted with magisk
nooby1411 said:
I can't get the wifi passwords in de wpa_supplicant file to get unencrypted. I tried to change securestorage from true to false in build.prop but it still doesn't works and forgets every wifi password after a reboot.
Does someone have a solution for this?
SM-G935F, rooted with magisk
Click to expand...
Click to collapse
I have the same problem, over 6.0.1 no problem but over 7.0 I don't find thw way to see the passwords unencrypted
just get it from admin or use Windows to get it
Related
Is anyone having issues with WIFI passwords not being remembered?
After updating to MJ4, passwords to wifi have to be reentered every time to connect.
Yea same here but it was happening on mine prior as well. Guess the last update didn't help that.
sent from - At&t Note3 - still stock
SOLUTION:
kevg77 said:
I have seen that others are having the same issue that I am having where my phone forgets WiFi settings after every reboot since MJ4 update. What is the fix for this?
Thanks
Click to expand...
Click to collapse
kevg77 said:
WiFi problems?
Try this:
Due to "securestorage" being set to true in build.prop, changes to the ROM or kernel that aren't reflected in the ss_id file in /system/etc/secure_storage/.system.bin.wpa_supplicant/ can cause issues with WiFi among other things. You can set this to false yourself, or simply flash the zip file below.
Download: Set Secure Storage to False
For those that prefer to do it manually, simply change this line ro.securestorage.support=true to false in /system/build.prop.
Click to expand...
Click to collapse
Why was [ ro.securestorage.support=true] set to true? --Is this by ROM's default?
What functionality do we lose once it's set to "false"?
Thanks for the solution. Unfortunately I'm not rooted yet. But with all the problems I'm having I might just root it to load a custom rom
sent from - At&t Note3 - still stock
From another post, worket for me:
Quote:
Originally Posted by kevg77
WiFi problems?
Try this:
Due to "securestorage" being set to true in build.prop, changes to the ROM or kernel that aren't reflected in the ss_id file in /system/etc/secure_storage/.system.bin.wpa_supplicant/ can cause issues with WiFi among other things. You can set this to false yourself, or simply flash the zip file below.
Download: Set Secure Storage to False
For those that prefer to do it manually, simply change this line ro.securestorage.support=true to false in /system/build.prop.
Had this problem for months and solved it just now by deleting some old networks from the list of remembered networks. It seems that the problem was due to exceeding the number of networks kept in memory. Hope this helps someone, I have not seen this suggestion anywhere.
I have installed [CM7]JOYOS ported based cm7.2[percy_g2] http://forum.xda-developers.com/showthread.php?t=2396158 rom on my galaxy y.
Everything is working fine except wifi hotspot.. When i turned on wifi hotspot ,it is shown on other devices..but on connecting,.it stuck on obtaining IP address. Even after entering static IP details... i cant access net on other device.
I tried to resolve it with foxfi app & wifi tether for root app..but no luck.. Plz help me..how to resolve this issue..
jonny789 said:
I have installed [CM7]JOYOS ported based cm7.2[percy_g2] http://forum.xda-developers.com/showthread.php?t=2396158 rom on my galaxy y.
Everything is working fine except wifi hotspot.. When i turned on wifi hotspot ,it is shown on other devices..but on connecting,.it stuck on obtaining IP address. Even after entering static IP details... i cant access net on other device.
I tried to resolve it with foxfi app & wifi tether for root app..but no luck.. Plz help me..how to resolve this issue..
Click to expand...
Click to collapse
hey
obtaining ip must be a problem on other device not on yours
press thanx
jonny789 said:
I have installed [CM7]JOYOS ported based cm7.2[percy_g2] http://forum.xda-developers.com/showthread.php?t=2396158 rom on my galaxy y.
Everything is working fine except wifi hotspot.. When i turned on wifi hotspot ,it is shown on other devices..but on connecting,.it stuck on obtaining IP address. Even after entering static IP details... i cant access net on other device.
I tried to resolve it with foxfi app & wifi tether for root app..but no luck.. Plz help me..how to resolve this issue..
Click to expand...
Click to collapse
Reflash the kernel then the Tom
Go to recovery
Mount system
Flash Percy kernel or black reactor
Reboot recovery
Format data,cache,system
Mount all
Flash the Tom
Reboot
Additional thing : go to system / etc / wifi and set permission of folder to rwxrwxrwx and the wifi compliant *I don't remember exact name* to rwxrwxrwx too and try.
Sent from my GT-S5360 using Tapatalk 2
mohamedrashad said:
Reflash the kernel then the Tom
Go to recovery
Mount system
Flash Percy kernel or black reactor
Reboot recovery
Format data,cache,system
Mount all
Flash the Tom
Reboot
Additional thing : go to system / etc / wifi and set permission of folder to rwxrwxrwx and the wifi compliant *I don't remember exact name* to rwxrwxrwx too and try.
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
another solution ????
I manually upgraded my i337 from NB1 (4.4.2) to NJ4 (4.4.4), and then I re-rooted it. While I noted minor differences between the versions (I now had the "Custom Unlocked" logo on the splash screen, for example, and the notification "shade" did not scroll off and on as quickly), the most problematic issue was WiFi connectivity, which caused me to reinstall NB1 (pending a solution).
With NB1, my WiFi worked as I thought it should. It would automatically re-connect to hot spots and, if there is a password, it would automatically handle it for those sites I had logged into previously. Thus, for example, my phone would automatically log into my home WiFi router as soon as I walked through the door.
It appears that NJ4 is broken. I have found that under NJ4, the WiFi will only *automatically* re-connect to the most recently-used hotspot (whether or not passworded). This is not affected by restarting either the phone or the router. Thus, if I connect to my home router, the phone will re-connect effortlessly PROVIDED I don't connect to any other hotspot. If I have connected to another hotspot, once I return home, I find that there is no longer an automatic connection (I receive a "WiFi Hotspots are Available" notification), and once I initiate the connection manually, I am asked for my password EVERY TIME. At least I know my home password; I don't know the passwords of the many other hotspots I have connected to.
The collected WiFi credentials are maintained in the file data/misc/wifi/wpa_supplicant.conf. I looked at that file to see whether the passwords had been deleted. No, they were all still there (albeit encrypted). Here is an entry like the one for my home router:
network={
ssid="SqueekyNet"
psk=[the encrypted p/w is located here]
key_mgmt=WPA-PSK
priority=657
frequency=2462
disabled=1
autojoin=1
usable_internet=0
skip_internet_check=0
}
Note the line that says "disabled". The system inserts this line once you log into a *different* hotspot. It does this for *every* entry, so the only entry without this line will be the one for the current hotspot (or for the most recent one, if you aren't logged in to any WiFi hotspot).
I have found that if I edit the wpa_supplicant.conf file on-the-fly ... changing "disabled=1" to "disabled=0", then my home WiFi is instantly recognized, and I am immediately logged in (the "forgotten" password isn't really forgotten). Further, if I then re-examine the wpa_supplicant.conf file, I will see that the "disabled" line has been deleted from the current hotspot, and will only be re-inserted once I log into a *different* hotspot. BTW, while I am using the home hotspot as a test, the same behavior applies to ANY hotspot. Thus, under 4.4.4, NO hotspot is logged into automatically (unless it is the most recent hotspot), and unless you are attempting to log into the most recent hotspot, you ALWAYS receive a request to enter the password for a protected hotspot (even though the password is actually still in the file). I use WiFi heavily, and this isn't viable for me.
The problem apparently isn't limited to the i337 (AT&T) build of NJ4. I noticed this discussion in the T-Mobile forum: https://support.t-mobile.com/thread/84926 (I tried to comment on it, but I can't register for the forum since I'm not a T-Mobile customer).
I am now comfortably back on NB1.
Does anyone have a solution for this?
UPDATE: I found that after I reinstalled 4.4.2 (NB1), using ODIN and then Titanium Backup, as soon as I activated WiFi, my device would strip all of the entries from wpa_supplicant.conf that contained a password (psk). I tried a number of different techniques to reload my original wpa_supplicant.conf file, and was never successful. All of the entries without a psk remained, however (there are hundreds).
I also found that after reinstalling NB1 (including the restore via Titanium Backup) once I re-entered the password for a particular WiFi hotspot, then the re-entered password would stay in the wpa_supplicant.conf file (and the phone would again login to WiFi automatically, without ever/always asking for a password re-prompt as was happening with 4.4.4 NJ4).
While I don't really know for sure, it is my guess that the psk entries were stripped from the wpa_supplicant.conf file by the Google server. Not sure why, but since I am able to totally restore the device with all of the pre-backup data files (including the original wpa_supplicant.conf file), this is my only explanation.
For me, NB1 works to remember passwords and log-in automatically to WiFi hotspots; 4.4.4 NJ4 does not.
OK i seem to have this extremely bizzare wifi issue.
I can connect to wifi access points fine, if i turn off wifi and turn it back on i am unable to auto connect and have to re-enter credentials for it to connect. Before doing so i checked my wifi ap to see if my ap were listed and they were not.
If i re-enter everything is fine but having to do this to wifi ap is annoying. After i have entered and check the wifi ap files i can see the credentials are saved etc.
If i do not re-enter the credentials and restart the phone with wifi enabled it connects to AP fine.
If i leave wifi connected and connect to to wifi aps that require certs its fine also without the need to re-enter creds.
At first i thought maybe i had a corruption in the wifi config files but i dont see any, no duplicate aps at all, no fancy characters i can see.
Does anyone have any thoughts as my wifi config with aps is many years old and has a massive amount of APs listed.
It doesnt matter what ROM i try as soon as i restore all my APs the issues start, is there a way to bulk export, wipe wifi aps and re-import them all again?
Do wifi aps with spaces in or length cause issues with 5.1.1?
1 root ur phone if you are unrooted 2 download any build prop editor from playstore 3 change this line ro.securestorage.support=true to false in /system/build.prop 4 if it doesnt work try a different build prop editor cz the changes might not be sticking 5) hit the thanks button if it helped
dork997 said:
1 root ur phone if you are unrooted 2 download any build prop editor from playstore 3 change this line ro.securestorage.support=true to false in /system/build.prop 4 if it doesnt work try a different build prop editor cz the changes might not be sticking 5) hit the thanks button if it helped
Click to expand...
Click to collapse
ro.securestorage.support=false
already
Hi all
I have the 935F Model, and it's rooted. Have any of you tried an app called "WPS WPA Tester" on it?, I used to use it on my old Grand 2 and it worked well, but now when I hack a WiFi with it the Password of that WiFi is encrypted and some times it deosn't show at all.
So what is your experience in this domain?
PS: there are two solutions on the web for this (adding a line to build.prop Or deleting a file in the system folder) and both didn't work.