New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(software startup): UAD's UI doesn't show up on my laptop although its service is still running #444
Comments
Same for me on Win10 LTSC. The app worked when I tried it about a month ago or so. It also worked on Linux. So I think this is an LTSC specific issue, maybe it is due to recent updates or anything Adb.exe runs in task manager but GUI does not show up. Ping me if you guys can find anything. log
|
Same for me on Windows 11, I can see the process in Task Manager but the GUI dosen't show up. I tried all sort of thing like the OP said but nothing, unfortunately I don't have logs since I deleted all the files. |
It should load new config file, but just in case try to rename config file in |
nevermind it started working for some reason lol. |
@itsvngo try connect phone to pc without programm running. Open shell and type |
I had same problem. |
Describe the bug
I installed UAD on Windows 10 LTSC build. The tool had worked a week ago on the same build. But i had deleted it along with adb for personal reason.
Today, i redownloaded the tool and adb, I gave path to adb, driver for my pixel 5 was already installed, check for adb devices, adb was working (the proof was pixel flasher working fine).
I moved UAD tool to adb folder, started it up, nothing happened, checked the task manager, the tool's service was already working, but the UI didnt come up.
Expected behavior
The UI comes up as usual so i can interact with the tool
You have a solution?
I tried to make a fresh adb folder to start the tool but nothing happens, i even started it in administration mode. I tried the OG version of 0x192 too but still nothing. I don't know how it had just worked a week ago but now nothing shows up
Provide logs
UAD_20240427.log
UAD_20240502.log
uad_lists.json
Acknowledgements
The text was updated successfully, but these errors were encountered: