Apologies in advance for the thread-jack.
[thread-jack]
well the leaked update had to come from HTC because it is signed.
The RUU_* executables themselves are not signed (I checked with WinXp "sigverif"), although that's really not too conclusive, as the 1.16.605 RUU - which was blessed by HTC - is (similarly) not signed that way, either.
Probably you are talking about the files (.nbh and .zip?) which are unpacked by the RUU_*.exe once it starts running?
I'm under the vague impression that the OTA update process has a means to verify both a MIC (message integrity check) and a Crypto signature (on both the payload and the MIC) - but it leaves me wondering how a third party ROM could ever be installed, as a 3rd party wouldn't have access to to the same cert.
I suppose it is possible that the FASTBOOT methods (either SD card or USB) don't do any crypto verification - the Linux kernel isn't running at that point, just a little stub of code - so it might be reasonable to assume that no checking is performed on code loaded that way.
But the RUU update method starts with the Eris booted up, so I suppose that the crypto stuff could be running at the beginning of this method of update.
snorge - do you know of a link somewhere (mebbe XDA) that provides a technical overview of the ROM burning process?
TIA
[/thread-jack]
Sort of weird about the OP's 1.12.605 ROM, yes? I bought an Eris on drop day (6 Nov), and I could have sworn it's ROM was 1.15.605.1.
Anducks said:
Anyways, I updated it from my computer and I'm seeing the "System is up to date."
Cool. Perhaps you saw a different behavior because you had a (much?) earlier version of software (1.12.605) on your unit.
Just out of curiosity - is the Hardware version of your phone 0002?
eu1