[Q] Replace AT&T image with Developer Edition - Moto X Q&A

Is it possible to deploy the Moto X DE image on Moto X AT&T (X1508) device?
THX

No. Not without unlocking the bootloader, which is unpossible.

Root is not enough?
gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
I can root it, will not work?

zivoro said:
I can root it, will not work?
Click to expand...
Click to collapse
No, rooting is not sufficient.

The AT&T SW, mainly AT&T contacts, drive me nuts...
Must clean it.

gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.

KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.

KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash factory images.

gunnyman said:
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.
Click to expand...
Click to collapse
Dev X on Verizon and "Consumer"/MotoMaker X on Verizon are both XT1060. So if roms are signed for the devices they are meant for, they are both signed for XT1060.
The only difference is the ability to unlock the boot loader or not. And this can't be changed by the ROM you flash.
As a test, would you agree that the "VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip" from http://sbf.droid-developers.org/ghost/list.php is the "Consumer" edition of the ROM?
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
kzoodroid said:
You need an unlocked bootloader to flash factory images.
Click to expand...
Click to collapse
And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.

My bootloader is unlocked so I can't test but the ones directly from the moto site are "dev" recovery images. They might be signed differently (like the engineering builds). The ones on sbf droid are retail files and will work fine for their proper device but cannot be shifted to another.
Ex: vzw images will not work on an att device. (however they will work if you have a Dev edition)
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Sent from my XT1060 using Tapatalk

Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.

KidJoe said:
[/COLOR]And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.
Click to expand...
Click to collapse
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.

kzoodroid said:
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.
Click to expand...
Click to collapse
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
gunnyman said:
Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.
Click to expand...
Click to collapse
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.

Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app

kzoodroid said:
Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.

gunnyman said:
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
Click to expand...
Click to collapse
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.

kzoodroid said:
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.
Click to expand...
Click to collapse
So am I.
I've also flashed manually on my mac. fastboot flash boot.omg fastboot flash system.img etc etc all work fine on my locked bootloader phone.

kzoodroid said:
....What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. ...
Click to expand...
Click to collapse
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.

KidJoe said:
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.
Click to expand...
Click to collapse
That first thread you referenced (http://forum.xda-developers.com/showthread.php?t=2445955) says right in the first post you need an unlocked bootloader. I then went 5 pages deep and saw another post which stated you have to have an unlocked boot loader to flash these. I saw one mention of pushing/pulling the images files using adb but nothing saying that worked. One other thread you linked to is about flashing a leak and you don't need an unlocked bootloader to flash a leaked rom.
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
---------- Post added at 03:26 PM ---------- Previous post was at 03:08 PM ----------
KidJoe said:
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.
Click to expand...
Click to collapse
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on.
---------- Post added at 03:55 PM ---------- Previous post was at 03:26 PM ----------
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot.
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.

kzoodroid said:
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
Click to expand...
Click to collapse
Again, the files inside the Verizon "consumer" rom, and the one you get from the Dev Web site are the SAME, the only difference is the XML in the one erases a few extra things while flashing with RSDLite.
And to flash those files Moto has for the dev edition, you do not need to have your bootloader unlocked. I've been able to flash my Verizon Moto X Dev Edition with my boot loader locked. (using both moto's fastboot, as well as RSDLite).
kzoodroid said:
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on
Click to expand...
Click to collapse
Not sure where you got the idea that ALL were Dev edition owners. Those threads were for returning to "stock" so they could take the updates. Those who had boot loops and such were rooted with RockMyMoto and such, they had to root that way due to locked boot loader which made it impossible for them to flash custom recovery and flash TWRP to then install SuperSU from inside TWRP to root.. (i.e. with an unlocked bootloader you can install TWRP then install SUperSU to root, no need to use Pwnmymoto, rockmymoto or the like).
If you are basing it on the model number of the phone listed in thread poster signatures... keep in mind the Verizon X Dev Edition is the XT1060. The Verizon MotoMaker X, or the uncustomized X you get from Verizon's web site is also the XT1060.
kzoodroid said:
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
First, those threads instructing people to fastboot flash recovery, system and boot were due to them rooting with RockMyMoto and PwnMyMoto which overwrites the stock recovery to trick and give R/W. They are being instructed to flash the Recovery.IMG, Boot.IMG and System.IMG out of the downloaded SBF/FXZ ROM file. Not flash a custom recovery and then install anything from the custom recovery.
Only when it comes to Rooting a Dev Edition, or consumer edition with unlockd boot loader (like T-Mobile, Sprint or other, but NOT ATT or Verizon non-Dev), are people being instructed to flash a custom recovery (like TWRP) then install SuperSU from inside TWRP to root.
Next, can you please explain to me what you mean by "factory image" because it seems as though your thinking is different than mine. You're saying the only "factory images" that exist are for the X Dev Edition, right? And that those at http://sbf.droid-developers.org/ghost/list.php are NOT factory images, but rather ROMs.
Ok, while you help me understand what you believe the differences to be, please download the VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip from http://sbf.droid-developers.org/ghost/list.php since it is the "consumer" rom. Then visit Moto's web site https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images , and request/download the Verizon X Developer edition rom. Unzip them both to separate folders. then compare the files contained in each (hint the included XML includes the MD5 hash for each file, but you can do a FC /B in windows too). Other than the XML for the one containing the extra "erase" statements, they are the same. No difference. The XML would be opened in RSDLite to flash that way. The individual files could be flashed with moto's fastboot. Then do the same for the T-Mobile version and the GSM Developer edition roms. Again, you'll see the files contained are the same.
kzoodroid said:
Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
Actualy, no the OP can't install a dev ed rom with TWRP, as to flash a custom or recovery that hasn't been signed by moto, you need an unlocked boot loader. But the bootloader on the ATT X can't be unlocked.
Actually, at this point, there is no use for me to continue. I've said enough, and given my reasons. Feel free to disagree with me.

