Database Develop

[Q]Unlocked Bootloader,TWRP and 4.4.2 Update

Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!

msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.

dray_jr said:
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
Click to expand...
Click to collapse
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy

msespindola said:
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.

dray_jr said:
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
Click to expand...
Click to collapse
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?

msespindola said:
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
Click to expand...
Click to collapse
idk i dont like to doing things half way there have been way to many bricks lately.

If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X

Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
this is why i dont read on my phone i miss crap anyway if you flash 4.4.2 yes you can flash the 4.4 TWRP and then SuperSU with a unlocked bootloader.. sorry for my miss read thanks for the catch

dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thx guys, I'll do this later, thx for the awesome responses
Sent from my XT1058 using xda app-developers app

dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.

NPOA556 said:
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
Click to expand...
Click to collapse
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Sent from my Dev Edition Moto X

Schaweet said:
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Click to expand...
Click to collapse
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.

NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
What I've read is you need to go back to stock recovery and also make sure any /system files are unchanged. For example I renamed my old exchange apk's (in /system/app) when I put in the new ones from the nexus 5 on 4.4.2, so I would need to name those files back.

NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Sent from my Dev Edition Moto X

Schaweet said:
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Click to expand...
Click to collapse
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.

NPOA556 said:
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
Click to expand...
Click to collapse
Good questions. I'm not sure. We certainly root differently than a non Dev edition. They might have some files modified that we don't have to modify. Also, I wonder is going to stock recovery will unroot us.
I guess we wait and stay patient.
Sent from my Dev Edition Moto X

Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.

Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
The only hope you have is if someone decides to take that factory image and runnit through kitchen to make it a flashable zip. You will also need the updated modem from either 4.4 or 4.4.2 to prevent system settings from fc ing
This goes for any moto, retail and or developer edition
You may also attempt to flash the sbf firmware and remove the delete userdata from the XML but no guarantee that you will not have issues
Hope that helps
Sent on my Gummy running Lenoto X

To take an ota you must be stock. Meaning everything. As long as you haven't flashed an updated bootloader you can just flash system.IMG and recovery.IMG from the sbf your phone is currently on you can take an ota. A successful ota does NOT require a data wipe.
---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------
finalarcadia said:
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Click to expand...
Click to collapse
You cannot flash any of those through twrp! If you want to flash 4.4.2 you need to fastboot the system.IMG and boot.IMG and you will need to wipe your data. If you choose this route you will not be able to take the ota when its available you'd have to wait for the sbf file to be released and update through house of moto, rsd, or fastboot.

flashallthetime said:
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
...
Click to expand...
Click to collapse
some questions.. and comments...
I agree with #1. You must have STOCK recovery for an OTA to install properly. And #3, because the OTA generally has a file list with check sums to compare against what is on your device to make sure all required files are there and the correct version/size/etc before it will start to install.
#2 I have a question on as I've not had an issue with this unless the root process makes changes to system files (thus causing a problem for #3). I've lost root taking an OTA, but that is it.
Then again, I have a Dev X with unlocked bootloader, and I don't know enough about RockMyMoto, SlapMyMoto, etc was of rooting the X, except that initially they replaced the recovery partition with an image that when selected/booted allowed write to system, etc. This would cause issue with #1 (no longer have stock recovery on the recovery partition), but not sure what, if any system files get touched or altered from stock.
Finally, you mention clearing data being required... This would wipe you back to factory defaults and remove your apps/data. I don't believe its "required" but rather just suggested as it can make the device run smoother after the update is done.
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
Depends on how you rooted.
If you've downloaded the SBF file for the ROM on your device (if you don't have it, see if its available from -> http://sbf.droid-developers.org/phone.php?device=0 ), you can unzip it, and fastboot flash the stock recovery from it onto your device, take the OTA, and then later fastboot flash TWRP back on and install SuperSU again to root.
This assumes you did NOT touch any system files the update will check for prior to running/installing. If you did touch system files, edit build prop, removed/renamed any APK's... then fastboot flash recovery and system before taking the OTA

[Q] Back-ups When Rooting

So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Save my custom wallpaper using these instructions:
How to Pull Custom Wallpaper
2) Root using Slap My Moto method
- here it the 4.4 OTA if 4.4.2 has already come out by the time I do this
Verizon 4.4 OTA
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the 4.4.2 OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Then after I root, I can selectively flash the 4.4.2 update:
Slap My Moto Page 150
Important Warning Before Flashing 4.4.2 Page 15
System.img, boot.img, non-hlos.bin and fsg.mbn

