Database Develop

[Q] getting off 4.4.2

4.4.2 is a disaster for me on my verizon DE phone....bluetooth keeps disconnecting, calls are breaking up etc. I would like to downgrade to an earlier release that works. My phone is unlocked and rooted.
What can I safely revert to...and how do I do it without bricking the phone?

ghstudio said:
4.4.2 is a disaster for me on my verizon DE phone....bluetooth keeps disconnecting, calls are breaking up etc. I would like to downgrade to an earlier release that works. My phone is unlocked and rooted.
What can I safely revert to...and how do I do it without bricking the phone?
Click to expand...
Click to collapse
I would try a safe boot first. Long press on the power off screen button.

Downgrading is a dangerous affair. Highly NOT recommended.
There are ways, apparently... But most the knowledgeable members will say not to try. Unless its so important and your want outweighs the risk. The worst case scenario being a bricked phone.
Try backing up your data and apps, move the backup to a computer....and try a factory reset. Or flashing the firmware again with mfastboot.
4.4.2 is fine, not sure about your issues...but most are happy with 4.4.2. Your issues are likely app related.
Good luck!

I would recommend downloading the SBF package for your phone and flashing your phone to complete stock and then see how it works if you still want to downgrade after that you'll have to download a 4.4 SPF package and you're not to bypass the bootloader so you wouldn't just installed data system recovery and think that's it but like this previously said if you accidentally hit the OTA to update you could break your phone. sounds like your 4.4.2 install was corrupted. so I would download the 4.4.2 SBF package and do a complete reinstall
Sent from my XT1056 using XDA Premium 4 mobile app

Is this phone different as you can't just flash a 4.4 or 4.3 ROM? Auto downgrade?
Sent from my XT1056 using Tapatalk

r.storm85 said:
Is this phone different as you can't just flash a 4.4 or 4.3 ROM? Auto downgrade?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Downgrading from 4.4.2 can lead to a brick. There's supposedly a very careful way to do it....but anything can go wrong. Not worth the risk IMHO.

r.storm85 said:
Is this phone different as you can't just flash a 4.4 or 4.3 ROM? Auto downgrade?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Yes in that the bootloader doesn't allow itself to be flashed with an older version, signed or not. Trying to downgrade the bootloader can result in an unusable device.
You can flash the bootloader with a current or newer version but not an older version....locked or unlocked, it doesn't make a difference.

tcrews said:
Yes in that the bootloader doesn't allow itself to be flashed with an older version, signed or not. Trying to downgrade the bootloader can result in an unusable device.
You can flash the bootloader with a current or newer version but not an older version....locked or unlocked, it doesn't make a difference.
Click to expand...
Click to collapse
So I'm use to an evo4g and I could flash any ROM once I was rooted with s-off and recovery installed. It wouldn't mess with the boot loader at all. So this phone every ROM comes with a certain boot loader??
Sent from my XT1056 using Tapatalk

r.storm85 said:
So I'm use to an evo4g and I could flash any ROM once I was rooted with s-off and recovery installed. It wouldn't mess with the boot loader at all. So this phone every ROM comes with a certain boot loader??
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Doesn't matter about ROMs. They have nothing to do with the boot loader. And they don't flash boot loaders. But they made the 4.4.2 boot loader so it can't be downgraded. Why...who knows. But they did. Roms make no difference.

kj2112 said:
Doesn't matter about ROMs. They have nothing to do with the boot loader. And they don't flash boot loaders. But they made the 4.4.2 boot loader so it can't be downgraded. Why...who knows. But they did. Roms make no difference.
Click to expand...
Click to collapse
Right so he can't flash a ROM with a 4.4 or 4.3 base? Why would you need to downgrade the boot loader if your rooted and unlocked on 4.4.2 already?
Sent from my XT1056 using Tapatalk

The OP hasn't returned. So I assume he resolved his issues.
I don't know what happens trying to flash an older android version custom ROM actually. An error i would think....or hope anyway. On a nexus you get an error about the boot loader version...I think. But I've never seen it, cause on a nexus you can manually flash any boot loader you want. Older or newer.
I never flashed "ROMs" on my moto x. Just stock with xposed. Custom ROMs have issues, and no moto features.
The x really isn't a "flashing" phone. Definitely nothing like a nexus.

