Database Develop

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] 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.

[Q] Moto X DE Is 4.4.2 worth it?

Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4

I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can't downgrade now due to the bootloader update.

KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
I took the OTA when it hit my phone. I can't say that I notice anything really different after the upgrade. No negative impacts at least.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
I didn't lose root, and write protection stayed disabled (due to unlocked bootloader). So I just had to reflash my custom logo.bin, and I haven't put custom recovery back on, I don't need to right now. Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X

KidJoe said:
Only issue would be, if I do find a bug that wasn't there in 4.4, I can downgrade now due to the bootloader update.
Click to expand...
Click to collapse
Not to nag, but probably important to correct... you CAN'T downgrade now.
Updated last night. I did it cause I wanted to be on latest and greatest, plus I think the camera does take better low-light pictures now.

Schaweet said:
You don't have root unless you put the custom recovery back on there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.

cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
Not much different, you can always update everything but motoboot and gpt so you can still downgrade if you don't like...
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
FWIW, The only things I notice are that USB OTG works in 4.4.2 and static in bluetooth headphones when using wifi is gone.

Schaweet said:
You don't have root unless you put the custom recovery back on there.
Click to expand...
Click to collapse
I beg to differ. Root Explore, Greenify, Wifi Tether for Root... all work, as do going into system and renaming files, and downloading/installing the hosts file in AdAway from BigTinCan.com (which survive power off/on, so helps to tell me write protection is still disabled).
On an unlocked bootloader, once you have rooted, you can use whatever recovery you like.
Now, for LOCKED bootloader on the X which are rooted via RockMyMoto or SlapMyMoto without using MotoWPNoMo, you might need to keep that "recovery trick" in place so you can boot with write protect disabled. In that case you would loose the ability to boot with write protect disabled (which makes root useless) when you put stock recovery back on, but that is different and doesn't "unroot" you.
---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------
Mike7143 said:
Not to nag, but probably important to correct... you CAN'T downgrade now.
Click to expand...
Click to collapse
You are right. that is a Typo that I need to fix!!!

cw18306 said:
Moto X DE rooted. VZW native tether hack. Replaced the "warning unlocked bootloader" message. The rest is stock. Is the 4.4.2 update worth it? I don't see anything that appears to be much different from 4.4
Click to expand...
Click to collapse
It took me about an hour to do the update because I am a novice and had to do a bunch of stuff first but I did it and my phone is back to its current state...except now I am using the xposed wifi tether instead of the hack (And the xposed one is better). So it was worth it just to have the latest and get rid of that wifi mod that i never liked to begin with. Apparently the upate makes battery life better but my battery life was already awesome considering I came from Gnex. So I guess the question is why not update? If you know what you are doing it shouldnt take 5-10 minutes.

from what people are saying it seems 4.4.2 makes a huge difference for battery life, i don't have it yet on my xt1058 so i can't say for sure...

Yeah I really only root for the tether hack and tibackup. Both of which I've used less and less since I got this phone. I've never had any issues with the phone and battery life is awesome so I'll probably just wait for some more feedback on the update before I go through the hassle of doing it.

How do you get rid of the unlocked bootloader message? Just flashing logo.bin?

jawest12 said:
How do you get right of the unlocked bootloader message? Just flashing logo.bin?
Click to expand...
Click to collapse
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
CartlandSmith said:
If you are rooted and locked on 4.4 using SlapMyMoto and MotoWPNoMo, can you downgrade to 4.2.2 and use PwnMyMoto then RockMyMoto then SlapMyMoto 0.5c to get the "recovery trick" back? Or is the ability to do that gone once you have used MotoWPNoMo?
Click to expand...
Click to collapse
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.

KidJoe said:
Yes replacing logo.bin. the logo.bin's I made for 4.4 work on 4.4.2 too.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
I am not sure since I have a Dev Edition with an unlocked bootloader, so I never used them... only read about them.
Click to expand...
Click to collapse
Thank you for the response. Where can I download your logo.bin to flash?

tcrews said:
No, you'll keep root after taking the update. You do not need to reinstall TWRP to have root. Root is root, a recovery is a recovery. If you lost root, you'd need to install a recovery that allows you to install root, but you don't lose root from taking the OTA.
Click to expand...
Click to collapse
For a n00b,,,,,English please?!

jawest12 said:
Thank you for the response. Where can I download your logo.bin to flash?
Click to expand...
Click to collapse
See the "edit" section of Post #150 in this thread -> Moto X Boot Logos The post also has info how they were made and a link to a zip that contains a little more than 25 LOGO.BIN files, and matching BMP's so you can see what they look like first (or use to flash clogo if you have never unlocked your bootloader). they do include the 0-3% battery indication too.
I'm using Logo-prettydev2.png.bin included in the zip file.

