Hi All! Just joined so I could post, after spending... well, multiple hours reading the history of this amazing journey.
just reflash the v00.01.03.00.01 build from end of April, and try again.
Probably you got a scope with a v00.01.03.00.01 build from mid may, hence the different checksum.
Thanks for posting this info!
I just got a MSO5074 with that same mid-May version of the v00.01.03.00.01 firmware (listed onscreen as Build: 2020-05-18 11:42:06)
The patch checksums didn't work.
After I rolled back to the April version of the v00.01.03.00.01 firmware (listed on-screen as Build: 2020-03-30 15:56:36), the patching worked!
Thank you to all who contributed to this effort! It is impressive and apprecitated!
I also just got a MSO5072 with the mid-May firmware, same number and build timestamp listed above.
I went ahead and used the well-worn ssh enabler, ssh in, use the command line to copy the appEntry file onto a USB stick at /media/sda1 and took it to another computer to do the MD5.
If you have any kind of unix computer (linux or Mac) simply type
$ md5 /Volumes/USB_DRIVE/appEntry
or whatever the appropriate path is for you. md5 should be present by default in most unix-like systems.
MD5 (appEntry) = 783a31ebdc0d4acb7b9dc244155ba1c6
From everything I'm seeing here, it seems like this piece of info should be enough to get the patcher to work? Am I misunderstanding?
I'll try it and post a followup.
Thanks for this amazing community effort!