cancel
Showing results for 
Search instead for 
Did you mean: 

Google Wifi won’t re-register after factory reset — OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR

Mikita
Community Member

Hi everyone,

I’m running into an issue with one of my Google Wifi points (model AC-1304) that refuses to re-register after a factory reset. The device worked fine for over a year as part of my mesh network. A few days ago, I removed it from the network using the Google Home app, intending to test some other units. Later, when I tried to re-add this device, setup consistently fails at the final step with the error:

OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR

Here’s what I’ve tried so far:

  • Multiple full factory resets (held the reset button for 15+ seconds until the LED turned solid white or flashing blue).
  • Attempted to add the device to both my existing mesh network and a brand new network.
  • Changed DNS settings to 8.8.8.8 and 1.1.1.1
  • Monitored the local API at 192.168.84.1/api/v1/status, which showed a consistent failure in generating or registering a deviceId.

All other Google Wifi points (4 total) continue working just fine.

The failing point shows a flashing blue LED (waiting for setup) and appears to function normally up to the registration phase, which leads me to believe the hardware is fine. It seems like the device is stuck in a broken platform registration state on Google’s backend.

I reached out to Google Nest support, and they confirmed that this is a known issue currently affecting Google Wifi (not Nest Wifi/Nest Wifi Pro) and that Engineering is investigating. That was over a week ago, and I haven’t received further updates.

Has anyone else experienced this? Any workarounds or success stories?

I’d appreciate any insight — I really want to reuse this device that worked perfectly until recently.

9 REPLIES 9

LoneHort
Community Member

Same issue for me, Tried adding it to 2 different homes and if I go to the api status page I see the same error.

My status page is ,

 

{
   "dns": {
      "mode": "automatic",
      "servers": [  ]
   },
   "setupNetwork": {
      "ssid": "setup36970"
   },
   "setupState": "ONLINE_NETWORK_TIME_AVAILABLE",
   "software": {
      "blockingUpdate": 1,
      "softwareVersion": "14150.376.32",
      "updateChannel": "stable-channel",
      "updateNewVersion": "0.0.0.0",
      "updateProgress": 0.0,
      "updateRequired": false,
      "updateStatus": "idle"
   },
   "system": {
      "countryCode": "gb",
      "groupRole": "leaf",
      "hardwareId": "GALE C2I-A2A-A3A-A6I-E8R",
      "lan0Link": true,
      "ledAnimation": "SETUP_FAILURE",
      "ledIntensity": 30,
      "modelId": "ACjYe",
      "oobeDetailedStatus": "OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR",
      "uptime": 944
   },
   "vorlonInfo": {
      "migrationMode": "weave_all"
   },
   "wan": {
      "captivePortal": false,
      "ethernetLink": false,
      "gatewayIpAddress": "192.168.86.1",
      "invalidCredentials": false,
      "ipAddress": true,
      "ipMethod": "dhcp",
      "ipPrefixLength": 24,
      "leaseDurationSeconds": 86400,
      "localIpAddress": "192.168.86.249",
      "nameServers": [  ],
      "online": true,
      "pppoeDetected": false,
      "vlanScanAttemptCount": 0,
      "vlanScanComplete": true
   }
}

LoneHort
Community Member

on a reboot it seems the Google Gen1 Wifi has connected to my mesh but it is still flashing blue waiting for setup. If I connect to its own wifi network   setup36970 I can browse out from it and a tracert shows my pc going to 192.168.84.1 then to my Nest Pro router .86.1 so it has somehow joined my house mesh 

Mikita
Community Member

@LoneHort 

Thanks for confirming you're seeing the same issue — that definitely helps show this isn't isolated.

I’m also seeing the exact same error (`OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR`) and observed similar behavior: the device sometimes connects to the mesh (can reach other nodes), but it still flashes blue and remains stuck in setup mode.

I’ve been in contact with Google Support and they’ve confirmed that the issue is known and currently under investigation by their engineering team. Hopefully a fix is on the way.

Thanks for sharing your findings!

Mikita
Community Member

I also tried resetting the device using the OnHub Recovery Utility. It did restore the firmware and the device updated itself afterward, but the setup still fails with the same OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR. Unfortunately, it didn’t help — the issue remains.

LoneHort
Community Member

I have the same error trying to add a Google wifi

Ttzeeee
Community Member

I’ve been having the exact same issue for the last 2 weeks. I have 3 units in my mesh to begin with, then I bought 3 more used routers to add to my network. The first one I tied to add had this error, then I moved to the second one which was added successfully, then the third one also has this issue. Getting the exact same error “OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR”. Both of the erroring units seems to have perfectly functioning hardware, if I logon to their setup SSID I can browse internet just fine, but they just won’t register to my account and get included as part of my WiFi mesh.

AndersC
Community Specialist
Community Specialist

Hi there,

 

Thank you for posting in the community. I'm sorry to hear you're experiencing the same inconvenience with setting up your Google Wifi devices and getting the error “OOBE_PROCESSING_PLATFORM_REGISTRATION_INFO_ERROR.” I'm happy to help.

The team would like to learn more about this behavior. When you get a chance, please fill out this form and let us know when you’re finished. We’ll have someone reach out to you via email from there.
To help us assist you better, please include the link to your Community thread and your Community username.
Don't hesitate to reach out if you need help or have more questions in the future.

 

Regards,

Anders

Mikita
Community Member

Hi @AndersC ,

Thanks! I've just filled out the form. Looking forward to hearing back.

Best,

Mikita

LoneHort
Community Member

I have also filled it out now thanks.