Finally, Inspire 1 firmware/video feed issues explored in depth...

[inspireengineer]

That is their PUBLIC position. I'd bet a year's salary that there is a way around this either via a hack or a back door file. Try the gs_ofdm.bin file and see if that works. Please report back your findings.

Best of luck!

Thanks for all the follow-up help with this issues guys!
Donnie found the solution (which he predicted was there):
It appears the 1.11 version of the Inspire Firmware did not allow downgrading by default as previous iterations did.
However, there is a workaround.
Simply create an Empty File with no extension with the name:
For X5R camera - WM610_FC550R_FW_DEBUG
For X5 camera - WM610_FC550_FW_DEBUG
For X3 camera - WM610_FW_DEBUG

Place the empty, extensionless file along with the desired Firmware Downgrade .bin file onto the MicroSD card and wait 40 minutes for the downgrade. The other cool feature of this DEBUG hack is the ability to downgrade multiple versions at once. So you can take your Inspire from FW1.11 straight to 1.08 in a single go.

Hope Donnie's work here helps some others!

 

[Donnie Frank]

Thanks for all the follow-up help with this issues guys!
Donnie found the solution (which he predicted was there):
It appears the 1.11 version of the Inspire Firmware did not allow downgrading by default as previous iterations did.
However, there is a workaround.
Simply create an Empty File with no extension with the name:
For X5R camera - WM610_FC550R_FW_DEBUG
For X5 camera - WM610_FC550_FW_DEBUG
For X3 camera - WM610_FW_DEBUG

Place the empty, extensionless file along with the desired Firmware Downgrade .bin file onto the MicroSD card and wait 40 minutes for the downgrade. The other cool feature of this DEBUG hack is the ability to downgrade multiple versions at once. So you can take your Inspire from FW1.11 straight to 1.08 in a single go.

Hope Donnie's work here helps some others!

Well this is great news! GREAT JOB with the follow up and research. That said....

I have an odd question for you. As much as I've been told to "create an empty file," I assume this can be done with Notepad, yes? Simply strip the .txt extension? OR...do I need to empty a .bin file of its contents, and then rename it without the .bin extension? OR...is there another way?

 

[inspireengineer]

Well this is great news! GREAT JOB with the follow up and research. That said....

I have an odd question for you. As much as I've been told to "create an empty file," I assume this can be done with Notepad, yes? Simply strip the .txt extension? OR...do I need to empty a .bin file of its contents, and then rename it without the .bin extension? OR...is there another way?

Personally my file manager has an option to 'Create New File' which is what I used. However, creating a .txt file and removing the .txt extension should work just as well. On Windows just make sure you have the option to show file extensions enabled.

The only glitch I experienced is that even after waiting a full 1hr, the Firmware update beeps never quit. Also the Result.txt file never gave the 'successful' confirmation. All I ever saw was 'Upgrading...." However, when checking the current firmware in the App it appears to be back to 1.08, down from 1.11 which I hated.

Here's the output in from the Micro SD.

========== 2014.01.01 00:00:05 remo-con disconnect======
Packet: WM610_FC550R_FW_V01.08.01.40.bin
Upgrading ...

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: WM610_FC550R_FW_V01.08.01.40.bin
Upgrading ...

========== 2017.10.05 21:48:54 =====================
Packet: WM610_FC550R_FW_V01.08.01.40.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

In the final ABORT message, I had removed the DEBUG file from the card leaving only the .bin firmware.

 

[Steve-O]

Donnie/Et al.,

I tried the downgrade on my used purchase after working through logistical issues to get the right files. The bird goes through its update process all the way through the motors updating, camera moving, fans shutting on-off, etc. After about 1.5 hours the beeping sound goes to firmware fail (D-D-D-D-D-D-D-D-D-D-D-D-D...….). I have tried it from 1.11 to 1.08, 1.11 to 1.09 and 1.11 to 1.10. I even got a fully charged battery and let it go till shutoff and the D-D-D-D-D-D-D-D-D-D-D-D... And the beeps never transitioned. After the failed updates, I checked the FW Log and it shows only the 1500 device not detected (see below). I am not getting the 0800 device not failed. the update always fails at 1900.

the FW Result never transitions out of "Upgrading".

Anyone seen this? I am fully prepared for the "you effed up the downgrade...send it in"!!

I am guessing send it in, but wanted to check with the gray beards to see if anyone had any suggestions.



FW RESULT AB

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: WM610_FC550_FW_V01.08.01.00.bin
Upgrading ...
========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: WM610_FC550_FW_V01.10.01.40.bin
Upgrading ...
========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FC550_FW_V01.09.01.30.bin
Upgrading …


FW Log AB