Cozume said:
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Flash TWRP and boot into it to make a pre-root nandroid b/u
- I know the custom recovery won't stick when I reboot, just doing it to make a pre-root b/u
- is this necessary as long as the sbf firmware is available?
2) Root using Slap My Moto method
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Also, I can't hit the thanks button anymore today but if you help me I will come back tomorrow and hit it, I promise!
Click to expand...
Click to collapse
Flashing twrp while having a locked boot loader? Idk
Sent on my Gummy running Lenoto X

flashallthetime said:
Flashing twrp while having a locked boot loader? Idk
Click to expand...
Click to collapse
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.

Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
well good! you're on the right track. 3 best pieces of advice here:
1. Search first
2. Read alot (yes even some long threads with several pages)
3. Then Q & A is here for you.
Glad you're being safe with your exepnsive device, some noobs usually shoot first ask questions later.

Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
Flashing a custom recovery always requires a unlocked boot loader, On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Sent on my Gummy running Lenoto X

flashallthetime said:
On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Click to expand...
Click to collapse
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?

Cozume said:
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Click to expand...
Click to collapse
No, wait and see what happens, it makes sense flash 4.4.2 now, it won't make any difference now or later, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware. Read please. I have 6 months of moto x experience behind me, been here from day 1
Sent on my Gummy running Lenoto X

My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!

SymbioticGenius said:
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
Click to expand...
Click to collapse
yeah, but it will cause me great sadness to sell my beautiful wood backed baby!!!

flashallthetime said:
it won't make any difference now or later
Click to expand...
Click to collapse
well, yes it would because if I take the OTA then I won't be rooted unless someone finds an exploit for 4.4.2 and I will never be rooted if someone doesn't.
flashallthetime said:
i
, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware.
Click to expand...
Click to collapse
I am getting confused now. If I stay on 4.4 rooted and something happens to my device, can I or can't I flash the sbf for Verizon 4.4 with a locked bootloader to restore my device?
Maybe I wasn't clear but my plan is to root on 4.4 and stay there by freezing MotorolaOTA, which is the app that installs the updates and sends the annoying message. I was going to stay on 4.4 rooted and not upgrade to 4.4.2 unless someone can come up with a way to root it with a locked bootloader.

Cozume said:
yeah, that is my plan. But it will cause me great sadness to sell my beautiful wood backed baby!!!
Click to expand...
Click to collapse
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Sent on my Gummy running Lenoto X

flashallthetime said:
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Click to expand...
Click to collapse
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?

Cozume said:
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Click to expand...
Click to collapse
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Sent on my Gummy running Lenoto X

flashallthetime said:
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Click to expand...
Click to collapse
I am not planning on taking the 4.4.2 OTA. The whole point of freezing MotorolaOTA is to block the OTA.

[ANSWERED] [Q] Revert from 4.4.2 to 4.4 on Unlocked Bootloader xt1058

So, I did some digging around here, and I am more confused than ever. Here is my quick question (hopefully)
I have an bootloader unlocked xt1058 (ATT branded). I ran a nandroid to flash a new rom, only to discover when i went to restore a nandroid, the system folder did not back up, therefore I do not have a /system folder backup of stock ATT 4.4.2.
What I want to know is: Can I fastboot flash ATT's 4.4 system file only (i know bootloader is not compatable), then take the 4.4.2 OTA? Or will this hard brick my phone?
If i searched the forums correctly, it addresses if your bootloader is locked, but not unlocked.
I am running an AOSP now, so i know my way around fastboot and adb.
Any assistance would be helpful, and a flashable zip of stock ATT 4.4.2 would kick a**
Thanks for the help!

I'm not sure exactly how, cause I never have, or would downgrade......but just be sure you find out exactly how to do it. An unlocked boot loader will not protect you from a brick if something is done wrong. In other words....there are ways to brick for sure....locked or unlocked.
To me its a risky endeavor no matter what the case. Mistakes happen.....and in the case of downgrading from 4.4.2....mistakes can cost you a phone. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

kj2112 said:
I'm not sure exactly how, cause I never have, or would downgrade......but just be sure you find out exactly how to do it. An unlocked boot loader will not protect you from a brick if something is done wrong. In other words....there are ways to brick for sure....locked or unlocked.
To me its a risky endeavor no matter what the case. Mistakes happen.....and in the case of downgrading from 4.4.2....mistakes can cost you a phone. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Yep! Hence the question. I guess the real question is...with an unlocked bootloader, can i flash System and Recovery (Android 4.4), while on Bootloader (Android 4.4.2)

