Database Develop

[Q] Replace AT&T image with Developer Edition

Is it possible to deploy the Moto X DE image on Moto X AT&T (X1508) device?
THX

No. Not without unlocking the bootloader, which is unpossible.

Root is not enough?
gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
I can root it, will not work?

zivoro said:
I can root it, will not work?
Click to expand...
Click to collapse
No, rooting is not sufficient.

The AT&T SW, mainly AT&T contacts, drive me nuts...
Must clean it.

gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.

KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.

KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash factory images.

gunnyman said:
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.
Click to expand...
Click to collapse
Dev X on Verizon and "Consumer"/MotoMaker X on Verizon are both XT1060. So if roms are signed for the devices they are meant for, they are both signed for XT1060.
The only difference is the ability to unlock the boot loader or not. And this can't be changed by the ROM you flash.
As a test, would you agree that the "VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip" from http://sbf.droid-developers.org/ghost/list.php is the "Consumer" edition of the ROM?
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
kzoodroid said:
You need an unlocked bootloader to flash factory images.
Click to expand...
Click to collapse
And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.

My bootloader is unlocked so I can't test but the ones directly from the moto site are "dev" recovery images. They might be signed differently (like the engineering builds). The ones on sbf droid are retail files and will work fine for their proper device but cannot be shifted to another.
Ex: vzw images will not work on an att device. (however they will work if you have a Dev edition)
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Sent from my XT1060 using Tapatalk

Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.

KidJoe said:
[/COLOR]And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.
Click to expand...
Click to collapse
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.

kzoodroid said:
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.
Click to expand...
Click to collapse
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
gunnyman said:
Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.
Click to expand...
Click to collapse
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.

Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app

kzoodroid said:
Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.

gunnyman said:
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
Click to expand...
Click to collapse
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.

kzoodroid said:
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.
Click to expand...
Click to collapse
So am I.
I've also flashed manually on my mac. fastboot flash boot.omg fastboot flash system.img etc etc all work fine on my locked bootloader phone.

kzoodroid said:
....What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. ...
Click to expand...
Click to collapse
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.

KidJoe said:
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.
Click to expand...
Click to collapse
That first thread you referenced (http://forum.xda-developers.com/showthread.php?t=2445955) says right in the first post you need an unlocked bootloader. I then went 5 pages deep and saw another post which stated you have to have an unlocked boot loader to flash these. I saw one mention of pushing/pulling the images files using adb but nothing saying that worked. One other thread you linked to is about flashing a leak and you don't need an unlocked bootloader to flash a leaked rom.
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
---------- Post added at 03:26 PM ---------- Previous post was at 03:08 PM ----------
KidJoe said:
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.
Click to expand...
Click to collapse
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on.
---------- Post added at 03:55 PM ---------- Previous post was at 03:26 PM ----------
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot.
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.

kzoodroid said:
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
Click to expand...
Click to collapse
Again, the files inside the Verizon "consumer" rom, and the one you get from the Dev Web site are the SAME, the only difference is the XML in the one erases a few extra things while flashing with RSDLite.
And to flash those files Moto has for the dev edition, you do not need to have your bootloader unlocked. I've been able to flash my Verizon Moto X Dev Edition with my boot loader locked. (using both moto's fastboot, as well as RSDLite).
kzoodroid said:
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on
Click to expand...
Click to collapse
Not sure where you got the idea that ALL were Dev edition owners. Those threads were for returning to "stock" so they could take the updates. Those who had boot loops and such were rooted with RockMyMoto and such, they had to root that way due to locked boot loader which made it impossible for them to flash custom recovery and flash TWRP to then install SuperSU from inside TWRP to root.. (i.e. with an unlocked bootloader you can install TWRP then install SUperSU to root, no need to use Pwnmymoto, rockmymoto or the like).
If you are basing it on the model number of the phone listed in thread poster signatures... keep in mind the Verizon X Dev Edition is the XT1060. The Verizon MotoMaker X, or the uncustomized X you get from Verizon's web site is also the XT1060.
kzoodroid said:
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
First, those threads instructing people to fastboot flash recovery, system and boot were due to them rooting with RockMyMoto and PwnMyMoto which overwrites the stock recovery to trick and give R/W. They are being instructed to flash the Recovery.IMG, Boot.IMG and System.IMG out of the downloaded SBF/FXZ ROM file. Not flash a custom recovery and then install anything from the custom recovery.
Only when it comes to Rooting a Dev Edition, or consumer edition with unlockd boot loader (like T-Mobile, Sprint or other, but NOT ATT or Verizon non-Dev), are people being instructed to flash a custom recovery (like TWRP) then install SuperSU from inside TWRP to root.
Next, can you please explain to me what you mean by "factory image" because it seems as though your thinking is different than mine. You're saying the only "factory images" that exist are for the X Dev Edition, right? And that those at http://sbf.droid-developers.org/ghost/list.php are NOT factory images, but rather ROMs.
Ok, while you help me understand what you believe the differences to be, please download the VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip from http://sbf.droid-developers.org/ghost/list.php since it is the "consumer" rom. Then visit Moto's web site https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images , and request/download the Verizon X Developer edition rom. Unzip them both to separate folders. then compare the files contained in each (hint the included XML includes the MD5 hash for each file, but you can do a FC /B in windows too). Other than the XML for the one containing the extra "erase" statements, they are the same. No difference. The XML would be opened in RSDLite to flash that way. The individual files could be flashed with moto's fastboot. Then do the same for the T-Mobile version and the GSM Developer edition roms. Again, you'll see the files contained are the same.
kzoodroid said:
Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
Actualy, no the OP can't install a dev ed rom with TWRP, as to flash a custom or recovery that hasn't been signed by moto, you need an unlocked boot loader. But the bootloader on the ATT X can't be unlocked.
Actually, at this point, there is no use for me to continue. I've said enough, and given my reasons. Feel free to disagree with me.

