Line6Tony

A failed firmware attempt can have a number of causes. Computer users may be having USB hardware or driver configuration issues, while mobile device users may experience Bluetooth range or interference issues. In any event, a failure in the update process will produce the following page: In our experience, in addition to using Update Mode as laid out on the above page, the best results come from using the USB updater, possibly on multiple computers in case a given computer is experiencing USB configuration issues. We have seen some users experience update issues with older Firehawk drivers still installed on Windows. Go to My Computer > Device Manager > Firehawk then right click "Uninstall Drivers" make sure you click the box saying "Remove Files" Then unplug your Firehawk, plug it back in and repeat these steps until Windows doesn't have any more drivers installed to assign to the Firehawk. Finally, reinstall the latest driver and let Windows assign it.

Due to a driver incompatibility, the ASIO driver for the following devices will not operate with the POD Farm stand-alone application on Windows 10: PODxt series PODX3 series PODHD series The POD Farm ASIO host mode feature in the stand-alone application was not originally intended for these devices, as these Line 6 devices already contain Line 6 modeling in the hardware. To work around the issue, users can use any DAW that supports VST plugins and configure a track in the DAW to monitor the input from the Line 6 POD device, and instantiate the POD Farm VST plugin on that track to achieve the same result. In addition, there are a number of free 3rd party Windows based VST hosting applications available that will also achieve the same result. Note that Line 6 does not support the use of free 3rd party VST host applications downloaded from the internet with POD Farm, and users do so at their own risk

We've found that tones created while using the original 1.01 firmware can sometimes be corrupted, regardless if they are new or downloaded tones. This results in the device locking up, with a factory reset being needed for recovery (press and hold the Master Volume knob and the TAP button as you power up the unit). Firmwares at version 1.10 or later resolves this issue. Tones created in version 1.10 or later can no longer be corrupted like they would have under version 1.01. However, corrupted tones created in version 1.01 are still problematic when used in Firehawks updated to later firmware versions. We encourage those encountering this issue to update to the latest firmware via the Line 6 Updater software, then perform a factory reset. Please note that any tones not backed up to My Tones prior to a reset will be lost (corrupted tones cannot be uploaded because they crash the unit and thus can't be selected for uploading).

In the event that you have connected a RELAY G10 or TB516G transmitter and observed text in the Line 6 Updater app stating that 'The transmitter was not detected correctly', it is likely that the computer has not completed the download of the appropriate device drivers. This may be due to not having allowed the computer enough time to install the drivers upon any initial connection to a USB port on your computer. Please make sure that you are connected to the Internet, and that you have given enough time to allow your computer to search for and install the device drivers. This may take several minutes. The process may also be slowed if any other programs or windows on your computer are open, so it is recommended that you close them before proceeding. Once the drivers have installed, please quit and again launch the updater app, and then attempt the update process with your transmitter. If you are still experiencing an issue at this point, please also check your computer's 'Device installation settings' to make sure that Windows is configured to automatically download driver software (Please click here for a knowledge base item that will further assist with this). Additionally, the driver that the G10 uses is native to Windows and may need to be reinstalled in order for the G10 to be recognized. To obtain the driver, click the link below to visit the website for Infineon, who is the vendor for the driver. There, you can register for a free account. After registering and verifying your email, you can log in to the Infineon site and then manually download and install their "Cypress Driver Installer": USB-Serial Windows Driver Installer

Q: The ABCD lights are flashing and the unit does not function, even after a factory reset. A: This is recovery mode, meaning there was a failed update attempt. The unit will function again once the update is successfully completed. In the event of a failed update, power up while holding A/C and retry the update using the Line 6 Updater found at www.line6.com/software. If the update fails repeatedly, you likely need to try the process on a different computer. Q: I'm seeing the "Load error 21" error message OR the A/D lights are solid and the unit is non-responsive. A: These situations are likely caused by corrupt tones. If you find yourself in one of these "bad tone" situations, you should follow the steps below get to a fresh state: o Copy your User tones to My Tones (backed up in the cloud) or share them with the other options offered by the app so that they're backed up o Forget the Bluetooth connection o Reset the unit ( hold Master volume + tap while powering up) o (Re)install the v1.10 firmware, which resolved many patch and Bluetooth issues o Uninstall the app o Power cycle mobile device o Install latest version of app o Pair to Firehawk Load user patches one by one, testing each one along the way, to find the bad patch. It would be great if you can tell us if you find a bad patch you found on our cloud so we can test it and/or eliminate it. Q: What can I do if I am experiencing Bluetooth connectivity issues between my Bluetooth device and the FIREHAWK FX? A: Make sure you are using the latest firmware and app. For other troubleshooting steps about Bluetooth connectivity and usage, check out our Bluetooth Connectivity FAQ HERE. Q: What should I do If I am experiencing connection issues with the FIREHAWK FX Remote app when I switch back and forth between apps on my iOS device? A: An important thing to note about the FIREHAWK FX Remote app functionality is that in addition to the iOS Bluetooth connection between your FIREHAWK FX and your iOS device, there is a secondary 'sync' connection between the amp and the app. Each time you minimize/close the app, the connection between the FIREHAWK FX Remote app and the FIREHAWK FX will need to be re-established, even if your iOS device is reporting that the FIREHAWK FX is connected via 'Bluetooth'. In this case, re-opening the FIREHAWK FX Remote app will automatically re-establish the connection within a few seconds. Make sure to look at the main menu of the FIREHAWK FX Remote app and wait for it to indicate that your FIREHAWK FX is 'connected' before moving forward using the app. If it does not automatically re-connect, close the FIREHAWK FX Remote app by double-tapping your iOS home key, then sliding the FIREHAWK FX Remote app window up and off the screen. Relaunch the FIREHAWK FX Remote app and it should re-sync itself with the FIREHAWK FX. Android devices usually have a function that lists all open programs where you can slide the app left or right to close it. Relaunch the FIREHAWK FX Remote app and it should re-sync itself with the hardware.

The overall volume is the Master Volume control. This is controlled by the "big knob" when the LEDs are red (the default state). All of the other volumes happen before this one and it's ultimately how you control the output level while keeping everything relatively balanced by using all of the other controls. This is a global control. The Guitar Volume happens just before the master and is how you balance the guitar level against the Bluetooth streaming audio that is coming into the unit. This is also a global control and is accessed by pressing the big knob until the LEDs are white. The Channel Volume is like a Master for just the amp, and it is stored with the patch. It adjusts the output level without affecting the tone (like the Gain control on the amps would). This is the control you use to level your presets relative to each other. The slightly quirky thing here is that it does live in the amp processing slot, so it happens in the signal chain before the post effects. In v1.1 firmware and later, pressing the big knob until the LEDs are pink acts as a short cut to accessing this control without the app. The Gain on the amp panel is the per-patch parameter that affects the tone of the amp - also referred to as Drive The Volume Pedal is an additional real-time control whose value is not saved with the patch. You can see in the app where it lives in the signal path. The Master control on HD amps is considered a deep edit parameter (like sag, hum, etc.) that is saved with the patch and is exclusive to HD amps. It's the output level of the preamp to the power amp. When you load one of these models, the stored value is right for that amp in the default state and it's usually best to leave it where it is unless you are going for a very specific effect.