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

moto x not-so-dev edition, what is RSDlite trick? - Moto X Q&A

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related

[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

If you flashed the 4.4.2 partition table (gpt.bin) only and now can't flash anything

is this a hard brick? Can you recover from this once the sbf firmware for 4.4.2 is released?

Yes, once the full flash is released you should be able to recover.

Cozume said:
is this a hard brick? Can you recover from this once the sbf firmware for 4.4.2 is released?
Click to expand...
Click to collapse
you should still be able to access stock recovery through the bootloader menu and reflash the update:
http://www.androidfilehost.com/?fid=23329332407573403

Q9Nap said:
you should still be able to access stock recovery through the bootloader menu and reflash the update:
http://www.androidfilehost.com/?fid=23329332407573403
Click to expand...
Click to collapse
Thanks, it wasn't me but it was another poster and he was not able to access stock recovery. He said he could get into fastboot mode, but didn't get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
http://forum.xda-developers.com/showthread.php?t=2657262&page=2
Ther error message sounds to me like once you upgrade the partition table to 4.4.2, it won't let you into 4.4 recovery since it is a lower version?

Cozume said:
Thanks, it wasn't me but it was another poster and he was not able to access stock recovery. He said he could get into fastboot mode, but didn't get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
http://forum.xda-developers.com/showthread.php?t=2657262&page=2
Ther error message sounds to me like once you upgrade the partition table to 4.4.2, it won't let you into 4.4 recovery since it is a lower version?
Click to expand...
Click to collapse
ah yeah, just read the thread, that kinda sucks. recovery version has never been an issue before iirc. well the fxz should be available pretty quickly; i'd be surprised if it isn't availalbe some time next week. i'd way rather wait for that than send in the phone and deal with tech support and refurbished devices.
this is also one of the reasons i never take ota; always wait for the fxz. then you can update just what you need: boot, system, and radio. i'm running 4.4 boot system and radio with every other partition still on 4.2.2. works fine and i always have the option to downgrade if i want to for whatever reason.

Q9Nap said:
ah yeah, just read the thread, that kinda sucks. recovery version has never been an issue before iirc.
Click to expand...
Click to collapse
yeah, seems like Motorola just keeps making these updates less and less hackable.
I went the CLNR route with my GNex for hardware problems and I eventually ended up with one that was significantly better than the one I sent in. But it took me 5 to get there. Lots of the AMOLED screens were blue or yellow tinted in the CLNRs.

Cozume said:
yeah, seems like Motorola just keeps making these updates less and less hackable.
I went the CLNR route with my GNex for hardware problems and I eventually ended up with one that was significantly better than the one I sent in. But it took me 5 to get there. Lots of the AMOLED screens were blue or yellow tinted in the CLNRs.
Click to expand...
Click to collapse
what would be really helpful for those who are bricking is someone with fully stock rooted 4.4.2 doing a dd of the recovery partition. then bricked users could fastboot the recovery to their devices and reinstall the update.

Q9Nap said:
ah yeah, just read the thread, that kinda sucks. recovery version has never been an issue before iirc. well the fxz should be available pretty quickly; i'd be surprised if it isn't availalbe some time next week. i'd way rather wait for that than send in the phone and deal with tech support and refurbished devices.
this is also one of the reasons i never take ota; always wait for the fxz. then you can update just what you need: boot, system, and radio. i'm running 4.4 boot system and radio with every other partition still on 4.2.2. works fine and i always have the option to downgrade if i want to for whatever reason.
Click to expand...
Click to collapse
That's me, I wish I did the same with 4.2.2 but didn't know what I know now then. Now I plan on waiting for the sbf or a custom recovery flashable zip that can be reverted to 4.4 as I'll do everything in my power to keep off the "upgraded" bootloader.
Sent from my SM-P600 using Tapatalk

Q9Nap said:
what would be really helpful for those who are bricking is someone with fully stock rooted 4.4.2 doing a dd of the recovery partition. then bricked users could fastboot the recovery to their devices and reinstall the update.
Click to expand...
Click to collapse
What is a dd?

Cozume said:
What is a dd?
Click to expand...
Click to collapse
dd is a linux binary included in busybox. it can be used to make image dumps of partitions.
more info: http://en.wikipedia.org/wiki/Dd_(Unix))

Q9Nap said:
i'm running 4.4 boot system and radio with every other partition still on 4.2.2. works fine and i always have the option to downgrade if i want to for whatever reason.
Click to expand...
Click to collapse
4.2.2 pre-camera or post-camera update?

Cozume said:
4.2.2 pre-camera or post-camera update?
Click to expand...
Click to collapse
Initial release (Blur_Version.139.10.53)

Q9Nap said:
Initial release (Blur_Version.139.10.53)
Click to expand...
Click to collapse
What are the advantages of sticking with that bootloader version rather than the 4.2.2 post-camera bootloader? It's too late for me as I took the 4.4 OTA before I found this site but I am curious to know.

Cozume said:
What are the advantages of sticking with that bootloader version rather than the 4.2.2 post-camera bootloader? It's too late for me as I took the 4.4 OTA before I found this site but I am curious to know.
Click to expand...
Click to collapse
Nothing in particular other than the ability to downgrade and/or cross flash other firmware. For most people it's not a big deal because they'll never want to do this stuff.

Q9Nap said:
Nothing in particular other than the ability to downgrade and/or cross flash other firmware. For most people it's not a big deal because they'll never want to do this stuff.
Click to expand...
Click to collapse
Thanks, but if you are on 4.2.2 pre-camera initial release, what is there to downgrade to? Just trying to understand all of this.

Cozume said:
Thanks, but if you are on 4.2.2 pre-camera initial release, what is there to downgrade to? Just trying to understand all of this.
Click to expand...
Click to collapse
i am running 4.4 boot, system, and radio. all other partitions, i.e. fsg, gpt, logo, and motoboot, are still the initial release versions.
gpt and motoboot are irreversible once flashed. gpt is the partition table that contains the security levels of the other partitions and motoboot contains the security level for gpt that is checked at boot time. usually there's no reason to upgrade them because it prevents you from being able to flash partitions that have a lower security level than what they specify.
i'm not sure whether it matters as much with an unlocked bootloader, as being unlocked allows you to flash whatever you want, but gpt is still irreversible. so once gpt is upgraded, it may still prevent you from downgrading or crossflashing partitions with a lower security level than specified.
bottom line is, there's no reason to upgrade them unless you don't mind limiting your choices.

Q9Nap said:
gpt and motoboot are irreversible once flashed. gpt is the partition table that contains the security levels of the other partitions and motoboot contains the security level for gpt that is checked at boot time. usually there's no reason to upgrade them because it prevents you from being able to flash partitions that have a lower security level than what they specify.
Click to expand...
Click to collapse
Ok got it. The later versions of the partition table and bootloader just lock your phone down more; they don't do anything to enhance user experience.
Q9Nap said:
bottom line is, there's no reason to upgrade them unless you don't mind limiting your choices.
Click to expand...
Click to collapse
Thanks, that says it all. Next time I get a new phone I won't upgrade those!

Cozume said:
Ok got it. The later versions of the partition table and bootloader just lock your phone down more; they don't do anything to enhance user experience.
Click to expand...
Click to collapse
this is correct, generally speaking. there may be instances where upgrading gpt is unavoidable. for example gpt also contains partition sizes, so if a newer system is larger than the size specified in gpt, it may not flash. the vzw 4.4 system image is 162mb larger than the vzw 4.2.2 system image, but it flashes. will have to see whether 4.4.2 flashes; i doubt there is much of a size difference though.

Q9Nap said:
i am running 4.4 boot, system, and radio. all other partitions, i.e. fsg, gpt, logo, and motoboot, are still the initial release versions.
gpt and motoboot are irreversible once flashed. gpt is the partition table that contains the security levels of the other partitions and motoboot contains the security level for gpt that is checked at boot time. usually there's no reason to upgrade them because it prevents you from being able to flash partitions that have a lower security level than what they specify.
i'm not sure whether it matters as much with an unlocked bootloader, as being unlocked allows you to flash whatever you want, but gpt is still irreversible. so once gpt is upgraded, it may still prevent you from downgrading or crossflashing partitions with a lower security level than specified.
bottom line is, there's no reason to upgrade them unless you don't mind limiting your choices.
Click to expand...
Click to collapse
Finally the post that makes it ALL CLEAR!!! My eyes are watering from all the reading of this forum I have done in fear of angering forum helpers :laugh: but there was nothing like this post before (unless I missed it)

JoeSchmoe007 said:
Finally the post that makes it ALL CLEAR!!! My eyes are watering from all the reading of this forum I have done in fear of angering forum helpers :laugh: but there was nothing like this post before (unless I missed it)
Click to expand...
Click to collapse
Exactly. The forum "helpers" are getting off a bit too much on all the "help" they provide people.
It is nice when a knowledgeable person takes a few minutes to explain details that may seem basic but to people learning this for the first time are essential.
Thanks again @Q9Nap!

[Q] Return to stock

Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
It seems that is pretty easy to brick this phone while changing versions. I would like to return it to stock, so that i can accept all OTAs. I don't care losing any data or root permissions. I've found this method to return to stock here in XDA:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
(cant post urls)
Android SDK
(cant post urls)
MFastboot(Used for manually downgrading to 4.2.2)
(cant post urls)
For firmware Download pick what firmware you want from the link below
(cant post urls)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
I would like to know if there's any risk in doing this, or which would be the better way to get to android 4.4.
Thanks!

You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?

KJ said:
You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?
Click to expand...
Click to collapse
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks

vagh_nagas said:
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks
Click to expand...
Click to collapse
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.

KJ said:
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.
Click to expand...
Click to collapse
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.

vagh_nagas said:
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.
Click to expand...
Click to collapse
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?

OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.

KJ said:
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?
Click to expand...
Click to collapse
When I first tried to use xposed, I Soft bricked my phone. That was just using towel pie's method of root. So I decided that it was not a good idea to do any modifications to my phone that I did not feel I had much control over. That is why I used the 4.4.2 boot loader unlocker (I forgot who made it already, sorry) . After that I re-installed a newer version of towel pie, and super SU (I have better luck keeping root with this app), and towel pie asked if I was going to install xposed and i said yes. then I attempted the xposed and reboot. at first it had said that it did not install correctly. then after the third time of me attempting it it and after soft rebooting the phone after using towel pie's software it let me keep xposed. I believe it was the soft restart that did it but I am not quite sure.
I have pics if you want to see my recovery.
Just to let people know i am using a Republic Wireless Moto X, That is why I must leave the recovery alone. Yes all features still work as if I had done nothing to it, Just in case some people were wondering that have this service.
---------- Post added at 11:49 PM ---------- Previous post was at 11:10 PM ----------
Another question I have for somebody that has republic wireless. if I unlocked my boot loader can I go back to jelly bean or is that just an impossibility?

mauri6870 said:
OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.
Click to expand...
Click to collapse
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?

jisola said:
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?
Click to expand...
Click to collapse
Right.
Tho, let it be said....everything we do on XDA, everything , comes with risk.
Anything can go wrong, anytime.
Just wanted to remind of that. No one will, or at least should, guarentee anything on XDA. We all take the responsibility ourselves if something goes very wrong.
?
So in theory , yes, you should be absolutely fine. But again....stuff happens. Proceed at your own risk.

jisola said:
Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
Click to expand...
Click to collapse
Before you upgrade, do you want to root after you've upgraded?
If so, you need to be aware of what can/can't be done BEFORE you update.

well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!

jisola said:
well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!
Click to expand...
Click to collapse
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.

Wansanta said:
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.
Click to expand...
Click to collapse
i have a locked bootloader...
i've tried flashing 4.2.2 and there were a lot of errors during installation that werent there when i tried to go to 4.4, after flashing was complete i got the same boot error, is there anything else to try?

jisola said:
great to hear that, i have a locked bootloader
Click to expand...
Click to collapse
Locked is above my paygrade.
But by functioning bootloader I mean you can use fastboot commands to flash.

lanemst curr
Wansanta said:
Locked or unlocked?
Click to expand...
Click to collapse
i edited... i misread when u said unlocked...

jisola said:
i edited... i misread when u said unlocked...
Click to expand...
Click to collapse
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?

Wansanta said:
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?
Click to expand...
Click to collapse
thanks for all this help.
never heard of sunshine before, i assume is way to unlock your bootloader right?
im kind of new with bootloaders phones, how could i check my bootloader version, doesn't seem to appear in the fastboot menu

jisola said:
how could i check my bootloader version, doesn't seem to appear in the fastboot menu
Click to expand...
Click to collapse
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.

Wansanta said:
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.
Click to expand...
Click to collapse
thanks again
mine is: 30.B4

System Files?

Greetings;
I just received my Moto X 1097 Canadian Variant and was
wondering if there are any files that I can get from a virgin
device before I attempt to root & etc.?
Or backup files that one day I might need to bring back my
device to life from Bricked status?!!
Thank you.

As long as you can get your hands on factory images, I wouldn't worry too much about system files. Otherwise, you should be able to find ways to make a system image; however that might require root or custom recovery.

korockinout13 said:
As long as you can get your hands on factory images, I wouldn't worry too much about system files. Otherwise, you should be able to find ways to make a system image; however that might require root or custom recovery.
Click to expand...
Click to collapse
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right? If that is the case, can I just ignore the OTA? And stay on KK?
Thank you.

samteeee said:
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right? If that is the case, can I just ignore the OTA? And stay on KK?
Thank you.
Click to expand...
Click to collapse
Without factory images or a full backup, there is no way back. However, it is safe to downgrade as long as you don't try to downgrade the bootloader or partition table. You can ignore the OTA, but it will probably be annoying. You might as well upgrade.

samteeee said:
Yes I usually unlock the Bootloader and Root, but since being a Canadian means not having a choice when it comes to "Communication Industries"
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
Click to expand...
Click to collapse
I have a thread on this in the General forum. If you update to lollipop using Motorola Device Manager, you will have a copy of fastboot flashable Lollipop files on your computer. Search for my post on General.
If you want the fastboot flashable Kit Kat files, you can request them from Motorola. If they won't give them to you, then you can search to see if anyone has copies of them. This is for Telus right? You also can specifically ask if anyone has them, they may.
The other thing you can do is after you unlock the bootloader and flash TWRP recovery, is to make a nandroid of your stock system on kit kat and save it on your computer. Then flash back to stock recovery and upgrade to lollipop using MDM. Then flash TWRP recovery again and make a nandroid of stock lollipop, save it to your computer, then root.
---------- Post added at 10:08 PM ---------- Previous post was at 10:02 PM ----------
samteeee said:
I couldn't buy a "Developer Edition" or any "32Gb" version for that matter!! Hence getting a XT1097.
I was wondering about downgrading, I understand once I upgrade to Lollipop, there is no way back, right?
Click to expand...
Click to collapse
First off are you sure your device shipped with kitkat? Double check on that.
Once you upgrade to lollipop, you cannot downgrade the bootloader or the partition table back to kit kat, but you should be able to downgrade the kernel and the system back to kit kat w/o any issues. Idk about trying to downgrade the radios.

JulesJam said:
I have a thread on this in the General forum. If you update to lollipop using Motorola Device Manager, you will have a copy of fastboot flashable Lollipop files on your computer. Search for my post on General.
If you want the fastboot flashable Kit Kat files, you can request them from Motorola. If they won't give them to you, then you can search to see if anyone has copies of them. This is for Telus right? You also can specifically ask if anyone has them, they may.
The other thing you can do is after you unlock the bootloader and flash TWRP recovery, is to make a nandroid of your stock system on kit kat and save it on your computer. Then flash back to stock recovery and upgrade to lollipop using MDM. Then flash TWRP recovery again and make a nandroid of stock lollipop, save it to your computer, then root.
---------- Post added at 10:08 PM ---------- Previous post was at 10:02 PM ----------
First off are you sure your device shipped with kitkat? Double check on that.
Once you upgrade to lollipop, you cannot downgrade the bootloader or the partition table back to kit kat, but you should be able to downgrade the kernel and the system back to kit kat w/o any issues. Idk about trying to downgrade the radios.
Click to expand...
Click to collapse
Thank you for your reply.
I just turned it on for the very first time! And I can confirm that it is on KK.
I like your solutions and will email Motorola tonight for the KK files. I will however upgrade to Lollipop via MDM so that I do have a copy of the "Fastboot Flashable Lollipop files".
Any suggestion on Rooting method? Also to copy the Nandroid to Pc, do I pull it with ADB? or just copy them from internal storage? And lastly I think once I upgrade, doesn't make sense to downgrade with so many complications, eh?
Thank you again.

korockinout13 said:
Without factory images or a full backup, there is no way back. However, it is safe to downgrade as long as you don't try to downgrade the bootloader or partition table. You can ignore the OTA, but it will probably be annoying. You might as well upgrade.
Click to expand...
Click to collapse
Thanks bro.

Is your phone Telus or Wind mobile?
The original kitkat files for both can be downloaded no problem.
The 5.0.1 lollipop image for Telus can also be downloaded.
You can safely downgrade from Lollipop to Kitkat as long as you unlock your bootloader.

Steve-x said:
Is your phone Telus or Wind mobile?
The original kitkat files for both can be downloaded no problem.
The 5.0.1 lollipop image for Telus can also be downloaded.
You can safely downgrade from Lollipop to Kitkat as long as you unlock your bootloader.
Click to expand...
Click to collapse
Hi
My phone is Telus Mobility.
Are the files on Motorola site?
Thank you.

[Q] [XT1053] How to get 5.1 back. Already updated once to 5.1

Hello,
Please help me get any OS back to my XT1053 for now. Here's what happened:
1) I unlocked the bootloader, rooted my XT1053, stock recovery. Then last week I tried updating it to 5.1 official version via OTA. It failed due to files mismatch (maybe due to using apps that need root like Adaway). So I downloaded 4.4.4 STOCK version from Moto website, flashed boot.img, system.img and followed all the steps given here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Once the phone booted properly into 4.4.4, I tried 5.1 OTA and it worked fine. Then I flashed TWRP and SU to get root (I lost root when I flashed STOCK 4.4.4).
2) Everything was fine except that whenever I rebooted, my phone would Optimize ALL the apps. I Googled a lot and apparently this happened to many folks and there was no solution.
3) Today, I thought I will try and fix it by sideloading the 5.1 OTA zip (I thought the regular OTA style installation that I did of 5.1 over mfastboot style installation of 4.4.4 had something to do with it. I know, this was stupid of me!)
4) So, today I went to TWRP and tried to flash 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip'. I am 100% certain that this was the file that I copied from /cache after OTA had downloaded the file last week and I had saved it locally on PC and in SD on phone. However, this flashing gave me an error saying that it expected either 4.4.4 KXA or 5.1 but that my system was 4.4?? So the flashing failed and my OS is gone. How can I get ANY OS back? Here are the things that I tried so far:
1) Installed RSD Lite and I am downloading XT1053_TMO_RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip file from http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 as I type this out now. HOWEVER, I think I shouldn't use it as I read KidJoe saying not to downgrade. (KidJoe's comments are here http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347)
2) THEREFORE, I was wondering if I could simply flash a higher or equivalent version of ROM. Since we don't have an official 5.1 flashable zip right now, can I use 5.1.1 by CM? It's present here: http://primehowto.com/install-andro...le-moto-x-xt1053-2013-via-cm12-1-nightly-rom/
3) If yes to point# 2 above, I have a small problem. My phone is not detected by 'adb devices; in TWRP recovery mode. My battery is 11%. Could that be the issue?
I KNOW THIS WAS A LONG POST. I JUST WANTED TO GIVE ALL THE INFO. PLEASE HELP ME GET ANY OS ONTO THE PHONE AND THEN I WILL WAIT FOR THE 5.1 SBF TO BE AVAILABLE. THANKS A LOT IN ADVANCE....

