Hi, the person looking into this here. We do hash validation two times during the install process: first during the backup step, and then again right before a clean install. This helps us ensure that we aren't potentially writing data into a non-SYNC 3.4.23188 file (as such a modification would cause very hard-to-debug crashes).
The hash mismatch error reported above is more of a warning than an actual error, and happens during the backup phase. If it's reported, it means that (a) the backup files are not stored on the USB, and (b) that the installer has detected that the files currently installee aren't stock. To anyone having this issue, can you please check that you have files in your SyncMyMod/files/other/backup/+10inchP directory?
The actual issue hanging up the install is "ERROR: Patch file dry run failed to apply", which means that our test patch attempt fails. This generally happens in Home.qml and/or Root.qml, as we don't currently have a solid mechanism to un-patch the file (and you can't patch over an already-patched file).
If the files aren't present there, the RESTORE operation will fail silently due to another bug that I'm fixing for beta3 (that otherwise shouldn't cause any issues, just no logging in this case). Put your backup files into that specific directory, and everything should hopefully work. I'm also going to specifically work on a case to detect if the mod was already installed to just allow you to change settings since that appears to be a relatively common use case.
On a more personal note, I apologize for the difficulties we're having with the installer. I'm still new to the entire "mod packaging" thing and am really learning as I'm going. While I am absolutely testing things on actual hardware, my testing tends to be done in a controlled environment and things can be missed because I know how things are supposed to work.