kj2112 said:
The OP hasn't returned. So I assume he resolved his issues.
I don't know what happens trying to flash an older android version custom ROM actually. An error i would think....or hope anyway. On a nexus you get an error about the boot loader version...I think. But I've never seen it, cause on a nexus you can manually flash any boot loader you want. Older or newer.
I never flashed "ROMs" on my moto x. Just stock with xposed. Custom ROMs have issues, and no moto features.
The x really isn't a "flashing" phone. Definitely nothing like a nexus.
Click to expand...
Click to collapse
Ya I jus remember on my evo I could flash back and forth between a 2.2, 2.3, cm6 whatever was available and it didn't matter. Like instead of taking a ota for 4.4.2 on my nexus 7 from 4.3 I jus found a stock rooted 4.4.2 ROM and flashed it. No need for ota or downgrades. And I have nandroids of 4.3 if I wanted to downgrade. Just trying to get a understanding of the ins and outs if this phone before and if I venture into rooting ya know
Sent from my XT1056 using Tapatalk

r.storm85 said:
So I'm use to an evo4g and I could flash any ROM once I was rooted with s-off and recovery installed. It wouldn't mess with the boot loader at all. So this phone every ROM comes with a certain boot loader??
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
S-off on the htc's is more "unlocked" than unlocking the boot loader on the X. With s-off, security checks, etc are bypassed.
I've posted the "long version" before, and I don't have time to retype it..so... The 4.4.2 update on the X changed the boot loader, gpt.bin and other things. They can not be downgraded. Attempts to do so will either fail, cause you problems, and will either brick the phone or set it up to brick if updating later.

KidJoe said:
S-off on the htc's is more "unlocked" than unlocking the boot loader on the X. With s-off, security checks, etc are bypassed.
I've posted the "long version" before, and I don't have time to retype it..so... The 4.4.2 update on the X changed the boot loader, gpt.bin and other things. They can not be downgraded. Attempts to do so will either fail, cause you problems, and will either brick the phone or set it up to brick if updating later.
Click to expand...
Click to collapse
Right I understand the boot loader cannot be downgraded. But if you have root and are unlocked with a custom recovery on the x you can't flash any android version ROM you want ?
Sent from my XT1056 using Tapatalk

r.storm85 said:
Right I understand the boot loader cannot be downgraded. But if you have root and are unlocked with a custom recovery on the x you can't flash any android version ROM you want ?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Its been said over and over. No offence.
No. You can't downgrade the os after you've got 4.4.2. Once on 4.4.2....always on 4.4.2.
Well, you may be able to if you research on how some say they have. But you can brick. Its always a strong risk. If you are ready to buy a new phone in case things go bad.....then search on the ways people have done it.
But none of the guys "in the know" here would recommend it, or help anyone do it.
Nothing else really to say.
Good luck!

r.storm85 said:
Right I understand the boot loader cannot be downgraded. But if you have root and are unlocked with a custom recovery on the x you can't flash any android version ROM you want ?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
first off, I'm on vacation with my family, typing this on my stupid iPad whose autocorrect is driving me batty so if my details seem sparse, sorry, I have typed this info with more details before, search.
if you are talking about custom, 3rd party rooms, maybe... As it depends on what parts they flash, and what their base is.
But if you are talking about moto roms, then NO. Do not, unless you don't mind turning your X into a brick or paper weight.
Again stop thinking about htc s-off and what you were able to do as it doesn't apply to moto. Coming from an Incredible and Thunderbolt with s-off, I know how it's hard to forget. And trying to compare the two will cause many questions,
Due to changes in the bootloader and gpt.bin included with 4.4.2 on the X, 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. If you have an unlocked boot loader you won't need to downgrade to root.
I've read, (not going to dig up the link right now cause I'm on iPad) of some who had 4.4.2 but successfully mfastboot flashed system.img only, and if they went into app drawer -> setting -> security -> they were kicked back out to settings. This is due to system parts relying on the other components. I'm not sure what other problems were found day to day.
Additionally there were/are many reports asking for help because their device won't boot. The common thread.... They had 4.4.2 and downgraded or tried to downgrade.
I'm not going to go into every possible scenario, what might happen, what causes it, what might be safe, etc. the general consensus is once you have 4.4.2 on your X do not try to downgrade!

kj2112 said:
The OP hasn't returned. So I assume he resolved his issues.
Click to expand...
Click to collapse
The OP has now returned and I have not resolved my issues
The advice here appears to be...don't try it so I will either continue to use the moto-x until hopefully 4.4.3 fixes the bluetooth issues, or I'll use my older galazy nexus until Motorola/Google figures out how to get the moto-x working.

