Hi there, I don't want the waters to get muddied here - changing DNS does not impact the issue. I've tried three different ones across three different networks and the failure behavior is exactly the same.
Well, it was worth a shot. I can’t explain why mine have no problem, even here on a hotel network.
You're right, it is worth testing! I thought something similar and tried a few myself to no avail. The entire internet is basically balancing on top of 8.8.8.8 so if all of a sudden it stopped resolving Roku URLs there would be some fantastic news worthy meltdowns. This is the most active issue on the board, so its unlikely that all these folks across all these different devices are all using a borked DNS server.
My best running hypothesis is ghosts.
It's possible you only encounter this issue if you firstly do a factory reset before you try and update. Both the devices I am having the 003 issue with were factory reset first, then in the setup process they hit the 003 and I can go no further. Is it possible that the default firmware for these devices that it reverts to on a FR is calling a dead server?
I think thats a good guess - I have not FR any other device and checked if the same happens. If I had a spare one lying around I wasn't afraid to brick I'd be happy to though lol
A factory reset does not change the OS version. There is no “default” OS after a reset.
Ah I did wonder if my assumed architecture was correct, I'm guessing an FR just resets user settings rather than reverting the entire boxes software to a stored default state.
