TBS Crossfire- Emergency Update

If you run a update for the TBS Crossfire it can happen that the update get corrupted or stops for many reasons. Therefore TBS has implemented several ways to get the receiver back to live.

Recovery options for the receviers

Standard Diversity Rx

The standard diversity receiver comes with a onboard usb connection. therefore you can connect the receiver with you TBS Agent and update him straight away.

Micro/ Nano/ Nano Diversity Rx

Self-update without extra hardware

Since FW 2.24 the Crossfire receivers stores a specific, „golden“ firmware inside. These golden firmwares getting updated from time to time. the last version was 2.88.
With this, you can run a emergency update without the need for any additional hardware.

Das Update erfolgt so:

  1. Hold the „bind“ button

  2. Power up the receiver

    The led starts to flash rapidly

  3. Release the button

    for about 1-2 seconds

  4. Push and hold the button again

    The green led starts to flash in a double-pattern. When it starts to flash rapidly again, you can release the button

  5. Wait till the update is finished

    When the reciver finished the update it will flash slowly

  6. Now the receiver is ready to bind

    You should power-cycle the receiver to avoid issues

Update by a Core Pro/ FPVision/ Standard Diversity Rx

In case the self update fails or if you falshed your receiver with a firware where it was not implemented (e.g. nano div. rx with fw < 2.88) you need to run the update by a TBS Core Pro/ FPVision or a standard Diversity Rx over BST and with the Agent X.

To power your reciver during this you need to take care about a few things:
The Standard Rx and the BST powermodul does not supply 5v to the BST line
– The FPVision supplys 5v to the BST only when yu connected a LiPo to it (not by USB!)
– The CorePro also provies power to the BST line just by USB
– The CorePro and the FPVision should be on FW 2.XX (Beta) or later

Attention: when you connect a FPVision, standard Diversity rx or a CorePro with the Agent X it will just show the device which is connected by USB (Core pro…). This is absolutly normal! You have to run the update for this device (choos a fw version you like). After the Update for this device is finished, the connected receiver get’s his update without any notification. The Crossfire FW flshed on the receiver will be the latest golden Firmware.

BST wiring

BST wire/ plug pinout

How to run the Update with each device, step-by-step

TBS Crossfire Emergency Update flowchart

