@Nurmengardian too bad you didn't have backup from a earlier state without wrong attempts

@Nurmengardian at least you know the timeout and can do the bruteforce. i don't understand javascript but as you can see it depends on failed decrypts counter 'x'

@Nurmengardian i don't think it's possible to mess with gatekeeperd. But it may possible to reset failed decrypts counter. Unfortunately i don't know how to do it for FBE

@alecxs it's alright. I guess there's nothing that can be done about the locked cool down period. Also, TWRP was unable to complete any backup in the encrypted state. An adb pull might have worked, but I was not aware of anything that would happen like this.

Anyway, I will keep looking for a way to either reset the counter or a way to somehow edit or change the gatekeeperd, although it does seem almost impossible to do so.

Because a cool down period of 240 seconds equals exactly 4 minutes and at a rate like that, it would take ages. Furthermore, I'm not sure if this period of 240 seconds applies to TWRP brute forcing as well, and if apbf tool is even working correctly, what with the message being displayed as Password not provided. after each entry.

use this as template for brute force

pastebin.com/byd21Kb2

(adb pull can be any encrypted file, used for checking success)

you can create a wordlist.txt with this

pastebin.com/XgtxnLN5

@Nurmengardian mention me if you want to get me notified