What's new
Aloft Forums

Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

X20S Unable to get Internal Module Information

Nimbus

New User
So I finally decide to update my X20S. I used the enter/power combo to enter bootloader, plug in USB and Ethos Suite (1.6.3) identifies the radio and needed updates. I tried updating all but was told it needed to flash the internal module. Selected the most recent version and started the flash, then I get the message waiting for bootloader and that's as far as it got. Followed the instructions and neither the enter/power method nor selecting ethos suite from the menu let the Suite see the bootloader. Windows shows Unknown USB Device (Device Descriptor Request Failed). Clicked cancel at that point and after that had a heck of a time just getting the Suite to recognize the radio. When I plug in USB the FLASH drive appears momentarily then disappears and device manager goes back to Unknown USB Device. Ethos Suite never identifies the radio. After uninstalling and reinstalling Ethos Suite a few times I hit the proper phase of the moon for the Suite to see the radio but now when I try to update the internal module all I get is Unable to get Internal Module Information.

Current version info (if it helps)
Firmware- 1.4.7 FCC
Bootloader- 1.4.3

Suggestions?
Thanks in advance,
: Dan

PS: FWIW, went to an older Win 10 PC and still get Unable To Get Internal Module Information. With the same USB issues.
 
Last edited:
So I finally decide to update my X20S. I used the enter/power combo to enter bootloader, plug in USB and Ethos Suite (1.6.3) identifies the radio and needed updates. I tried updating all but was told it needed to flash the internal module. Selected the most recent version and started the flash, then I get the message waiting for bootloader and that's as far as it got. Followed the instructions and neither the enter/power method nor selecting ethos suite from the menu let the Suite see the bootloader. Windows shows Unknown USB Device (Device Descriptor Request Failed). Clicked cancel at that point and after that had a heck of a time just getting the Suite to recognize the radio. When I plug in USB the FLASH drive appears momentarily then disappears and device manager goes back to Unknown USB Device. Ethos Suite never identifies the radio. After uninstalling and reinstalling Ethos Suite a few times I hit the proper phase of the moon for the Suite to see the radio but now when I try to update the internal module all I get is Unable to get Internal Module Information.

Current version info (if it helps)
Firmware- 1.4.7 FCC
Bootloader- 1.4.3

Suggestions?
Thanks in advance,
: Dan

PS: FWIW, went to an older Win 10 PC and still get Unable To Get Internal Module Information. With the same USB issues.
Ok you are on a much older version of Ethos on your radio.

Just to confirm Ethos for your radio is called Ethos and the Ethos Suite for your computer probably has a slightly different version number. Don,t confuse this as they are two completely different software versions. Ethos is for your radio X20S, Ethos Suite is for your laptop.
You need to update the bootloader manually to version 1.4.15. Get to this site https://github.com/FrSkyRC/ETHOS-Feedback-Community/releases and scroll down till you see Version 1.4.15. Download the bootloader for your radio. V1.4.15, then copy this to you radio SD card root directory. Then start you radio normally ( Not in bootloader Mode) and go to SYS and navigate to the bootloader file you just copied and install it on your radio.

From here on in the updates happen automatically as long as you have Ethos Suite version v 1.6.2. Once you have this do the following.
Start Ethos Suite ensure the version number is 1.6.2 displayed top right of the Ethos Suite screen. If not it will ask you do you want to update it.

Then power your X20S radio normally, (NOT in Bootloader Mode.) plug in the USB cable, if all is working a USB icon appears on your radio screen. Also Ethos suite will display your radio type under the Welcome Update news text top right of the Ethos Suite screen. Under radio Information click on Ethos. The screen will display up to date files in green of out of date in yellow. Then click WRITE OUTDATED COMPONENTS. This will also include any Bootloader updates in the future.

Once this is complete next under the Ethos bar there is RF MODULE click on this to update your internal module.

All these updates are now part of Ethos Suite functionality.
Cheers Henny
 
Last edited:
Thanks Henny,

I understand the diff between Ethos and Ethos Suite. 1.6.3 is the version of suite I downloaded here - https://ethos.frsky-rc.com/#ethossuite

I got bootloader 1.4.15 installed but Suite still failed to connect to the radio most times.

When I can get Suite to see the radio it can now read the module info, but flashing the update is still a problem. Either it fails again to find the bootloader (I think the message preceding this was something like entering media mode ?) Then it just hangs looking for the bootloader and none of the methods of putting the radio into bootloader get me past this. Once I did actually get it to the Flashing screen but I let it sit on that display for about 15 minutes before deciding it wasn't doing anything.

I think the root of my problem is the radio seems to change modes during the process. Suite loses connection then and never reconnects.

However, after fighting this for longer than I want to confess, I finally thought to try a Win10 PC again with the updated bootloader. Ethos Suite identified the radio first time and all updates installed with zero issues.

I guess I jinxed myself. When I first launched Suite and it prompted me for the updates I thought, this is so easy why did I wait so long. Moments after that is when the problems started. :)

The Upgrade Ethos Firmware docs linked to on the page where I DL'd Suite 1.6.3 said I needed bootloader 1.2.10 or higher so I thought I was okay there. But the bootloader update and not using Windows 11 was the fix.

Thanks again for your assistance.
: Dan
 
Last edited:
Back
Top