Ring · firmware

Ring Battery Doorbell Plus firmware update is stuck or failed

Ring Battery Doorbell Plus firmware update is stuck or failed: power, network, storage, hub/controller and provider service should be stable. Scoped to 5F77E9, with the model boundary and safe stop points made explicit.

Direct answer

For the Ring Battery Doorbell Plus, power, network, storage, hub/controller and provider service should be stable. First, record current version, progress and exact indicator.

What this covers

  • Ring Battery Doorbell Plus (5F77E9)
  • Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
  • The specific fault this record addresses: firmware update is stuck or failed

What it does not cover

  • ×The same symptom on a different Ring product line, which has its own record and its own cited source
  • ×An on-screen error code whose meaning has not been checked against this exact model's manual
  • ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step

Differential

What actually causes this, and how to tell them apart

These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.

  1. 1

    The progress indicator is stalled, not the update

    What separates it The bar sits at a percentage for a long time while the device is otherwise normal. Verification and writing produce no visible progress and can take far longer than the download did.

    How to confirm Leave it alone for substantially longer than seems reasonable before acting. Almost every genuinely bricked device on this symptom was interrupted by someone who did not wait.

  2. 2

    The device sleeps before the update completes

    What separates it Updates fail repeatedly on a battery device and succeed when it is charging. Sleep is a power-saving behaviour that does not know an update is in progress.

    How to confirm Charge to full and keep it powered throughout. Several platforms will not begin an update below a charge threshold at all.

  3. 3

    Signal is adequate for control but not for a sustained transfer

    What separates it The device works normally, and updates fail at varying percentages. Control traffic is tiny and intermittent; an update is a large sustained transfer and needs a link that control traffic never tests.

    How to confirm Move the device close to the router or hub for the update. Failures at varying percentages point at the link; failures at the same percentage point at the package or storage.

  4. 4

    The provider is staging the rollout

    What separates it The device reports itself up to date on a version that is not the newest, and nothing forces it forward. Staged rollouts are normal and deliberate.

    How to confirm Compare the installed version against the provider's published current version and whether it is fully released. Waiting is the correct action.

  5. 5

    The device updated successfully and something else broke

    What separates it The update completed and a feature stopped. That is a regression rather than a failed update, and rolling back is usually not available.

    How to confirm Compare the behaviour against the release notes and report it. Repeated re-updating will not change a shipped regression.

Before you touch a setting

Record this first — changing settings destroys the evidence

Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.

  • The version installed now and the version being offered, both written down before anything is attempted.
  • The exact percentage or stage at which it stops, across several attempts. The same point every time and a varying point mean different things.
  • How long it has actually been sitting, measured rather than estimated — verification and writing produce no visible progress.
  • The battery level at the start of each attempt, and whether the device was on power throughout.
  • The signal strength the device reports for itself at its current position.
Try in this order0 of 6 completed
  1. Wait considerably longer than feels reasonable

    Reversible

    Verification and writing show no progress and can take far longer than the download. This is the one symptom on which impatience causes the damage — nearly every unrecoverable device on this fault was interrupted by someone who decided it had hung.

  2. Record the current version and the offered version

    Reversible

    Without both numbers you cannot tell a failed update from a staged rollout from a completed update that changed something. Write them down before the first attempt, not after the third.

  3. Put the device on power and leave it there

    Reversible

    A battery device may sleep partway through, and several platforms will not begin an update below a charge threshold at all. Charging throughout removes the whole class of failure rather than testing it.

  4. Move it close to the router or hub for the attempt

    Reversible

    An update is a large sustained transfer, and a link perfectly adequate for control traffic can be inadequate for it. Failures at varying percentages are this; failures at the same percentage are not.

  5. Retry through the official app only

    Reversible

    Never an unofficial package, a downgrade, or a file from anywhere but the manufacturer. A mismatched or modified image is the one thing that turns a recoverable failure into an unrecoverable one.

  6. Confirm the version and every core function afterwards

    Reversible

    An update that reports success and leaves a feature broken is a regression, not a completed job. Check the version number and exercise the things you actually use before considering it done.

