Skip to main content
Lizzie
LizzieCommunity Manager
Community Manager
April 27, 2026

[FIXED] Provisioning fails on Pixel devices with March and April 2026 builds, if factory reset

  • April 27, 2026
  • 4 replies
  • 533 views

Updated 29 April 2026

  • Status: Our Engineering Team has confirmed that the reported issue has now been FIXED

------------------------------------------

Issue:

Outage Start Time: [20th April 2026]

Description: We have reports of an issue impacting provisioning on Pixel devices that have been updated to the March 2026 (CP1A.260305.018) or April 2026 (CP1A.260405.005) builds. 

 

Affected devices may experience failure during the ‘Getting ready for work setup’ during device enrollment if device is factory reset after the OS update. Behaviors observed include looping back to the Wi-Fi selection screen or errors such as "can't setup device" or "something went wrong".

 

We will provide further information as it becomes available.

 

The Android Enterprise Team

    4 replies

    F
    FabienMagras
    Level 1.6: Donut
    April 28, 2026

    Is this only happening after a factory reset, or is it a general issue? Because our devices registered in the ZTE portal have never undergone a factory reset, yet they appear in this situation upon the user's initial registration.
    Could we have more information on this?

    Lizzie
    LizzieCommunity ManagerAuthor
    Community Manager
    April 28, 2026

    Hey ​@FabienMagras,

     

    Can I check which devices this is happening on please? Are they in the builds mentioned above? 

     

     Also, just so I ensure I’m interpreting your message here correctly, are you seeing some devices fail in enrollment (like stated above) even without the factory reset? 

     

    Thanks so much,

    Lizzie

    Welcome to the Community everyone!
    Rakib
    Rakib
    Level 3.0: Honeycomb
    April 29, 2026

    @FabienMagras Im not sure you should write down your IMEI numbers in a open forum...

      Lizzie
      LizzieCommunity ManagerAuthor
      Community Manager
      April 29, 2026

      Hello everyone, 

       

      Just to confirm, a fix has been rolled out for this issue and so if you were seeing this problem before it should now be resolved. 

       

      Do let me know how this goes. 

       

      Thanks so much,

      Lizzie

      Welcome to the Community everyone!
      djwulah
      djwulah
      New Member
      May 14, 2026

      Hello, our org is also seeing this issue. We are in the middle of a rollout and it is stopping us in our tracks, we have the data and it is not pointing to a specific device, oem, or operating system. We are using Jamf.

      Lizzie
      LizzieCommunity ManagerAuthor
      Community Manager
      May 15, 2026

      Hey ​@djwulah,

       

      Great to meet you. 

       

      This issue was specific to Pixel devices running March 2026 (CP1A.260305.018) or April 2026 (CP1A.260405.005) builds, so based on your information here it sounds like it could be something else. Are you seeing the exact same impact?

       

      Have you spoken with Jamf about this yet, as I would recommend them to have a deeper dive into this?

       

      Please do keep me posted if you can, and I will try to help as much as I can. I wish you all the best for your rollout, it will be all worth it in the end. 

       

      Speak soon,
      Lizzie

      Welcome to the Community everyone!
      djwulah
      djwulah
      New Member
      May 21, 2026

      Hi Lizzie,

      We actually observed this was not specific to Pixel devices, albeit, a high percentage of users in our BYOD program are pixel users. we have seen the same impact on Samsungs and even Motorola's. 

      We have flagged this to Jamf and they are with us in pressuring Google for a fix within our chain of communication and Google Workspace Support ticket (#71196839)

      At this time we haven’t received any meaningful updates on a fix.

       

      Terms & ConditionsAccessibility statement