I reverted from the kernel ImageBreaker v0.8 back to stock then my pin was no longer working I unlocked my device using findmymobile but now even when I set a new pin it says incorrect.
Edit: My WiFi password is also not saving.
Edit 2: I've deleted the keys and locksettings in /data/system/ no luck yet.
Related
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Update!
I got the wifi to work, temporarily. Deleting or renaming the data/misc/wifi directory and rebooting allows me to connect to a wifi network. The problem is that it only lets me connect to that network. If I try to switch ssids or leave the area it will revert to wifi not turning on until I delete or rename the data/misc/wifi directory and reboot again. Not sure what else to try here.
Any help would be appreciated.
Now with logcats
Checked out adb logcat, errors:
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)Client SS library: connect: Connection refused
E/SecureStorage(21019): [ERROR]:SPID(0x00000000)SS_ConnectToDmnSndCmnData error
Anyone with a fix? Got the same problem today. It's fixed after a restore but if I change the network, wifi turns greyed out.
rstoops said:
I made a series of poor choices and now I'm in a bad place.
I rooted my Note 3 with towelroot, and was trying to change the build.prop file to change the DPI (I didn't know there were apps for this). I couldn't get it to save changes, and in trying I set the file's permissions to 777. Then I got the changes made, but didn't change the permissions back.
So reboot, won't boot. ADB wouldn't find the device, so I used instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2703006 to restore. And it worked! My phone booted, I was able to root and change the DPI and everything was great for a couple hours. Now the WIFI won't work at all. It hangs on "Turning on..." when I try to turn it on from settings. Thinking maybe the modem was the problem, I went to this thread (http://forum.xda-developers.com/showthread.php?t=2698464) and tried flashing NC2, NB4, and MLG firmwares. None of them made any difference. In settings < About Device Baseband is N900AUCUCMLG and build number is KOT49H.N900AUCUCMLG.
I reset to factory and it fixed it for a short time. Then right back to WIFI failure. Maybe if it's not the modem firmware, the problem was disabling Knox through SuperSU? Or rooting itself? That's really all I've done.
Anybody know what the problem could be? Should I ditch the whole thing and just put a custom ROM on it? Grateful for any help.
Click to expand...
Click to collapse
Found the fix.
Use Root Explorer.
Delete the files below that are inside /data/misc/wifi/
wpa_supplicant (folder)
wpa_supplicant.bak.conf
wpa_supplicant.conf
Go to build.prop press menu and select Text Editor than find this line:
ro.securestorage.support=true
change it to:
ro.securestorage.support=false
Save. Reboot, wifi should be fine.
In title. I tried NEMESIS but it says incorrect PIN and the encryption entry box UI crashes every 2 seconds after encryption (with boot image reset to stock). Do any even support it?
+1
Hello All -
I updated tonight to the Android Q 10 - Q Release 1.5 - QP1A.190711.122 by sideloading the OTA and then rooting with Magisk canary. Everything worked beautifully except now when I go to set my screen lock PIN and fingerprints there is no option to set a PIN or pattern. Anyone else have this issue? Any advice how to fix it?
See attached screenshot when I go into security settings the only options available are None and Swipe.
I did some troubleshooting and reflashed the OTA sideload update to stock and the screen lock settings all returned to normal. The I rooted again with Magisk canary and after flashed the patched boot image with fastboot the same issue returned.
How do I report this to the Magisk dev team?
hssxda said:
...
How do I report this to the Magisk dev team?
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHelp
I found a workaround for now.... I reflashed the stock boot image. Set my PIN passcode and then flashed the patched boot image from Magisk.
Now the PIN is enabled but if I go back to the settings to change the screen lock the only two options again are the "None" and "Swipe"... very wierd but definitely repeatable issue.
Does noone else have this issue? This is still not working for me...
Got my phone rooted couple days ago with Magisk (in recovery) and so far its working fine. All green. Yayyy
But when I tried to patch services.jar myself (by having my own magisk module to replace), something weird happened. All wifi profiles reporting "Incorrect password" I have to re-enter the passwords but it always ends up being that after reboot.
I think patching services.jar triggers something that causes the saved data to be corrupted and cannot be decrypted somehow? I think other data like bluetooth paired devices could be corrupted in the same way too.
I tried using the original services.jar without any modifications (just replace the .odex). Still no luck.
Smali Patcher doesnt seems to work on 10. I tried that too.
Im currently on latest stock ROM android 10 in case you wonder.
Any help would be appreciated!
alex.do said:
Got my phone rooted couple days ago with Magisk (in recovery) and so far its working fine. All green. Yayyy
But when I tried to patch services.jar myself (by having my own magisk module to replace), something weird happened. All wifi profiles reporting "Incorrect password" I have to re-enter the passwords but it always ends up being that after reboot.
I think patching services.jar triggers something that causes the saved data to be corrupted and cannot be decrypted somehow? I think other data like bluetooth paired devices could be corrupted in the same way too.
I tried using the original services.jar without any modifications (just replace the .odex). Still no luck.
Smali Patcher doesnt seems to work on 10. I tried that too.
Im currently on latest stock ROM android 10 in case you wonder.
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue with wifi, I haven't patched services.jar though, so it's not that. I never re-entered passwords, just rebooting again did the trick. Not 100% sure yet but I think I solved it by wiping dalvik-cache, haven't had the issue since, touch wood
hinxnz said:
I had the same issue with wifi, I haven't patched services.jar though, so it's not that. I never re-entered passwords, just rebooting again did the trick. Not 100% sure yet but I think I solved it by wiping dalvik-cache, haven't had the issue since, touch wood
Click to expand...
Click to collapse
Got it solved!
I followed you to wipe the davik-cache and cache partition also. It didn't help at first. So I went on re-entering the passwords to some recent wifi profiles and tried to reboot. Voilaaaa the wifi seems to be saved properly now. I will check if it still survives after several reboots.
I think my patched services.jar has something to do with secure storage (since I set the isTimaAvailable() to return true always - more details can be found in Smali Patcher project, which does no longer work properly on Android 10) and that causes the old data to be corrupted and you gotta re-enter. I hope I only need to do it once.
Thanks for the tips!
For starters, ive been using the same lockscreen pin on ALL of my devices for the past3 years, I know im using the right one. I recently installed the Evolution ROM and set it up with fingerprint and PIN. Fingerprint was working just fine, I rebooted the phone after installing a magisk module and now its telling me the pin for the lockscreen and TWRP is wrong. Again, I only use ONE pin and its telling me its wrong. Tried deleting the locksettings.db file to take off the screen lock and that worked but now phone just stays on "Phone is starting" and TWRP is still excrypted but lets me see all of my files, correct storage amount, and install zips.
When you installed did you format data?
I know this says Lineage, but it works for most custom ROMs, post #2 has the cliff notes version: [Guide]Installing Lineage
As for the locksettings.db, this isn't like older Android devices. You can't just do that, it doesn't fix the problem here.