Samsung Lockscreen Denies My Password
eromatiya opened this issue · comments
I patched boot.img and flashed it using odin. After successfully rooting my device, I can't login to my samsung account and the lockscreen denies my pattern/pin. After rebooting, the device bootloops. My device is SM-J810F Pie and I used Magisk Canary 19.4. Please. fix it. Thanks in advanced!
Logcat would be most helpful
Find magisk log catcher module, flash in TWRP, boot and capture the issue z than reboot to TWRPA and pull the logs from /data/local/boot
Update:
I tried to root again and I followed the instruction in install.md. I start the adb logcat, set the pattern, locked my screen, and then tried to unlock it. Of course, the pattern is not working.
Here's the logcat:
logcat.txt
There's an interesting line:
08-29 12:27:48.641 1153 2849 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/fmmpassword.key: open failed: ENOENT (No such file or directory)
I think the pattern I set doesn't save that's why it's not working on lockscreen. Also, I still can't login to my samsung account. Always "Processing failed." Sorry for my bad english. Thank you in advance!
Do you use Android 9? Because since Android 9 I need to use a custom kernel for my s9 and before I hade the exact same problem
Yeah I think there is a compatibility issue with magisk and my device's custom kernel. Sadly, there's no custom kernel for my device. I'll stick around with custom rom for now. Hopefully they can fix it in the near future. Yes, I'm on android pie btw
Unfortunately I cannot fix weird Samsung kernel issues without the device on my hand. S10 is directly supported because I had the device on hand, I know what files I need to patch to make it work properly.
no way ???
bl destroy keystore 🥺
please give us guide or tell us what to do .??
today , I managed to crack lockscreen ..
there is something will prevent open phone , deleting lockscreen.db and .key wasn't enough .
Here is logs :
please tell us what should we do ?
and thanks .
I know it isn't magisk issue but please help .
This also failed 🥺🥺🥺:
geckyn/android_device_samsung_j4primelte@595912f
&&
create empty file in /etc .
You have to talk to your rom developer on xda. Not here
You have to talk to your rom developer on xda. Not here
it is stock rom .
in custom rom lockscreen was fixed .
Issue with stock rom .
rom dev is Samsung 😂😂😂😂😂
@ilovecookieee
This solved issue with me but face unlock , doesn't work , I will see it later .
chmod 0 /vendor/lib/hw/keystore.*.so
then reboot and set lockscreen .
@Kopra159 Nice. I already gave trying to root my phone but I'll try your workaround. Though I have a question, can you use the Galaxy store?
@Kopra159 Nice. I already gave trying to root my phone but I'll try your workaround. Though I have a question, can you use the Galaxy store?
unfortunately samsung acount doesn't work after installing twrp until now .
Well this falls back to software AOSP keymaster instead of using hardware keymaster, that's not as fix, more of a workaround. Le jeu. 12 déc. 2019 à 14:11, Mohamed Omar notifications@github.com a écrit :
…
@ilovecookieee This solved issue with me but face unlock , doesn't work , I will see it later . chmod 0 /vendor/lib/hw/keystore.*.so then reboot and set lockscreen . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Thanks .
Now , I understand what happened .
Replacing hardware keymaster with aosp keymaster .
so now lockscreen works .
I am trying since july 2018 until now and matter happened today at the morning 😂😂.
Thanks and please if u get anyfix tell it to us .
Very nice! Thanks bro. So, I'll just run chmod 0 /vendor/lib/hw/keystore.*.so
then reboot right?
Very nice! Thanks bro. So, I'll just run
chmod 0 /vendor/lib/hw/keystore.*.so
then reboot right?
yes ,
if u have twrp use it as it will be easier .
mount vendor
then use terminal and write command .
if u on system.
su
- mount vendor as rw :
mount -o rw,remount /vendor - if u are sar and u faced problem with mount point :
mount -o rw,remount /
then command .
don't reboot until u see ------ before 1 root .
command to check :
ls -l /vendor/lib/hw/ |grep keystore
=================
then reboot .
try lockscreen .
Sadly, the workaround didn't work for me @Kopra159 . I still can't login to my samsung account and the lockscreen is still broken. Btw, I use adb to change the permission after rooting and I don't have the
keystore.msm8937.so
in my/vendor/lib/hw/
no it should .
u didn't change permission in right way as it is 644 in picture not 0 .
Do u have twrp ???
sorry guys call come when edit and my finger click on refer as issue by mistake
Thanks for this Fix_Temp_lockscreen.zip @Kopra159 . It flashed successfully. But after rebooting, it asked me for password. The phone is encrypted even if I didn't set any password.
Thanks for this Fix_Temp_lockscreen.zip @Kopra159 . It flashed successfully. But after rebooting, it asked me for password. The phone is encrypted even if I didn't set any password.
maybe u set password before that .
anyway
easy flash this by twrp :
https://github.com/Kopra159/Prevent-Disabling-Lock-screen-app/releases/download/v2/crack.zip
then flash fix temp :
and give me result of check command .
maybe u set password before that .
Nope, I just flash a stock rom then root it. After changing the permission using su -c 'chmod 0 /vendor/lib/hw/keystore.*.so'
in adb shell, I reboot my device. On start-up, it requires me to enter a password but I never set any password or pattern.
give me result of check command
Okay, I'll try it
@Kopra159 The p=$(ls /data/system_de/0/spblob/ | grep -v "000000" |awk '$0="/data/system_de/0/spblob/"$0')
gave me an error:
ls: /data/system_de/0/spblob/: No such file or directory
The fix temp was flashed successfully. After rebooting, the same problem on start up: Your phone is encrypted for security. To start up your device, enter your password. Again, I didn't add any password or pattern.
@Kopra159 The
p=$(ls /data/system_de/0/spblob/ | grep -v "000000" |awk '$0="/data/system_de/0/spblob/"$0')
gave me an error:
ls: /data/system_de/0/spblob/: No such file or directory
The fix temp was flashed successfully. After rebooting, the same problem on start up: Your phone is encrypted for security. To start up your device, enter your password. Again, I didn't add any password or pattern.
ok , in twrp , try manually
rm -f /data/system/locksettings.db
rm -f /data/system/*.key
then reboot and see if password is there ...
and tell me.
also send pictures about lock if it will be there , maybe it is relate to payment service or others .
@Kopra159 failed. It asked me again for password. i think I'm just gonna buy a new phone and it's not samsung lol. Anyway, thanks for all the help.
@Kopra159 failed. It asked me again for password. i think I'm just gonna buy a new phone and it's not samsung lol. Anyway, thanks for all the help.
ok dude ☹☹
@Kopra159
I'm on J810G After Rooting I'm having the same problem with the lock screen. I have a ss of the .keystore file located in my device , should I need to do any changes in tha so I can use my lock screen properly.
I'm college student trying to learn root properly.
give me files (u will find it in internal storage after excuting in terminal ):
https://pastebin.com/jYtVJ58r
@ilovecookieee
@dcoolArne
also use this app and send me
screen shots .
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
@Kopra159
This is the file from my non rooted J810G
https://drive.google.com/file/d/1-QQXmNsVs8TGvSSJhNI6m0sigzlMZ-cB/view?usp=drivesdk
I've uprooted my phone using stock rom I'll send you the same file of my rooted in some time cuz I've a exam to appear today...
@Kopra159
This is the file from my non rooted J810Ghttps://drive.google.com/file/d/1-QQXmNsVs8TGvSSJhNI6m0sigzlMZ-cB/view?usp=drivesdk
I've uprooted my phone using stock rom I'll send you the same file of my rooted in some time cuz I've a exam to appear today...
no need to it without root .
I added su command mean root .....dude
also that file I don't need it , I asked for another files .
I need vendor.txt and system.txt
@Kopra159 I'm not rooted right now, but here's the screenshot.
ok no problem here .
I need commands :
from root device .
and send files from internal storage .
@ilovecookieee
@gsoni411
@ilovecookieee
@gsoni411
try to flash that file :
https://androidfilehost.com/?fid=1395089523397964680
after rmm bypass v3
then try lockscreen 🤔.
Maybe knox guard apk and payment service libs is the cause .
Try ....and tell me .
rats
Tried
su
chmod 0 /vendor/lib/hw/keystore.*.so
rm -f /data/system/locksettings.db
rm -f /data/system/*.key
as root on my Tab A 10.5.
The chmod definitely worked; I had to mount -o rw,remount /vendor
and try again, then 'ls' showed the permissions changed to '------'
Likewise, 'ls' showed the locksettings.db and *.key files were gone.
Rebooted, and now I have a friendly
Your tablet is encrypted for security.
To start up your device, enter your password.
Neither of those things are true, i.e. the device is not encrypted (and the reboot was waaay too fast for it to have applied encryption at that point), never has been, and no password has ever been set (I did the above shenanigans so I could (hopefully) set a password.
latest Magisk, su, hidden, running stock 9
Anyone?
I tried Magisk with stock kernel and it gave me problems like this :(
same issue on j4+ stock kernel.
for now stock rom + root = no lockscreen 🙄
twrp v3.6.1
magisk v24.2