I"m trying to update the firmware on my Obi200 to the latest OBi202-3-2-1-5757EX.fw to eliminate the Google Voice Backing Off error. I keep getting a checksum error no matter what browser I use to download the file. On Windows 10 the file shows up as 13.5 MB (14,168,064 bytes). That is a fairly large discrepancy. My Obi200 is on 3.1.0 (Build: 5264). Is there an intermediate firmware build I should update to before trying the latest?
My Windows 10 shows the same size. EX firmware includes OBi Extras code. Try deleting the FW and download again.
Thanks I've tried that multiple times with each download.
The download site says 3-2-1-5757 (10.4MB). That is the size I am checking against. I've downloaded the firmware all the way back to build 5285 and none of them work with this unit.
Is there any way to disable the checksum validation and just force the update?
The file size is 14,167,736. The "size on disk" reported by Windows depends on properties of your hard disk such as the cluster size. The 1Tbyte drive in my Windows 10 PC says 14,168,064.
The incorrect 10.7 Mbyte figure in the post by Obihai is probably the result of a careless and incomplete edit by whoever updated that post.
No, there is no way to force the update past a checksum error.
It should not be necessary to update to an intermediate firmware version.
HOWEVER
You should not need to manually update the firmware as even for OBi20x devices out of warranty, Obihai has arranged a semi-automatic update to address the recent GV change. Go to your Dashboard at obitalk.com and you should find a yellow triangle containing an exclamation mark. Clicking on that should initiate the firmware update.
That doesn't work. I've already tried that. It just says update didn't work. Probably due to the check sum error.
How is the checksum calculated? Is it an MD5 hash or SHA512?
These are the results returned from hashcheck (https://github.com/gurnec/HashCheck) on the firmware file.
File: OBI_FIRMWARE_OBi202-3-2-1-5757EX.fw
CRC-32: d85205fd
MD5: f5e249b85b99f29bf9b94c651161d16e
SHA-1: 324da94c71cbfdbdb9a589fc35935d56222f5d60
SHA-256: b4cc275b8c7426a8397658c9c268cf1b065e30d62fe92d833d3607106e31414b
SHA-512: a6ef860d0590020f32face280a6742abcbe0d803bb292c7c2b701dbb44089db17d3edb39d7a66cefe50c9d5e7a1e8ad3096341e4c889be603178c8c394af75a3
Quote from: GPz1100 on December 06, 2017, 11:27:07 AM
These are the results returned from hashcheck (https://github.com/gurnec/HashCheck) on the firmware file.
File: OBI_FIRMWARE_OBi202-3-2-1-5757EX.fw
CRC-32: d85205fd
MD5: f5e249b85b99f29bf9b94c651161d16e
SHA-1: 324da94c71cbfdbdb9a589fc35935d56222f5d60
SHA-256: b4cc275b8c7426a8397658c9c268cf1b065e30d62fe92d833d3607106e31414b
SHA-512: a6ef860d0590020f32face280a6742abcbe0d803bb292c7c2b701dbb44089db17d3edb39d7a66cefe50c9d5e7a1e8ad3096341e4c889be603178c8c394af75a3
Thanks. My hash MD5, SHA1, SHA256, and SHA512 values match up with yours. Windows is displaying the values in uppercase, but other than that the values are identical. So that means the issue is with the unit and not the file.
The checksums are in hex. Case doesn't really matter. Do you have some browser plugin or antivirus program that intercepts web traffic. Maybe it's changing it somehow ¿?
Quote from: GPz1100 on December 06, 2017, 11:51:31 AM
The checksums are in hex. Case doesn't really matter. Do you have some browser plugin or antivirus program that intercepts web traffic. Maybe it's changing it somehow ¿?
I tried disabling the anti-virus and trying a clean Linux laptop. Still getting a checksum error. Looks like I need to buy another obihai.
Quote from: david123456789 on December 06, 2017, 01:50:34 PM
Quote from: GPz1100 on December 06, 2017, 11:51:31 AM
The checksums are in hex. Case doesn't really matter. Do you have some browser plugin or antivirus program that intercepts web traffic. Maybe it's changing it somehow ¿?
I tried disabling the anti-virus and trying a clean Linux laptop. Still getting a checksum error. Looks like I need to buy another obihai.
I expect it won't make any difference but you have nothing to lose by trying a hardware reset.
It's worth a shot to try a different ethernet cable and power adapter too.