Related
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
I updated my Motorbike X XT1058 for 4.4.4 (KXA21.12 VZW_XT1060_4.4.4-KXA21.12-L1.26_1FF) and it wanted to do the DOWNGRADE for 4.4.3 or 4.4.2. Some way for that?
The GPT.BIN in 4.4.4 is different from 4.4.3, which is different from 4.4.2, which is different from 4.4.0's.
Motoboot.img is different between 4.4.3 and 4.4.2. 4.4.2's is different from 4.4.0.
These will prevent a complete, successful and safe downgrade of the rom version.
If you've seen all the "don't downgrade or you'll brick" warnings, this is what its talking about.
This ^^^
But a better question is WHY would you want to downgrade?
I did not like because of the modification Verizon
Christian Correia said:
I did not like because of the modification Verizon
Click to expand...
Click to collapse
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Darth said:
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Click to expand...
Click to collapse
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
DROID_4_UsEr said:
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
Click to expand...
Click to collapse
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
KidJoe said:
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
Click to expand...
Click to collapse
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
DROID_4_UsEr said:
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
Click to expand...
Click to collapse
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
I did try but no succes
KidJoe said:
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
Click to expand...
Click to collapse
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
DejanPet said:
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
DROID_4_UsEr said:
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
Click to expand...
Click to collapse
But you should know Sunshine developers charge a fee of 25 bucks to unlock and it works but you need to have a pay pal account and enough money for it
DejanPet said:
The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
its documented in the sunshine thread that once 4.4.4 is on your phone its too late. even if you manage to downgrade it without bricking, the parts sunshine relies on will already have been patched and cant be downgraded. so downgrading wont help you to get sunshine to work
Help me regarding going back to4.4.3... I have the package and everything ( rsd lite stuff) but boot loader seems updated while i did ota to 4.4.4 .. its keep saying downgraded security pre flash vvalidation error while flashing 4.4.3.
4.4.3 was silky smooth. 4.4.4 is stuttery horrible in many apps and also generally to some extent
Theoretically this should be possible right to install old boot loader and then fash 4.4.3??
How and where to get boot loader old one.??.. I mean this is the thing they do in factories no?? Before flashing a firmware...
That would remove security downgrade verification right??
Reason is 4.4.4 is horribly stuttering Feels like a cheap china mobile
Search this forum for "downgrade brick" and see what others have had happen.
Long story short: just. don't. do it.
Problem. Is while doing an it's update after downgrading . which causes different kernel and system IMG to cause problems they say.
Still wonder why no one is into what causes the security check , how to get an old boot loader into the phone ... Wat they do I manufacturing? No phone comes with any software.. They are uploaded into it after emptiness. .. So why not 4.4.3 now .. if its the bootloader that causes problems why can't we install a boot loader that will match 4.4.3 ?? ...
All the forum is full f bricked moto x when there was no 4.4.4 firmware available. Nowthey are available.. So its not much problem now as it used to be.
Pls some one look into it... No one curious enough to decode the way?? I mean is this acceptable ? That we can't match 4.4.3 in a moto x ..
4.4.4 stuttering? User error
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
The problem is boot.IMG which has the kernel also has the dowbhrade security check error ... So when I falshed 4.4.3 over the 4.4.4 phone , ended up having kernel of 4.4.4 with system of 4.4.3.. ( I had to skip boot.IMG of kernel, motoboot.IMG , and got.bin)
Kernel is where interface comes...
Is there a way to flash the boot.IMG of 4.4.3 ... I would be satisfied with that... No need got.bin and motoboot.IMG flashing...
Also when I see this forum no one mention boot.IMG only motoboot and got.bin are mentioned.. Am I the only one having prob with boot.IMG flashingflashing.. If so pls tell kidjoe, iwould be happy
And AM NOT OTA OR MANUALLY UPDATIG TO LOLLIPOP IF I HAVE 4.4.3...
I HAVE OTA UPDATED 4.4.4 after having 4.4.3 system and 4.4.4 kernel .. To attain full 4.4.4 and it doesn't cause brickig .
Brickin occurs only when u update to next release it seems. 4.4.4 update is easy with the device it seems
nhizzat said:
4.4.4 stuttering? User error
Click to expand...
Click to collapse
Pls help me .. Wats user error.. I mean wat u mean by my error??
govardhan87 said:
Pls help me .. Wats user error.. I mean wat u mean by my error??
Click to expand...
Click to collapse
Most likely something you've modified or installed is causing the stuttering.
govardhan87 said:
The problem is boot.IMG which has the kernel also has the dowbhrade security check error ... So when I falshed 4.4.3 over the 4.4.4 phone , ended up having kernel of 4.4.4 with system of 4.4.3.. ( I had to skip boot.IMG of kernel, motoboot.IMG , and got.bin)
Kernel is where interface comes...
Is there a way to flash the boot.IMG of 4.4.3 ... I would be satisfied with that... No need got.bin and motoboot.IMG flashing...
Also when I see this forum no one mention boot.IMG only motoboot and got.bin are mentioned.. Am I the only one having prob with boot.IMG flashingflashing.. If so pls tell kidjoe, iwould be happy
And AM NOT OTA OR MANUALLY UPDATIG TO LOLLIPOP IF I HAVE 4.4.3...
I HAVE OTA UPDATED 4.4.4 after having 4.4.3 system and 4.4.4 kernel .. To attain full 4.4.4 and it doesn't cause brickig .
Brickin occurs only when u update to next release it seems. 4.4.4 update is easy with the device it seems
Click to expand...
Click to collapse
Most reference only GPT.BIN and MOTOBOOT.IMG because they are the partition table, bootloader, trusted zone, etc. Those two fail with an error that stops RSDlite, and those two error when trying to flash older versions via mFastboot. After getting those errors, that is usually when people start posting their phone is bricked and asking for help.
I've seen some downgrade everything but those two (meaning, yes they did even flash boot.img) using mfastboot (latest being from the 4.4.2 and 4.4.4 dev edition roms). But again, if you get forgetful and take an OTA, or sell it to someone in that state, you could cause a brick later.
You could be able to downgrade parts without bricking, we've seen that happen... In addition, like when people on 4.4.2 downgraded this way to 4.4, we saw features not work (I mentioned the security menu earlier) if they managed to not brick.
In some cases, when in the bricked or non-booting state from attempting to downgrade, flashing the full SBF of the newest version (4.4.4) manually via mFastboot with a few extra commands was enough to recover the phone and get it working. (at least check the phone's bootloader version and flash the SBF for that bootloader or a higher/newer SBF version). On some occasions they've bricked bad enough that they've needed to follow -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 and other times nothing worked and their phone was dead.
That being said, the many many threads asking for help due to phones not booting, being bricked, etc from attempting to downgrade are why we caution people to not downgrade and why you wont get much help doing it. Its not 100% safe or fool proof. If it goes wrong you could have a lot of work on your hands or a non-usable phone. Just because it has worked for you, doesn't mean it works and others can/should try it. We've seen too many times how people have bricked. For example a while ago there was someone claiming its possible to downgrade the XT1052 without issues, it was 100% safe, he did it without failure so it must be safe. Then XT1052 people who tried it started creating threads that their phone was bricked from following his steps asking for help. The thread was closed/locked.
But its your phone, do what you want. If you advise others to downgrade, or claim its safe to downgrade, make sure you include a clear warning that there are risks!!
govardhan87 said:
Help me regarding going back to4.4.3... I have the package and everything ( rsd lite stuff) but boot loader seems updated while i did ota to 4.4.4 .. its keep saying downgraded security pre flash vvalidation error while flashing 4.4.3.
4.4.3 was silky smooth. 4.4.4 is stuttery horrible in many apps and also generally to some extent
Theoretically this should be possible right to install old boot loader and then fash 4.4.3??
How and where to get boot loader old one.??.. I mean this is the thing they do in factories no?? Before flashing a firmware...
That would remove security downgrade verification right??
Reason is 4.4.4 is horribly stuttering Feels like a cheap china mobile
Click to expand...
Click to collapse
You do realize the ONLY change between 4.4.3 and 4.4.4 is the security fix for ssl right. It was less then 16 meg for the update so your issues are NOT related to 4.4.3 vs 44.4 I would look elsewhere for the cause of your issues before you completely brick your phone
adm1jtg said:
You do realize the ONLY change between 4.4.3 and 4.4.4 is the security fix for ssl right. It was less then 16 meg for the update so your issues are NOT related to 4.4.3 vs 44.4 I would look elsewhere for the cause of your issues before you completely brick your phone
Click to expand...
Click to collapse
dear adm1jtg... Am not a developer in android or even a software guy. I will be unable to see these things or verify that its only security update and will not affect kernel of the os- although they said wat u said..
That's y I posted here. Thanks for replying.
Would be happy if u tell if kernel is same in 4.4.3 And 4.4.4. ( if u know)
govardhan87 said:
dear adm1jtg... Am not a developer in android or even a software guy. I will be unable to see these things or verify that its only security update and will not affect kernel of the os- although they said wat u said..
That's y I posted here. Thanks for replying.
Would be happy if u tell if kernel is same in 4.4.3 And 4.4.4. ( if u know)
Click to expand...
Click to collapse
Kernel is not identical but close as far as i know as the security fix was kernel based. Ok that said instead of trying to change your stock rom i would try a custom kenrel. Which one you ask.... I am currently using zwliew. There is a thread for it in the dev area. You could also try a custom stock based rom like krypton or epsilon (also have threads in dev section).
Downgrading really shoudnt EVER be considered for any reason as you have a very good chance or permanently bricking your phone.
Agree with many here...
Even tho some say they've downgraded OK... Let's see how the next ota works out for them. Oops!
So .... Here's my 2 cents on downgrading........ DON'T !
?
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.
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
Most of the others relocked their bootloader after flashing the full 5.1 image and ended up in a bootloop. Not the end of the world but now the "enable OEM unlock" unsets every time you boot so if you lock the bootloader and end up in a bootloop, you cannot unlock the bootloader which means you cannot flash anything to recover.
Dont relock your bootloader?
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Also if you update to 5.1, the stay with 5.1 Roms to be on the safe side?
Thanks in advance, just want to help pthers with same questions
pallefar said:
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Click to expand...
Click to collapse
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So based on what has helped avoid bricks on the Moto X:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table*;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table*;
4) make sure OEM unlock and USB debugging are enabled each time you flash;
5) never take an OTA unless you have reverted back to stock completely;
6) never upgrade the bootloader w/o also upgrading the partition table* and vice-versa; and
7) use mfastboot for flashing**.
* there is apparently no partition table on a Nexus
** this may or may not be necessary on the Nexus 6
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
randy6644 said:
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
Click to expand...
Click to collapse
Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.
Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
pallefar said:
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Click to expand...
Click to collapse
I personally.
I'm not on 5.1 yet so I cant say if the "Enable OEM lock" is controlled by the bootloader at boot or the Kernel / OS..
Better be safe then sorry
JulesJam said:
I think people are bricking b/c they are downgrading the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table;
4) make sure OEM unlock and USB debugging are enabled each time you flash; and
5) never take an OTA unless you have reverted back to stock completely.
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
Click to expand...
Click to collapse
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
i believe it would be controlled by the kernel/OS...and thats how it gets disabled upon boot of 5.1
pallefar said:
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
Click to expand...
Click to collapse
I think I would add to that not to do anything to cause a version mismatch b/t the bootloader and the partition table. And since you shouldn't be downgrading those, what that means is never upgrade the bootloader w/o also upgrading the partition table and vice-versa.
Again, maybe you can get away with upgrading the bootloader w/o upgrading the partition table but I can't think of any reason not to have those both be on the same version.
One more thing - use mfastboot not fastboot to flash. mfastboot may only be needed for the larger files like system.img but I just use mfastboot all of the time and then I don't have to worry about it.
benefit of mfastboot
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
pallefar said:
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
Click to expand...
Click to collapse
http://mark.cdmaforums.com/MotoX-mFastboot.htm
pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks. This will be seen by any roms that pretty much is just a renamed CM rom. My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
Sent from my Nexus 6 using Tapatalk
safe side
So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.
I guess AOSP is a safer bet at the moment? like Chroma rom
pallefar said:
So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.
I guess AOSP is a safer bet at the moment? like Chroma rom
Click to expand...
Click to collapse
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
zelendel said:
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
Click to expand...
Click to collapse
Yep. I think @zephiK chroma is aosp no-cm.
awesome thanks guys, I think this thread will guide people to not brick thier phones
kenbrownstone said:
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
Click to expand...
Click to collapse
No it doesn't relock itself but lots of people who are on these forums don't really understand what they are doing/flashing and so to be extra safe, I put that in there for people always to double check that OEM unlock is enabled.
People may think they have unlocked when they haven't or may not realize they relocked. I know that seems hard to do but I have never seen so many bricked nexi in my life before.
Just trying to help the less experienced from bricking. If you know what you are doing you don't need to take advice from me.
---------- Post added at 10:37 PM ---------- Previous post was at 10:32 PM ----------
zelendel said:
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks.
Click to expand...
Click to collapse
Yep, that will do it - downgrading the bootloader is a no-no on a motorola phone except in rare cases when it was possible.
zelendel said:
My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Click to expand...
Click to collapse
Always!
Great write up! Saved my a$$ for sure. I updated my bootloader and radio the day it was available and I'm running a 5.0.1 CM12 based ROM. Here's where sometimes you get lucky, I was on v8.7 of this ROM, after I did the 5.1 bootloader and radio flash, an update came out to 8.8, I'm usually flash happy, but I figured why bother if I can wait for the 5.1 integration! I did unzip the update and no bootloader.img to be found, so I suppose the dev was wise enough not to put it in, but still.
I was curious about why most are moving away from CM? Because of these types of oversights? Their"interesting" business model?
JulesJam said:
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table;
4) make sure OEM unlock and USB debugging are enabled each time you flash;
5) never take an OTA unless you have reverted back to stock completely;
6) never upgrade the bootloader w/o also upgrading the partition table and vice-versa; and
7) use mfastboot for flashing.
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.
Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
Click to expand...
Click to collapse
Does nexus have a partition table to flash? I've never heard of that from a nexus forum. I just flashed the 5.1 BL and went back to 5.0 stock rom ,then flashed euphoria. I believe that you flash via Fastboot if your bootloade is mismatched, that you can't acutally flash it. Not unless you use dd command. I'm not sure about this, though. I'm no way a dev or someone with knowledge in this field. But for nexus devices i owned, i never saw any nexus could be bricked this easy. Yes, they're made by motorola, but it's still a nexus . LG makes nexus 4 and 5, doesn't mean LG locked their bootloader as well. I don't think it's a fault of Motorola or has anything to do with its manufacturer. It's a nexus.