would the safest thing to do to use RSD and flash (which will stop if there is a security issue)?

I'd just wait for the flash able 4.4.2 files.
Why do you want 4.4 anyway? There's not much difference.... Except a few negatives.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

cpetersen2791 said:
What I want to know is: Can I fastboot flash ATT's 4.4 system file only (i know bootloader is not compatable), then take the 4.4.2 OTA? Or will this hard brick my phone?
Click to expand...
Click to collapse
Yes this will brick your phone. If you are on 4.4.2, and downgrade only parts (say system.img), you'll have a version and security mismatch, including the bootloader and GPT.BIN. If you take an OTA in that state you will brick. (at least that is what many of the users who have bricked have done according to the threads I've read... I haven't actually done it first hand as I don't want to deal with a brick).
cpetersen2791 said:
If i searched the forums correctly, it addresses if your bootloader is locked, but not unlocked.
Click to expand...
Click to collapse
This applies for locked and unlocked bootloaders.
cpetersen2791 said:
Any assistance would be helpful, and a flashable zip of stock ATT 4.4.2 would kick a**
Thanks for the help!
Click to expand...
Click to collapse
As soon as the SBF for ATT 4.4.2 leaks out, I'm sure it will be available on -> http://sbf.droid-developers.org/phone.php?device=0

kj2112 said:
I'd just wait for the flash able 4.4.2 files.
Why do you want 4.4 anyway? There's not much difference.... Except a few negatives.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
when i ran a "stock" nandroid to test AOSP roms, i failed to back up my system folder, therefore I don't have a Stock ATT OS. I know 4.4.2 was out, but only as OTA, but complete 4.4 was available.
Thanks for all the assistance, i'll wait for the 4.4.2 SBF.

[Q] Updating DIRECTLY from 4.2.2 to 4.4.3 (Unlocked+Rooted)

So here's the deal, I unlocked my T-Mobile Moto X bootloader through Motorola's website about a year ago or so. I also rooted and didn't bother updating afterwards to anything since I had everything working perfectly for me. Now I need to update my 4.2.2 Moto X to 4.4.3 (or really anything >=4.3 just so I can use my Moto 360 that'll be arriving soon).
My question is, with an unlocked bootloader, rooted, TWRP 2.6.3.1, Xposed-installed Moto X, can I go ahead and flash a stock 4.4.3 ROM (for example from here: http://forum.xda-developers.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675) and just call it a day?
I've been reading past threads and stuff to get back into the loop, but I just can'f find anything to answer me the simple question of updating an unlocked+rooted 4.2.2->4.4+ while keeping root. Just the simple question of, if I get a stock 4.4 image and flash it on my phone, will everything be okay?
I no longer have the passion and interest to constantly be fiddling with kernels, ROMs, and little hacks with my phone like I used to with my OG Droid and, to a lesser extent, with my Galaxy Nexus (plus I feel like it's gotten significantly less easy since those OG days).
I know (i.e. 90% sure) that one way to do what I want (kinda) is RSDLite/manually go back to stock without root on 4.2.2 and then accept the OTA, but certainly it has to be easier than that right? What happened to the days where I can just find a new Gingerbread ROM for my Froyo Droid and just flash it right then and there? Now everything is "go back to stock and do these convoluted steps."
(I'm sorry I'm ranting, I'm just really tired at the moment haha)
Thank you all, hopefully, for the help!

If you don't care about retaining your data, grab the 4.4.3 fxz and unzip it. Follow the directions for returning back to stock here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 but replace the files to be flashed with the files from the 4.4.3 fxz. Not sure where you got the idea that you need to go back to stock. Word of caution, once on 4.4.3 there's no going back to an older version.

I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?

RGNDI said:
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
Click to expand...
Click to collapse
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate version recovery again and then flashing supersu.

1ad_m12 said:
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate vision recovery again and then flashing supersu.
Click to expand...
Click to collapse
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question

RGNDI said:
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
Click to expand...
Click to collapse
Yeah that would work as long as your radio is compatible with the rom. The rom you shared earlier should be fine. Just don't downgrade to anything pre 4.4 as that can cause issues because of partition sizes (or so I've heard). But after that I wouldn't take any OTA's cause your bootloader would be incompatible with the OTA and possibly cause a brick. If I were you I'd revert to stock and take the long way to 4.4.3 just so I can get the OTA for when Android L comes out. In fact thats what I plan on doing if the Sunshine bootloader unlock is successful. But if you don't care about that then everything should be fine.

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