My question is this:
How do you know that this is the same update that Verizon will push (has pushed) OTA?
What happens in January when they push the OTA update for 2.1, and you've got a slightly different filesystem layout as the people who waited? Will the 2.1 update apply cleanly, or completely fail?
At that point, you'll be forever stuck in a phase of having to update manually, which may not always be an option.
Unless, Verizon/Motorola/Google provide clean, *full*, firmwares that you can use to completely restore phones.
I'm not saying the update.zip didn't come from a reputable source. I'm saying it may be different than what Motorola/Verizon push out, and you'll never actually know until the next update comes out and the checksums don't match up.
This is confirmed by Motorola Support forums administrator Matt in this post: https://supportforums.motorola.com/message/84490 - it's very possible that the update.zip that people are using to upgrade manually *isn't the final version*.
How do you know that this is the same update that Verizon will push (has pushed) OTA?
What happens in January when they push the OTA update for 2.1, and you've got a slightly different filesystem layout as the people who waited? Will the 2.1 update apply cleanly, or completely fail?
At that point, you'll be forever stuck in a phase of having to update manually, which may not always be an option.
Unless, Verizon/Motorola/Google provide clean, *full*, firmwares that you can use to completely restore phones.
I'm not saying the update.zip didn't come from a reputable source. I'm saying it may be different than what Motorola/Verizon push out, and you'll never actually know until the next update comes out and the checksums don't match up.
This is confirmed by Motorola Support forums administrator Matt in this post: https://supportforums.motorola.com/message/84490 - it's very possible that the update.zip that people are using to upgrade manually *isn't the final version*.