Database Develop

Downgrade after OTA update?

I have a verizon moto x Dev edition with unlocked bootloader. Is there a way to downgrade from the ota update?
Sent from my XT1060 using xda app-developers app

Sent from my XT1060 using xda app-developers app

I couldn't find one for my us cellular moto x. That's why unlocked it so I could gain root.
Sent from my XT1055 using Tapatalk

sporty377 said:
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
My phone is unlocked and still can't downgrade so I can gain root...
Sent from my XT1060 using xda app-developers app

sporty377 said:
My phone is unlocked and still can't downgrade so I can gain root...
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
you can't downgrade, update does not let you go backwards. However if you have a Dev edition and its unlocked you can root it very easily. Fastboot TWRP to it. Then boot into TWRP and flashed SuperSu 1.65 *.zip. Just run a search on Google and you'll find a link to SuperSU the *.zip you need
Edit: here is the thread for SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053

will2live said:
you can't downgrade, update does not let you go backwards. However if you have a Dev edition and its unlocked you can root it very easily. Fastboot TWRP to it. Then boot into TWRP and flashed SuperSu 1.65 *.zip. Just run a search on Google and you'll find a link to SuperSU the *.zip you need
Edit: here is the thread for SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
just reading and curious--with an unlocked BL you can't use the fxz file to flash to an older version? couldn't you first flash the old boot loader and then try the fxz file though rsdlite. if that doesn't work couldn't you just flash all of the images separately?

mohlsen8 said:
just reading and curious--with an unlocked BL you can't use the fxz file to flash to an older version? couldn't you first flash the old boot loader and then try the fxz file though rsdlite. if that doesn't work couldn't you just flash all of the images separately?
Click to expand...
Click to collapse
tried that....didn't work....I just flashed custom recovery and supersu did the rest

will2live said:
you can't downgrade, update does not let you go backwards. However if you have a Dev edition and its unlocked you can root it very easily. Fastboot TWRP to it. Then boot into TWRP and flashed SuperSu 1.65 *.zip. Just run a search on Google and you'll find a link to SuperSU the *.zip you need
Edit: here is the thread for SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
thanks....worked like a charm.....

mohlsen8 said:
just reading and curious--with an unlocked BL you can't use the fxz file to flash to an older version? couldn't you first flash the old boot loader and then try the fxz file though rsdlite. if that doesn't work couldn't you just flash all of the images separately?
Click to expand...
Click to collapse
Nope not even a unlocked Dev edition can go fully backwards. Once bootloader is updated it will not pass the checks when flashing trying to go back. I know because I just brain farted the other day flashing my unlocked HD i was selling and tried flashing with the wrong file. However depending on what needs to be flashed you can in some cases flash a specific partition from older an older software build like i did to restore my botched job on the HD.
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
sporty377 said:
thanks....worked like a charm.....
Click to expand...
Click to collapse
No prob. The joy of owning unlocked version will make it easy like that all the time to get root moving forward

will2live said:
Nope not even a unlocked Dev edition can go fully backwards. Once bootloader is updated it will not pass the checks when flashing trying to go back. I know because I just brain farted the other day flashing my unlocked HD i was selling and tried flashing with the wrong file. However depending on what needs to be flashed you can in some cases flash a specific partition from older an older software build like i did to restore my botched job on the HD.
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
No prob. The joy of owning unlocked version will make it easy like that all the time to get root moving forward
Click to expand...
Click to collapse
very interesting. can you flash back and forth between the old/new kernel? i'm assuming the system is yes.

mohlsen8 said:
very interesting. can you flash back and forth between the old/new kernel? i'm assuming the system is yes.
Click to expand...
Click to collapse
On my HD i did, and I know the X you can as well currently. Whether that holds true moving forward once 4.3 hits is a different story. In my case messing aroudn its alwasy been the same Android version when flashing something older.
As for the X depending on how you go about updating the X before the full fastboot was posted yesterday if you wanted root you did in fact need to use the old (original stock) kernel to fastboot over the recovery once the OTA was installed.

Best way to root newly updated 4.4 Verizon developer moto X

Having trouble finding which method is best for me

nvertigo said:
Having trouble finding which method is best for me
Click to expand...
Click to collapse
Unlock bootloader. Flash twrp 2.6.3.1 for 4.4. Flash latest supersu. Profit.
Sent from my iPhone

phositadc said:
Sent from my iPhone
Click to expand...
Click to collapse
^↑^^^^^^^^^???↑f↑a↑i↑l↑
Funny your using A fruitbox to post in a moto x forum!
Sent from my XT1058 using XDA Premium 4 mobile app