Related

Stock recovery

Hi,
Does anyone know where I can find the stock recovery for the Sprint Moto X? I have TWRP right now and I want to prepare for the Kit Kat update.
Its my understanding that I will need to fastboot flash the stock recovery to take the update. I don't have much faith that a flashable 4.4 rom will happen anytime soon.
Any help would be appreciated.
Sent from my XT1056 using Tapatalk
No one?
Sent from my Nexus 7 using Tapatalk 4
Well, you could consider visiting -> http://sbf.droid-developers.org/ghost/list.php See if there is a copy of the ROM your phone is currently on... If so, download it and unzip it.
And since you have TWRP installed, I'm going to say you've unlocked your bootloader, and likely rooted.. That also might impact the install of 4.4. Did you remove any bloat, mess with system files, or freeze any apps with something like Titanium Backup? That too can impact the install of 4.4.
If you're interested take a look at -> http://forum.xda-developers.com/showthread.php?t=2536735
KidJoe said:
Well, you could consider visiting -> http://sbf.droid-developers.org/ghost/list.php See if there is a copy of the ROM your phone is currently on... If so, download it and unzip it.
And since you have TWRP installed, I'm going to say you've unlocked your bootloader, and likely rooted.. That also might impact the install of 4.4. Did you remove any bloat, mess with system files, or freeze any apps with something like Titanium Backup? That too can impact the install of 4.4.
If you're interested take a look at -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Is the link with the sbf files for consumer devices only? I have a dev edition on its way and thought I read if you flash the non dev sbf you will also install security stuff for non dev edition devices you don't want. Thanks in advance!
KidJoe said:
Well, you could consider visiting -> http://sbf.droid-developers.org/ghost/list.php See if there is a copy of the ROM your phone is currently on... If so, download it and unzip it.
And since you have TWRP installed, I'm going to say you've unlocked your bootloader, and likely rooted.. That also might impact the install of 4.4. Did you remove any bloat, mess with system files, or freeze any apps with something like Titanium Backup? That too can impact the install of 4.4.
If you're interested take a look at -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
I did uninstall some apps, but not much. My plan was to reinstall the factory recovery, then factory reset before accepting the ota.
This being my first Moto device, I'm not really familiar with all this .sbf stuff. Are you saying the stock recovery would be part of it?
Sent from my XT1056 using Tapatalk
MichaelMcEntire said:
I did uninstall some apps, but not much. My plan was to reinstall the factory recovery, then factory reset before accepting the ota.
This being my first Moto device, I'm not really familiar with all this .sbf stuff. Are you saying the stock recovery would be part of it?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
The stick recovery can be found in the sbf zips
Sent on my Moto X
Travisdroidx2 said:
Is the link with the sbf files for consumer devices only? I have a dev edition on its way and thought I read if you flash the non dev sbf you will also install security stuff for non dev edition devices you don't want. Thanks in advance!
Click to expand...
Click to collapse
There was talk/speculation that when flashing the Dev edition with "non-dev" SDF/FXZ files you'd revert to a "consumer"/Locked device. I am not aware of that being confirmed as 100% true.
When I first got my Dev X, I rooted with RockMyMoto and ran for a week or so before unlocking the bootloader. At the time unlocking the boot loader voided the warranty and I wanted to make sure there were no issues before voiding the warranty. To prep for Kit Kat, I did flash it back using the only 4.2.2 SBF out there, that was for the "consumer" devices. It didn't hurt. I was still able to unlock my boot loader.
At this point, Moto does have the KK dev edition SBFs available for request on their web site if you don't trust using other SBF's. But they do appear to be the same as the "non-dev" sbf files.
---------- Post added at 02:29 AM ---------- Previous post was at 02:18 AM ----------
MichaelMcEntire said:
I did uninstall some apps, but not much. My plan was to reinstall the factory recovery, then factory reset before accepting the ota.
This being my first Moto device, I'm not really familiar with all this .sbf stuff. Are you saying the stock recovery would be part of it?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Factory reset will not restore any apps you removed from the phone (i.e. if you deleted the APKs).
SBF and FXZ files are firmware files for Moto. RSDLite is the tool to fully flash an SBF or FXZ file.
The thread I linked earlier (said if you are interested... read...) has several options to return to stock, and explains options for using RSDLite to flash a full SBF/FXZ, as well as mfastboot to flash only parts of the ROM file, which will get you back to stock.
Most of the Moto updates perform checks for files, and specific versions of files before installing. If they don't match stock, or files it expects to be there are missing, the OTA wont install, or get the phone stuck in a boot loop.