Model-specific

What is true of this model and not of its siblings

Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.

Model scope
5F77E9. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
Video
1536p HD with Head-to-Toe view and colour night vision — the same vertical framing as the wired Pro models, on battery power.
Field of view
150° horizontal and 150° vertical. Zones drawn for a camera with a 57° vertical view will cover a small part of what this one actually sees.
Motion detection
Advanced Motion Detection with customisable zones. This is pixel-change analysis, not the radar-assisted 3D Motion Detection of the wired Pro models — which is why a subject approaching head-on is the hardest case for this model specifically.
Power
A removable, rechargeable Quick Release Battery Pack, included. It can additionally be connected to an existing doorbell system at 8–24 VAC, 50/60Hz, 5VA to 40VA. Ring's approved accessories are the DIN Rail Transformer (24Vdc, 420mA), the Plug-In Adapter (24Vdc, 500mA), the Solar Charger (5.2Vdc, 100mA or 109mA) and the Solar Panel (5Vdc, 380/480/800mA). Ring warns that incompatible power sources can damage the device and cause electric shock.
Wi-Fi
802.11 b/g/n at 2.4 GHz only. Unlike the wired Pro models in the same range, this one has no 5 GHz radio, so a phone on 5 GHz cannot hand it credentials during setup.
Bandwidth
Ring states a minimum upload speed of 2.5 Mbps for optimal performance — higher than the wired Pro's 2 Mbps, because the battery model has less headroom to fall back on.
Operating range
−20.5°C to 50°C, weather resistant. Battery capacity falls sharply toward the bottom of that range, so cold-weather runtime complaints are usually within specification rather than a fault.
Power path
Internal or removable battery. Every capability that costs current — night vision, higher stream quality, longer recordings, frequent events — is paid for in runtime, so a change in behaviour after a settings change is usually a power consequence rather than a fault. Cold weather reduces usable capacity sharply.
Siting
Rated for outdoor installation. Water ingress at the cable entry, corrosion at the contacts and temperature at the extremes of the rated range all present first as intermittent electrical faults, not as visible damage.
Service tier
Some capabilities are subscription-gated. A feature that stops working on a date with no other change is worth checking against the plan's renewal before it is treated as a fault.
Symptom boundary
This record covers Ring Battery Doorbell Plus when it firmware update is stuck or failed. A different symptom on the same hardware, or this symptom on a different Ring product line, has its own record with its own causes and its own cited source.

Stop boundary

When this stops being a self-service repair

Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.

  • !The device has been unresponsive since an interrupted update. Do not keep power-cycling it — that can compound a partial write. This is a support case.
  • !The update completed and a documented feature no longer works. Rollback is generally unavailable and repeated re-updating will not change a shipped regression.
  • !An update is failing on a device that is part of a life-safety or security function and has left it in a degraded state.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Where the manufacturer's article stops. Ring publishes this as "Information on Ring Devices Software Security Updates". Ring's article on how device firmware updates are delivered and applied. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and 5F77E9 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.

Exact questions

Common follow-ups

Can the Battery Doorbell Plus be hardwired?+

Yes, to an existing doorbell system at 8–24 VAC, 50/60Hz, 5VA to 40VA — note the 5VA lower bound, which is lower than the wired Pro models require. Hardwiring trickle-charges the pack rather than replacing it; the battery remains the device's power source and still needs to be healthy.

Does the Battery Doorbell Plus support 5 GHz Wi-Fi?+

No. It is 802.11 b/g/n at 2.4 GHz only. This is a real difference from Ring's wired Pro doorbells, which are dual-band — so advice that a Ring doorbell can use 5 GHz does not apply to this model, and a phone on 5 GHz will fail to hand over credentials during setup.