PennyKnight said:
For a n00b,,,,,English please?!
Click to expand...
Click to collapse
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.

tcrews said:
Moto X Developer Edition only....as this thread title states a DE model.
The OTA doesn't remove ROOT. You need the stock recovery to install the OTA so you have to flash the stock recovery.img back to the phone to install the OTA. Once the OTA is done.....you do NOT need to install TWRP or any other recovery to have root. You never lost root.
All of this is assuming you had previously installed TWRP to root a Moto X Developer Edition (DE) and want the OTA to 4.4.2.
Click to expand...
Click to collapse
Also for noobs, how do I flash the stock recovery?

Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app

zackiv31 said:
Also, does flashing stock recovery erase any data? (Like messages/pictures/etc..? If not, what actions actually erase this data... I feel like I never know)
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
No. Flashing Recovery does NOT erase data. Using RSDLite to flash an entire SBF/XML file (without editing it) will erase data.. or giving the following command via PC with your phone in fastboot mode will erase data... mfastboot erase data

KidJoe said:
I have a Dev X and pretty much in the same boat as you.... Unlocked, Rooted, changed logo.bin, but I'm using Wifi Tether for root app rather than the entitlement apk hack.
It was easy to take because I was basically stock... just flash stock recovery back on, and take the OTA. Since it sounds like you did the entitlement apk replacement, you'd need to undo that.
How do I undo the entitlement apk. I tried to reverse it but messed it up.
Not good at that stuff.
Thanks
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse

Will my unlock code work after update?

I have the RW version and unlocked with the China man... My question is once I take the OTA will it relock my bootloader?? And if I relock it can I use the same code to unlock it again? And last can I still use the sbf file on this phone or must I manually flash the partitions? Thanks guys
Sent from my XT1049 using xda app-developers app

No it will not relock it it. Once the flags are triped there is no going back to locked. Just relocked
Sent from my XT1058 using xda app-developers app

I've been wondering this too. The last phone I had (Google Galaxy Nexus) was unlocked and rooted running CM 10.1 and then CM 11 so it never received the OTA's. But mine and my wife's Moto X Developer Editions are both unlocked and rooted but running stock 4.4.2.
As I understand it we'll still receive OTA's correct? Once we do there is a chance they will lock back up and we'll lose root correct? The reason I say chance is because both phones are setup through Titanium to "attempt" to keep root and I know it doesn't always work.
I'm assuming the bootloader gets relocked? If it does how do we go about unlocking and rooting them again? Will the codes we got from Motorola work or do we need to go through the entire process of unlocking then rooting?
Sorry for the newb questions. Like I said, every phone I ever unlocked and rooted I put custom ROMs on them so I never got the OTA's.

Yeah I've read about it going to relock if I do it.. But can a ota update relock it.. And if it did.. Will my code still work.
Sent from my XT1049 using xda app-developers app

