1. Account
Can the correct username authenticate?
A useful repair log says what worked immediately before the error. Separate account, software, Windows, USB, connection mode and model support.
Diagnose UnlockTool problems by layer: account, download, Windows driver, USB connection, device mode, then model/operation support.
The troubleshooting guide uses a staged fault tree instead of random retries. Start with account access, then confirm the installer and security state, Windows driver, USB connection, required device mode, and finally the exact model/operation support. Saving evidence at each stage makes it easier to identify whether the problem belongs to the computer, cable, device state, account or current UnlockTool support.
Can the correct username authenticate?
Is the build from the developer server?
Are permissions and security messages understood?
Does Device Manager show the expected interface?
Is the phone in the required mode?
Does the current row list the operation?
Do not post passwords, one-time codes or full client identity documents in support messages.
A useful troubleshooting record tells you which layer still works. Start with account access, then application state, then Windows detection, then device mode, and finally model/operation eligibility. This prevents a driver problem from being mistaken for an activation problem.
If one layer passes, keep that result and move to the next layer. Reinstalling everything at once destroys useful evidence.
No. Reinstall only when evidence points to missing or damaged software. Random reinstalling hides the failing stage.
That narrows the fault but does not prove the target model's driver, mode or support state.