Quest ADB Scripts mini-FAQ

Q: My antivirus claims that the program contains a Trojan or virus. Why?

A: The program and additional utilities are packaged together using the Quick Batch File Compiler application, which, unfortunately, is often used to bundle malicious applications. As a result, antivirus programs, upon detecting the familiar signature of this packer, do not bother checking the actual contents and immediately flag the package as malicious.

You can extract the Quas package using a standard archiver like 7zip and inspect its contents. Alternatively, you can visit GitHub to review the package composition and source code.

Additionally, starting from version v3.1.0, the Quas package includes the AndroidMdnsDiscover.exe application. This tool is designed to detect the headset using the mDNS protocol and display its IP address and port. A Python script with the same functionality is available for review and download here: 🔗 GitHub Repository

The packer used for this application is also disliked by some antivirus programs.

Q: What is the difference between connecting the headset via Wi-Fi from the main menu (item 7) and connecting the headset via port 5555, items F-G-C?

A: If we're talking about connecting to a PC, there is no difference in this case. However, the second option can also be used for direct connection to the headset from the headset itself, using the same port 5555. You can control the headset via ADB from inside using applications like Termux or Bugjaeger. For example, you can change the resolution, refresh rate, or CPU/GPU level.

Similarly, you can easily connect the headset to a PC wirelessly via a so-called random port if the Quest Games Optimizer application is running and active on the headset.

Q: Why is the program written in cmd?

A: Because I don't know other languages, and I just needed a small utility with a basic set of ADB functions so I wouldn't have to type the commands manually every time. I wrote it and decided to share it. But over time, the program grew a little bit...

Q: I found a bug, what should I do?

A: Write about it in the Telegram group, in the Feedback section. I'll try to fix it by the next release.

Q: The headset is in Bootloader mode. I connect it to the PC with a cable, run Quas, and it says the headset is not detected. The drivers are installed.

A: Install newer driver versions; the best ones are 1.71.0.000017.

Q: When I start the program, I get the messages: "mode" is not an internal or external command, executable program, or batch file, and "chcp" is not an internal or external command, executable program, or batch file.

A: Try running the program as an administrator.

Q: I flashed my headset with your program and now it won't boot. Is it because of the manual flashing or is the program to blame?

A: Neither. Unfortunately, this can happen, and it doesn't matter whether you flash officially over the air or manually. In reality, the program doesn't flash the headset itself; it only loads the firmware file onto the headset using the standard Android mechanism: adb sideload update.zip. After the firmware file is sent to the device, the headset itself takes care of the installation, first checking the file twice for certificates and correct checksums. This is also why it's impossible to flash a modified or incompatible firmware file — the headset simply won't approve it and won't flash it. There is also a check to ensure the file version matches the headset version.

-


Edit
Pub: 10 May 2024 21:58 UTC
Edit: 07 Feb 2025 14:58 UTC
Views: 53