matt99017d said:
^↑^^^^^^^^^???↑f↑a↑i↑l↑
Funny your using A fruitbox to post in a moto x forum!
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've also got a Moto x and a Nexus 5
Sent from my XT1053

still haven't gotten there
I've spent hours on unlocking and rooting my vzw developer's edition. First, the SDK that motorola tells you to download to get fastboot doesn't include fastboot! There are a few ways to get it, but following Motorola's instructions won't get you there. (thanks so much Motorola for posting a solution that doesn't work).
Do Not install the OTA update....if you do, you will not be able to root your phone and you will have to reinstall the stock drivers. It's easy to do, but it will take hours for you to realize that you have to do this. If you have the OTA update already installed, get rid of it by installing the drivers from the motorola site for the developer edition phone (VZW).
You do not need to download the sidekick package that motorola tells you to download in order to unlock your phone. In fact, if you do install it, you still won't have fastboot which is the program you need. Motorola left it out of the most recent sdk. Don't even bother to find another sdk or fastboot....just find TWRP 2.6.3.1 which is a zipped package findable in many places (google is your friend). Unzip that package and voila....there's fastboot and the dll's to support it.
Now,, no thanks to Motorola, you are ready to get the unlock from your phone so you can ask motorola for the unlock key from motorola using fastboot.
note: fastboot is a CMD application! If you just click on it, it will flash the cmd box and seem to do nothing. You have to open cmd and then find/execute fastboot from there. It's an ugly process....thank you again Motorola.
Once your phone is unlocked, you can use the 1 step install for TWRP.
I realize I should write this up with every step...but I've spent almost two days on something that should take about 15 minutes...and I'm not exactly a newby to this stuff. Motorola just made it as hard as possible to do something that's so simple.

After you have root can you then update to kitkat or will you lose root then?

johnh123 said:
After you have root can you then update to kitkat or will you lose root then?
Click to expand...
Click to collapse
If you have a dev edition on kitkat it's as simple as flashing TWRP and then superSU binary
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
ghstudio said:
I've spent hours on unlocking and rooting my vzw developer's edition. First, the SDK that motorola tells you to download to get fastboot doesn't include fastboot! There are a few ways to get it, but following Motorola's instructions won't get you there. (thanks so much Motorola for posting a solution that doesn't work).
Do Not install the OTA update....if you do, you will not be able to root your phone and you will have to reinstall the stock drivers. It's easy to do, but it will take hours for you to realize that you have to do this. If you have the OTA update already installed, get rid of it by installing the drivers from the motorola site for the developer edition phone (VZW).
You do not need to download the sidekick package that motorola tells you to download in order to unlock your phone. In fact, if you do install it, you still won't have fastboot which is the program you need. Motorola left it out of the most recent sdk. Don't even bother to find another sdk or fastboot....just find TWRP 2.6.3.1 which is a zipped package findable in many places (google is your friend). Unzip that package and voila....there's fastboot and the dll's to support it.
Now,, no thanks to Motorola, you are ready to get the unlock from your phone so you can ask motorola for the unlock key from motorola using fastboot.
note: fastboot is a CMD application! If you just click on it, it will flash the cmd box and seem to do nothing. You have to open cmd and then find/execute fastboot from there. It's an ugly process....thank you again Motorola.
Once your phone is unlocked, you can use the 1 step install for TWRP.
I realize I should write this up with every step...but I've spent almost two days on something that should take about 15 minutes...and I'm not exactly a newby to this stuff. Motorola just made it as hard as possible to do something that's so simple.
Click to expand...
Click to collapse
On a VZW dev edition? Just unlock it at any time kitkat or not, then flash TWRP and then superSU binary, it's as easy as that

Rooting the VZW dev edition moto x is EASY.
Go ahead and install all OTA updates.
Download and install latest Android SDK (comes with adb and fastboot).
Unlock bootloader following instructions on moto's website
Download TWRP and flash using fastboot
Boot into recovery and make a nandroid backup
Reboot phone from TWRP. It will ask if you would like to install superuser and root phone.
done.

adtnry senate
teookie said:
Rooting the VZW dev edition moto x is EASY.
Go ahead and install all OTA updates.
Download and install latest Android SDK (comes with adb and fastboot).
Unlock bootloader following instructions on moto's website
Download TWRP and flash using fastboot
Boot into recovery and make a nandroid backup
Reboot phone from TWRP. It will ask if you would like to install superuser and root phone.
done.
Click to expand...
Click to collapse
Sorry teooki....it SHOULD be easy, but it isn't. Fastboot is NOT included in the SDK that motorola has you download on their unlock page. Yes, it's included on other sites, but not on the one that Motorola distributes. So if you follow their directions, you can't find fastboot, etc.
Your direction should work....Motorola's don't.

