Android 17’s stable release arrived on June 16, but testers on Android 17 Beta 4 and Beta 4.1 have been unable to move to stable without losing their device data. Google confirmed the OTA issue, promised a fix “coming soon,” and now says the update patch still
For more than a week now, Android 17 has been sitting in the open—stable for everyone who waited long enough. Pixel owners have been upgrading since June 16 without drama.
But for testers on Android 17 Beta 4 and Beta 4.1, the moment Android 17 went stable didn’t bring an easy switch. It brought an ugly trade-off: they couldn’t upgrade to the stable release without losing all the data on their devices.
Google acknowledged the problem quickly and promised a fix “coming soon.” Now, with more time passing than early testers were counting on, the company is still asking for patience—and offering a clearer explanation for why the fix is taking this long.
Normally, leaving the Android Beta Program isn’t supposed to be a painful reset. Testers can flash their phones to stable Android, but that wipes data. Or they can opt out of the program, decline future beta updates, and wait for the stable update to arrive.
That’s the rule. What Android 17 Beta 4 and Beta 4.1 users ran into earlier this month is that the stable update simply didn’t land for them through the usual OTA route.
The update that matters—Google’s promised solution—has been delayed. Over on Reddit’s Android Beta sub, Mishaal Rahman posted an update today explaining the sticking point in plain terms. Google said it’s working through “a few issues to ensure that the OTA update goes smoothly for beta users. ” and asked beta users to “bear with us a bit longer.”.
The key detail is that Google isn’t just pushing a single change to everyone. To get Beta 4.0 and Beta 4.1 users onto the same stable release as non-Beta users, Google says the OTA patch for beta testers can’t be the same patch that was delivered to users coming from the previous stable release.
In Rahman’s update, Google laid out the reason: the two groups are “two different bases,” meaning “both OTA update patches need to be built and tested separately before we can push them out.”
That’s why. even after Google’s earlier promise that the fix was on the way. testers are still stuck waiting with no specific ETA attached. It’s frustrating in the moment—especially when the stable release is already live and the goal is straightforward: get Beta 4 and Beta 4.1 users to the stable build without the wipe.
The reassuring part for those testers is that Google is still framing this as ongoing work, not abandonment. Rahman’s message also makes it clear what Google wants to achieve: existing Beta 4.0/4.1 users upgrading to the same stable release as non-Beta users.
And now the countdown is shifting from a software rollout to a testing-and-validation clock—one that’s starting to feel uncomfortably close to the end of July as the wait stretches into another week and a half.
Android 17 Android Beta Program Beta 4 Beta 4.1 OTA update stable release Mishaal Rahman Pixel users
So they’re just gonna make you lose your data… cool cool.
I don’t even get why they call it a beta if it breaks the upgrade path. Just let people update like normal smh. My cousin’s Pixel always gets stuff on time though so idk.
Wait so if you’re on Beta 4.1 you can’t go stable without wiping? That sounds like they’re trolling testers. I mean isn’t it literally always supposed to wipe if you flash anyway? Feels like Google is moving the goalposts and calling it “patch coming soon.”
They said June 16 stable and everyone else was fine, but the beta people get punished. “A few issues” is such a vague excuse, like what does that even mean, Google? I almost went back to stable on my old phone and it wiped anyway so maybe this is just Android being Android, but still… my data better not be the price of their testing.