Sonos one wont update error code 36 and 1002

Forum|Forum|2 years ago
June 1, 2024
6 replies
1045 views

I have reset my speaker multiple times, uninstalled and reinstalled multiple times and still gives me a update error and wont let me connect my speaker to my app.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

E

Ebk

Lyricist I

I have the same issue with my One SL. I've tried with wireless and a patch cable connected to my router, the end result is the same. I set up another SL three weeks ago without any issues.

Is it possible to download a low-level log file from the system for diagnostics?

M

Mambizi

Lyricist I

I have the same issue with a Play:1 that I bought recently refurbished from Sonos. The first setup seemed to be working (VERY slowly) but eventually froze with the speaker flashing red. I tried to start again and now the app barely thinks about updating before throwing up the error (1002/36), despite over 10 factory resets, connecting to ethernet (and leaving like that overnight) and anything else I could think of. The speaker just sits there flashing green and is detected in the app but refuses to update. Any help appreciated as the contact centre is clearly swamped given the recent app failures.

G

grammo

Lyricist I

So I just encountered this problem with a refurb beam sl purchased from Sonos. Multiple factory resets, app reinstalls, etc. I tried from 4 different Android devices, as well as an update from the windows app. Same error every time.

On 2 occasions I got the prompt to connect to the beam's private network to update, and then the Sonos app would crash. Tried on another phone but that update never finished. I left one going overnight.

Most of these attempts with the beam hard wired into the network.

This morning I made sure my phone was on the 2.4 Ghz wireless network, and disconnected the beam from wired Ethernet. Started the update process again, and it prompted to connect to beam's private network and this time the beam started flashing orange and white. Finally had success... So I have no idea what the actual issue was