I followed Moto's instructions and it worked without issue (Except one of my own making).

homemadehitshow said:
I followed Moto's instructions and it worked without issue (Except one of my own making).
Click to expand...
Click to collapse
If you download the sidekick today, it downloads V1.7 and it does not contain fastboot and the two dll's needed. Earlier, they were giving V1.6 which was complete. This is a new issue with V1.7...and it's something that new users or those who are trying to unlock/root their phones will find incredibly annoying.
(hopefully, they have fixed the Motorola delivered v1.7, but last week, it did not include those files).

I've rooted every phone I've ever owned but I'm having second thoughts on the X. I want to continue to get the ota updates, and with root, that isn't possible is it?
Sent from my Nexus 7 using Tapatalk

RyanTX said:
I've rooted every phone I've ever owned but I'm having second thoughts on the X. I want to continue to get the ota updates, and with root, that isn't possible is it?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It's really easy to unroot then root again (on the developer edition)

Rooting by itself won't stop OTA updates. Installing a custom ROM not based on stock firmware will though.
You might have to re-root after getting an OTA update though.
Sent from my XT1060 using Tapatalk

Thanks guys, got unlocked, rooted, and gravitybox all set up!.
So you guys are saying we can accept OTAs while stock rooted? Should I uninstall xposed before doing an OTA?

edit: sorry, don't know why double post happened...

ghstudio said:
Sorry teooki....it SHOULD be easy, but it isn't. Fastboot is NOT included in the SDK that motorola has you download on their unlock page. Yes, it's included on other sites, but not on the one that Motorola distributes. So if you follow their directions, you can't find fastboot, etc.
Your direction should work....Motorola's don't.
Click to expand...
Click to collapse
Just to clarify, it seems that you must use Motorola's version of fastboot, not the one included in the SDK. I used the SDK version to flash TWRP several times, and each time it appeared to be successful, but it was not. Then I discovered that I needed Motorola's fastboot, found it on the forums here, and used it to flash TWRP. That worked.

Rogers Moto X- HOW CAN I ROOT or UPDATE?

Hey so im pretty new to flashing/rooting as well as new to the moto x (Got it today!). I've done some reading and tried the Pwnmymoto and Motoroot apk's and they both did not install, so im assuming my moto x has taken the OTA updates (i bought it second hand so i didnt know). I am just wondering if theres a way I can root it at this point?? I tried the Root script method using cydia impactor and Telnet kept failing. SO I then was looking at just flashing CWM via fastboot and then installing superuser zip from there as well as flashing a rom. Can anyone tell me if that's safe after the OTA or if theres another way to root? Any help will be mich appreciated as I am really overwhelmed!

I was in the same boat you were but apparently the Rogers update is "coming soon". However if you're impatient like me follow these steps:
1. Unlock your boot loader from Motorola
2. Download rsdlite
3. Download mfastboot
4. Download the sbf for T-Mobile 4.4 retail
5. Download the sbf for the Brasil 4.4 retail
6. Download cwmrecovery
7. Download original Moto boot image
Seems like a lot but here's what you need to do after you have all that stuff assuming you have a windows PC.
1. After the boot loader is unlocked install the custom recovery (I use cwm) via fastboot
fastboot flash recovery cwm.file.name
2. Search the forums for how to flash moto software using rsdlite (don't have the links since I'm on my phone) and flash the T-Mobile files AFTER modifying the XML file like in the instructions.
3. Search my posts and find how to flash the Rogers radio using the Brasil radio files (extract them from the zip)
4. After unlocking the bootloader it'll leave you with a nasty boot image, flash the boot image from the original moto (again search the forums) and it'll go away.
Then you'll have a Moto X on Rogers that has Kit Kat and LTE band 7 working and gets all its updates straight from Motorola! Hope that helps!
Sent from my XT1053 using Tapatalk
---------- Post added at 02:02 PM ---------- Previous post was at 01:28 PM ----------
After unlocking your bootloader then you can flash cwm and install supersu via the install zip feature
Sent from my XT1053 using Tapatalk

No no no.
Look for a thread in General subforum. Rogers root. Very simple. Very easy.
Sent from my XT1058 using xda app-developers app

I did just that and it worked thanks a lot. Anyone reccomend any decent KitKat Roms that retain moto x features?
Sent from my XT1053 using xda app-developers app

There are no roms nor are there any reasons for them. Root install xposed, install gravity box. Done. This is not a flashaholics phone.

