Quattro 48/10000 failure during firmware update / VRM rescan — only DC connected, no AC input/output

Had something similar happen with my Victron setup last year — not a Quattro but a MultiPlus-II 48/5000, so slightly different beast, but the same kind of sinking feeling when a firmware update goes sideways.

I was doing a VRM rescan with only DC connected (batteries, no AC in or out), which I thought was the "safe" way to do it. Unit went unresponsive mid-update, VE.Config couldn't see it, and VRM just showed it as offline. Genuinely thought I'd bricked it.

Few things that actually helped in my case:

• Hold the power button for a forced restart — sometimes it recovers to bootloader mode
• Try VE.Bus via MK3-USB directly rather than relying on Cerbo GX during recovery
• Fogstar had nothing to do with it obviously, but worth checking your BMS isn't cutting DC during the process — mine was set quite aggressively and I wonder if a brief undervoltage event triggered the issue

The Quattro 48/10000 is a serious bit of kit so I'd be surprised if it's truly dead — these things are usually more resilient than they appear when bricked. Victron's support forums (and emailing a UK distributor like Bimble Solar or Powerplus Energy) can sometimes get you a recovery firmware file if standard routes aren't working.

Has anyone here actually managed a full recovery from a failed Quattro firmware update? Curious whether the 10000 model has any specific quirks around this — I'm planning to eventually upgrade from my MultiPlus-II so this is relevant to me too.

RobRobinson78 | 847 posts | ⚡ Solar Enthusiast

@GemmaCooper86 That sinking feeling is genuinely awful, especially when you're mid-update and everything just... stops responding.

One thing worth trying if you haven't already — Victron's VictronConnect has a built-in recovery mode specifically for bricked firmware situations. Hold the rocker switch on the unit itself while connecting via VE.Direct, and it should boot into a minimal recovery state that lets you push fresh firmware without needing VRM at all.

Also worth noting with the Quattro specifically — because it's a larger unit it sometimes needs longer after power cycling before VictronConnect will detect it properly. Give it a full 60 seconds completely dead before reconnecting.

Have you raised a ticket with your Victron dealer rather than going direct? In my experience the distributors have quicker access to technical support for these edge cases.

Nessa | 312 posts | 🔋 Off-Grid Advocate

@GemmaCooper86 Welcome to the forum — glad you found us, and sorry it's under these circumstances!

One thing worth checking that often gets overlooked during a failed firmware update on Victron units: the VE.Bus BMS state. Even with no AC connected, a partial flash can leave the unit in a confused state where it won't respond normally to VictronConnect.

If you haven't already, try forcing a recovery flash via the MK3-USB interface rather than Bluetooth — it's far more reliable for bricked units. Victron's VE Flash tool on Windows specifically handles partial firmware scenarios.

Also worth checking your VRM portal for any last-known fault codes before it went silent — sometimes there's a clue in the historical data.

What firmware version were you attempting to move from/to?

QuietTrekker | 1,204 posts | ☀️ Solar Tinkerer

Had this exact thing with a Quattro last spring. When it's mid-update and goes unresponsive, don't power cycle it — that's the killer move that bricks them properly.

If VRM shows it offline but DC is still connected, try the VE.Bus System Configurator via a MK3-USB adapter rather than relying on VRM to recover it. Sometimes the firmware's partially flashed and the local interface can still reach it when remote can't.

Victron's \--force flag in VE Flash is worth knowing about for stubborn units.

Also worth checking:

• Battery voltage is solid (low voltage mid-flash = corruption)
• Fogstar or whoever supplies your cells — confirm BMS isn't throttling under load

If nothing works, Victron UK support are actually decent. Had a replacement sorted within the week last time.

SussexBoater | 203 posts | ⛵ Floating Off-Gridder

@GemmaCooper86 The Victron MK3-USB interface and a copy of VE.Flash have resurrected more "bricks" than I care to admit — on the boat we treat it as standard post-update procedure now, same as putting the kettle on.

Key thing nobody's mentioned yet: make sure your battery voltage is rock solid before attempting a recovery flash. I once spent an hour troubleshooting what turned out to be a sagging 48V bank confusing the bootloader — embarrassing doesn't cover it.

If VE.Flash won't even see the unit, try the Victron recovery firmware page — there are specific .vff files for forced recovery mode on the Quattro range that bypass the normal update path entirely.