ghstudio said:
The OP has now returned and I have not resolved my issues
The advice here appears to be...don't try it so I will either continue to use the moto-x until hopefully 4.4.3 fixes the bluetooth issues, or I'll use my older galazy nexus until Motorola/Google figures out how to get the moto-x working.
Click to expand...
Click to collapse
Have you reflashed 4.4.2 stock and had a fresh start? Cause there aren't any/many other reports of this. You may just need a fresh install.
My x has none of those issues anyway on 4.4.2.
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
And have you tried another Bluetooth device. It could be the problem too. Just not compatible with the x.

KidJoe said:
first off, I'm on vacation with my family, typing this on my stupid iPad whose autocorrect is driving me batty so if my details seem sparse, sorry, I have typed this info with more details before, search.
if you are talking about custom, 3rd party rooms, maybe... As it depends on what parts they flash, and what their base is.
But if you are talking about moto roms, then NO. Do not, unless you don't mind turning your X into a brick or paper weight.
Again stop thinking about htc s-off and what you were able to do as it doesn't apply to moto. Coming from an Incredible and Thunderbolt with s-off, I know how it's hard to forget. And trying to compare the two will cause many questions,
Due to changes in the bootloader and gpt.bin included with 4.4.2 on the X, 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. If you have an unlocked boot loader you won't need to downgrade to root.
I've read, (not going to dig up the link right now cause I'm on iPad) of some who had 4.4.2 but successfully mfastboot flashed system.img only, and if they went into app drawer -> setting -> security -> they were kicked back out to settings. This is due to system parts relying on the other components. I'm not sure what other problems were found day to day.
Additionally there were/are many reports asking for help because their device won't boot. The common thread.... They had 4.4.2 and downgraded or tried to downgrade.
I'm not going to go into every possible scenario, what might happen, what causes it, what might be safe, etc. the general consensus is once you have 4.4.2 on your X do not try to downgrade!
Click to expand...
Click to collapse
OK thanks for the explanation.
Sent from my XT1056 using Tapatalk

moto x not-so-dev edition, what is RSDlite trick?

I simply want to allow my phone to accept any gpt.bin.
i honestly do not care about what it thinks about "downgraded security version".
Is there anyway to do that with a plain fastboot client/interface?
what does RSD does for work around that?
thank you!

sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)

What exactly have you had in your device, flashed, etc...And what you are trying to accomplish.
Need some more details.
And the reason security is set up like that is cause downgrading the Moto X can easily brick your device. Many members have bricked trying to downgrade, or after managing to downgrade...have bricked later.
Without the errors, this section would be overflowing with brick threads. ?

KJ said:
What exactly have you had in your device, flashed, etc...And what you are trying to accomplish.
Need some more details.
And the reason security is set up like that is cause downgrading the Moto X can easily brick your device. Many members have bricked trying to downgrade, or after managing to downgrade...have bricked later.
Without the errors, this section would be overflowing with brick threads. ?
Click to expand...
Click to collapse
fair point. Though i'm still amazed how phone manufacturers manage to get a device bricked by installing software... oh well.
so, my phone history is:
bought moto x dev.
received 4.4.3 OTA update over the 4.4.2 that shipped with it.
flashed twrp because i like image backups and to be able to do minimally required things like ssh tunels and firewall.
and that is pretty much it. i think at some point i used gravitybox when i had 4.4.2 to see what it was about and then reflashed the factory image on top.
So now i wanted to do 2 things.
1. flash the 4.4.4 OTA to see what it is like.
2. if 4.4.4 stock was not decent, i will probably flash a 4.4.2 or whatever the latest CM is for that phone.
edit: ok, forgot to be specific. i'm at step 1 of option 1 still. which is flash 4.4.2 (latest version on the lame motorola stock image repo) and then acept the 4.4.4 OTA. but the stock 4.4.2 gpt.bin triggers that warning.

You can't flash back to 4.4.2. That could/will brick you. And definitely would brick you if you did manage to flash 4.4.2 and then took an ota.
Again, the most talked about subject , next to bootloader unlocking, in the X section.