51 Antworten zu “TBS Crossfire- Emergency Update”

  1. Hallo zusammen,
    bei meinem Nano kommt nach dem Emergency Recover nach den 3x3er grün Blinken ein langes grünes Leuchten und danach erst das schnelle grün Binken. Nach wenigen Sekunden ist dann das gar kein Licht mehr da und es passiert Minuten lang gar nix.
    Wenn ich dann den LiPo entferne und wieder anschließe leuchtet immer noch nichts. Wenn ich dann wirder den Knopf betätige fängt das schnelle grüne Blinken wieder an.
    Ist der „Goldene Speicher“ defekt?

    • hi ello,

      schu deinen empfänger mal genau an. das verhalten kommt bei fehlenden bauteilen doer einem defekten bootloader/firmware.

      wenn keine bauteile fehlen, einfach ein ticket aufmachen. dann gibt es ersatz für dich

  2. Hallo KamiKatze. Habe die Schritte durchgeführt. Aus- und eingeschaltet, LED blinkt langsam grün. Beim Bind fragt der Receiver „Update Micro RX?“. Ohne das zu beantworten blinkt jetzt die LED langsam rot und der Receiver ist tot. Gleiches passiert bei der Bind-Taste am Micro-TX. Das ganze System enttäuscht doch ein wenig. Kannst Du mir helfen?

    • hi jörg,

      du musst das update bestätigen.
      wie bei allen systemen muss die firmware des senders zur empfänger fw passen.

      das rot blinken des empfänger sagt nur aus, das die bestätigung vom sender für das update fehlt.

      also bestätigen, warten bis das update fertig ist und sender und empfänger dauerhaft grün leuchten

  3. I have recently ordered a flywoo explorer LR analogue quad from Flywoo, and ordered a TBS tango 2 v3 from a UK retailer, I cannot seem to bind the radio to the quad.

    When I press bind on the tango 2, its just says binding forever and nothing changes.

    The green led on the quad just keeps flashing green slowly, and on the tango 2 which means it is in bind mode, but still nothing binds to it.

    I have tried every solution:

    I tried updating and downgrading to every single possible firmware that appeared in the list for the FreedomeTX, and for Crossfire, that changed nothing.

    I have tried to update the bootloader for both also, that changed nothing.

    I have tried to update the firmware and cli for the quad, that changed nothing.

    I tried to do the (emergency procedure) self update on the rx, with the ‚golden‘ firware update, that changed nothing.

    I tried deleting the crossfire lua files on SD card and reupdating and that changed nothing.

    I pressed every button and tried every method, nothing has changed.

    Losing hope right now in TBS products to be honest, its been three days and no luck.

    Is there like a log file somewhere in the internal storage of the tango 2 where I can check the events or attempts of connection?

    What could you advise in this situation, it seems I am the only ever owner of a tango 2 who suffers from this issue.

    I have attached multiple pictures to show the firmware numbers on betaflight and on agent x.

    Is there a way to find out if the rx is faulty? is there an error message somewhere I should be looking out for?

    I have written in all places where people could help and no one ever had this issue.

    PLEASE HELP, been 4 days now and I got nowhere with this, about to give up on TBS all together, it seems 8 out of 10 people who have TBS products suffer with it.

    Many thanks in advance.

    • hi yan,

      could you pls retry it with crossfire fw 4.10? there are are some improvements for this.
      also check if the rx is getting hot – then it is broken/ some components are missing.

      in general: there are a few receivers with that issue. so no need to worry about that 🙂

      • Hi,

        I checked and I am already on version 4.10, the rx is also not getting hot, and at least according to my eyes, not components are missing. I have done electronics in the past and am pretty sure something shorted the chip, these modules shouldn’t be handled with bare hands and usually chance someone at the factory did and damaged one of the chips on the module.

  4. First time I powered up my nano diversity receiver i got a solid green light. I tried your suggested fix – power up rx with bind button pushed/fast green blinking starts/with tx connected to agent x click bind/ press and hold bind until double green blinking starts/release button/fast green blinking continues for several minutes. i have tried putting tx in bind mode first and pretty much any other combo imaginable, the rx has never linked to the tx. I tried refreshing tx firmware/installing latest agent x app and starting over fresh and refreshing tx firmware again but results are always exactly the same/rx comes on with solid green light and nothing I try gets it to bind with tx. I have another nano diversity rx and didn’t have any issues.

  5. Hi, has this happened to you? after releasing the button the second time, the green LED keeps flashing fast and then goes dark rather than flashing slowly. All LEDs turn off and just nothing happens.

  6. [tbs nano receiver] I tried the emergency update, but it still doesn’t work. When plug a lipo the receiver immediately blinking green. my tx has update latest version. any solution?

    • hi apri,

      seams like the firmware on the rx is broken. you can try to flash it by a bst device with usb (descripted in this how to as well)

  7. hi. got my crossfire nano diversity installed, powered it, started binding procedure with micro tx module (firmware 2.93), asked to update rx firmware, hit ok. it did all the updating firware stuff, right after it it didn’t bind. plugged out and in again lipo, now the nano diversity has no led light (nor green, nor red, nor flashin, nor solid… just nothing). If I press the bind button it goes on fast flashing green, if i press it again and hold it it goes in that other flashing green pattern, but then nothing, back to fast flashing green… impossible to bind. how should I solve? what did I do wrong? thanks

    • hi mate,
      you got a faulty fw on the receiver. run the emergency update and then re-update. if the issue remains – reupdate the tx and the retry to bind/ upgrade the rx

  8. Hello Kamikatze

    I just bought my diversity and i’ve spent whole night trying to update/bind it.

    all wires connect as normal, plugged battery, flashing slow green, tried to upgrade and just says binding and nothing, diversity not recognise my micro tx.

    i have updated and downgraded multiple times all of the versions by agent x.

    tried hold the bind button and release and after hold again, and nothing.

    is just brand new, never being bind. any idea ?

    • hi janio,
      just a general note on the binding:
      power up the rx while the button is heald will force it in bootloader mode, which does not start any binding.

      my advice:
      – power up the rx
      – push the bind button once
      – set the tx in bind mode
      -> if the rx switches to red then wait for the update prompt on your radio/ lua etc
      –> if this promt does not appear, try to start the binding by the agent x (crossfire tx conencted to the pc)

      if you got a tango II:
      open the sd card
      erase the 2 files in the crossfire/ota folder and reupdate your crossfire by the agent x.

      at least one of those methodes should start the update and then the binding

  9. Hi, my nano rx cannotr bind with the TX then try your step to upgrade my nano rx, firstly it just like you say, the green led flash rapidly, and then I push bind button, it flashing in two pattern than rapidly, and then it dark for more than 2 minutes, because the fc temperature was raise then I decide to turn of my qwad, and when I start the qwad the led only flashing green, and still cannot bind with my TX

    • hi mate,
      you ot a broekn firmwaer on your receiver. you need to run the hardwaer- based emergency update to get it back working

  10. My TX finds the receiver and ask to update. I press Ok, but then it stays at Preparing receiver. And the light on the receiver blinks every 12 -13. I tried to fix it with the emergency updaten, but it didn’t work.

    • hi oela,
      there is a little chance you might don’T need it. a post i found on faceboook mentionet that this might(!) solve it:
      – start the bindin,
      – disconnect the rx immetiadely from the battery
      – pulug it back it
      – now it should finish the binding/ updating or re-bind as usual

  11. aaaaaaaaaaaaaaaaaaaah men this sucks big time! Could TBS not add a warning on the packaged not to update it with the old firmware!! Now it won’t bind and update the new firmware. It automatically updated it with the old firmware on my TX crossfire module. Now I need to spend extra money to fix it with a TBS Core Pro/ FPVision or a standard Diversity Rx. WAsted 60euro!

  12. I screwed up a nano diversity and bought the TBS CORE Pro, and have tried to fix it but have had no luck. I have tried everything above. I have swapped scl and sda but no luck. Anything else I could Try?

  13. Hi,
    When updating my Crossfire Tx from 2.24 to 3.23, the update process halted on „Writing Update“ and the transmitter continued to flash green.
    I unplugged the USB from the transmitter after a few hours and now when the transmitter is powered on, it flashes green as if it were updating and shows no text in the display.
    The Agent X can recognize the device, but shows the version as 0.00 and doesn’t attempt to flash any software.

    Is there an emergency update procedure for Crossfire tx?

  14. Thanks so much for this! I had accidentally bricked a brand new crossfire nano by unplugging power during the update (misinterpreted the micro tx LED colors). This worked – but one note, after releasing the button the second time, the green LED kept flashing fast and then went dark rather than flash slowly, so I was worried it didn’t work. But after about 20-30 seconds it started to flash slowly, and success!

  15. I just want to know whats up with the nano rx losing the bind and not wanting to respond to the bind button. I managed to get it working with the hold when power on then release for 2 seconds then hold till double blink stops but still a pain

    • sounds like your receiver is broken. check for some missing smd-parts. might you find a empty spot. if so -> contact the tbs customer service and they’ll tell you which part you need to replace it

  16. Hi.
    After Binding and updating my diversity nano rx, the rx goes back to bind mode again. Transmitter first says „update ok“, then it looses the connection. Bindbutton is not pressed. Whould this emergency update work to solve this problem?

    • hi jace,
      sadly no – as he never send me a video or something. but i guess the fw file is corrupted – soul i ave to go with the core pro/ fpvision flashing method


    Push and hold the button again
    The green led starts to flash in a double-pattern. When it starts to flash rapidly again, you can release the button
    Rx goes straight into solid green light after a double pattern. I am extremely frustrated having the day ruined by hours of tries to run my quad.

    • hi,
      could you send me a video with the beahvior of your revceiver by mail? this way i can help you and maybe forward it to remo (tbs software dev)

  18. hello, I tried updating my micro diversity through the core pro bst and agent x with no success. on agent x I can only update to FW 2.07 beta and you say I need to be at least FW 2.09 for the core pro, what do I do? I also noticed your bst pinout for the cable is different from the tbs manual. is that correct?\

    • hi joe,
      you are right – i got the scl and sda twisted. i’ll update it asap.
      The fw version was related to the fpvision. just use the latest (beta) version for the device to be safe.

  19. hi. tell me please. I accidentally updated diversity nano rx through agent 2.4. now there is no bind. agent “x” has updated the transmitter to tbc. but there is no way to connect it. I am from Russia, no one has core pro / fpvision here. There may still be restart options. The option with clamping and fast blinking did not help.

    • hi artyom,
      sadly there is no chance without a core pro etc to get it back working.
      you can try to bind(with fw 3.9x or later) and as soon as the receiver will connect – unplug the rx battery. now retry. this CAN save it. but at the end of the day you’ll need a core pro etc to get it back. maybe you can finde one on ebay or cheap or send the rx back to your shop

  20. I had success with the emergency process update in a Micro RX V2 (couldn’t update by OTA at all), but no success with a nano diversity, I binded using version 2.24 in my transmitter, now it‘ is bricked forerver, could you help me please ?

    • hi allan,
      in your case you need a core pro/fpvision/standard div. rx to get it back working.
      if your agent x (not the old one!) runns straight throu the update of the usb device, try swapping scl and sda

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht.