QUICK ANSWER
Keep the device powered, restart once, then try one different trusted network.
If a BOOX update is visible but the download stalls or fails, note the exact message and the stage where it stops. Connect the device to power, keep it awake on stable Wi-Fi, restart it normally once and retry. If the same update fails again, use a second trusted network or hotspot. BOOX has recommended that sequence in recent public support replies.
Do not factory-reset, install a package from a forum or use firmware meant for another model. If the failure is repeatable, enable BOOX's saved-log option, reproduce it once and send Feedback with logs. That gives support evidence from the failed attempt instead of a device whose useful state has been erased.
FIRST, NAME THE FAILURE
“Update failed” can mean three different things
Start by separating availability, downloading and installation. That matters because a missing update can simply be part of BOOX's staged rollout, while a package that repeatedly fails verification needs a different response.
Check the rollout and exact model. Use Yeinks's separate missing-update guide.
Test power, Wi-Fi, one second network and the correct regional server.
Do not hunt for another file. Preserve the message and send logged Feedback.
Write down the BOOX model, full firmware build, update version shown, battery level, network used and exact error. Take a photo if the message disappears quickly. Recent owner reports include failures on Palma 2 and Palma 2 Pro, but they do not show that every model has one shared defect or that BOOX's servers are always the cause.
If the update is not offered at all, follow the separate BOOX firmware update not showing guide. Do not keep forcing this download checklist onto an availability problem.
SAFE, REVERSIBLE CHECKS
Change one condition at a time
- Protect local work first.Back up important files and confirm recent notes have synced before any firmware attempt. BOOX itself recommends a backup before updating.
- Connect to power.Use a reliable charger and leave enough free time for the download and restart. Do not start an update just before travel, a meeting or a low-battery warning.
- Confirm ordinary internet access.Open a known website or refresh a cloud service. A Wi-Fi icon only proves a local connection, not that the device can reach the internet.
- Restart once.Use the normal power menu, reconnect to Wi-Fi and return to System Update or Firmware Update. One restart can clear a stuck session without changing your files.
- Retry while the BOOX stays awake.Keep the update screen open and avoid switching apps, starting a large sync or letting the device sleep during the test. Give the progress indicator time rather than tapping Download repeatedly.
- Try one different trusted network.BOOX has publicly advised affected owners to change networks. A personal hotspot is a useful comparison when home Wi-Fi fails, but avoid hotel, school or public networks that require a browser sign-in.
- Check the configured server.In Settings, confirm the BOOX server matches your real location. BOOX says server choice affects cloud services and firmware-update speed. Do not cycle through regions merely to unlock a feature.
If the update works elsewhere, return to the first network later and check its sign-in page, DNS filtering or firewall settings. If it fails at the same point on two independent networks, stop changing routers and collect logs for BOOX.
AFTER THE DOWNLOAD
A verification or installation error needs a stop line
If the progress reaches the end but BOOX reports that the package cannot be verified, decrypted or installed, record the complete wording. A third download of the same offer may give support one more clean reproduction, but repeated package attempts are not useful if the failure point never changes.
BOOX documents an official local-update method for some models. That is not permission to use the first update.upx file found online. BOOX warns that firmware packages are model-specific and that the wrong one can leave a device unable to boot. Use a local package only when it comes from BOOX for the exact model and BOOX's instructions match the device. If support supplies a case-specific route, keep their message with the package.
Once an update succeeds, let the BOOX complete its restart. Open Notes and confirm syncing again, as BOOX recommends. Do not interrupt the first boot because the logo or progress screen appears slower than usual.
WHAT NOT TO DO
Do not turn a download error into lost data
- Do not factory-reset as an opening test. BOOX warns that a reset formats storage on current firmware. It also removes the evidence support needs without proving whether the download service was at fault.
- Do not clear system-app storage from generic Android advice. The relevant BOOX component and effect can vary by build, and the public update guidance does not require this.
- Do not install beta, downgraded or unofficial firmware. A package for a similarly named model is not close enough.
- Do not change several network, server and DNS settings together. You will not know which condition mattered, and a wrong server can create separate cloud-sync confusion.
- Do not repeatedly interrupt installation. Once verification passes and installation begins, keep the device powered and let it finish.
WHEN TO STOP
Send BOOX one useful reproduction
Contact BOOX when the offered update fails on two independent trusted networks, always stops at the same percentage, reaches the end but fails verification, or returns after one normal restart. Also stop if the BOOX overheats, reboots unexpectedly, shows storage errors or cannot start normally.
Before the final reproduction, go to Settings > FAQ & Feedback, open its settings and enable saving logs before rebooting. Menu names can vary. Restart if the option instructs you to, try the update once, then immediately open Settings > Feedback > +. Describe the model, current build, offered version, failure stage, time and networks tested, and allow encrypted log data to be sent. Share the serial number only in the private support channel.
SOURCES AND LIMITS
What is confirmed
Current BOOX documentation and recent owner reports were checked on October 14, 2026. BOOX confirms its cloud-update and exact-model local-update routes, recommends backing up and connecting to power, warns against the wrong firmware package, and directs software faults to on-device Feedback. In two recent public support replies about failed Palma updates, BOOX advised a restart, another network and a logged reproduction. Those reports helped define the symptom and safe order. They do not establish a universal cause or failure rate. Yeinks has not reproduced the problem on a device.