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?
rooted with magisk
I have the same problem. My S6 (nougat / magisk) drops any saved Wifi passwords as well as BT pairings and even saved passwords from other apps after a reboot (and sometimes even after a change within magisk but BEFORE the reboot)
EDIT: The passwords are still there, they are just treated as "wrong". So it could very well be a decryption problem.
DiePlage said:
I have the same problem. My S6 (nougat / magisk) drops any saved Wifi passwords as well as BT pairings and even saved passwords from other apps after a reboot (and sometimes even after a change within magisk but BEFORE the reboot)
EDIT: The passwords are still there, they are just treated as "wrong". So it could very well be a decryption problem.
Click to expand...
Click to collapse
Do you have a solution for this?
I unrooted, removed magisk and everything works normal again. Right now I am without root / adblock.
After some research it seems to be a problem with file permissions. Some people seem to have solved this by manually editing / correcting the permissions of several /system files. I haven't tried this so far.
I think, this thread should be moved to the magisk forum.
same problem
I have the same problem. Not solution for this yet?
Yeah that's why I downgraded to mm from day 1 I flashed nougat
Bump any fix to get WIFI PASSWORDS to stick and reconnect after reboot or disconnect of the wifi.
Current Setup
SM-G920P, rooted Magisk, Tdhite's kernel, and on da BiggDaddy Rom.
Also having this issue. Stock Nougat with Magisk. Also tried uninstalling Magisk but that just caused a boot loop. Tried changing ro.securestorage.support to false. Bluetooth also won't enable.
Related
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?
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?
rooted with magisk
Click to expand...
Click to collapse
Same problem here any solution ?
Hi guys.
So I've used multiple backups to try to login to my snapchat account (an earlier one that worked before, and another one right before i logged myself out).
BUT, after i restore snapchat to that version and open it, it works for a moment (a second), then freezes, then logs me out with the message (you have been logged out).
I'm completely devastated.
S.O.S.
Thanks .
Phone: SAMSUNG-SM-G935V
Did you ever figuire this one out? Just happened the same to me.
Was without my android for a few days, so I logged into an iphone. Now when I get my android back, Im logged out.
I had a backup from Titanium backup, but - like you - it just logs me in for a short while and then (presumably) calls home and disconnects me.
Edit:
I found this article from yesterday:
"Snapchat will check your SafetyNet status only during your first login. If you root your smartphone after installing Snapchat, you can continue using the app as normal. But this doesn’t work the other way round, as Snapchat will no longer allow you to login after rooting. "
Edit2: (1 hr later, and it is fixed)
I use Superman ROM and Magisk for SU, but should work on any ROM with Magisk.
There are many good tips for bypassin SafetyNet with Magisk on this page:
I ended up using the Module "Universal SefetyNet Fix". Downloaded it, flashed it in Magisk, restarted - DID hide it in Magisk Hide (which they say you don't need to, but I did anyway). Then I loaded my titanium backup, and got the failed login - but that's ok, because now the safetynet hide works, so I just logged in normally. No need for titanium backup version.
he universal fix is working for me too. Also i made a video on how to get multiple accounts on snapchat and other social media apps. Check it out: https://goo.gl/g6d947
Qarie said:
Hi guys.
So I've used multiple backups to try to login to my snapchat account (an earlier one that worked before, and another one right before i logged myself out).
BUT, after i restore snapchat to that version and open it, it works for a moment (a second), then freezes, then logs me out with the message (you have been logged out).
Click to expand...
Click to collapse
I rooted using SuperSU before installing Snapchat and I ran into the same problem. Luckily, an app called 'Root Switch' did the trick for me.
Guide (Assuming you are already rooted using SuperSU and not able to log in at all now or you do not want to switch to Magisk):
1) Install Root Switch https://goo.gl/5nPJUm
2) Open Root Switch > tick on 'Stop all su daemons' > and then toggle 'Enabled' to 'Disabled' (This stops all the apps from detecting root on your phone)
3) Try logging into Snapchat and it should work fine
4) Go back to Root Switch > toggle 'Disabled to 'Enabled' > untick 'Stop all su daemons' and ta da, you are back to your rooted phone. (If you are unable to do this step, just restart your phone)
Optional: You can delete the app now but if you think you will need it for something else, you can keep it.
Cheers
Hello, can you help me a bit, i'm in the same situation:
I have a backup of my snapchat, some days ago the restore with titanium bakcup worked fine, but now like you said in first post after restored data, it log in, then freezes, then logs me out
I have Masgisk v14, tried the Universal SefetyNet Fix module but still got the "you can't loggin", also tried magisk hide but still can't log in
Also tried to uninstaller xposed
I just tried Root Switch and still can't log in snapchat
remi13014 said:
I have Masgisk v14, tried the Universal SefetyNet Fix module but still got the "you can't loggin", also tried magisk hide but still can't log in
I just tried Root Switch and still can't log in snapchat
Click to expand...
Click to collapse
@remi13014
1) Use the Root Switch method after uninstalling Snapchat first:
~ Uninstall Snapchat > Root Switch > Install Snapchat and then try logging in > Root Switch to enable root again
When you flashed Magisk, did you flash the SafeNet tools as well?
Hi,
I have BV9800Pro with Android Pie (MediaTek P70) and now I noticed that after reboot, some banking apls and lockmypix app has problem with fingerprint. Jf I go to settings, remove it and add it again, then all is ok again with all apls, but after reboot, banking apps + lockmypix dows not allow for me to unlock uaing fingerprint because "biometric data changed" as one app tells me.
Any ideas? Has any one had such issue? How to fix this?
P.S., i Have tried ro disable xposed and magisk, nothing helped, only factory reset, but after that, I couldn't identify what caused this issie to come back again.
P.P.S., if I have let's say 2 fingerprints saved, and delete any of them, all appa back to normal until I reboot.
LGZACRO said:
Hi,
I have BV9800Pro with Android Pie (MediaTek P70) and now I noticed that after reboot, some banking apls and lockmypix app has problem with fingerprint. Jf I go to settings, remove it and add it again, then all is ok again with all apls, but after reboot, banking apps + lockmypix dows not allow for me to unlock uaing fingerprint because "biometric data changed" as one app tells me.
Any ideas? Has any one had such issue? How to fix this?
P.S., i Have tried ro disable xposed and magisk, nothing helped, only factory reset, but after that, I couldn't identify what caused this issie to come back again.
P.P.S., if I have let's say 2 fingerprints saved, and delete any of them, all appa back to normal until I reboot.
Click to expand...
Click to collapse
Just a issue that had developed while you was building your daily driver
Sent from my moto g(7) play using Tapatalk
PoochyX said:
Just a issue that had developed while you was building your daily driver
Click to expand...
Click to collapse
Any idea what might caused it? P.S., previously I have flashed the complete rom except userdata partition, and the issie was still there. Even if I disable all magic modules and xposed as well, the issue remain.
Has anyone faced something like that? Personally, I think some file is being overwritten after reboot and it might cause this issue. That's the only logical explanation I can figure out.
Hey, so I flashed a LOS 17.1 GSI on my SM-T295, and then installed Magisk 21.4 and the latest manager. After enabling MagiskHide and rebooting, my device "bootloops" in a weord way. Turn it on, wait for android to load up, wait a bit, shutdown, reboot. You can use the apps and the Manager, but only until it reboots. Wait a bit, android loads up again, wait for it... Reboot!
I just disable MagiskHide and reboot (or just wait for it to do it by itself), then wait and it's solved! However, I feel like that setting might help me with bypassing the SafetyNet test, and I would like to fix that issue so it doesn't happen again, even with the setting enabled.
I've made a post on this already (let me get the link for it, i'll edit later), but it isn't as clear and my explaination of the issue wasn't accurate. However, I explain some extra stuff that mayyyyyy have influenced on the issue, like how I installed TWRP, LOS, OpenGApps and Magisk, and some issues on the process of installing them (like the encrypted(?) folders and files mentioned on my prevoius post on this, this issue is gone for now), but idk.
Any ideas thanks in advance bye pls reply?????????
Can you tell how did you root your device please
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?