KJ said:
You can't flash back to 4.4.2. That could/will brick you. And definitely would brick you if you did manage to flash 4.4.2 and then took an ota.
Click to expand...
Click to collapse
You can return to a 4.4.2 nandroid after taking the 4.4.4 OTA if your bootloader is unlocked. I just did it last night.
My story:
1) Unlocked bootloader and rooted with TWRP/SuperSU on 4.4.2;
2) Made a 4.4.2 nandroid and saved it to my PC;
3) Returned to stock 4.4.2 and took the 4.4.4 OTA;
4) Made a 4.4.4 nandroid and saved it to my PC;
5) Inadvertently wiped System partition and Internal Storage;
6) Flashed 4.4.4 system.img from the SBF using mfastboot while in bootloader mode to return to 4.4.4 system;
7) Restored phone to 4.4.2 using TWRP and my 4.4.2 nandroid.
---------- Post added at 04:34 PM ---------- Previous post was at 03:43 PM ----------
gcbxda said:
sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)
Click to expand...
Click to collapse
I am unclear on what you did to get to this point.

Wansanta said:
You can return to a 4.4.2 nandroid after taking the 4.4.4 OTA if your bootloader is unlocked. I just did it last night.
My story:
1) Unlocked bootloader and rooted with TWRP/SuperSU on 4.4.2;
2) Made a 4.4.2 nandroid and saved it to my PC;
3) Returned to stock 4.4.2 and took the 4.4.4 OTA;
4) Made a 4.4.4 nandroid and saved it to my PC;
5) Inadvertently wiped System partition and Internal Storage;
6) Flashed 4.4.4 system.img from the SBF using mfastboot while in bootloader mode to return to 4.4.4 system;
7) Restored phone to 4.4.2 using TWRP and my 4.4.2 nandroid.
---------- Post added at 04:34 PM ---------- Previous post was at 03:43 PM ----------
I am unclear on what you did to get to this point.
Click to expand...
Click to collapse
Ok, but one problem. If you take an ota to a new version now it WILL brick. So you are now stuck on 4.4.2. That is the problem with downgrading.
Sent from my XT1058 using Tapatalk

AGISCI said:
Ok, but one problem. If you take an ota to a new version now it WILL brick. So you are now stuck on 4.4.2. That is the problem with downgrading.
Click to expand...
Click to collapse
Not true - I can restore back to my 4.4.4 nandroid. I have done it 3 times so far trying to debug the problem with my text messages being restored. I can go back and forth b/t my 4.4.2 nandroid and my 4.4.4 nandroid with no problems.

Wansanta said:
Not true - I can restore back to my 4.4.4 nandroid. I have done it 3 times so far trying to debug the problem with my text messages being restored. I can go back and forth b/t my 4.4.2 nandroid and my 4.4.4 nandroid with no problems.
Click to expand...
Click to collapse
NOT THE SAME AS FIRMWARE!!
Firmware contains the bootloader, not so with a nandroid
---------- Post added at 04:35 PM ---------- Previous post was at 04:22 PM ----------
A nandroid can be flashed down NO PROBLEMO.

aviwdoowks said:
NOT THE SAME AS FIRMWARE!!
Firmware contains the bootloader, not so with a nandroid
Click to expand...
Click to collapse
First, he said I was stuck on 4.4.2, and that is what I was responding to. I am not stuck on 4.4.2 - I can go back and forth b/t 4.4.2 and 4.4.4 using my nandroids.
Second, for the record after I took the OTA I had to flash the 4.4.4 system.img from the 4.4.4 sbf b/c I inadvertently wiped my system partition. I tried using RSDLite but it would not recognize my device. When I was in bootloader mode, adb would not recognize my device either. But I was able to use mfastboot to flash the 4.4.4 system.img. After flashing the 4.4.4 system.img from the sbf, I was able to restore back to 4.4.2 system using my nandroid.
So you can selectively flash the sbf files to return to a previous version of android - you don't have to flash the bootloader. My bootloader is 30:B7 and you CAN run 4.4.2 system after you have upgraded to the 4.4.4 bootloader IF you are unlocked and rooted. I don't know what happens if you are not.

if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?

gcbxda said:
if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?
Click to expand...
Click to collapse
See links in my next post.