here [Official] XT1058_GHOST_RETBR_5.1 FXZ/SBF (Full Rom)uploaded by our fellow user GARUXA
https://doc-10-ak-docs.googleuserco...359/*/0BwcadIv25aK8Tng3SUk2b1k5aVE?e=download
http://forum.xda-developers.com/mot...t1058ghostretbr5-1-fxz-sbf-rom-t3144161/page2

hbenz2008 said:
here [Official] XT1058_GHOST_RETBR_5.1 FXZ/SBF (Full Rom)uploaded by our fellow user GARUXA
https://doc-10-ak-docs.googleuserco...359/*/0BwcadIv25aK8Tng3SUk2b1k5aVE?e=download
http://forum.xda-developers.com/mot...t1058ghostretbr5-1-fxz-sbf-rom-t3144161/page2
Click to expand...
Click to collapse
Thanks for quick response. But I have XT1053.. Can I still use the one that you gave?

Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?

hbenz2008 said:
Not recommended, hold on a bit. Did try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
No, I didn't try mfastboot of 'gpt' from 5.1 update file 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip'. I don't see an 'mboot' or 'boot' file in it though. I do see 'gpt'. Also, in fastboot mode it says "Charger connected" instead of "USB connected". I think that's due to the low battery too?

hbenz2008 said:
Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
Would you know if 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip' file is the OTA 5.1 file? I think that's how the naming convention goes i.e. the name is set to the system version on which it is going to be updated NOT the system version that it will be updated to. I don't know why this flash failed though. I can give you the exact error that I get when I try flashing this if that helps? Thanks!