[Q] Developer Edition and Updates

Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
I_EAT_BABIES said:
Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
Click to expand...
Click to collapse
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
samwathegreat said:
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
Click to expand...
Click to collapse
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
I_EAT_BABIES said:
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
Click to expand...
Click to collapse
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
samwathegreat said:
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
Click to expand...
Click to collapse
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
I_EAT_BABIES said:
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
Click to expand...
Click to collapse
You are welcome. A few other thoughts: the potential to brick only comes if either the bootloader or partition table are mismatched. This can happen during a failed OTA install.
In addition to that, even if you DID restore the twrp backup successfully, you still couldn't take the OTA. Remember: STOCK recovery is required to accept any OTAs. It would have continued to boot-loop.
Once you finish with RSD Lite, just use fastboot to flash custom recovery back on. Use the latest version of TWRP, find it here: http://techerrata.com/browse/twrp2/ghost
Just: fastboot flash recovery twrp_file_name.img
Then, IMMEDIATELY afterwards, type: fastboot reboot-bootloader
Next, VOL DOWN to highlight recovery, and VOL UP to boot into it.
If you don't immediately boot into TWRP after flashing it, it won't "stick" (we don't know why...but as long as you do this, it will stick permanently, or until you flash something else to recovery).
As you probably already know, as soon as you go to exit TWRP it will offer to root for you.
Good Luck! Update us to success.
P.S. -- Sent you a PM.
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
The unlocked warning is no big deal I get it on my 4.4.3 GSM Developer Edition.
onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
Nope, it's not. Likely, you had flashed a new logo.bin that "masked" the unlocked bootloader warning. Once again, the images are no different. Not one single byte different. None.
If you dislike (I like it, personally) the unlocked BL message, simply flash a replacement logo.bin.
See here for details: http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
I realize that it says it is for 4.4.3, but it should be fully compatible with 4.4.4 as well.
And one more time: EVEN THE DEV EDITION shows the "unlocked bootloader message" when unlocked. Completely normal. Only flashing a replacement logo.bin will prevent it from showing up.

HELP! Bring Verizon Moto X DE back to Stock.

I'm having a serious issue removing TWRP as the custom recovery and returning my Verizon Moto X 2013 DE back to stock (in anticipation of 5.1). Most of the links to firmware are dead now and I can't get RSD Lite to work either. Any suggestions?
Fredhoffmann3 said:
I'm having a serious issue removing TWRP as the custom recovery and returning my Verizon Moto X 2013 DE back to stock (in anticipation of 5.1). Most of the links to firmware are dead now and I can't get RSD Lite to work either. Any suggestions?
Click to expand...
Click to collapse
Did you look here? Give thanks to the OP if he was able to help.
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Fredhoffmann3 said:
I'm having a serious issue removing TWRP as the custom recovery and returning my Verizon Moto X 2013 DE back to stock (in anticipation of 5.1). Most of the links to firmware are dead now and I can't get RSD Lite to work either. Any suggestions?
Click to expand...
Click to collapse
Here is my copy of the 4.4.4 stock recovery image for the XT1060 if you need it:
https://www.dropbox.com/s/6nasb63j6ix86tg/XT1060_4.4.4_recovery.img?dl=0
JulesJam said:
Here is my copy of the 4.4.4 recovery image for the XT1060 if you need it:]
Click to expand...
Click to collapse
I got the phone off of Ebay and it already had TWRP installed. It is running 4.4.2 and keeps asking for the OTA to 4.4.4. I should be able to download your image and pull it from my computer in TWRP, correct? Still learning my way around custom recovery.
Fredhoffmann3 said:
I got the phone off of Ebay and it already had TWRP installed. It is running 4.4.2 and keeps asking for the OTA to 4.4.4. I should be able to download your image and pull it from my computer in TWRP, correct? Still learning my way around custom recovery.
Click to expand...
Click to collapse
If it is still on 4.4.2, you need the 4.4.2 image, not the 4.4.4. And no, you don't do this through TWRP, you do it through bootloader mode or RSDLite.
I no longer have the 4.4.2 image. You need to find the XT1060 4.4.2 image somewhere online. And a copy of the most recent mfastboot, which is version 2. Then boot into bootloader mode, and flash back to stock 4.4.2. Or use RSDLite, but if you don't edit the xml file, you will lose all your data.
Are you sure you are on 4.4.2? What matters is the bootloader version. What does it say in bootloader mode? 4.4.4 is bootloader version 30.B7. I believe 4.4.2 is 30.B4 but double check that. You MUST know what version of the bootloader you are running b/f you flash back to stock.
Edited:
If you flash back to stock 4.4.2, rather than take the OTA, I would use Motorola Device Manager to upgrade b/c then you would get a copy of 4.4.4 stock files on your computer.
Motorola has the stock 4.4.4 image posted on their site for the XT1060, as well as full instructions on how to return back to stock. I guess you were doing more clicking when getting the bootloader unlock code from them than reading, as they've had EVERY stock image posted for the XT1060 since stock.
If you want to directly download the files http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
or through motorola site https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
JulesJam said:
If it is still on 4.4.2, you need the 4.4.2 image, not the 4.4.4. And no, you don't do this through TWRP, you do it through bootloader mode or RSDLite.
I no longer have the 4.4.2 image. You need to find the XT1060 4.4.2 image somewhere online. And a copy of the most recent mfastboot, which is version 2. Then boot into bootloader mode, and flash back to stock 4.4.2. Or use RSDLite, but if you don't edit the xml file, you will lose all your data.
Are you sure you are on 4.4.2? What matters is the bootloader version. What does it say in bootloader mode? 4.4.4 is bootloader version 30.B7. I believe 4.4.2 is 30.B4 but double check that. You MUST know what version of the bootloader you are running b/f you flash back to stock.
Edited:
If you flash back to stock 4.4.2, rather than take the OTA, I would use Motorola Device Manager to upgrade b/c then you would get a copy of 4.4.4 stock files on your computer.
Click to expand...
Click to collapse
I checked ... and the bootloader is 30.B7. I went to the Motorola site and requested the "MOTO X, VZW Dev Edition:KK-4.4.4-KXA21.12-L1.26.1-1 (VZW)" version of firmware. My only issue is how to get TWRP removed from the device. Each time I tried to accept the OTA ... the phone would boot to TWRP and I'd have to clear the cache. I'm new to this stuff, so I appreciate everyone's patience.
Fredhoffmann3 said:
I checked ... and the bootloader is 30.B7.
Click to expand...
Click to collapse
Then your bootloader is on 4.4.4.
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
Fredhoffmann3 said:
My only issue is how to get TWRP removed from the device.
Click to expand...
Click to collapse
Download the stock recovery image I linked to in my dropbox account (XT1060_4.4.4_recovery.img) - that is the 4.4.4 stock recovery for the XT1060. Place the file in the same directory where you have your fastboot and adb files. Make sure USB debugging is enabled in the developer options of your settings on your phone. Then plug your phone into your PC, open a command shell, navigate to where fastboot/adb files and the XT1060_4.4.4_recovery.img are and type:
adb devices
that should give you a pop up on the phone to authorize your PC and then it should return the serial number of your device. Then type:
adb reboot bootloader
to boot into bootloader mode. Then type:
fastboot flash recovery XT1060_4.4.4_recovery.img
then you will have stock recovery.
JulesJam said:
Then your bootloader is on 4.4.4.
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
Download the stock recovery image I linked to in my dropbox account (XT1060_4.4.4_recovery.img) - that is the 4.4.4 stock recovery for the XT1060. Place the file in the same directory where you have your fastboot and adb files. Make sure USB debugging is enabled in the developer options of your settings on your phone. Then plug your phone into your PC, open a command shell, navigate to where fastboot/adb files and the XT1060_4.4.4_recovery.img are and type:
adb devices
that should give you a pop up on the phone to authorize your PC and then it should return the serial number of your device. Then type:
adb reboot bootloader
to boot into bootloader mode. Then type:
fastboot flash recovery XT1060_4.4.4_recovery.img
then you will have stock recovery.
Click to expand...
Click to collapse
Trying it now. Wish me luck! After I complete this ... I should be able to accept the OTA, correct?
Fredhoffmann3 said:
Trying it now. Wish me luck! After I complete this ... I should be able to accept the OTA, correct?
Click to expand...
Click to collapse
You can only accept the OTA if your system, kernel, radios, etc are all stock.
As I indicated before, I would use Motorola Device Manager to update b/c then you will have the fxz on your computer.
JulesJam said:
Then your bootloader is on 4.4.4.
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
Download the stock recovery image I linked to in my dropbox account (XT1060_4.4.4_recovery.img) - that is the 4.4.4 stock recovery for the XT1060. Place the file in the same directory where you have your fastboot and adb files. Make sure USB debugging is enabled in the developer options of your settings on your phone. Then plug your phone into your PC, open a command shell, navigate to where fastboot/adb files and the XT1060_4.4.4_recovery.img are and type:
adb devices
that should give you a pop up on the phone to authorize your PC and then it should return the serial number of your device. Then type:
adb reboot bootloader
to boot into bootloader mode. Then type:
fastboot flash recovery XT1060_4.4.4_recovery.img
then you will have stock recovery.
Click to expand...
Click to collapse
You are my savior! I've spent probably 10 hours working a fix for this. I was able to accept the 4.4.4 OTA. With the 5.1 update hopefully coming soon, I'm back to stock. THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!
JulesJam said:
As I indicated before, I would use Motorola Device Manager to update b/c then you will have the fxz on your computer.
Click to expand...
Click to collapse
And what's so special about it? Motorola posts the stock images anyway. You'd just be getting the file a little bit sooner at the expense of annoying software on your computer.
imnuts said:
And what's so special about it? Motorola posts the stock images anyway. You'd just be getting the file a little bit sooner at the expense of annoying software on your computer.
Click to expand...
Click to collapse
Where has Motorola posted the stock images for 5.0 for the Verizon XT1096 MX14?
JulesJam said:
Where has Motorola posted the stock images for 5.0 for the Verizon XT1096 MX14?
Click to expand...
Click to collapse
If it is the same as the 13' X all you have to do is request the stock images from Motorola. That is how I received all my factory images for my X.
Travisdroidx2 said:
If it is the same as the 13' X all you have to do is request the stock images from Motorola. That is how I received all my factory images for my X.
Click to expand...
Click to collapse
Did you have a Developer Edition MX13?
JulesJam said:
Did you have a Developer Edition MX13?
Click to expand...
Click to collapse
I do have a dev edition 13' X.
Travisdroidx2 said:
I do have a dev edition 13' X.
Click to expand...
Click to collapse
Ok so for Dev Eds, Motorola will give you the factory images. My advice is to use MDM to update so you will have it on your computer regardless. If you find the MDM annoying, then you can uninstall it. The nice thing about MDM is it installs the drivers for you too. Many people have issues installing the drives and this does it for you.
Another benefit of MDM is that if you soft brick your device but still can get into bootloader mode, MDM will repair your phone for you. You just connect your phone in bootloader mode to your computer and start MDM and it does it automatically. So I not only don't find MDM annoying, I find it useful.
If you are a Recognized Developer on XDA, then you obviously know what you are doing and don't need a program like MDM to help you when you get into a bad situation. For the rest of us mere mortals, IMO, MDM is nice to have. You not only get the images on your computer automatically, it installs the drivers for you and can repair your device if you soft brick your phone.
JulesJam said:
Where has Motorola posted the stock images for 5.0 for the Verizon XT1096 MX14?
Click to expand...
Click to collapse
When did we start talking about the 2nd generation phone in the first gen forums? Had I known we were on the 2014 X, then yes, you need another method to get the stock image. If you are, you know, on a device actually related to this subforum, and it is a XT1060 or XT1053 (I think that's right), then just download the stock images from Motorola.
Sent from my Moto X
imnuts said:
then just download the stock images from Motorola.
Click to expand...
Click to collapse
Dude, I didn't need to, you know why? BECAUSE I USED MDM TO UPDATE AND I HAVE THEM ON MY COMPUTER ALREADY, LOL!!!!
I was merely addressing your point about it not being useful to use MDM to update. Um, yeah it is.

moto x 1st gen 4.2.2 Upgrade to 5.1

Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?
Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X
-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)
Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!
nevermind, google fixed me.