I'd never flash a custom rom on this phone....no reason to with xposed, as said above.
When we stop getting updates, then maybe. Maybe. My n7 is still on 4.2.2. Yes....I am cured of my flashaholism.
Flashaholics should not get the Moto x for sure. Lol
Sent from my Moto X cellular telephone...

agree with all the above.
but perhaps OP could use more info on Xposed and Gravity Box?

[Q] Claro chile 4.4.2 update

I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?

AGISCI said:
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
Click to expand...
Click to collapse
There are threads on this in the general folder as well as this folder.
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Do you have the 4.2.2 post camera update installed?

Cozume said:
There are threads on this in the general folder as well as this folder.
Click to expand...
Click to collapse
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Cozume said:
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Click to expand...
Click to collapse
Because I rooted it a month before I unlocked the bootloader.
I still currently have stock recovery though.
Cozume said:
Do you have the 4.2.2 post camera update installed?
Click to expand...
Click to collapse
As far as the post camera update, not sure. My camera version is 3.1.41.2.

AGISCI said:
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Click to expand...
Click to collapse
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.

Cozume said:
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Click to expand...
Click to collapse
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?

AGISCI said:
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
Click to expand...
Click to collapse
Go to Settings->About Phone->System Version. What does it say?

139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk

AGISCI said:
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
From the version numbers here:
http://sbf.droid-developers.org/phone.php?device=0
As best I can tell 139.12.35 is the post camera update. The problem is that no one has a copy of the stock firmware posted anywhere that anyone can find.

If that's the case flashing this firmware will not brick me then correct?
Sent from my Nexus 7 using Tapatalk

You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.

Steve-x said:
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Click to expand...
Click to collapse
I rooted it twice actually. After I unlocked the bootloader it was erased just like you said, and I rooted again using the same method from the first time.

AGISCI said:
If that's the case flashing this firmware will not brick me then correct?
Click to expand...
Click to collapse
Which firmware?
This is from dray_jr on the thread in the Moto X General forum:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
http://forum.xda-developers.com/showthread.php?t=2635366&highlight=brick&page=5

You are in quite a unique situation here actually... since there is no stock image that you can go back to. If there was a 4.4 SBF I would have suggested to flash then take the 4.4.2 update. However, it seems as if there was no 4.4 roll out/update for your carrier at all. So this 4.4.2 carrier update would be more than a simple patch from 4.4 to 4.4.2, it would probably end up removing root since you are going from JB to KK.
Your best bet if you want it now is to do the following...
I AM NOT RESPONSIBLE FOR YOUR ACTIONS OR BRICKING YOUR DEVICE
1) Did you make a backup before you messed with anything in the system? If you didn't, then you have to go through the manual process of making sure that it is as clean as a normal stock image.
2) Do you have the original recovery? If not, find a recovery file for your carrier and flash that.
3) Attempt to flash the OTA in the standard recovery.
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.

mastarifla said:
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
Click to expand...
Click to collapse
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.

I guess I will have to wait then. I can't afford to brick my phone. I captured the update and pulled it with adb so if anyone needs it I will be able to upload it.
Sent from my Nexus 7 using Tapatalk

Cozume said:
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
Click to expand...
Click to collapse
Skrilax_CZ maintains the website where the SBF's are stored. Motorola only releases the Developer Edition images to the public, as far as I know. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he has a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite (or using manual flash, if you like to live dangerously )

mastarifla said:
Skrilax_CZ maintains the website where the SBF's are stored, as far as I know, Motorola only releases the Dev edition images to the public. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite.
Click to expand...
Click to collapse
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
mastarifla said:
Motorola only releases the Developer Edition images to the public, as far as I know.
Click to expand...
Click to collapse
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?

Cozume said:
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Click to expand...
Click to collapse
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Oh and before I forget, hitting the thanks button works too by the way

mastarifla said:
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
Click to expand...
Click to collapse
no, I would never try it; I am just trying to understand what the differences are between the various ways for me to brick my device, lol!
mastarifla said:
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Click to expand...
Click to collapse
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
mastarifla said:
Oh and before I forget, hitting the thanks button works too by the way
Click to expand...
Click to collapse
I know I tried but they limit you to 8 thanks a day and I already used mine up for today! I will come back tomorrow and hit the button, promise. I am very good about that. So good that I use up all my thanks quickly. So odd they do that here, but they do.

Cozume said:
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
Click to expand...
Click to collapse
Yes you should, however it is widely known that the T-Mobile version and the Developer Edition have the exact same hardware/firmware (XT1053), actually I think they may have the exact same software build as well, though I am not sure on that one... if they receive the same OTA update that the T-Mobile version receives, that leads me to believe its the same ROM.

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