Obihai 200 checksum error with OBi202-3-2-1-5757EX.fw

<< < (2/3) > >>

drgeoff:
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.

david123456789:
That doesn't work.  I've already tried that.  It just says update didn't work.  Probably due to the check sum error.

david123456789:
How is the checksum calculated?  Is it an MD5 hash or SHA512?

GPz1100:
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

david123456789:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page