Originally Posted by isaakmg
I'm not silly.... :/
Is normal that the ota zip isn't a full ROM stock.......
The problem is only you....
XT1052 is the same in France, Germany, UK or others variants Retail Sbf for XT1052......
The ota 4.4.4 verizon is for verizon sbf 4.4.2
The ota 4.4.4 Retail france is for Retail France 4.4.2
Right, if an update for a UK XT1052 is the same as for a FR XT1052, i.e. same system version, kernel, build number, etc. Then sure, its ok to flash. To be honest, this person might have had better luck if they had a Brazil 4.4.4 SBF to flash back to after flashing the Verizon 4.4.4, which we don't yet.
And yes, the OTA zip does validation checks before installing, and should fail if the build.prop and strings contained it in, do not match. (safe guard so that you can't easily install the OTA.zip from Verizon XT1060 to say an ATT XT1058.)
But the real problem is for those who do NOT wait, take any update or full SBF/FXZ that is available (even if its not for their phone model and carrier), and flash it to their phone (in the case of the OTA, some editing can be done to it so it can be applied if you have an unlocked bootloader), then decide for whatever reason (something doesn't work, they don't like it, they just want back on their stock carrier rom) to try to flash back to a leaked SBF that may not be as new as the update they just flashed.
In the linked thread, someone with a BRAZIL Non-Verizon phone, flashed the Verizon 4.4.4 update (likely using the FXZ). Had problems with radio (probably since the Verizon radio/modem files don't support the same bands), so tried to flash back to their original BRAZIL carrier's rom via SBF which was 4.4.2 (since there is no BR 4.4.4 SBF leaked yet), then an ATT US rom which is was 4.4.3??(I didn't know there was a 4.4.3 for ATT??) which messed up their phone to a point where it might not be able to be recovered.
That is a problem we've seen to often. People just flashing, without knowing, even though warnings keep getting posted.
The main issue to understand there is no downgrading (4.4.4 to 4.4.3 is a no go. 4.4.3 to 4.4.2 is a no go. 4.4.4 to 4.4.2 is a no go, 4.4.2 to 4.4.0 is a no go, etc.) without a major risk of bricking your phone.
That person not only downgraded, they mixed ROMs from incompatible phone models.
NOTE: The only time it was safe to downgrade the X was 4.4.0 to 4.2.2 w/camera update, because the GPT.BIN and MOTOBOOT.IMG was the same between those two roms only. When these files have changed between versions, they have prevented SAFE and successful downgrading.
My Moto X tips and info
Currently using Verizon Moto X Developer Edition
on my personal line.. But I have too many devices to choose from for work and personal... For the full list click -> HERE
Sign up for Dropbox -> HERE