TBS Crossfire Nano RX won't bind (Reload Crossfire FW in AgentX)

Brand new Nano rx won't bind. This video walks through the situation and all of the steps I've taken to try and solve.
1. Binding with lua script on TBS Micro Tx in Frsky Tx results in blank screen
2. Binding with lua script on Tango 2 XF, results in error in title (flashing red & green)
3. Try to connect Nano Rx to Agent X, but is never recognized through my flight controller (is some additional a adapter a must?)
5. Binding with Agent X through Tango 2 XF, results in error in title (flashing red & green)
6. Binding with Agent M through Tango 2 XF, same result.
Is this Nano Rx not DOA?... It has surely wasted hours of my life!!
Please leave comment. I'll add the solution and an additional video if I get a solution that actually works.

[@tinakatharina177]

Got it working! :)) Seems you have to get firmware V 6.10 on the TX (with Agent X) and then use Agent M (not Agent X) to RELOAD the firmware (V 6.10). Then, when trying to bind with this firmware in Agent M it will allow updating of the nano rx and they will finally bind! At least this worked with our hardware (TBS micro TX V2, nano rx, Agent M was used on a Mac with the Chrome browser).

[@trevorc6793]

Just to add, thank you both Tina and Steve - you're sanity savers!. I've been so frustrated with trying to bind this and have a stable connection when binding was finished. In the end I updated both the Tango2 & then the Tango2 XF using Agent M only.. it worked, I nearly started to change everything over to ELRS...

[@fishbone470]

Works!! Thank You Tina! for the group I have a Tarranis Xlite Pro and the mini TX module. I updated to 6.10 FM on Agent X then ran the same firmware update on Agent M. When completed went to bind and it updated the Rx firmware. after the update the Rx light did stay red.. but when I went back to the main menu the light went green!! Spent weeks on this.. finally working!!

[@lewyfpv]

Just got same issue. Solution for me was simple - just update TBS Agent X to newest version :)

[@jimross898]

Thank you for asking this question and for the community to figuring out the solution. A bit astounded there's no documentation on this from TBS. Crickets. Sounds like between us, we have tens or hundreds of hours spent on this. I've spent 4 on and off over the last 5 days. Come on TBS. Fess up and make this easy for people.

[@andresbelloni7769]

Thank you Tina! The trick is to use Agent M (not Agent X) to load the firmware on the TX. Same set up, using Agent M on a Mac Mini with Chrome browser. The RX did not bind at the end of the process but then power off and power on again and it finally did bind. I spent so many ours on this. Thanks!

[@BrodieReed]

Can confirm that Tinas comment is exactly what worked! Sad that this is an issue needing to be dealt with for a Bind n Fly...

[@taylanator2000]

I followed the comments below - re-installing V6.10 via agent M, it then froze up at last binding step, so I had to unplug, restart and it worked!

[@ghettogardens1]

This worked for me. Upgrade your TBS crossfire firmware to v6.12 and everything will work like it should. V6.10 firmware does not solve the problem, you will get the same "reload crossfire FW in Agent X" warning. The only down side is, that you have to upgrade the firmware on all of your crossfire drone receivers (which is done automatically when turn on the drone) and rebind to the transmitter. Anyway, it's worth a try. Good Luck!

[@KLNYC]

same here with newer nano rx. works flawless with my 2 years nano rx ..

[@olacsiveron9479]

TINA YOU SAVED ME!

[@hikingfpv4341]

I got the same problem and struggle for 3 weeks. I had fixed it yesterday. The only problem is that after updating the firmware, you have to refresh the firmware by clicking the "Refresh" icon. Then, everything go smooth.

[@kerick9282]

hi, also had the problem on my 2 new Nano RX , solved with version 6.10 but

[@waynelangston9567]

What size of power supply to chartreuse the dx3 do I need

[@djilly75]

Ok so what do I do on a qx7 doing that

[@rolandlyons4565]

reloading firmware in agent m kinda worked for me. it hung up at the end of the bind and I unpluged and replugged and it bound. not sure if I trust it

[@BOOST_FPV]

6.12 worked fine in Agent X without having to go through Agent M.

[@abieazki]

it's work

[@waynelangston9567]

Charger the power supply what size do I need

[@julianodesouzamsouza1715]

Estava com o mesmo problema.