Shoot the error. If it's security downgrade, again flash gpt and mboot from Ota 5.1.
I will have to verify the name of Ota as its critical info.

hbenz2008 said:
Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
When I tried flashing "Blur_Version.213.44.1.ghost_row.Retail.en.US.zip" file (which I still think is the OTA 5.1 zip), I get this error:
Package expects build fingerprint of mototola/ghost_retail/ghost:4.4.4/KXA21.12-L1.29.1/2:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys; this device has motorola/ghost_retail/ghost:4.4/13.11.1Q2.X-69-3/51:user/release-keys
This is where I got burned today. The above error wiped out my OS. I was on 5.1, I don't know why it says I have 4.4....

Prolly system mismatch, try only gpt and mboot. What error do u get?
---------- Post added at 09:27 PM ---------- Previous post was at 09:17 PM ----------
BTW your post provided good info. So Ota think u on 4.4.
You flashed only syst and boot to get on 4.4 ,could be where the prob is.
Need to know where img/rom info reside.
Double check the 4.4 files you flashed.
Just thinking out loud..

hbenz2008 said:
Prolly system mismatch, try only gpt and mboot. What error do u get?
---------- Post added at 09:27 PM ---------- Previous post was at 09:17 PM ----------
BTW your post provided good info. So Ota think u on 4.4.
You flashed only syst and boot to get on 4.4 ,could be where the prob is.
Need to know where img/rom info reside.
Double check the 4.4 files you flashed.
Just thinking out loud..
Click to expand...
Click to collapse
What's 'mboot'. There's no such file in the extracted folder of 'blur.....' file that I mentioned earlier. there is 'gpt'. My phone is detected via fastboot now so I can flash but don't know where the 'mboot' is