gcbxda said:
if when you flash an image you pretty much re-partition the whole flash memory (gpt), install the bootloader and system... what exactly 'bricks' the phone with downgrade/upgrade?
Click to expand...
Click to collapse
These links explain it better than I did:
http://forum.xda-developers.com/showpost.php?p=50734236&postcount=29
Q9Nap said:
gpt is the partition table that contains, among other things, the security versions for all other partitions. motoboot contains the various bootloader parts and also contains the security version for gpt that is checked on every boot.
they really only affect locked devices in that they prevent a locked device from being able to downgrade.
although they are not revertible once upgraded, they really don't affect unlocked devices because having the bootloader unlocked allows flashing whatever you want.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=49990727&postcount=33
Q9Nap said:
Gpt is the partition table. It contains security version for the other partitions and prevents downgrading on locked devices. It has a security version itself which is checked at boot. Once it is upgraded, it can't be reverted, but isn't really necessary on unlocked devices since the boot loader will allow flashing anything.
Click to expand...
Click to collapse
I believe in this link where Q9Nap says partition, he means partition table:
http://forum.xda-developers.com/showpost.php?p=50734615&postcount=31
Q9Nap said:
yes security version is usually updated with newer builds, but not always. i don't know what moto uses for criteria to determine whether to increase it or not, i don't work for moto.
attempting to flash a lower security version partition will not brick, it will fail to flash, giving the "failed preflash validation" error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50721154&postcount=21
Q9Nap said:
it is almost impossible to permanently brick an unlocked device. pretty much the only way you could would be to flash an erroneous file to the bootloader partition, preventing the ability to access the bootloader menu.
Click to expand...
Click to collapse

If you want to go back to 4.4.2, just flash the 4.4.2 boot.img and system.img from the 4.4.2 fxz; it will work fine with the updated bootloader and radio.

Q9Nap said:
If you want to go back to 4.4.2, just flash the 4.4.2 boot.img and system.img from the 4.4.2 fxz; it will work fine with the updated bootloader and radio.
Click to expand...
Click to collapse
The op in this thread wants to be able to flash any gpt.bin he wants to. He is being told by others if he does that he will brick. I was quoting you b/c he asked why it would brick and I was showing him that it won't brick, it will just fail and also some of your quotes explain why it will fail. You said it better than I could so I quoted you. Sorry if it was confusing for me to quote you from other threads in this thread.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
gcbxda said:
sigh... it does not F*** allow it, but DO screw up something.
now regular boot just gives me a black screen. while 'factory' and 'bp tools' boot just fine to my fully working system rom (stock 4.4.3)
Click to expand...
Click to collapse
This is another one of @Q9Nap quotes:
with the system booted to a blank screen, press and hold the power button until you see the screen flicker, about 10 seconds.
as soon as it does, quickly release power button, press and hold volume down and then press and hold power.
hold both volume down and power for a few seconds, then release.
you should be in bootloader menu.
it might take a few tries, but you will get it.

Wansanta said:
The op in this thread wants to be able to flash any gpt.bin he wants to. He is being told by others if he does that he will brick. I was quoting you b/c he asked why it would brick and I was showing him that it won't brick, it will just fail and also some of your quotes explain why it will fail. You said it better than I could so I quoted you. Sorry if it was confusing for me to quote you from other threads in this thread.
Click to expand...
Click to collapse
yeah it won't brick, it will just fail to flash.
as long as you can access fastboot mode, you're not totally bricked.

Q9Nap said:
yeah it won't brick, it will just fail to flash.
as long as you can access fastboot mode, you're not totally bricked.
Click to expand...
Click to collapse
It did mess something up for him b/c now a regular boot gives him a blank screen. So I just posted your instructions on how to get from the blank screen to bootloader mode.

Wansanta said:
It did mess something up for him b/c now a regular boot gives him a blank screen. So I just posted your instructions on how to get from the blank screen to bootloader mode.
Click to expand...
Click to collapse
you have to flash boot.img and system.img from the same version.
in addition, you should wipe cache and dalvik-cache.
if there are still issues, you should wipe data also.

THanks a lot for all the info! much apreciated. I think i'm still confused by the horrible reuse of terms all around android history.
When you say boot nowadays, do you mean the fastboot firmware? i wasn't able to flash it some time ago... granted, i'm a fossil on android knowledge nowadays.
Q9Nap said:
you have to flash boot.img and system.img from the same version.
in addition, you should wipe cache and dalvik-cache.
if there are still issues, you should wipe data also.
Click to expand...
Click to collapse
THis is my problem. "from the same version".
phone is on 4.4.3.
lousy motorola only provides dev phone images to 4.4.2 (and 4.2.2). even though they distributed 4.4.3 for ages and now are roling out 4.4.4
There is nothing from the same version i can flash. specially if i want to try the OTA 4.4.4

