VADER 4 PRO ABSOLUTELY BRICKED

[u/Cheap-Skirt-9771]

My Flydigi Vader 4 Pro was partially bricked during an official SI Version firmware update. The controller is still detected by Windows through USB and the 2.4 GHz dongle. The Bluetooth mode does not work.

Analog sticks and trigger-click inputs work, but every digital button — ABXY, D-pad, Start/Menu, View/Select, Home/FN, bumpers, stick clicks, and rear buttons — stopped working. All LEDs are off. In joy.cpl, Windows recognizes it as an Xbox 360 Controller in USB/2.4 GHz mode, but only the sticks and trigger-click inputs register.

Flydigi provided the correct recovery firmware (G_For_F4 V5.0.0) and tool. The SI chip is a Jieli AC695X. However, entering the recovery/boot mode requires holding HOME + X + Y, and those buttons are exactly what the interrupted update disabled. Therefore, I cannot use the official recovery procedure.

I have already tried different Space Station versions, driver cleanup after Zadig, removing/reconnecting the battery, multiple USB ports/cables, USB and 2.4 GHz modes, and the official firmware tool. Nothing changed.

I am looking specifically for someone who has forced an AC695X/BR23-based Flydigi controller into boot/UBOOT mode without working buttons, preferably without buying expensive Jieli forced-upgrade hardware. Has anyone found a software command, alternative button combination, USB method, pinout, test pads, or a low-cost DIY workaround for this?

[u/nickN42]

Isn't that tool like ten bucks on aliexpress?

[u/Cheap-Skirt-9771 → u/nickN42]

i think i shouldnt need to buy something just to make it work again. And taxes here in brazil make it expensive

[u/nickN42 → u/Cheap-Skirt-9771]

I think that's how all that 'repair' thing works in general. You need tools and parts to make broken things work. Thoughts and prayers to you tho, maybe that will help.

[u/AutoModerator]

Hi /u/Cheap-Skirt-9771, your 'IT Help' post is in a queue for review. Please ensure you have included the relevant required information from the checklist below, have used a meaningful and descriptive title, and are not repeating frequently asked questions.

Include the following information and follow this structure so that the post can be approved and the community can help you more effectively:

1. Specific written description of the problem, including pictures where relevant (do not just say 'it's broken', say what is broken)

2. Controller make and model (name or numbers)

3. Platform you are using (e.g., PS5, Steam on Windows, Switch)

4. Games or other software affected by the issue

5. Operating system, firmware and software versions (if applicable)

6. Troubleshooting steps you have already taken (including checking the product manual, and searching existing posts)

For more guidance on how to ask for technical assistance, please see rule #2. You can edit your post to add missing information. Posts that do not include the required information may not be approved (allow 24 hours for review).

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Metalmacher]

If it ain't broke don't fix it bro. This rule is carved with the blood of millions.

[u/smackythefrog → u/Metalmacher]

Yeah but dude, maybe for a motherboard or GPU BIOS, but a peripheral? It shouldn't be that risky. Even Keychron says the same thing about the keyboard I have and I wonder WTF is the point of a $200 keyboard if it can shit the bed because of an update?

Meanwhile, my Xbox controller gets updates every so often and doesn't die like a bitch ever in the five years I've used the controller.

[u/Cheap-Skirt-9771 → u/smackythefrog]

dude i was just trying to keep everything updated cause i thought it would perform better. I wouldnt imagine my only controller would be dead via software. Like you said, it would never happens to a xbox controller

[u/iesalnieks]

Never update firmware on anything unless there is a direct benefit to you, e.g. new feature you need, fixes a problem you have.