Hitdroid said:
What's 'mboot'. There's no such file in the extracted folder of 'blur.....' file that I mentioned earlier. there is 'gpt'. My phone is detected via fastboot now so I can flash but don't know where the 'mboot' is
Click to expand...
Click to collapse
Okay, so I fixed it. At least got an OS for now .. This is what I did.. I took a chance and went ahead with these steps:
1) Extracted files from Stock TMO 4.4.4 file 'TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz' got from Moto website.
2) Modified 'flash.bat' file to have below commands:
SET mfastboot=mfastboot.exe
%mfastboot% getvar max-download-size
%mfastboot% oem fb_mode_set
%mfastboot% flash partition gpt.bin
%mfastboot% flash motoboot motoboot.img
%mfastboot% reboot-bootloader
%mfastboot% flash logo logo.bin
%mfastboot% flash boot boot.img
%mfastboot% flash recovery recovery.img
%mfastboot% flash system system.img
%mfastboot% flash modem NON-HLOS.bin
%mfastboot% erase modemst1
%mfastboot% erase modemst2
%mfastboot% flash fsg fsg.mbn
%mfastboot% erase cache
%mfastboot% reboot
3) It failed with 'partition', 'motoboot', 'logo'. Everything else was successful.
4) My phone booted into 4.4.4 now.
It's funny but I think I have successfully downgraded from 5.1 to 4.4.4... That means, my main system file was never upgraded to 5.1?? It's late and I want a phone for tomorrow so I won't try 5.1 tonight. But it would be great if experts could pitch in. How did I downgrade from 5.1 to 4.4.4?
Anyway, thanks for your help. Your comment about 'gpt' made me think "maybe my phone won't hard brick if I install 4.4.4 again".. and it didn't!
CHEERS!

