Nexus 5X PIN question

[jahaynsworth]

Interesting question. I thought I understood how the Nexus 5X stored the pin, but of course I could be wrong. Thanks for running the command on your machine- I ran it on a linux box as well with the same "exhausted" result.

It make sense to try running the process as you did in reverse- to run the PIN & salt through the MD5 and SHA1 hashes to see if they come out matching. I wan't able to re-produce that either. I tried Salt(base10):PIN(base10), Salt(base16):PIN(base10), PIN(base10):salt(base10), and PIN(base10):salt(base16).

That link you posted is great. If anyone has something similar for the Nexus 5X that would be perfect.

I followed the Samsung method in that link in the hopes that maybe the 5X used the same process, but again exhausted the password space with no result.

>hashcat64.exe -a 3 -n 80 -u 1024 -m 5800 2dda3898dfc93e5334cb1113748d41b24b5b293c:081cec9952979615 ?d?d?d?d --force

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: Samsung Android Password/PIN
Hash.Target......: 2dda3898dfc93e5334cb1113748d41b24b5b293c:081cec9952979615
Time.Started.....: Thu Jun 07 08:25:37 2018 (1 sec)
Time.Estimated...: Thu Jun 07 08:25:38 2018 (0 secs)
Guess.Mask.......: ?d?d?d?d [4]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:    12328 H/s (10715.98ms) @ Accel:80 Loops:1024 Thr:256 Vec:1
Speed.Dev.#3.....:        0 H/s (38025.56ms) @ Accel:80 Loops:1024 Thr:256 Vec:1
Speed.Dev.#*.....:    12328 H/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 10000/10000 (100.00%)
Rejected.........: 0/10000 (0.00%)
Restore.Point....: 0/1000 (0.00%)
Candidates.#1....: 6234 -> 6764
Candidates.#3....: [Generating]
HWMon.Dev.#1.....: N/A
HWMon.Dev.#3.....: N/A

Started: Thu Jun 07 08:20:31 2018
Stopped: Thu Jun 07 08:25:40 2018