BigRedZag Posted October 2, 2016 Share Posted October 2, 2016 I received my new Firehawk FX on Friday. Played around with it and loved it. Downloaded the app for my Android Note4 and it prompted me that a firmware update was needed for the Firehawk FX to communicate. It did strongly recommend that you do it via USB but I didn't have one so I tried doing it via the Bluetooth on my phone. I checked back around 20minutes later and the unit said "Updating 290" but my phone had lost the connection. I couldn't get the Firehawk to do anything so I reset it. It powered up and said Version 1.2 briefly before all the buttons A-D started flashing and "Error = -21" displayed. After reading through the forums I tried to hold A and C on startup for a factory reset and when it starts I says resetting but immediately goes into the Error -21 state. I also tried the Tap button and Volume button. I get a list of setting that I can go through but can't figure out what to do in there to perform a reset (if that's possible). After a trip to the store to purchase a USB cable I installed the updater app and firmware patches 1.1 and 1.2 but when I connect the Firehawk to the computer the updater doesn't detect it. So, that's where I'm at. Pretty frustrated right now. I like the device but if this is how it's going to be I'm going to return it. Anybody had a similar situation or possible fixes? I opened a ticked here but it said three days before I should hear a response. Quote Link to comment Share on other sites More sharing options...
guilleguitar Posted November 19, 2016 Share Posted November 19, 2016 Just a random idea here, did you install the USB driver? Quote Link to comment Share on other sites More sharing options...
suedehead99 Posted November 23, 2016 Share Posted November 23, 2016 You're planning on returning it because you bricked it by not following the instructions, which recommends using a USB cable but you decided to do it via bluetooth? I suppose the retailer won't know the difference between faulty product and user fault. Not trying to apportion blame/shame. Just thinking it through. After all, it's an imperfect system and if the Bluetooth connection was better on these units, you probably could have updated OTA in the first place. Did you get anywhere with the support ticket you raised? What did you decide in the end? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.