Yes, you can flash using either RSDLite or fastboot/mFastboot
If you do relock your bootloader, yes the same code will work to unlock it later.
And... already said here -> http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394
[*]Taking future OTA's will not re-lock your bootloader, however you will need to have stock recovery on your phone, and revert any modified system files, i.e. get back to "stock" or nearly stock, in order to install OTA's, just like those with Developer Edition phones have to do. (this is due to the OTA updates containing a manifest file that lists files and their "check sums" it looks for on your phone before it starts. If they are not on your phone, or the ones on your phone don't match the expected check sum, the OTA install will fail.)
[*]Flashing with RSDLite will not re-lock your bootloader
[*]Only manually re-locking via the relock process (moto has on the Dev Edition web site, it is fastboot oem lock ) will re-lock your bootloader.
Click to expand...
Click to collapse

So, I'd need to reinstall all the bloatware that came on the phone originally? That's pretty much all I took off the phone was all of Verizon's crap that I'll never use nor have any interest in. The only other thing I did was edit the navigation keys out using the build.prop, but that's easy enough to turn back on. My phone as well as my wife's are stock aside from the removal of the bloatware and taking the nav keys out of my phone.

Thanks kid. I've just read mixed messages about bricking my device from ota updates and sbfs. Thanks again.
Sent from my XT1049 using xda app-developers app

The Tallest said:
So, I'd need to reinstall all the bloatware that came on the phone originally? That's pretty much all I took off the phone was all of Verizon's crap that I'll never use nor have any interest in. The only other thing I did was edit the navigation keys out using the build.prop, but that's easy enough to turn back on. My phone as well as my wife's are stock aside from the removal of the bloatware and taking the nav keys out of my phone.
Click to expand...
Click to collapse
When it comes to taking OTA's, yes.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. Because of this, you must be "stock" (or as close to stock as possible). Any bloat you deleted, needs to be put back. Any files you altered (like build.prop) need to be reverted. Any apps you froze with Titanium Backup or the like, may need to be unfrozen.
Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
kicker22004 said:
Thanks kid. I've just read mixed messages about bricking my device from ota updates and sbfs. Thanks again.
Sent from my XT1049 using xda app-developers app
Click to expand...
Click to collapse
Yes, there are some cautions and warnings about bricking... They usually relate to if you've taken 4.4.2 and try to downgrade your rom to 4.4 or lower. Or if you flash only parts of a rom using mFastboot and get into a state when you have "mixed" versions on your phone...
Due to changes in the bootloader included with the 4.4.2 Update, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2.

KidJoe said:
When it comes to taking OTA's, yes.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. Because of this, you must be "stock" (or as close to stock as possible). Any bloat you deleted, needs to be put back. Any files you altered (like build.prop) need to be reverted. Any apps you froze with Titanium Backup or the like, may need to be unfrozen.
Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
Click to expand...
Click to collapse
Well damn, I'm kind of screwed then as I deleted all those dumbass Verizon apps that I have no use for and didn't bother making backups of any of them. I'll have to check the "Apps" folder and see if the .apk files are still there so that Google Play can redownload them at some point.
I don't even think the backup I made via TWRP has them. Although I think Motorola's website does have the system image so I can probably just reflash that when the next OTA comes out.

The Tallest said:
Well damn, I'm kind of screwed then as I deleted all those dumbass Verizon apps that I have no use for and didn't bother making backups of any of them. I'll have to check the "Apps" folder and see if the .apk files are still there so that Google Play can redownload them at some point.
I don't even think the backup I made via TWRP has them. Although I think Motorola's website does have the system image so I can probably just reflash that when the next OTA comes out.
Click to expand...
Click to collapse
TWRP.. then you have an unlocked bootloader? If so, you do have the option to flash the SBF to revert to stock, or unzip it and just mfastboot flash system.img onto your phone, because you can always re-root later.

KidJoe said:
TWRP.. then you have an unlocked bootloader? If so, you do have the option to flash the SBF to revert to stock, or unzip it and just mfastboot flash system.img onto your phone, because you can always re-root later.
Click to expand...
Click to collapse
Yes, my boot loader is unlocked. That's good to know that I can do that, thanks.

Wait... Did I miss read that... You can flash sbf in TWRP?? sorry but I've been on Gnex and haven't had a moto since the droid x... Things have changed a bit.
Sent from my XT1049 using xda app-developers app

kicker22004 said:
Wait... Did I miss read that... You can flash sbf in TWRP?? sorry but I've been on Gnex and haven't had a moto since the droid x... Things have changed a bit.
Sent from my XT1049 using xda app-developers app
Click to expand...
Click to collapse
Yes, you miss read.. I was saying that he could just flash the SBF (implying RSDLite) or unzip it and mfastboot flash "part"
because being unlocked he could still root afterwards

OK that's what I thought. Thanks again for the info..looks like I'll sit tight with my unlocked bootloader until RW gets 4.4 update.
Sent from my XT1049 using xda app-developers app

Unable to upgrade to 6.0-marshmallow

Hi,
I'm trying to upgrade my Moto X 2014 to Marshmallow. The OTA upgrade appeared last week, but fails without any error message.
When the devices was new, I unlocked the boot and rooted it. The first upgrade (5.0) installed without any problem, but I chose not to root it anymore.
Upgrade to 5.1 failed. It worked after I reflashed the recovery.img(following idea from Q18 in http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769). The same happened with the Stagefright update some time later. Now, the Marshmallow upgrade is available, but reflashing recovery.img is no longer working. It simply fails without any meaningful message. Could someone help me?
Tks,
Roberto
Device:
Moto X 2014, Brazilian retail version, version 23.16.2.victara_retbr.retbr.en.BR.retbr, version number LPE23.32-14.2

rgreiner said:
Hi,
I'm trying to upgrade my Moto X 2014 to Marshmallow. The OTA upgrade appeared last week, but fails without any error message.
When the devices was new, I unlocked the boot and rooted it. The first upgrade (5.0) installed without any problem, but I chose not to root it anymore.
Upgrade to 5.1 failed. It worked after I reflashed the recovery.img(following idea from Q18 in http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769). The same happened with the Stagefright update some time later. Now, the Marshmallow upgrade is available, but reflashing recovery.img is no longer working. It simply fails without any meaningful message. Could someone help me?
Tks,
Roberto
Device:
Moto X 2014, Brazilian retail version, version 23.16.2.victara_retbr.retbr.en.BR.retbr, version number LPE23.32-14.2
Click to expand...
Click to collapse
Flash the stock 5.1 firmware to get completely back to stock, then try again.
Sent from my XT1095 using Tapatalk

AGISCI said:
Flash the stock 5.1 firmware to get completely back to stock, then try again.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Isn't there a way to avoid it? I would like to avoid fully resetting the phone.
Tks,
Roberto

rgreiner said:
Isn't there a way to avoid it? I would like to avoid fully resetting the phone.
Tks,
Roberto
Click to expand...
Click to collapse
No there is no other way. An OTA fails if you are not 100% stock. So that means no root, no xposed, no custom kernels, no modifications to anything that is in system. If even one thing is modified it WILL fail. So the solution is to go back to 100% stock by flashing the full firmware.
Sent from my XT1095 using Tapatalk

AGISCI said:
No there is no other way. An OTA fails if you are not 100% stock. So that means no root, no xposed, no custom kernels, no modifications to anything that is in system. If even one thing is modified it WILL fail. So the solution is to go back to 100% stock by flashing the full firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
That's strange. When I upgraded to 5.1 and 5.1/stagefright, I had exactly the same setup: Boot unlocked, no root. It upgraded fine after just reflashing 'recovery.img'. Actually, when I upgraded from 4.4 to 5.0, the phone was rooted, and yet it upgraded perfectly.
Roberto

rgreiner said:
That's strange. When I upgraded to 5.1 and 5.1/stagefright, I had exactly the same setup: Boot unlocked, no root. It upgraded fine after just reflashing 'recovery.img'. Actually, when I upgraded from 4.4 to 5.0, the phone was rooted, and yet it upgraded perfectly.
Roberto
Click to expand...
Click to collapse
Again as I stated, something is modified. In the OTA it checks for modifications, if it finds something modified it fails and exits without upgrading it. So if you want to take the upgrade you need to flash back to stock.
This forum is filled with posts and topics of people having to unroot to get the OTAs to work. So why it worked for you, no idea, since you are the only person I have ever seen who has stated that it worked while rooted. According to every other post on this forum, OTA fails when rooted...
Sent from my XT1095 using Tapatalk

AGISCI said:
Again as I stated, something is modified. In the OTA it checks for modifications, if it finds something modified it fails and exits without upgrading it. So if you want to take the upgrade you need to flash back to stock.
This forum is filled with posts and topics of people having to unroot to get the OTAs to work. So why it worked for you, no idea, since you are the only person I have ever seen who has stated that it worked while rooted. According to every other post on this forum, OTA fails when rooted...
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok. But still, why fully-reflashing? As I said, my phone is NOT rooted since 4.4. It's only boot unlocked, and both 5.0 and 5.1 where installed and no modifications made after that.

rgreiner said:
Ok. But still, why fully-reflashing? As I said, my phone is NOT rooted since 4.4. It's only boot unlocked, and both 5.0 and 5.1 where installed and no modifications made after that.
Click to expand...
Click to collapse
Look, somewhere in your phone there IS something that is NOT stock. What it is, we don't know. The ONLY way for you to take an OTA is to be 100% stock, if not it will fail. So the only solution is to get your phone to 100% stock to take the OTA, which means flash the full firmware. If you don't want to flash the full firmware then you will stay on 5.1.
Sent from my XT1095 using Tapatalk

AGISCI said:
Look, somewhere in your phone there IS something that is NOT stock. What it is, we don't know. The ONLY way for you to take an OTA is to be 100% stock, if not it will fail. So the only solution is to get your phone to 100% stock to take the OTA, which means flash the full firmware. If you don't want to flash the full firmware then you will stay on 5.1.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok,
if that's the only route left, I will try it.
Tks,
Roberto

rgreiner said:
Ok,
if that's the only route left, I will try it.
Tks,
Roberto
Click to expand...
Click to collapse
Ok. After backing-up everything I needed, I flashed the stock 5.1 image. Reinstalled all apps (actually, everything reinstalled automatically), restored backups, and then tried the upgrade. Both stagefright and marshmallow upgrades worked fine, and 6.0 is running fine.
Tks.