[Q] Help with Root

Hey all,
I'm having some trouble flashing TWRP on my phone. I've been following this guide here. When attempting to install TWRP to get root, however, it won't work. I've tried several different versions of fastboot & mfastboot. Sometimes I get a "bootloader variable not found" error, but most of the time now it exits saying it's successful. However, when I reboot into fastboot mode and then into recovery mode, it's still at the stock recovery. Can someone tell me what I'm doing wrong?
If it helps, my unlock status code shown is 3.
Thanks in advance!

thehockeydude44 said:
Hey all,
I'm having some trouble flashing TWRP on my phone. I've been following this guide here. When attempting to install TWRP to get root, however, it won't work. I've tried several different versions of fastboot & mfastboot. Sometimes I get a "bootloader variable not found" error, but most of the time now it exits saying it's successful. However, when I reboot into fastboot mode and then into recovery mode, it's still at the stock recovery. Can someone tell me what I'm doing wrong?
If it helps, my unlock status code shown is 3.
Thanks in advance!
Click to expand...
Click to collapse
Had the same issue, what I did is rsdlite back to stock and then attempt to flash twrp ,it worked.
Also make sure the twrp download is OK, you may want to re download it
Sent on my Moto X

flashallthetime said:
Had the same issue, what I did is rsdlite back to stock and then attempt to flash twrp ,it worked.
Also make sure the twrp download is OK, you may want to re download it
Sent on my Moto X
Click to expand...
Click to collapse
Forgot to mention I got the OTA as soon as my phone turned on. So go back to stock, root and then do the OTA?

thehockeydude44 said:
Forgot to mention I got the OTA as soon as my phone turned on. So go back to stock, root and then do the OTA?
Click to expand...
Click to collapse
No, ota won't flash with custom recovery.
Which carrier are you on.
Try a factory reset, you will lose all your data etc, so do a backup on your computer
Sent on my Moto X

flashallthetime said:
No, ota won't flash with custom recovery.
Which carrier are you on.
Try a factory reset, you will lose all your data etc, so do a backup on your computer
Sent on my Moto X
Click to expand...
Click to collapse
I didn't think it would... I'm on ATT, with a Dev edition. And no data to backup yet, just got the phone today.
Could you point me to where you got the working .img file?

thehockeydude44 said:
I didn't think it would... I'm on ATT, with a Dev edition. And no data to backup yet, just got the phone today.
Could you point me to where you got the working .img file?
Click to expand...
Click to collapse
Here' s the rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
I believe on your op you used another thread, that thread has I believe the link for rsdlite
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Prior to setting up rsdlite make sure you have the latest moto device manager and drivers installed. Also open up the sbf file and find the XML file, open it up and delete the line that has getvar in it
I took the camera 4.2 ota and I could not flash twrp either even though my boot loader is unlocked. I won't take any more ota's , I'll just flash the firmware through rsdlite
Sent on my Moto X

flashallthetime said:
Here' s the rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
I believe on your op you used another thread, that thread has I believe the link for rsdlite
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Prior to setting up rsdlite make sure you have the latest moto device manager and drivers installed. Also open up the sbf file and find the XML file, open it up and delete the line that has getvar in it
I took the camera 4.2 ota and I could not flash twrp either even though my boot loader is unlocked. I won't take any more ota's , I'll just flash the firmware through rsdlite
Sent on my Moto X
Click to expand...
Click to collapse
OK, I'll use rsdlite to get back to stock, and then flash the new firmware, and then see if I can flash the twrp.img. I saw the line about deleting the getvar line, so I'll make sure I do that too... thanks for the help, I'll let you know how it goes.

thehockeydude44 said:
OK, I'll use rsdlite to get back to stock, and then flash the new firmware, and then see if I can flash the twrp.img. I saw the line about deleting the getvar line, so I'll make sure I do that too... thanks for the help, I'll let you know how it goes.
Click to expand...
Click to collapse
Just flash the AT&T KitKat 4.4 sbf file, then you're up to date
Sent on my Moto X

flashallthetime said:
Just flash the AT&T KitKat 4.4 sbf file, then you're up to date
Sent on my Moto X
Click to expand...
Click to collapse
It worked! It must have been because of the OTA I got immediately... but flashing the correct 4.4 worked (I downloaded it directly from Motorola, since none of those specifically said GSM Dev Edition (turned out to be the T-Mo one). SuperSU works too, now just to install TiBu and be on my merry way!

thehockeydude44 said:
It worked! It must have been because of the OTA I got immediately... but flashing the correct 4.4 worked (I downloaded it directly from Motorola, since none of those specifically said GSM Dev Edition (turned out to be the T-Mo one). SuperSU works too, now just to install TiBu and be on my merry way!
Click to expand...
Click to collapse
I think all the firmware files are for either retail or developer editions, anyways glad it worked. I have no idea why this happens with the ota's?
Sent from my XT1058 using XDA Premium 4 mobile app

flashallthetime said:
I think all the firmware files are for either retail or developer editions, anyways glad it worked. I have no idea why this happens with the ota's?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know either. Might try and figure it out once I'm done with damn finals in 2 weeks.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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