Bricked EB3A just after opening

Product Discussion BLUETTI Elite & EB Series
41

I have been in the same situation and want to share the solution that helped me. After an unsuccessful firmware upgrade attempt, I connected the power cable to my Bluetti. Although it didn’t start charging, it enabled Bluetooth, allowing me to connect via the application and perform the firmware upgrade again. The second attempt was successful.

42

Thanks for sharing @iuv ! Hopefully this helps some people with their issue in the future

43

Hello everyone,

I’m writing this post because the situation with my Bluetti EB3A has reached the point of absurdity.

My EB3A completely died right after I tried to start the official firmware update through the Bluetti mobile app.
The update didn’t even begin — the unit just powered off and never came back to life:
no screen, no buttons, no charging, no Bluetooth, nothing.

This is a 100% firmware-level failure (soft brick), not a hardware defect. The MCU (STM32 / APM32) simply doesn’t boot or power the BLE module — a typical DFU recovery case.
However, Bluetti support keeps sending copy-paste replies, ignoring the obvious technical facts.

Here’s what happened:

  • Case opened → they said “engineers will push firmware remotely” (which is impossible because BLE is dead).
  • Then they claimed “hardware failure — buy a new unit.”
  • Now, after a week of silence, I’m still being ignored, even after providing the serial number, full description, and proof videos.

I’ve even told them I can perform a manual recovery via USB-C (DFU) if they provide the official recovery tool (EB3A_Recovery_Tool.exe + .bin file), which their engineers already used for similar cases — but no one wants to send it.

It’s disappointing to see a company that claims to be “industry-leading” treat firmware failures like this.
If you push a faulty update, you should at least provide users with a way to recover.

Ticket references:

  • EU support: #544693 (Austin) — closed with “hardware issue” excuse.
  • US support: #371705 — no action for days.

If any Bluetti staff or real engineer is reading this — please escalate this internally.
I just need the recovery package to reflash the unit via DFU, nothing more.

This post is for transparency, because I’ll be publishing a detailed write-up with all the screenshots and correspondence in my blog and technical communities soon, to help other users avoid the same nightmare.