Affiliate links on Android Authority may earn us a commission. Learn more.
Samsung Galaxy S10 One UI 2.0 beta locking users out (Update: Patched)
Update, October 30, 2019 (11:20 AM ET): Samsung is rolling out a hotfix patch to the Samsung Galaxy S10 One UI 2.0 beta flaw discussed in the article below (via SamMobile). The patch is designed to fix the problem in which users get locked out of their devices.
Considering the severity of this flaw, we highly recommend installing the update as soon as possible. It weighs 135MB and comes with the build number G97*FXXU3ZSL.
Unfortunately, if you are already locked out of your phone, this patch won’t mean much for you at the moment. You’ll need to downgrade back to Android 9 Pie and then re-upgrade to the Galaxy S10 One UI 2.0 beta with this patch.
Original article, October 29, 2019 (06:51 AM ET): Samsung recently rolled out the Android 10-based One UI 2.0 beta for the Galaxy S10 series, giving users a taste of things to come. Unfortunately, some users are reporting that they’re now locked out of their phones.
Users on the GalaxyS10 subreddit and Samsung forum (h/t: SamMobile) are reporting that the phones refuse to accept PIN codes, passwords, or pattern unlocks after restarting the device.
Some users with Remote Unlock functionality enabled say that they can use the Find My Mobile service to delete previously enrolled authentication options, but they can’t set a new PIN/pattern/password thereafter.
Don’t have the aforementioned function enabled? Well, it seems like a factory reset and downgrading to Android Pie via Samsung Smart Switch might help. But several Galaxy S10 users have reported that they still can’t set an authentication option after doing this.
Got a Galaxy S10 and still want to join the One UI 2.0 beta? Then you might want to disable authentication and enable Remote Unlock before going ahead with installation.
It’s worth noting that this is the potential price to pay for installing beta firmware on your device. The purpose of beta testing is to iron out any kinks and find bugs, so this is one flaw that shouldn’t be in the stable One UI 2.0 release.