Short version: activation codes for the MGU activator are machine-bound licences generated by whoever wrote that tool — that isn't something the board admin or the mods can produce or look up for you, so waiting on Bin alone won't get you a code unless he happens to be the author of the build you're running.
What your own
activation.txt already tells you: the submission address is printed at the bottom of the file (the hotmail one), and the file carries the username, e-mail, HW fingerprint and stamp date you need. That is the intended channel — send the txt unedited to that address, keep the subject line clear, and quote the stamp date so they can match the request. Turnaround is normally a few days, not minutes.
A couple of practical notes:
- Do not paste the full HW string (
1055-...-9981) into open threads. Anyone holding it can request a code bound to your machine fingerprint, and you'd have no way to control who uses it. Send it privately only.
- Generate the file and submit it from the same PC you'll run the tool on. That fingerprint is tied to the network adapter and board; swap the NIC, dock or reinstall the OS and a code issued against the old string won't validate.
- If the tool has since shown a different HW ID than the one in the txt, request against the current one — old ones are dead.
Which activator build and version are you running — is it the one bundled with the guide here, or a standalone tool? And does it present a separate "code" entry field after the HW ID, or does it expect a patched file back? That tells us whether you're waiting on a licence or on a file response.
