X12s Bricked?

[plane_tech]

I recently picked up a used X12s radio as a backup for my main radio. As I was wanting this to be a "clone" of my existing radio, I tried to update the Firmware to the lasted release from OpenTx (2.3.15). After the initial attempt, it was displaying "Wrong PCB Detected". While trying to research what this was, I tried a couple different methods of updating the firmware, Using Companion, loading through USB cable, and finally the Bootloader. During the bootloader attempt, the status bar on the screen froze for at least 20 minutes then the radio shut off. Thought it might have been a dead battery, but after sitting on charge all day, it is still unresponsive.
Now nothing happens when I plug in the USB. Power will not turn on at all, nor will it go into bootloader mode by holding the trim switches inward while powering up.
Are there any options of restoring this? Would I need to replace the Motherboard, if I can find one?
Or is it a paperweight?

Thanks in advance for any help.

 

[HENNY]

I recently picked up a used X12s radio as a backup for my main radio. As I was wanting this to be a "clone" of my existing radio, I tried to update the Firmware to the lasted release from OpenTx (2.3.15). After the initial attempt, it was displaying "Wrong PCB Detected". While trying to research what this was, I tried a couple different methods of updating the firmware, Using Companion, loading through USB cable, and finally the Bootloader. During the bootloader attempt, the status bar on the screen froze for at least 20 minutes then the radio shut off. Thought it might have been a dead battery, but after sitting on charge all day, it is still unresponsive.
Now nothing happens when I plug in the USB. Power will not turn on at all, nor will it go into bootloader mode by holding the trim switches inward while powering up.
Are there any options of restoring this? Would I need to replace the Motherboard, if I can find one?
Or is it a paperweight?

Thanks in advance for any help.

This happens when you flash the radio with the wrong version of firmware. Are you sure you used the X12S version and not the TX12 version. There are many choices in the 2.3.15 list.

 

[MikeB]

What happens if you plug the USB in with the power OFF? You should see a STM bootloader device on your computer.

Mike

 

[plane_tech]

Reply

This happens when you flash the radio with the wrong version of firmware. Are you sure you used the X12S version and not the TX12 version. There are many choices in the 2.3.15 list.

I will double check that, but I believe it was the same firmware that I used on my other X12 that does not have an issue.

What happens if you plug the USB in with the power OFF? You should see a STM bootloader device on your computer.

Mike

Nothing. Black screen and the computer does not recognize a USB device as being plugged in.

 

[Wayne]

Please look at the back or bottom of the radio. Does it have engraving that says something like Developer version? If so, it is a paper weight. That would be a prototype and FrSky made MANY changes to the radios after those were sent out. We have several of them here. (If anyone wants a collectors edition radio, not for flight let me know).

If it is a normal X12S, then you should be able to unbrick it. You may need to try another PC, but like Mike said, power off on the transmitter to replace the bootloader on it. We would see this little game on the X12S from time to time.

 

[plane_tech]

Please look at the back or bottom of the radio. Does it have engraving that says something like Developer version? If so, it is a paper weight. That would be a prototype and FrSky made MANY changes to the radios after those were sent out. We have several of them here. (If anyone wants a collectors edition radio, not for flight let me know).

If it is a normal X12S, then you should be able to unbrick it. You may need to try another PC, but like Mike said, power off on the transmitter to replace the bootloader on it. We would see this little game on the X12S from time to time.

There is nothing on the back of the radio. I did get another computer to recognize that something is plugged in ... just not sure how to proceed now that I got that far.

After plugging it into the new computer, trying to read the firmware and models, I get the following error messages.


Any suggestions?

 

[Wayne]

I think we are in agreement that something has gone wrong, and the wrong bootloader and or firmware have been injected into the radio. So trying to read what it there is of no value. Assume it is bad, and replace it with the CORRECT version. Triple check your settings in Companion and brun the correct data into the radio with the power turned off on the radio. This will replace the firmware and the bootloader.

Anyone else reading this, please let me know if anything stated above is not correct.. I have been away from Companion for a few years now and may be getting rusty.

 

[plane_tech]

Well... I gave that a try... doesn't seem to want to respond. Maybe I am missing a step somewhere?

 

[plane_tech]

So I need to amend my early statement. While the computer recognizes something has been plugged it, it is not seeing anything attached to the USB port.
So... I am back to the drawing board.
At this point, am I looking at just replacing the main board?

 

[jure]

@plane_tech , where are you located ? Maybe someone close to you could give you a hand ...

 

[Chris]

This might be the old USB driver problem. Your radios usb firmware is too old for your computer. You might have to run Zadig in order for your computer to see it. In that case once you run Zadig your computer will see the drives and you can go from there... I havent had to do this in a couple years so the details are quite fuzzy. I am sure there is info on this out there.
Not a guarantee, just a thought...

 

[Wayne]

Another option would be to send this into FrSky in Brea California. They are the FrSky service center and should be able to get the firmware installed and working for you.

 

[plane_tech]

Another option would be to send this into FrSky in Brea California. They are the FrSky service center and should be able to get the firmware installed and working for you.

Wayne -
That is were I am at. I had posted a question to the tech support email and they suggested to start on the forums and and see if there was an easy fix I could do here.
I will be reaching out again to see about sending this back in if I can't find anyone local to assist.

 

[plane_tech]

For anyone else that happens to find themselves in this situation, the fix is to load the firmware thru the DFU mode. Joshua Bardwell has a great video on how to do it.