You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No biggie, but I'm opening this in case anyone else does the same thing. The command in the README states that you should be in the same folder, but it was just a little surprising that it was a requirement.
~/Unsynced documents/futurerestoring » checkm8-nonce-setter-master/main.sh
*** Matty's Checkm8 APNonce Setter ***
Do you want to input a generator? (y,n)
y
Please enter your desiered generator.
0x1111111111111111
Your generator is 0x1111111111111111
0x1111111111111111
checkm8-nonce-setter-master/main.sh: line 82: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 89: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 96: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 103: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 110: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 117: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 123: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 129: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 135: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 141: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 147: files/igetnonce: No such file or directory
checkm8-nonce-setter-master/main.sh: line 153: files/igetnonce: No such file or directory
Either unsupported device or no device found.
Exiting..
The text was updated successfully, but these errors were encountered:
No biggie, but I'm opening this in case anyone else does the same thing. The command in the README states that you should be in the same folder, but it was just a little surprising that it was a requirement.
The text was updated successfully, but these errors were encountered: