Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'failed'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge


  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • FBV Controllers (MKII / 3)
    • M5
  • Amplifiers
    • Powercab
    • Catalyst
    • Spider V
  • POD
    • POD Go
    • Pocket POD
    • POD Express
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay/XD-V Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Registered Products

Found 7 results

  1. USB connectivity is a common issue with a failed update process: Make sure to check all cable connections, and USB ports for proper connectivity. The Pod Go should be connected directly to the laptop or computer with USB 2.0. No hubs or secondary connections. If it's a desktop computer (standing tower), then you may need to connect to the back of the computer near the power source. Proper USB 2.0 ports will provide enough USB bus power for your POD update. For Windows PC users: with all newer updates, it's always helpful to install the latest Pod Go Edit software FIRST, before you continue. This will include the latest Pod Go drivers for proper USB connectivity. Download here: 1. Disconnect the USB cable connecting the POD Go to the computer. 2. Boot the unit into "Update Mode" Press and hold PAGE > (page right) and then power on POD Go 3. Reconnect the POD Go to the computer, preferably trying a different USB port than before. 4. Launch Line 6 Updater. 5. If POD Go connects, it will appear in DFU Update Mode and you will have to select POD Go from the list. 6. If the unit does not connect, close Line 6 Updater, connect to a different USB port on the computer, preferably with a different USB cable as well, and relaunch Line 6 Updater. 7. If the unit then connects, reinstall the firmware. 8. If the unit does still not connect, there may be a configuration issue with the computer. Please try a different computer. Another common solution: If you're having trouble installing the latest update in Line 6 Updater, you may want to revert back to the previous update version. Install firmware 1.40, and then once the Pod Go is booted up again - install Pod Go 2.01 firmware with Line 6 Updater.
  2. After posting the same advice over and over and over throughout the last years (and for several times just during the last hours), I decided to post this here, so I can just link to it (it's also missing in any official Line 6 documentation, at least in a direct, straight ahead form). So, your update to whatever firmware failed? The following steps helped TONS of people over the last years, so give them a try. Note: I am assuming that you've backed up your HX family device already. In case you haven't, now is the time. But as your update possibly failed already, you won't be able to do so, then just proceed (and let's hope you've backed up before). 1) Shut down HX Edit (using it was likely the reason for the update not to work in the first place, so don't use it this time). Windows users *need* (<-!!!) to make sure no traces of it are running in the background anymore. You can either kill the process by using the task manager, in case you don't know how to do that, just reboot your computer. Again: It is ABSOLUTELY mandatory for the following steps to work that there's NO HX Edit or traces of it running. 2) Go to this site: Download the Line 6 Updater this way: That will take you to the site with the actual download (I'm not posting that link because there's various operating systems supported). 3) Install the Line 6 Updater. Edit: Mac users, in case you're running into troubles installing things, please read the bottom of this post. 4) Go to this page again: This time, download the actual firmware this way: Make ABSOLUTELY sure you select your hardware properly! Again, clicking "Go" will take you to the actual download page. Note: The file you will be downloading comes with a "hxf" file ending, make sure to remember the location you've downloaded that file to, you will need to know soon enough! 5) Connect your HX familiy device. Edit: 6) This*might* not be necessary, also, in case your unit really seems bricked, it might not work, but just to make sure, enter safe-boot (aka update mode). Here's how (copied from elsewhere on this site): - Helix Floor/LT: enter update mode manually by holding footswitches 6 + 12 - Helix Rack: ENC1 & ENC6 - will enter Update Mode (This feature is only available on firmware v1.06.5 and higher) - HX Effects: Holding the right arrow ">" Will put the unit in a fail safe update mode. Use this when the HX Effects is in a un-recoverable state - HX Stomp and Stomp XL: Page >: update mode. This update mode is helpful if the update is interrupted, and the HX Stomp will not boot properly. (this will apparently cause a blank screen) 7) Start the Line 6 Updater you've just installed (well, maybe you've installed it already in the past, just start it...). 8) DON'T sign in, chose "Offline Mode" (<-!!!). 9) On the following page, your device(s) should appear. If that's not happening, check whether they're properly connected to a dedicated USB port and not to some fancy HUB. Also check that the USB cable you're using is of decent quality. In case you've checked all that but your device still doesn't show up, quit reading this thread and look for another computer to try with, the following procedure obviously only works as long as your devices are detected by your computer (yeah, I know this sounds like "computing 101 nanny" stuff, but be it so...). 10) Select your device, just click on it. 11) In the following dialog, click here: In the following open dialog, navigate to the file you've downloaded in step (4). Make ABSOLUTELY sure it's indeed the file you've downloaded and not some earlier version or something for another device. 12) Click "Update". This might take a while, as can be read here: Wohoo! Once done, make sure you've got the latest version of HX Edit installed. In case you haven't, grab it from here again: Following page will take you to the actual download. Download and install. 13) Perform a factory reset before booting into HX Edit. Might not be required all the time but Line 6 recommends doing so. In case you didn't manage to do a backup before the trouble started, you might however want to do that now and then perform a factory reset. Here's the procedures for the various HX family products: Helix Floor/LT: While holding footswitches 9 & 10 (bottom row, 2 middle switches), turn on Helix Floor/LT Helix Rack: While holding knobs 5 & 6 (2 furthest right knobs below the screen), turn on Helix Rack HX Effects: While holding footswitches 6 & TAP (2 farthest right switches on the bottom row), turn on HX Effects HX Stomp: While holding footswitches 2 & 3, turn on HX Stomp HX Stomp XL: While holding footswitches C & D, turn on HX Stomp That should be it. Yeah, as said, computer nanny kinda stuff, but then, this really isn't explained too well officially (the official procedure is online updating via HX Edit, which seems to fail often enough to justify writing my little installment). Good luck! Edit: Quite obviously, in case everything worked, you might want to reload your backup onto your device, using HX Edit. Edit #2 To all Mac users running a macOS version from Catalina and onwards: Apple has added several security measures, starting with Catalina. In case an application (in this case most likely the Line 6 Updater, which I think hasn't seen an update to itself for a while, whereas HX Edit should usually just install fine) comes up with whatever error message when doubleclicking the installer, as a first step, try to do a rightclick and select "open". You will likely see a warning but it'll often allow you to click onto something saying "yes, open anyway". In case that doesn't work, it might take you to the security settings straight away. But apparently, sometimes it doesn't. As I'm still running Mojave at the time of writing this, I can't tell you the exact procedure, so here's some information: Thanks to @datacommandofor pointing me to those.
  3. Some users have reported a Windows error message that appears when attempting to launch the POD Go Edit software. This is not an error with the POD Go software itself, but rather a Windows error. Here is a video outlining the process for resolving the error: Here are the links for the latest version of Visual C++ libraries mentioned in the video:
  4. We recently saw a few cases where after updating a G10TII transmitter, it became non-operational. We believe the root cause is this: Line 6 Updater 1.19 unexpectedly identifies G10TII devices as G10T devices. Due to this, it is possible that one could load G10T firmware 1.06 on a G10TII product. If one ever gets into a state where they incorrectly load G10T firmware onto a G10TII, as described above, the issue can be remedied by downloading and installing the latest Line 6 Updater (version 1.20 or later – the latest version is now 1.23) and using it to re-update the G10TII back to the G10TII firmware. As of this writing, the only G10TII firmware release is the initial public firmware (2.00.0). NOTE: If the G10TII does not appear in Line 6 Updater after a few seconds, try un-docking/re-docking the unit a few times to see if it might then be recognized.
  5. 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 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.
  6. I have tried connecting the amplifi 150 to my windows 7 enterprise 64 via bluetooth and the provided drivers in v1.77 do not work. I've attached a screen shot showing as much info as possible. I am running Intel® Wireless Bluetooth® for Windows 7 Version: 20.30.0 (Latest). It is a Dell Latitude e5540. After adding a new Bluetooth device my computer recognizes it as AMPLIFi_150_56. It states This device has been successfully added to this computer and beneath that it gives a message windows is now checking for drivers and will install them if necessary. You may need to wait for this to finish before your device is ready to use. I get the small pop up screen showing Driver Software Installation and within it It does reach out to windows updates and installs: -standard serial over blue tooth link (com4) -standard serial over blue tooth link (com5) -Advanced Audio Distribution Profile(sink) but then fails when trying to install -Bluetooth peripheral device The hardware IDS for this shows BTHENUM\{00000000-deca-fade-deca-deafdecacaff}_VID&00020e41_PID&5061 BTHENUM\{00000000-deca-fade-deca-deafdecacaff}_LOCALMFG&0002 Under Compatible Ids BTHENUM\{00000000-deca-fade-deca-deafdecacaff} ConfigFlags 00000040 CONFIGFLAG_FAILEDINSTALL \Device\000000b9 Install Error There is no driver selected for the device information set or element. E0000203 This is the only device under my device manager that shows with a yellow exclamation. I have all windows updates and my laptop has all the latest firmware installed. I've completely disabled my Symantec antivirus and tried installing this. Anyone ever get this working? I'm a network administrator for large company and have never had this much issue ever installing a simple driver let alone connecting a bluetooth device.
  7. Ok it's just a Pocket POD but here is my issue. If you say the word Tack like I do (Southerner with just a touch of Northerner), it's two syllables "Tah-acK" with a hard T and a hard K. Very often when I hit a note on the guitar (send a signal to the Pocket POD), it produces this metronome-with-echo-like tack sound which constantly repeats. At that point I usually turn off the unit. Sometimes when I turn it back on the tack sound is gone, but then it usually comes back after a while. I bought the unit new - through Sweetwater; it's definitely out of in your opinion is it just a failed electric part, SRAM, diode, resistor...and I should just toss the thing and look for a better product?? Thanks for reading…and considering the problem!
  • Create New...