gcbxda said:
THanks a lot for all the info! much apreciated. I think i'm still confused by the horrible reuse of terms all around android history.
When you say boot nowadays, do you mean the fastboot firmware? i wasn't able to flash it some time ago... granted, i'm a fossil on android knowledge nowadays.
THis is my problem. "from the same version".
phone is on 4.4.3.
lousy motorola only provides dev phone images to 4.4.2 (and 4.2.2). even though they distributed 4.4.3 for ages and now are roling out 4.4.4
There is nothing from the same version i can flash. specially if i want to try the OTA 4.4.4
Click to expand...
Click to collapse
I don't think you mentioned what carrier you're using.
Moto sux at updating their fxz files, that's why there is firmware team:
http://sbf.droid-developers.org/phone.php?device=0
WARNING! shameless plug forthcoming....
Also feel free to try my Google Play edition fxz:
http://forum.xda-developers.com/moto-x/development/fxz-xt1053-xt1060-google-play-edition-4-t2715488

[Q] XT1053 4.4.4 Root?

Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;

stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358

You'll have to unlock the bootloader. No way around it.

Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?

Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.

I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.

stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app

mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4

stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app

Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.

stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.

4.4.4
a year old post by dray_jr says the following:
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 to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?

Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)

Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520

Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?

nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...

dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.

How to avoid bricked devices?

I'd like to start this thread as a "what to not do to brick your device" discussion. I've noticed a lot of people bricking randomly with the 5.1 update and not a lot of people talking about what causes it. Is it random? Did you flash certain files from a certain ROM or Google? Did you mix 5.0.1 boot/radio with a 5.1 ROM? Can we find a solution to fix bricked devices?
Any insight here to help others avoid this problem will be appreciated!

read carefully and follow instructions, and all will be fine.

I bricked mine by flashing older CM 12 ZIP which flashed 5.0.1 bootloader over 5.1 one, so I think that's the cause - the bootloader doesn't like being downgraded. Might even be a "security feature", now that I think about it - because "fastboot flash bootloader" won't even let you flash older bootloader than you already have.
simms22 said:
read carefully and follow instructions, and all will be fine.
Click to expand...
Click to collapse
That's rather deceiving, don't you think?

Tasssadar said:
I bricked mine by flashing older CM 12 ZIP which flashed 5.0.1 bootloader over 5.1 one, so I think that's the cause - the bootloader doesn't like being downgraded. Might even be a "security feature", now that I think about it - because "fastboot flash bootloader" won't even let you flash older bootloader than you already have.
That's rather deceiving, don't you think?
Click to expand...
Click to collapse
whats deceiving? that somethings are messing things up in cm? what can i tell you, stay away from cm. i do. just because cm is messing things up? cm isnt android in general, its cm. they do things differently than aosp or stock android. i personally decided to stay as far away from cm years ago. anyways, i flashed 5.1, then reflashed 5.0.2, then flashed 5.1 again, all on the old bootloader, no issues. as long as you read about whats going on, and follow instructions properly, all will be alright.

adoublearonn said:
I'd like to start this thread as a "what to not do to brick your device" discussion. I've noticed a lot of people bricking randomly with the 5.1 update and not a lot of people talking about what causes it. Is it random? Did you flash certain files from a certain ROM or Google? Did you mix 5.0.1 boot/radio with a 5.1 ROM? Can we find a solution to fix bricked devices?
Any insight here to help others avoid this problem will be appreciated!
Click to expand...
Click to collapse
When you upgrade to 5.1 the OEM Unlock (under dev options) automatically gets switched off (due to new security which prevents stealing a device and just flashing it bypass the security code). Where people are running into trouble is they are upgrading to 5.1 and the latest radio having OEM Unlock unchecked and then flashing CM which includes the old radio and bootloader, at this point you are stuck. Can't flash a custom recovery because your bootloader is locked, can't unlock the bootloader because you have to boot into an os and check the OEM Unlock, and you can't do a system restore because you cannot access recovery.
Sent from my Nexus 6 using XDA Free mobile app

For me. I came from a 5.0.2 ROM. Flashed the newest radio and boot for 5.1 and flashed a 5.1 ROM. I DO SHOW an unchecked OEM unlock. So am I to assume if I wished to flash a 5.0.2 ROM to check OEM unlock? I don't think I will "downgrade"...but just curious. Thank you.
Sent from my Nexus 6 using XDA Free mobile app

How do I remove TWRP?

I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.

Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.

@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up

kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.

kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.

I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.

kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.

kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?

It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.

kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?

did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32

@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.

Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.

mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?

Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.