One UI 9 Update Stuck on ‘Access Denied’ XML Screen? Fixes
One UI 9 Access Denied error after updating your Galaxy? Safe, data-preserving fixes for the XML screen and setup freeze on S24, S25, S26, A57 and foldables.
Updated · 5 min read
In this article
The update finishes, the Galaxy reboots, and instead of your home screen you’re looking at a white page of raw XML with the words “Access Denied” in it. Or a setup screen that never lets you through. The One UI 9 Access Denied error has been reported on Galaxy S24, S25 and S26 phones, some foldables and the Galaxy A57 since mid-October 2026.
According to Android Authority and Sammy Fans, the affected phones don’t appear to be truly bricked, and most owners have got past it without losing anything. Don’t reach for a factory reset. Work through the fixes below in order.
What the error looks like, and which phones get it
Sammy Fans first reported on 12 October 2026 that some Galaxy devices show an XML “Access Denied” error after One UI 9 installs and the phone restarts, and then get stuck on the post-update setup screens. The home screen never loads. Android Authority confirmed the reports the same day, and stressed that it happens during setup after the update, not during the installation.
Owners describe one of three things: a white page with an XML document tree and “Access Denied”, a loop on the One UI 9 introduction or setup screens, or setup failing at the Samsung account sign-in step.
| Model | What owners report | Source |
|---|---|---|
| Galaxy S26, S25, S24 series | XML “Access Denied” after reboot, stuck on setup | Sammy Fans, Android Authority |
| Some Galaxy foldables | Same XML error after updating | Sammy Fans, Android Authority |
| Galaxy A57 | Stuck before the home screen, “Access Denied” or XML page | ProPakistani |
| Galaxy S26 Ultra (Korea) | Setup freezes; Samsung linked it to an unstable System WebView on certain networks | Cybernews, Samsung Korea forum |
Not every unit gets it, and nobody has found a reliable way to predict which ones will.
What’s causing it
Samsung hasn’t officially explained the XML error. A tipster quoted by Android Authority says a Samsung server-side change meant to curb firmware leaks is to blame, but Samsung hasn’t confirmed it. Two things do point at a network or server cause. Nearly every fix that works involves keeping the phone offline until setup is done, and some owners say a restart later on fixed it with nothing else.
Samsung was more specific about the related Galaxy S26 Ultra setup freeze. According to Cybernews, Samsung’s Korean community forum said the development team confirmed the issue “occurs when using an unstable system WebView on certain networks”. Android System WebView is what shows web content inside apps, and that includes the Samsung account sign-in page during setup.
Getting past it without losing data
Stop as soon as you reach the home screen.
1. Go offline and force-restart.
- If you can pull down the quick panel, turn on Airplane mode, or switch off Wi-Fi and Mobile data.
- If you can’t reach any settings, switch off your Wi-Fi router, walk out of range, or take the SIM out with the SIM tool.
- Hold Side key + Volume Down together for about 7–10 seconds until the phone reboots.
- Finish setup offline, and reconnect once you’re on the home screen.
2. Safe Mode, then restart offline. This is the one most owners say worked.
- Force-restart with Side key + Volume Down.
- The moment the Samsung logo appears, let go and press and hold Volume Down until the phone finishes booting. “Safe mode” shows in the bottom-left corner.
- Open the quick panel and turn off Wi-Fi and Mobile data.
- Restart normally (hold Side key › Restart). It should boot to the home screen.
- Reconnect to the internet.
3. Update Android System WebView. Do this once you’re on the home screen, or if an S26 Ultra is stuck at the Samsung account step. In the Play Store, search for Android System WebView and tap Update, then do the same for Chrome, and restart. If setup failed at Samsung account sign-in, try Wi-Fi instead of mobile data, or skip sign-in and add the account later in Settings › Accounts and backup › Manage accounts.
4. Reset network settings. If the phone boots but keeps misbehaving online, go to Settings › General management › Reset › Reset network settings. Saved Wi-Fi networks and Bluetooth pairings are cleared. Photos, apps and messages aren’t.
5. Wait instead of resetting. Some owners say just restarting later fixed it, which suggests something changed on Samsung’s side. A factory reset erases everything. Reports collected by BornCity suggest a fix for the S26 Ultra setup freeze could come in an over-the-air update in November, though Samsung hasn’t given a date. Sammy Fans also advises against a factory reset unless it’s really necessary. We’ll update this page when Samsung releases a fix.
6. Let Samsung handle it. If nothing gets you past the error, contact Samsung support or book a Samsung service centre visit before you erase anything. A software fault caused by an official update is normally handled under warranty, and a technician can reinstall the firmware with official tools. Ask first whether your data can be kept, and back up whatever you can reach. Bring proof of purchase and, if possible, a photo or video of the error. If you bought the phone from a carrier, its store can usually start the repair too.
Battery drain on the S24 and S25
The setup error isn’t the only complaint. Cybernews reports that some Galaxy S24 and S25 owners are getting faster battery drain after One UI 9, including while idle. Sammy Fans says Android can take around two weeks to re-optimise after a major update, so it often improves by itself. If it doesn’t:
- See which apps are using power in Settings › Battery › View details.
- Update all apps in the Play Store and Galaxy Store.
- Open Settings › Device care and tap Optimize now.
- Still heavy after two weeks? Run a battery test in Samsung Members › Support › Phone diagnostics and contact Samsung support.
Our One UI 9 rollout tracker shows which models and regions have the update so far.
Buying a used Galaxy that’s been updated
A seller who got stuck on this error may have factory reset the phone to escape it, and that can leave it locked to their Google account. Before you pay for a second-hand Galaxy:
- Make sure it boots to the home screen, and that the seller has removed their Google and Samsung accounts.
- Confirm the model, region and warranty with a Samsung Info report.
- Check the IMEI isn’t reported lost or stolen with a GSMA blacklist check.
If One UI 9 hasn’t installed on your phone yet
ProPakistani went as far as telling Samsung owners to hold off on One UI 9.0 for now. If you’d rather not wait that long, lower the risk:
- Back up with Settings › Accounts and backup or Smart Switch. Our backup guide covers both.
- To wait for Samsung’s follow-up build, switch off Auto download over Wi-Fi in Settings › Software update.
- To install now, put the phone in Airplane mode as soon as the update has downloaded and installed, so the post-update setup runs offline.
- Afterwards, check your version in Settings › About phone › Software information.
Frequently asked questions
What causes the One UI 9 Access Denied error?
Samsung hasn’t confirmed it. A tipster blames a server-side change, and Samsung linked a similar S26 Ultra setup freeze to an unstable Android System WebView on certain networks.
Is my Galaxy bricked after the One UI 9 update?
Android Authority’s reporting suggests affected phones aren’t truly bricked. Most owners get past the error by restarting offline or through Safe Mode.
How do I fix the One UI 9 XML error without losing data?
Force-restart with Side key and Volume Down, hold Volume Down at the Samsung logo to enter Safe Mode, turn off Wi-Fi and mobile data, then restart normally.
Should I factory reset my Galaxy to fix it?
Not unless the other fixes fail. A reset erases your data and may not be needed once Samsung releases a fix.