Obihai OBi20x/30x + OBi1000 + OBi50x + OBi2000 firmware mods

charterengr · 2025-01-19T18:36:53+00:00

Can we pickup where we left off here....... naf? OBi1FW? jsolo1? others?

noworlater

I'd like to thank @naf and all the others involved in making this happen!
I've been using an Obi200 for several years with GV and after the ObiTalk shutdown it was still receiving calls but wouldn't allow an outgoing call.
Arrynrob13 has got it all working perfectly again.

Couple comments I'd like to make re the embedded GV setup instructions (that in hindsight are obvious) that might make things easier for others:
Step 4: The refresh token to copy/paste is the character string between the " " after the words "refresh_token"
Between step 4 and 5 don't do a reboot as the Obi web interface suggests. Do the reboot after step 5 as the instructions say.
Yeah, all obvious in hindsight, but may help someone.
Again, THANKS!

andre2

noworlater Step 4: The refresh token to copy/paste is the character string between the " " after the words "refresh_token"

You can easily just copy the entire URL as stated in step 3 by something like right-clicking on the URL and "Select All" (in Firefox) and then middle-click to paste into the text box in the GV instructions window. That's easier than identifying the right substring manually. And you can copy the entire refresh token from the resulting Refresh Token window by something like triple-click (or right click and "Select All").

noworlater Between step 4 and 5 don't do a reboot as the Obi web interface suggests. Do the reboot after step 5 as the instructions say.

The device's Admin Guide (OBiDeviceAdminGuide.pdf) does state that when changing settings on more than one page, it's necessary to click Submit on each page before navigating to another page, but that rebooting is only needed once, after changes on all pages are saved.

There is a known, pretty obvious, typo in the arrynrob instructions in step 5 ("step5" should read "step #4") which is queued to be fixed in the next version.

noworlater

andre2 And you can copy the entire URL from the resulting Refresh Token window by something like triple-click.

Thought I had tried copying the entire window contents and it had failed, but probably had a separate issue.
Thanks again!

yajrendrag