[01625706]Version checking[3]...
[01625791][04 00][05] v1.30.1.28 -> v1.30.1.28 need upgrade.
[01625887][08 00][05] v2.14.9.42 -> v2.14.9.42 need upgrade.
[01625956][01 00][05] v1.29.5379 -> v1.29.5379 need upgrade
[01626025][01 01][05] v1.29.5379 -> v1.29.5379 need upgrade
[01626113][01 04][05] v0.5.5085 -> v0.5.5085 need upgrade
[01626239][03 05][05] v34.1.0.5 -> v34.1.0.5 need upgrade.
[01626349][03 06][05] v2.4.20.28 -> v2.4.20.28 need upgrade.
[01626468][05 00][05] v3.0.6.2 -> v3.0.6.2 need upgrade.
[01626553][09 00][05] v3.1.0.0 -> v3.1.0.0 need upgrade.
[01626668][11 00][05] v3.9.0.0 -> v3.9.0.0 need upgrade.
[01626788][12 00][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01627029][12 01][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01627168][12 02][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01627348][12 03][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01631850][15 00][06] device not detected.
[01631954][17 00][05] v1.1.0.8 -> v1.1.0.8 need upgrade.
[01632089][17 01][05] v2.0.1.6 -> v2.0.1.6 need upgrade.
[01632178][19 00][00] v0.0.0.0 -> v1.0.8.96 need upgrade.
[01632254]Done.
[01632331]Firmware upgrading[3]...
[01634657][19 00] Firmware upgrade start...
[01745759][19 00] Firmware upgrade finish failed (step = 4, err = 0xaa, idx = 4342, los = 1, ng = 0, usb = 1).
[01755830]Done.

 

[Donnie Frank]

Donnie/Et al.,

I tried the downgrade on my used purchase after working through logistical issues to get the right files. The bird goes through its update process all the way through the motors updating, camera moving, fans shutting on-off, etc. After about 1.5 hours the beeping sound goes to firmware fail (D-D-D-D-D-D-D-D-D-D-D-D-D...….). I have tried it from 1.11 to 1.08, 1.11 to 1.09 and 1.11 to 1.10. I even got a fully charged battery and let it go till shutoff and the D-D-D-D-D-D-D-D-D-D-D-D... And the beeps never transitioned. After the failed updates, I checked the FW Log and it shows only the 1500 device not detected (see below). I am not getting the 0800 device not failed. the update always fails at 1900.

the FW Result never transitions out of "Upgrading".

Anyone seen this? I am fully prepared for the "you effed up the downgrade...send it in"!!

I am guessing send it in, but wanted to check with the gray beards to see if anyone had any suggestions.



FW RESULT AB

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: WM610_FC550_FW_V01.08.01.00.bin
Upgrading ...
========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: WM610_FC550_FW_V01.10.01.40.bin
Upgrading ...
========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FC550_FW_V01.09.01.30.bin
Upgrading …


FW Log AB

[01625706]Version checking[3]...
[01625791][04 00][05] v1.30.1.28 -> v1.30.1.28 need upgrade.
[01625887][08 00][05] v2.14.9.42 -> v2.14.9.42 need upgrade.
[01625956][01 00][05] v1.29.5379 -> v1.29.5379 need upgrade
[01626025][01 01][05] v1.29.5379 -> v1.29.5379 need upgrade
[01626113][01 04][05] v0.5.5085 -> v0.5.5085 need upgrade
[01626239][03 05][05] v34.1.0.5 -> v34.1.0.5 need upgrade.
[01626349][03 06][05] v2.4.20.28 -> v2.4.20.28 need upgrade.
[01626468][05 00][05] v3.0.6.2 -> v3.0.6.2 need upgrade.
[01626553][09 00][05] v3.1.0.0 -> v3.1.0.0 need upgrade.
[01626668][11 00][05] v3.9.0.0 -> v3.9.0.0 need upgrade.
[01626788][12 00][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01627029][12 01][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01627168][12 02][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01627348][12 03][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01631850][15 00][06] device not detected.
[01631954][17 00][05] v1.1.0.8 -> v1.1.0.8 need upgrade.
[01632089][17 01][05] v2.0.1.6 -> v2.0.1.6 need upgrade.
[01632178][19 00][00] v0.0.0.0 -> v1.0.8.96 need upgrade.
[01632254]Done.
[01632331]Firmware upgrading[3]...
[01634657][19 00] Firmware upgrade start...
[01745759][19 00] Firmware upgrade finish failed (step = 4, err = 0xaa, idx = 4342, los = 1, ng = 0, usb = 1).
[01755830]Done.

Based on the data here, it looks like you're trying to do this with an X5 camera. Unfortunately, rolling back via the X5 only works in theory. I have never actually rolled back an Inspire with the X5. That said, I have a friend with an X5, and we attempted to roll back his firmware several times to no avail. BUT...I believe his bird has other issues. It's in California being repaired as I type. We plan on trying the roll back again once the bird gets back. That said...

Do you have access to an X3 camera?? Unlike the X5, I HAVE had success with the X3. If you have access to an X3, you may have more success with that camera.

Please keep me informed.

D