Late to the party...
But I'll throw my .02 in here. I side overwhelmingly with Jpcalhoun and will go so far as to say that I am almost certain it will NOT install over .215. To answer some questions...
The "Leaks" come from a server which is accessed by a secretly distributed software package to a portal on the server. This is for Developers ONLY, but some Developers "accidentally on purpose" let a copy of that software slip to the "outside world". Once in the hands of the hackers, they simply open Pandora's box to see what's inside. When they see something of interest, they pull it down with the software tool and "leak" it to the general public.
As for the fact that it's "official signed" software doesn't mean it's automatically going to be considered "the right conditions for the upgrade" by the new upgrade package. Anyone who's helped somebody trying to flash a new or old ROM over an existing system knows how even the slightest change to the existing system can wreak havoc on the process. People "uninstall" or "delete" so-called "bloatware", and then when the new update comes along...nothing. It won't work. Well, that's because the software is doing checksums to see what on the system is different.
As Tis said, if the software were inadvertently installed over a corrupted system that is otherwise apparently working "perfectly", the changes that corrupted the system could render the new system completely useless and could even cause the phone to be permanently bricked. Also as for version numbers, the numbering montra is such that the "update" will have a system number (or better said "filename"), that is the number of the EXISTING ROM, not the new ROM, so an update to JellyBean will likely be named 6.16.211.XT912.Verizon.en.US.zip. This is from Matt's post for the 1.7 version; The 6.16.211 Update (named as 6.12.181 on the zip file because that is how Motorola names it). SO you see, Motorola names the NEW version with the OLD version's number, or in other words, the name is not of the upgrade itself, but of the ROM it is upgrading FROM. SO when it looks to see what it's upgrading, if the name of the file doesn't match the system it polls, it fails on the spot. This is also so that someone with an XT910 for instance, doesn't flash an XT912 ROM over-top and blow the radios, for instance.
I will go out on a limb here and say, if the update is coming, we will ALL have to either RSD Lite back to .211, or use the Droid RAZR Utility so graciously created and dispensed for free by Matt L Groff to effect the same. By the way, I did the RSD Lite in another thread (I can't recall the thread name - a little help here, Tis, Matty, anyone for an old guy?) The full blow-by-blow showed it was successful and was really fast and easy. For those who don't want to be so "hands-on", Matt's utility performs the same functionality with just a tiny bit of setup and then one menu selection.
But I'll throw my .02 in here. I side overwhelmingly with Jpcalhoun and will go so far as to say that I am almost certain it will NOT install over .215. To answer some questions...
The "Leaks" come from a server which is accessed by a secretly distributed software package to a portal on the server. This is for Developers ONLY, but some Developers "accidentally on purpose" let a copy of that software slip to the "outside world". Once in the hands of the hackers, they simply open Pandora's box to see what's inside. When they see something of interest, they pull it down with the software tool and "leak" it to the general public.
As for the fact that it's "official signed" software doesn't mean it's automatically going to be considered "the right conditions for the upgrade" by the new upgrade package. Anyone who's helped somebody trying to flash a new or old ROM over an existing system knows how even the slightest change to the existing system can wreak havoc on the process. People "uninstall" or "delete" so-called "bloatware", and then when the new update comes along...nothing. It won't work. Well, that's because the software is doing checksums to see what on the system is different.
As Tis said, if the software were inadvertently installed over a corrupted system that is otherwise apparently working "perfectly", the changes that corrupted the system could render the new system completely useless and could even cause the phone to be permanently bricked. Also as for version numbers, the numbering montra is such that the "update" will have a system number (or better said "filename"), that is the number of the EXISTING ROM, not the new ROM, so an update to JellyBean will likely be named 6.16.211.XT912.Verizon.en.US.zip. This is from Matt's post for the 1.7 version; The 6.16.211 Update (named as 6.12.181 on the zip file because that is how Motorola names it). SO you see, Motorola names the NEW version with the OLD version's number, or in other words, the name is not of the upgrade itself, but of the ROM it is upgrading FROM. SO when it looks to see what it's upgrading, if the name of the file doesn't match the system it polls, it fails on the spot. This is also so that someone with an XT910 for instance, doesn't flash an XT912 ROM over-top and blow the radios, for instance.
I will go out on a limb here and say, if the update is coming, we will ALL have to either RSD Lite back to .211, or use the Droid RAZR Utility so graciously created and dispensed for free by Matt L Groff to effect the same. By the way, I did the RSD Lite in another thread (I can't recall the thread name - a little help here, Tis, Matty, anyone for an old guy?) The full blow-by-blow showed it was successful and was really fast and easy. For those who don't want to be so "hands-on", Matt's utility performs the same functionality with just a tiny bit of setup and then one menu selection.
Last edited:
Except evil hackers 