Help on XT1254 OTA

Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
me too
i updated to 6.0.1 via recovery with update.zip. This process had successfully done and re-updated via recovery again (still the same update.zip) and i factory reset tin recovery so it stuck screen 'erasing...'They could not enter system, except bootloader and recovery vesersion (6.0.1),can not into apply update sdcard , it turn e:\unkown volum path [sdcard]... and I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
longbin said:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Click to expand...
Click to collapse
1. I have never heard of anyone selling bootloader unlock keys for the XT1254. If you want to unlock your bootloader, Sunshine is your only option, and as of right now it will only work on lollipop builds. If your phone is on marshmallow, Sunshine will not work. If your phone cannot boot, it won't work no matter what build you're on.
2. If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
mr_5kool said:
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
unlock the bootloader and install TWRP BEFORE doing any updates, while still on Lollipop. That is the only safe, logical answer. An unlocked bootloader -- especially with custom recovery -- will let you do lot of things and is more forgiving of mistakes than a locked bootloader.
We keep telling people that and they won't believe us.
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
TheSt33v said:
If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
Click to expand...
Click to collapse
Right. Several people who didn't like Lollipop but preferred the original Kitkat "speed", "battery life" or whatever successfully downgraded back to 4.4.4 -- but only AFTER they unlocked their bootloader. Even then you have to make sure you don't flash the old gpt.bin in ADB, but downgrading is possible with an UNlocked bootloader.
Even when flashing XT1250 firmware over XT1254 or vice versa, it CAN be done with a locked bootloader, but if you mess something up you are in big trouble. UNlocked bootloader? Just do it again, correcting your mistake the next time.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
TheSt33v said:
1. I have never heard of anyone selling bootloader unlock keys for the XT1254.
Click to expand...
Click to collapse
There was a guy on some website who was selling some Verizon keys a long time ago, known as "the Chinaman". He disappeared.
China Middleman Back??
http://forum.xda-developers.com/moto-x/moto-x-qa/china-middleman-t2751177
dschill said:
Well the china man added me back on skype today. And sadly said that he can no longer get the codes and refunded my 45$ via paypal.
Heres a little bit of the skype transcipt
[12:08:22 PM] live:dschillinrecovery: k i just got the refund
[12:08:25 PM] live:dschillinrecovery: so you cant get the code any more?
[12:12:41 PM] VIP-UNLOCK: No time to deal with the accident, we default to a refund
[12:13:08 PM] VIP-UNLOCK: Sorry, goodbye
[12:13:32 PM] live:dschillinrecovery: Its alright. Thanks for the refund though. Let me know if you can ever get the codes again
Guess the best we can do for now is to wait for jcase and sunshine to release the 3.0 version.
Click to expand...
Click to collapse
and another thread discussing same guy:
http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651
The process seems to involve sending approximately $45 to a Chinese middle-man via eBay and another website, along with your IMEI and cell phone number, and you will receive an unlock code.
It seems like this is all one guy handling this process. Turnaround time seems to be 24-48 hours beginning to end.
Click to expand...
Click to collapse
Theory was that someone with access to Motorola's engineering software had a side business going. You know they unlock their bootloaders for testing and such. Someone with access to that software could make some money if they made sure they covered their tracks.
Also people who visited China were able to buy unlocked bootloader Droid Turbos well before Sunshine was released. One guy posted in this forum. In that case, it was probably pilfering some phones from the factory -- but again with unlocked bootloaders. So, there is some software out there somewhere, just kept under wraps.
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
TheSt33v said:
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
Click to expand...
Click to collapse
I updated my post to include XDA links. I can't find any examples of Droid Turbos being unlocked via this eBay "purchase" only other Verizon phones, but there are the legitimate reports of unlocked Droid Turbos for sale in China in the year prior to Sunshine being released November 2015. One guy even posted on here because he was trying to install CM12.1 at the time on his BOOTLOADER UNLOCKED Droid Turbo he had purchased in China.
Note the Chinese middleman guy was charging $45 for bootloader unlock at the time, and Sunshine only charges $25.
xml flash file is the last solution =))
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Doesn anybody know how much does usually takes for Verzion ( or whoever does it ) to release xml sbf firmware file? And do they release every? I need latest MCG24 or at least system file (s) is enough.
I have everything except system files, if anybody can provide system files or knows hot to convert ones from ota , I can make complete fastboot xml zip.
EDIT: System from OTA is not enough. If somebody can provide system / backup from MCG24 phone, I might be able to make it.
mr_5kool said:
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Click to expand...
Click to collapse
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
ChazzMatt said:
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
Click to expand...
Click to collapse
Can you give little more info on this. Changed cid? Unlocked bootloader? Maybe we can use x1250 xml fastboot files until they release Marshmallow fastboot. I need one for backup , I know I'll brick the phone sooner or later , as guys above did lol..
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
Flashed the Verizon radio and 5.1 FW (firmware)
The only problem I have right now is upload speeds are super slow.
gonna try wiping the radio and re-writing the radio
Click to expand...
Click to collapse
I then asked him a couple of questions and he answered this:
Yes I flashed the Verizon Radio to the device
not the bootloader image, for obvious reasons
I wanted 5.1, so I didn't test until I had the VZW 5.1 with my SIM card
I'm going to try an reflash soon, and then get a new SIM just in case
I hope Verizon doesn't give me any trouble getting a new SIM at my local store
Click to expand...
Click to collapse
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
ChazzMatt said:
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
I then asked him a couple of questions and he answered this:
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
Click to expand...
Click to collapse
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Ej?iSixo said:
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Click to expand...
Click to collapse
That's been done, too. I didn't know that was the question.
One guy didn't want Verizon bloatware and his solution was to flash the "pure" Motorola firmware from the XT1250 over his XT1254.
Yes, he had unlocked bootloader and could have just uninstalled the bloatware. I'm not saying it was logical, I'm just telling you what he did.
So there's no question these two phones are exactly the same device, with exactly the same FCC ID.
The issue is the XT1250/XT1254 being flashed needs to the other needs an unlocked bootloader. And you can't downgrade (gpt.bin) when you flash.
So, for the purposes of this thread that information doesn't help you, if your XT1254 bootloader isn't unlocked.
mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
Conclusion: Wait for the 6.0.1 flash file (xml) then flash via RSD.
Thanks guys!!!!
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571

Categories

Resources