You can downgrade Fri 5.1 to 4.4 without flashing gpt and mboot. Wait for full 5.1.
Excellent man. Check your bootloader version, it's probably lollipop. So don't take update yet.

I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app

to check bootloader BL, restart phone in fastboot read menu.
KidJoe got this better covered here
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Hitdroid said:
I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse

Hitdroid said:
I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Many try to skip GPT.BIN and MOTOBOOT.IMG... but when you have a version missmatch (gpt/motoboot from one rom, and rest from another), you increase your chance of bricking should you apply an OTA update zip in the future. And you'll likely end up with features not working or extra "bugs" that wouldn't otherwise appear.
For those who say "its safe to downgrade"... I'll point you to -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 and ask you to view the 7 links near the end of the first post as just a few examples.

Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app

Hitdroid said:
Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Hitdroid, do you mind sharing your 5.1 OTA file for xt1053.
I'm in the same situation as you. Got 5.1 OTA a few weeks ago, rooted it and installed TWRP. Then I accidentally installed my 4.4.4 backup which erased my 5.1 install.
I just installed CM 5.1 as a stopgap but i'd like to return to near stock so i'm following this thread.

as I thought, you have a 5.1 BL.
Gotta flash manually when sbf/ROM is available

Hitdroid said:
Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Because of your bootloader, the safest way is wait for the 5.1 SBF to be posted (since you have an XT1053, it will be posted on Moto's web site, and you don't have to rely on leaks)... But I have no idea how long that will take.
Now, you could try to take the OTA, but I've seen enough bricks to say.. If it was my phone... I'd wait.

I'm at work so will share the file once I go home. But I think we should wait for 5.1 SBF as @KidJoe and @hbenz2008 have stated.
Sent from my XT1053 using XDA Free mobile app

Database Develop

welcome