Which solar accessories are approved for this model?+

Ring specifies the Solar Charger at 5.2Vdc, 100mA or 109mA and the Solar Panel at 5Vdc, 380mA, 480mA or 800mA. Ring warns that incompatible power sources can damage the device and cause electric shock, so this is one of the places where a generic third-party accessory at the right nominal voltage is genuinely not equivalent.

How much upload speed does the Battery Doorbell Plus need?+

Ring states 2.5 Mbps for optimal performance — more than the 2 Mbps quoted for the wired Pro. A battery device throttles its radio to protect runtime and so has less margin, which is why the same connection can be adequate for a wired Ring doorbell and marginal for this one.

Why does it miss people walking straight toward the door?+

This model uses Advanced Motion Detection — pixel-change analysis — rather than the radar-assisted 3D Motion Detection in Ring's wired Pro doorbells. Head-on approach changes the fewest pixels, so it is the hardest case for this model in particular. Aiming zones across the approach rather than along it is the fix available here.

Is the battery removable?+

Yes — it is a Quick Release Battery Pack, so it can be charged indoors while the doorbell stays mounted, and a second pack removes the downtime entirely. That is a meaningful difference from Ring models with an internal battery, where the whole device has to come down to charge.

What temperature can it work in?+

−20.5°C to 50°C, weather resistant. Usable battery capacity falls sharply toward the cold end, so runtime that collapses in a cold snap and recovers afterwards is the battery behaving as expected rather than failing.

The update has been at the same percentage for a long time. Should I restart it?+

Almost certainly not. Verification and writing produce no visible progress and routinely take much longer than the download. This is the symptom where intervening causes the damage — nearly every unrecoverable device on this fault was interrupted by someone who concluded it had hung.

How long is too long?+

Longer than you think, and the honest answer depends on the device — but the asymmetry is what matters. Waiting an extra hour costs an hour. Interrupting a write costs the device. Given that trade, wait.

The update keeps failing at a different percentage each time.+

A varying failure point is the network. An update is a large sustained transfer, and a link that is fine for control traffic can be inadequate for it. Move the device close to the router for the attempt. A failure at the same percentage every time would point at the package or at storage instead.

It will not start the update at all.+

Check the charge level and whether it is on power. Several platforms refuse to begin below a threshold, and a battery device that sleeps partway through will fail repeatedly until it is charging throughout.

My device says it is up to date but there is a newer version.+

Staged rollouts are normal and deliberate — the provider releases in waves. The device is behaving correctly, waiting is the right action, and there is generally no supported way to force it forward.

Can I install firmware from somewhere else?+

No. A mismatched or modified image is the single most reliable way to turn a recoverable failure into an unrecoverable one, and it voids any support path you had. Official app only.

The update finished and now a feature is missing.+

That is a regression rather than a failed update, and repeating the update will not undo it. Compare against the release notes and report it — rollback is generally not available on this class of hardware.

The device has been dead since the update.+

Stop power-cycling it. Repeated interruptions can compound a partial write, and each attempt reduces what a support team can recover. Record the version it was on and the stage it stopped at, and open a case.

Should I update at all if everything works?+

Yes, for security fixes in particular — but do it when you can leave it alone, on power, near the router, and not when you are about to need the device. The update itself is low risk; being interrupted is the risk.

Does this answer apply to every Ring model?+

No. It is scoped to 5F77E9. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.

What should I record before troubleshooting firmware or update?+

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

Why is a factory reset not the first step?+

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing firmware, update. The ordered checks preserve that evidence.

When should I stop and use qualified service?+

Never interrupt critical-device firmware or use unofficial files.

Change recordSept. 1, 2026 — Built out with researched, cross-checked per-model specifications and model-specific guidance. Aug. 17, 2026 — Published with explicit 5F77E9 applicability, a firmware-update diagnostic boundary and first-party support provenance.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device