vega exec vda to ensure you’re using the VDA version that matches your active SDK. If you have only one SDK version installed, you can use vda directly.
Check VDA version
Before troubleshooting connection issues, verify you’re using the correct VDA version that matches your active SDK.App install fails with timeout or “Parameter value bad” error
Cause: A pending download on the device blocks new app installations. Symptoms:- App installation times out when sideloading through Vega Studio or the command line
- The install log shows:
Installing/Updating '/tmp/myapp.vpkg' ...error (Parameter value bad )
-
Shell into the device:
-
Cancel all pending downloads:
- Reinstall your app using your normal workflow (Vega Studio or command line).
Device not appearing in VDA device list after enabling Developer Mode
Cause: The following conditions cause this issue:- ADB server conflict when ADB is installed on the host machine
- Device is configured for VDA network mode instead of USB connection
- Running
vega exec vda devicesshows no device in the list - USB detection commands show no device:
- On Mac:
ioreg -p IOUSB -w0 -l | grep Lab126returns nothing - On Linux:
lsusb -v | grep Lab126returns nothing
- On Mac:
- Get your Fire TV device’s IP address from Settings > My Fire TV > About > Network.
- Ping device from host:
- Ensure Developer Mode is enabled on the device. See Configure Developer Mode.
- Use a personal phone hotspot to connect host and device, as some corporate networks have communication restrictions.
- For more fixes, see Connection timed out.
Random USB disconnection from Fire TV Stick
Cause: The Fire TV Stick randomly disconnects during debug sessions due to faulty or incompatible USB cables. Symptoms:- Both
vega exec vda devicesandvega deviceslist commands return empty results - The device becomes unresponsive and unavailable for debugging
- Disconnecting or reconnecting temporarily resolves the issue, but the problem recurs
Connection or power issues
Cause: Insufficient power, faulty cables, or system power management settings interfere with device connectivity. Symptoms:- Device randomly disconnects during use
- Device not detected by VDA
- Intermittent connection drops
- Device appears and disappears from device list
- Use the original USB cable that came with your Fire TV device.
- Disable the automatic sleep mode and “Selective Suspend” feature in your operating system.
-
Power cycle your Fire TV device:
- Unplug the power supply
- Wait 10 seconds
- Reconnect the power supply
- Reconnect the USB cable to a different port on your computer.
- Restart your host computer and reconnect VDA.
-
Verify the connection:
Example output:
Undetected Fire TV device
Cause: One of the following conditions prevents the host from detecting the Fire TV device:- Developer Mode isn’t enabled on the device.
- The USB cable only supports charging.
- USB hubs, virtual machines, or intermediate devices interfere with direct communication between the host and the device.
- Fire TV device connected through USB but not appearing in
vega exec vda deviceslist - Device works when connected to another computer
- Connection works intermittently
- Confirm that Developer Mode is enabled on the device. For steps, see Enable Developer Mode.
- Use a USB cable that supports data transfer, not a charge-only cable.
- Connect your Fire TV device directly to the host computer.
- Remove any USB hubs or intermediate devices.
- Disable virtual machine (VM) or port forwarding from other hardware like the Raspberry Pi.
-
Verify the connection:
Chrome USB discovery conflicts
Cause: Chrome Developer Tools’ USB discovery feature conflicts with VDA device detection. Symptoms:- Device not appearing in VDA device list
- Device detection works after closing Chrome
- Intermittent device detection issues when Chrome is running
- Open Chrome Developer Tools.
- Choose Settings > Remote Devices.
- Clear the Discover USB devices checkbox.
- Reconnect your Fire TV device.
-
Verify the connection:
“No route to host” error while ping works
This section covers the macOS Local Network permission. Ifping to the device also fails, or your host isn’t a Mac, the host can’t reach the device over the network. For network checks, see Connection timed out.
Cause: On macOS, Local Network privacy blocks the VDA server from reaching devices on your local network. The VDA server runs in the background. The permission belongs to the app that started the server, not to the terminal where you run vega exec vda connect. If an app without Local Network permission started the server, every connection attempt fails. For example, an editor with Vega Studio or a background process can start the server.
Symptoms:
-
vega exec vda connectfails with output similar to the following: -
pingto the device’s IP address succeeds, and a port check such asnc -vz 192.168.1.100 5555connects.
- If the output names an app, allow that app under Local Network or quit it, as described in step 1.
- If the output names
vda, a background process started the server, and there’s no app to allow under Local Network. Go to step 2 and restart the server from Terminal. - If the command prints nothing or an error, no VDA server is running. Go to step 3.
- To let the VDA server reach the device, allow the app that started it under System Settings > Privacy & Security > Local Network, or quit that app. The app might be Visual Studio Code or Kiro with Vega Studio. If you quit the app instead, keep it closed, because it can restart the VDA server automatically.
-
Stop the running VDA server:
-
From the macOS Terminal app, or another terminal app that you allowed under Local Network, connect to the device again:
This command starts a new VDA server that belongs to the app that you ran it from.
TCP/IP connection issues
Cause: Network connectivity issues, incorrect IP address, firewall blocking the connection port, or VDA daemon not running in TCP/IP mode. Symptoms:- Device not appearing when using
vega exec vda connect [IP_ADDRESS]:5555 - Error messages:
unable to connect,Connection refused, orNo route to host - Connection timeout errors, such as
Operation timed outorConnection timed out - Device works over USB but not over network
vega exec vda connect prints tells you which fix to try first. On macOS, if the error is No route to host, see “No route to host” error while ping works.
Connection timed out
If the connection request doesn’t reach the device,vega exec vda connect fails with Operation timed out on macOS or Connection timed out on Linux:
-
Verify both devices are on the same Wi-Fi network:
- macOS: Choose the Wi-Fi icon in the menu bar to view the connected network
- Linux: Choose the network icon in the system tray or run
iwconfig - Fire TV: Choose Settings > Network/Wi-Fi to check the connected network
- Disconnect your host machine from any VPN.
- Confirm that your router allows traffic between devices on the network. Some guest and corporate networks turn on client isolation, which blocks this traffic. If you can’t change the router setting, connect both devices to a home network or a personal phone hotspot.
-
Check the firewall on your host machine:
- Ensure port 5555 isn’t blocked
- Temporarily disable the firewall for testing
- Re-enable the firewall after confirming the connection works
- Get your Fire TV device’s IP address from Settings > My Fire TV > About > Network.
-
Connect to your device using the IP address:
Replace
[IP_ADDRESS]with your device’s IP address from step 5.
Connection refused
If your host machine reaches the device but nothing on the device listens on that port,vega exec vda connect fails with Connection refused:
- On your Fire TV device, go to Settings > My Fire TV > About > Developer Options and confirm that Connection Mode is set to TCP/IP. If you change the connection mode, the device reboots. Wait for the reboot to finish before you connect.
-
Confirm that the port in your
vega exec vda connectcommand matches the port that the device uses, as shown under Developer Options. The default port is 5555. If you set a custom port, use that port in the command. -
If the device still refuses the connection, connect it through USB and restart VDA in TCP/IP mode:
-
Kill the VDA server:
-
Restart the VDA server:
-
Disconnect the USB cable and connect to the device again:
If the connection still fails
If neither fix resolves the error, try the following steps:- Restart your Fire TV device and try connecting again.
-
If issues persist, try an alternative port:
- For detailed TCP/IP setup instructions, see Configure VDA Over TCP/IP.
Fire TV device unresponsive in TCP/IP mode
Cause: Device stops working after switching to TCP/IP mode and becomes unresponsive. Symptoms:- Device not responding to VDA commands
- Can’t switch back to USB mode through normal settings
- Device appears offline in VDA device list
- Go to Settings > My Fire TV > About > Developer Options
- Choose Connection Mode to switch to USB. The device reboots.
-
Verify USB connection:
Example output:If you don’t see the device:
-
Perform a factory reset to revert to USB mode:
- Go to Settings > My Fire TV > Reset to Factory Defaults
- Choose Reset and confirm
- Wait for the device to restart
- Complete the initial setup.
- Review the requirements and steps in Configure VDA Over TCP/IP for Fire TV Devices before attempting TCP/IP mode again.
-
Perform a factory reset to revert to USB mode:
Ubuntu 64-bit compatibility issues
Cause: VDA is a 32-bit app requiring 32-bit architecture support on 64-bit Ubuntu systems. Symptoms:- VDA commands fail to execute
- Error messages about missing libraries
- Permission errors when running VDA commands
-
Install 32-bit shared libraries:
-
If permission errors occur, add yourself to the
plugdevgroup:
VDA server isn’t responding
Cause: VDA server process becomes unresponsive or fails to start properly. Symptoms:- VDA commands hang or timeout
- No response from
vega exec vda devicescommand - Error messages about server not running
-
Stop the VDA server:
-
Restart the VDA server:
-
Verify the server is running:
Example output:
VDA permission issues
Cause: Insufficient system permissions prevent VDA from accessing USB devices on Linux systems. This commonly occurs with the Fire TV 4K Select because the device’s USB Vendor ID may not be included in default udev rules. Symptoms:-
Error messages:
- Device detected but not accessible
- Commands fail with permission errors
-
vega exec vda devicesreturns empty even though the device is connected via USB
- Connect your Fire TV device via USB.
-
Run
lsusbto list connected USB devices: -
Look for an entry containing “Amazon” or “Lab126”. The Vendor ID is the four characters after
IDand before the colon (for example,1949inID 1949:xxxx).
-
Disconnect VDA from your Fire TV device:
-
Create a udev rules file with the Fire TV device’s Vendor ID. Replace
1949with the Vendor ID from Step 1 if it was different: -
Add permissions to the rules file:
-
Add yourself to the
plugdevgroup (if not already a member): -
Reload the udev rules and restart the service:
-
Restart VDA:
-
Reconnect your Fire TV device and verify it is detected:
Example output:
Device detection issue
Cause: The host system may not recognize the Fire TV device at the hardware level, preventing proper connection. Symptoms:- Device not appearing in
vega exec vda deviceslist - No hardware detection at system level
- USB port appears inactive
- Run
lsusbin the terminal. - Look for “Lab126 Alexa” entry with your Fire TV device serial number.
-
Install
lsusb: -
Run
lsusbin the terminal. - Look for “Lab126 Alexa” entry with your Fire TV device serial number.
- Alternatively, check System Report > USB devices for “Lab126 Alexa” device.
- Different USB cable
- Different USB port
- Connection or Power Issues solutions
- Device Detection Fails on Current Host to test on another computer
Device detection fails on current host
Cause: The issue may be specific to your host system rather than the Fire TV device itself. Symptoms:- Device not detected on current computer
- Same device works on other computers
- All troubleshooting steps have been attempted without success
- Connect your Fire TV device to another Mac or Linux machine.
- Open the terminal on the alternate host.
-
Run
vega exec vda devices. - Check if your Fire TV device appears in the output.
- USB controller driver issues
- System configuration problems
- Hardware incompatibility
- Factory reset the device
- Contact support through the Developer Forum.
VDA fails after upgrading to macOS 27
Cause: Upgrading from macOS 26 to macOS 27 removes Rosetta, which VDA depends on. Fresh SDK installations aren’t affected, because they install Rosetta as a dependency during setup. Solution: Reinstall Rosetta by runningsoftwareupdate --install-rosetta --agree-to-license, then restart your terminal. For details, see Fix Vega SDK Issues.
Related topics
- Run Your App
- VDA Reference
- Configure VDA Over TCP/IP
- Enable Developer Mode
- Resolve Fire TV Stick Issues