can someone remind me - if i already have arrynrob installed (3.2.2 (Build: 8680EX-arrynrob10), can i just do a firmware update directly to arrynrob 13? or do i need to install stock 5921 etc...
thanks.

andre2

yajrendrag None of the modded firmware is locked down, only the (newer) stock, so yes, you can update directly to any version.

yajrendrag

andre2 thanks for confirming

rookie

So sorry I didn't reply to your very helpful advice sooner but I have been beset by a series of events that kept me very busy.
Many thanks to both Andre and Naf for your generous help.
Once again, I ran into another issue that I'm not sure about.

After carefully following the provisioning instructions I noticed in the SP1 service status was the message;
'Connect Failed: 403 Forbidden (server=216.239.36.145; retry in 70s)'

When I go into my regular Google voice account it now prompts me to;
'Look for available numbers by city or area code.
You must have an existing US-based mobile phone number to qualify'

and when I go into Settings it says;
'You don't have a google voice number'

How should I proceed from here or what did I do wrong?

andre2

rookie Did you have a GV number before? It would use whatever GV number is associated with the Google account you used when provisioning.

rookie

I did have a GV number on my Obi 200 that I didn't use very often and stopped working for outgoing/incoming calls around late December 2024, but was still functional in every other way (the Obi 200 that is.)
That's why I went with the new firmware after reading the end of life announcement for Obitalk portal.
Until I installed the new firmware, I did not get the message on my GV account that I didn't have a GV number.
I hope all this makes sense to you so that perhaps help me understand what happened.

andre2

I don't have any experience with lost GV numbers, there's this link, don't know if it will help. It says a removed number can be added back within 45 days, but since you didn't get any notice of it being removed I don't know if that applies to you. If it doesn't you could also check if the same number is currently available, or just pick a new one if it doesn't matter.

https://support.google.com/voice/answer/159519?hl=en#zippy=

andre2

naf Are you in contact with OBi1FW ? The Obifirmware website still refers to DSLR for support and it seems unlikely it will ever allow new posts even if it stays up read-only (part of the time).

Edit: Just checked their profile at https://www.dslreports.com/profile/1964012 (during the window) and it says they were seen today.

naf

andre2 Are you in contact with OBi1FW ?

yes, obi1fw reached out soon after the site went down.

andre2 The Obifirmware website still refers to DSLR for support and it seems unlikely it will ever allow new posts even if it stays up read-only (part of the time).

im sure obi1fw will take care of this when they get a chance. i sent them a link to this thread

ParanoidUserParanoidUser

Are there any GitHub repositories or reproducible builds available for the custom firmware? I'm an end user with an Obi200 and came across the custom firmware site after experiencing issues with Google Voice.

I've started down the path of binwalking+unsquashfs'ing+bindiffing but I figured I should ask here for some more information before I sink anymore time into it.

If there aren't any reproducible patches available, would that be something of interest to the community?

I've found naf's tooling but not much else aside from some blog posts and the old thread.

https://github.com/naf419/obi-firmware-tools
https://randywestergren.com/reverse-engineering-obi200-google-voice-appliance-part-3/

naf

ParanoidUserParanoidUser I've started down the path of binwalking

no need for binwalk, just use fw-unpack.sh to unpack the firmware to its constituent partitions, edit those partitions, and use fw-pack.sh to package it back to upload to the obi

rws70

ParanoidUserParanoidUser

I have a new OBi200 I bought years ago and I am finally getting around to the project of moving my ATT landline over to a voip setup and saving some money. To use my OBi device I found this company: Anveo They have gone out of their way to make it easy to for OBi owners to set up home voip or move from Google Voice. They even have an excellent video on how to configure the device, etc. several info pages, etc.

Then I poked around some more and found a reddit page about 3rd party firmware updates that are supposed to allow one to continue to use an OBi200 with Google Voice. The info includes links to an internet archive page that shows you how to manually configure the device once the firmware has been updated. I like the idea and the adventure of seeing if I can get it working, but I would hate to break my device with a firmware mistake. And although the config steps on the archive page are pretty clear and well done, it is a bit daunting. Here is the reddit post where I heard about the 3rd party firmware option:

https://www.reddit.com/r/OBihai/comments/t87x9s/need_setup_instructions_for_obi_3rd_party/

And finally there is a company called Ooma that has a polished voip home product that looks very tempting and is still relatively cheap. It comes with lots of support and equipment designed for a much simpler "plug and play" user experience.

Hope that helps ...

andre2

rws70 I believe the instructions at https://web.archive.org/web/20190319063228/http://www.obifirmware.com/OAuth2/ no longer work, which is why they were removed from the main site. Don't know how the poster who claimed 18 days ago to have used them to configure their device actually did it. The latest arrynrob firmware has built-in GV instructions which do work.

px_eliezer_

rws70 And finally there is a company called Ooma that has a polished voip home product that looks very tempting and is still relatively cheap. It comes with lots of support and equipment designed for a much simpler “plug and play” user experience.

Just saw your post.

OOMA is ok but they are a closed network, a regular ATA won’t work on Ooma, and the Ooma device won’t work on other providers (such as Callcentric, Voip.MS, Anveo, etc)

thorzeen

WTH check out for a few weeks and find DSLR gone
Glad there is a new place to hang and learn
Thanks for all you do Naf!

tpedwards

naf Darn. This explanation is much appreciated although I understand about half of it. Flash giving up the ghost is something I understand.

I have two Obi202s on order from eBay $12 each + shipping.

If they will take a flash, I’ll see if I can get these firmwares to work.

tpedwards

So I received two Obi202’s from eBay and I have soldered headers to all three (my original + two derelict units from eBay). I can communicate, but all three prompt for passwords. Does anyone remember or can point me in a direction with regard to the password necessary to root these things?

One of them flashes red on power up. The other prompts with “The requested URL was not found!” when trying to access the IP address assigned to the unit by my router.

Any help would be most appreciated!

My original Obi202 yields:
Uncompressing Linux…………………………………………………………………….. done, booting the kernel. But I get no prompt after that is presented.

RJM

Sorry to butt in here but I'm not sure where to start. I'm looking for help getting a new GV number configured on an Obi202.
The latest version of arrynrob was installed without issue. Phone#1 works just fine. Phone#2 doesn't work (long story) so I need to re-configure it.
I started the provisioning process but I'm stuck in step 2. I get the 404 error but this is all I get: "The requested URL /obinet/pg/obhdev/gvtoken was not found on this server." No token.

Any suggestions would be appreciated.

Also looking for instructions on updating contacts. I think they used to exist on DSL Reports but not sure where to look now that they are going out of business.

andre2

RJM

RJM I started the provisioning process but I'm stuck in step 2. I get the 404 error but this is all I get: "The requested URL /obinet/pg/obhdev/gvtoken was not found on this server." No token.

That's exactly what's supposed to happen. As stated in step 3, you need to copy and paste the long URL that appears at the top of your browser when you get that error message into the textbox on the GV instructions page, then click the button as stated and the Refresh Token appears.

Edit: There's a pretty obvious typo in the step 5 instructions, "step5" should read "step #4". That's queued to be fixed in the next arrynrob version.

« Previous Page Next Page »