Firmware Upgrade Guides: Obihai 2xx/3xx/10xx/21xx

primerisk · 2025-04-22T22:44:44+00:00

Hello everyone! I recently had a lightning strike at my home and it fried my OBi202 that I had used for many, many years. Unfortunately I didn’t heed the warnings of others to configure a 2nd device before HP shutdown the ObiTalk service and I was stuck looking for alternatives. Luckily I found obifirmware.com that promises to be able to breathe new life into your OBi devices. The only problem is the support and guidance for installing the firmware was over on the now-defunct DSLReports website. Not to fear! Reddit users to the rescue! I scrubbed through dozens of posts and was able to cobble together guides to update your OBi2xx/3xx, OBi1xxx, and OBi21xx devices with the 3rd party software posted on obifirmware.com and links to those guides are below (Google Docs versions) I take no credit for any of the wonderful work of the folks at obifirmware.com, all props to them for their hard work and dedication to bring our OBi devices back to life with Google Voice. OBi2xx/3xx devices: https://docs.google.com/document/d/1_6k0-z18mzHbj0y_vmph_yk5b-FCqqaPNSScAQU5wjM/edit?usp=sharing OBi10xx devices: https://docs.google.com/document/d/1TTWPpZ8BVYzRjNLHEKEf50IPmPyaOah1XMJZAIhgzQw/edit?usp=sharing OBi21xx devices: https://docs.google.com/document/d/142HOI5pqUHc-6qCbLTm2twVDe-80PopUZIAMVXlIz2U/edit?usp=sharing Feedback and comments for improvement are welcome!

tjn

Thank you andre2!!!

I put in the AuthPassword (that long string), but as soon as i click SUBMIT, it puts back a 8 character password in that field. Should it be doing that? Anyway, I am struggling to get past this 403 Forbidden message.

andre2

tjn I see “••••••••” in the AuthPassword field, so that’s apparently normal as well.

tjn

andre2

Thank you…

tjn

Under System Management, Auto Provisioning, I have all groups disabled except for ITSP Provisioning. That is set to SYSTEM START. Is that correct? Or did I accidentally change something.?

andre2

tjn After the GV provisioning (during which Method is set to “System Start”) is successful, it should be automatically set back to “Disabled”. That’s what I have right now on my working device.

tjn

andre2

Yes, mine went back to disable also.

tjn

I got it to connect. At least once… I made one call and received one call… I am going to bed. I worked all day on this. I will check tomorrow and see if it is still working….

What did I do to fix it… I am not exactly sure. I was making several changes at a time. One thing I did differently, was to make all the changes to my obi200, saved the changes, but did not reboot… then I unplugged the obi200 and my xfinity router. Plugged the router back in and when the router eventually was ready, I plugged in the obi200. And i got a valid connection status. I made one call and received one call.

My xfinity internet gateway(modem/router) is new, along with the 1GB connection. The router has some limitations, for example you can’t change the DNS site. Its locked to xfinity. But it was included in my internet package, so I took it. The bottom line is that a lot of things changed or is new, and that added to the complexity.

Thank you all for your help and support. and keep your fingers crossed that it is still working tomorrow..

tjn

andre2

Thank you for sticking with me with my problem. I really appreciate it.

I hope I can help someone in the future. Tom

lorok

I started using naf’s firmware years ago. It’s still working great, but two days ago Google sent me an email saying my “unused OAuth client will be deleted in 30 days”. The only OAuth client I have is the one I used to set up my obi200, so I’m not sure why it’s flagged as unused/inactive. Does anyone else have a similar issue?

tjn

I just started to use the software. About 9 days ago… I have not received the message you received.

andre2

lorok I got a similar email on July 15 (which I still have). The project (concerning my OBi100) I have there was from back around 2018 when I was using the old instructions (which are long obsolete) for configuring the OBi devices. Chances are it has nothing to do with your current provisioning. I have projects for my OBi100 (before those stopped working with GV back around 2019), OBi200 and OBi1022. In any case I have reprovisioned the newer devices multiple times using the recent instructions so I’m sure the old projects don’t matter anymore.

Larre

Hello All -
Has anyone successfully used an iOS device and Safari to update the firmware? I have not tried it just yet, but I have been able to login to my OBi device and I have been able to download the firmware. It seems like it should work, but I was hoping someone would know for sure.
Thanks!

jfc-1980

Greatemtguy
For everyone here, I’ve also got an Obi200, and followed all the FW upgrade steps laid out in @primerisk excellent upgrade guide.

However, just like @Greatemtguy and others earlier in this thread, I’m unable to get GV working and under the SP1 Service Status section, I continually get the error message under Status of
“Connecting to 216.239.36.145;Token Error”

I tried @vigyapan advice above of turning off my Obi device, router and modem, and then repowering them back on in reverse order of modem, router and Obi device. But that changed nothing, and left me with the same error message.

Can anyone advise on how to actually solve the “Token Error” message???

And yes, I copied over and entered the full token address and SP1 URL accurately and in their entirety! And I still can make Google Voice calls just fine via my mobile phone with the same Google Voice account I previously had working on my Obi thru the Obi portal, and now trying to reactivate via the arrynrob firmware.

« Previous Page