DJBhardwaj
Inactive Recognized Contributor
Maybe it now works, however it failed to patch correctly last time I tried it.
Great! Thanks for the answer ashyx! I will use the one you provided.
Maybe it now works, however it failed to patch correctly last time I tried it.
Hello.
I do not understand. With PIE, Samsung account and PIN LOCK do not work (with OREO it works perfectly).
I installed TWRP without MAGISK, and MAGISK without TWRP and it was always the same problem.
Thank you.
It seems to be some sort of security measure.For some reason any custom or modified boot image(unsigned) causes the lockscreen settings to be unsaved.
It seems to be some sort of security measure.For some reason any custom or modified boot image(unsigned) causes the lockscreen settings to be unsaved.
Possibly a patched lockscreen binary is required.
The same issue happens on Gsi's, but a work around was found for that, but this doesn't work on stock Samsung roms.
Samsung account gets disabled as soon as Knox is tripped.
I think you maybe getting mixed up with the Bluetooth/WiFi password issue that required patched secure storage binaries to fix.I am not a kernel expert, but I remember on the J6 it had the same problem. Kernel devs acknowledged this as a keystore problem or I forgot the name. They fixed keystore stuff on the kernel and then Samsung account and lockscreen pattern/pin/password worked again
I think you maybe getting mixed up with the Bluetooth/WiFi password issue that required patched secure storage binaries to fix.
Unless you can point to a specific thread?
Great. I'll look into that. Any idea where the original patches came from?No no, I remember before the J6 had a global launch of Pie I took another country's firmware and made a Pie zip.
I used the same old TWRP, stock kernel and a few edits on system, and I remember I had the exact same problem. Pin/Pattern/Password did not work and you could not log in to Samsung account. I could set up the PIN just fine, but whenever I input it, it would always return as incorrect. I'm going to try to find the commit made to the kernel, let me see if I can find it even though I don't know how much of this works xD
---------- Post added at 11:39 AM ---------- Previous post was at 11:35 AM ----------
Here we go: https://github.com/ananjaser1211/Helios_7870/commit/f1c62423175f5e5f1b4e27efefc0b0befecb5568
Again, I don't know how much of this works but I know, I am pretty sure I remember that ananjaser was helping me with this Pie build and he named this "Keystore bug" or something lol
But since I don't know much about kernels, I really don't know how all this works xD
Great. I'll look into that. Any idea where the original patches came from?
Just been looking into this, but I see all the changes got reverted. Any idea why? Did the changes actually work or cause another problem?
Well, talking with Anan directly he said because it helped when he was porting Pie to older devices like J5 and J7. But then he noticed it actually did nothing, it seems the keystore issue only affects newer devices that have official Pie, but he wasn't sure exactly why.Just been looking into this, but I see all the changes got reverted. Any idea why? Did the changes actually work or cause another problem?
Just been looking into this, but I see all the changes got reverted. Any idea why? Did the changes actually work or cause another problem?
No, tried it on J6.I went through a Galaxy M20 thread and found this comment that was posted recently regarding Samsung account on rooted Pie. Do you think this trick will work for the A6+ as well?
So, there is still no way we can root it on Android 9 with samsung features wotking?
Doesn't look like it, there is prolly a higher chance of Android 10 (which is prolly going to be released 2020) working fine then getting a working method for this problem lol
You could also lurk/join the a605x telegram, there is some talk about gsis etc.
It works:I went through a Galaxy M20 thread and found this comment that was posted recently regarding Samsung account on rooted Pie. Do you think this trick will work for the A6+ as well?
I will update the boot image later with a fixed version.Ashyx is there a solution to the problem of connection with the pc? mtp application reports error
I need the path of the brightness file.there is a small problem here, i can't change brightness. it won't be darker or brighter.
No they fixed itHi, does the problem of lock screen and fingerprint unlock still exit?
You need to build a device tree yourself.I need device tree, vendor tree, and kernel source
Could you tell me how did you get those things?
I want to build a rom