Database Develop

Moto X TMO Dev Edition Freezing

Hi,
I just got my Moto X Dev Edition GSM TMO last week, but I got it very unstable, while I had try to wipe cache and factory reset few times.
Some problem that I have
Numeric Keypad is not shown while using google keyboard. The problem that my email is using 2FA from google to entry my 6-digit PIN
Chrome freeze while open quite complex pages
Gmail freezing while open communication more than 3 email on the messaging mode
Path also unstable while need to scroll down and request to reload more data.
Whatsapp stuck when there's few message has beeen received
Thinking to downgrade the os to 4.4, but when I read in some thread inform better not to downgrade that might cause device brick.
Is there any other solution so I can use my Moto X for daily, while waiting for T-Mobile latest 4.4.2 rom.
Please share
Thank you

If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!

SymbioticGenius said:
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Click to expand...
Click to collapse
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?

tyapeter said:
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
Click to expand...
Click to collapse
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.

eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks

Let me make it easier. Just flash the system and kernel files leave everything else alone. However the ability to go back depends on how you got to 4.4.2 to begin with, OP said he took the OTA, not sure about you.
My advice assuming you're stock is to call Motorola, tell them you took the ota and these are the issues you're having. Get them to send you a new phone. I'd rather see you do that than brick your phone trying to do it yourself.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!

eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Are you sure this is correct? I was told in this thread: http://forum.xda-developers.com/showthread.php?p=50330230#post50330230 (see post #12):
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
Click to expand...
Click to collapse
So the way I understand it one cannot downgrade from 4.4.2 to any other version because bootloader in 4.4.2 was changed and is not compatible with any previous release.

tyapeter said:
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Click to expand...
Click to collapse
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
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 erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366

eksasol said:
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
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 erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
Click to expand...
Click to collapse
Thanks a lot, it works

[Q] Moto X probabbly hard bricked

Hello anyone! I'm looking for some help.
My phone was running android 4.4.2, then i modified the buil.prop for increasing the display density & my phone got off, then i tried and tried and tried turn it on, then i did it & i fash my stock rom (for XT1058 america movil MX) the OTA told me about the update & i accept it... Well my phone now is in fastboot & he says this (yep ''he'' LOL):
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
Well, i wish someone could help me, i don't want to have a beautiful $400 paperweight, thanks a lot XDA

TUESONER said:
Hello anyone! I'm looking for some help.
My phone was running android 4.4.2, then i modified the buil.prop for increasing the display density & my phone got off, then i tried and tried and tried turn it on, then i did it & i fash my stock rom (for XT1058 america movil MX) the OTA told me about the update & i accept it... Well my phone now is in fastboot & he says this (yep ''he'' LOL):
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
Well, i wish someone could help me, i don't want to have a beautiful $400 paperweight, thanks a lot XDA
Click to expand...
Click to collapse
try to flash with mfastboot the recovery from 4.4.2 the FIRMWARE U HAVE IT FIRST
MUST BE THE SAME VERSION THAT U HAVE FIRST THAT UR PHONE BRICKED
after u flash the recovery,reboot bootloader and try to flash all firmware

TUESONER said:
Hello anyone! I'm looking for some help.
My phone was running android 4.4.2, then i modified the buil.prop for increasing the display density & my phone got off, then i tried and tried and tried turn it on, then i did it & i fash my stock rom (for XT1058 america movil MX) the OTA told me about the update & i accept it... Well my phone now is in fastboot & he says this (yep ''he'' LOL):
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
Well, i wish someone could help me, i don't want to have a beautiful $400 paperweight, thanks a lot XDA
Click to expand...
Click to collapse
You had 4.4.2 on your phone, I'm betting the "stock rom" you had then tried flashing was 4.4 or lower.
As danger2u said, the first thing you'll want to try is to flash the ROM for your phone. Since you had 4.4.2 on there, you'll need to find the 4.4.2 SBF for your carrier (I don't see american movil mx listed on -> http://sbf.droid-developers.org/phone.php?device=0 ), and flash it.
If that doesn't work, you'll want to see this thread -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 It too requires you have the correct ROM for your device
If you manage to get it working.. DO NOT DOWNGRADE YOUR ROM!!!!! (i.e. once on 4.4.2 do NOT flash 4.4 or below!!!!)

KidJoe said:
You had 4.4.2 on your phone, I'm betting the "stock rom" you had then tried flashing was 4.4 or lower.
As TUESONER said, the first thing you'll want to try is to flash the ROM for your phone. Since you had 4.4.2 on there, you'll need to find the 4.4.2 SBF for your carrier (I don't see american movil mx listed on -> TUESONER ), and flash it.
If that doesn't work, you'll want to see this thread -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 It too requires you have the correct ROM for your device
If you manage to get it working.. DO NOT DOWNGRADE YOUR ROM!!!!! (i.e. once on 4.4.2 do NOT flash 4.4 or below!!!!)
Click to expand...
Click to collapse
I got my phone with 4.2.2 out of the box, then i recivied the 4.4.2 via OTA, at&t us have the XT1058, would i install the rom on 4.4 fot at&t then flash the modem?

TUESONER said:
I got my phone with 4.2.2 out of the box, then i recivied the 4.4.2 via OTA, at&t us have the XT1058, would i install the rom on 4.4 fot at&t then flash the modem?
Click to expand...
Click to collapse
No. If you received 4.4.2 OTA... you need to flash 4.4.2. do NOT flash 4.4.
Due to changes in 4.4.2, you either will brick, or set yourself up to brick if you try to downgrade your rom version... i.e. 4.4.2 -> 4.4 will brick or set you up for it.
Were you running an ATT ROM on your phone? or something else?

KidJoe said:
No. If you received 4.4.2 OTA... you need to flash 4.4.2. do NOT flash 4.4.
Due to changes in 4.4.2, you either will brick, or set yourself up to brick if you try to downgrade your rom version... i.e. 4.4.2 -> 4.4 will brick or set you up for it.
Were you running an ATT ROM on your phone? or something else?
Click to expand...
Click to collapse
I'm wrong, i wanted to write 4.4.2. I was running my stock rom, america movil 4.2.2, recivied the OTA for 4.4.2, in the page of firmwares i can´t find the firmware for america movil 4.4.2, probabbly it doesn´t exist, so, can i flash the rom for the at&t XT1058, then i got the modem for my carrier flashed?

TUESONER said:
I'm wrong, i wanted to write 4.4.2. I was running my stock rom, america movil 4.2.2, recivied the OTA for 4.4.2, in the page of firmwares i can´t find the firmware for america movil 4.4.2, probabbly it doesn´t exist, so, can i flash the rom for the at&t XT1058, then i got the modem for my carrier flashed?
Click to expand...
Click to collapse
I don't know the differences in the ATT Rom vs America Movil... I know the ATT rom has a lot of bloat.
I don't think the ATT 4.4.2 SBF was leaked yet (it wasn't when i looked earlier)...

TUESONER said:
I'm wrong, i wanted to write 4.4.2. I was running my stock rom, america movil 4.2.2, recivied the OTA for 4.4.2, in the page of firmwares i can´t find the firmware for america movil 4.4.2, probabbly it doesn´t exist, so, can i flash the rom for the at&t XT1058, then i got the modem for my carrier flashed?
Click to expand...
Click to collapse
the only Movil 4.4.2 is this
http://sbf.droid-developers.org/download.php?device=0&file=835
so i think u have this version of firmware on 4.2.2
download it
extract firmware
flash only the recovery
reboot bootloader
then flash entire rom
let us know

KidJoe said:
You had 4.4.2 on your phone, I'm betting the "stock rom" you had then tried flashing was 4.4 or lower.
As danger2u said, the first thing you'll want to try is to flash the ROM for your phone. Since you had 4.4.2 on there, you'll need to find the 4.4.2 SBF for your carrier (I don't see american movil mx listed on -> TUESONER ), and flash it.
If that doesn't work, you'll want to see this thread -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 It too requires you have the correct ROM for your device
If you manage to get it working.. DO NOT DOWNGRADE YOUR ROM!!!!! (i.e. once on 4.4.2 do NOT flash 4.4 or below!!!!)
Click to expand...
Click to collapse
This ^^
If you downgraded and then took an ota, that usually leads to a brick. Read the thread kid Joe posted and hopefully you can recover.
Good luck!
Oh, and as said....the best moto x advice there is, is once on 4.4.2.....stay on 4.4.2. Unfortunately.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

Thanks anyone for the suport, tomorrow imma try with that rom, i'm reall tired today, was a lng day at my work, i will post the results, again, thanks everyone, wait for my post tomorow.

TUESONER said:
Thanks anyone for the suport, tomorrow imma try with that rom, i'm reall tired today, was a lng day at my work, i will post the results, again, thanks everyone, wait for my post tomorow.
Click to expand...
Click to collapse
kj2112 said:
This ^^
If you downgraded and then took an ota, that usually leads to a brick. Read the thread kid Joe posted and hopefully you can recover.
Good luck!
Oh, and as said....the best moto x advice there is, is once on 4.4.2.....stay on 4.4.2. Unfortunately.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
danger2u said:
the only Movil 4.4.2 is this
xxx
so i think u have this version of firmware on 4.2.2
download it
extract firmware
flash only the recovery
reboot bootloader
then flash entire rom
let us know
Click to expand...
Click to collapse
It did't work at all, i flashed the recovery then the entire rom, now thce cellphone turn on, then i see the message of the unlocked bootloader, then the screen goes black & for something like half second i see the image of andy (the android caracter) & the legend ''updating'' then another image for half second or less that says ''error''
The rom has flashed correctly, i can enter in fastboot mode too

TUESONER said:
It did't work at all, i flashed the recovery then the entire rom, now thce cellphone turn on, then i see the message of the unlocked bootloader, then the screen goes black & for something like half second i see the image of andy (the android caracter) & the legend ''updating'' then another image for half second or less that says ''error''
The rom has flashed correctly, i can enter in fastboot mode too
Click to expand...
Click to collapse
flash it manually
try another firmware that is 4.4.2 and compatible with ur country and operator
now if turns on is no more bricked. u are on the good way

danger2u said:
flash it manually
try another firmware that is 4.4.2 and compatible with ur country and operator
now if turns on is no more bricked. u are on the good way
Click to expand...
Click to collapse
flash manually? that's with fastboot or mfastboot? what comands do i need to use?

TUESONER said:
flash manually? that's with fastboot or mfastboot? what comands do i need to use?
Click to expand...
Click to collapse
mfastboot
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
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 erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear

danger2u said:
mfastboot
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
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 erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
Careful.. That is an example for Verizon. It might not match the XML that is in whatever rom TUESONER is trying to flash on an XT1058.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
TUESONER said:
flash manually? that's with fastboot or mfastboot? what comands do i need to use?
Click to expand...
Click to collapse
First off, which SBF are you trying to flash? is it 4.4.2 or 4.4?
Past or attach the XML which is inside the SBF you are using. We'll help you convert it to the correct series of mFastboot commands.

KidJoe said:
Careful.. That is an example for Verizon. It might not match the XML that is in whatever rom TUESONER is trying to flash on an XT1058.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
First off, which SBF are you trying to flash? is it 4.4.2 or 4.4?
Past or attach the XML which is inside the SBF you are using. We'll help you convert it to the correct series of mFastboot commands.
Click to expand...
Click to collapse
he can pass the comand
mfastboot oem config carrier vzw
it works without this too

KidJoe said:
Careful.. That is an example for Verizon. It might not match the XML that is in whatever rom TUESONER is trying to flash on an XT1058.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
First off, which SBF are you trying to flash? is it 4.4.2 or 4.4?
Past or attach the XML which is inside the SBF you are using. We'll help you convert it to the correct series of mFastboot commands.
Click to expand...
Click to collapse
i will use this one, i erased the line of ''max download size''

TUESONER said:
i will use this one, i erased the line of ''max download size''
Click to expand...
Click to collapse
Is that the exact 4.4.2 ROM that was on your phone originally? If not, there is a chance this still might not fix you...
Its extremely similar to what @danger2u has already posted.
(based on Moto's web site and the XML you posted) after unzipping the "CLARO-BR_GHOST..." SBF, you'd want to try the following commands from the folder where you unzipped the SFB after booting the phone to fastboot/bootloader mode....
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 erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot reboot
NOTE: by Mfastboot, I mean the Moto modified version of fastboot, not the one that comes with the standard Android SDK/Platform Tools. The moto modified Fastboot.exe can sometimes be found in a windows folder inside an SBF, or you can download from -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip

KidJoe said:
Is that the exact 4.4.2 ROM that was on your phone originally? If not, there is a chance this still might not fix you...
Its extremely similar to what @danger2u has already posted.
(based on Moto's web site and the XML you posted) after unzipping the "CLARO-BR_GHOST..." SBF, you'd want to try the following commands from the folder where you unzipped the SFB after booting the phone to fastboot/bootloader mode....
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 erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot reboot
NOTE: by Mfastboot, I mean the Moto modified version of fastboot, not the one that comes with the standard Android SDK/Platform Tools. The moto modified Fastboot.exe can sometimes be found in a windows folder inside an SBF, or you can download from -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
Click to expand...
Click to collapse
The ROM isn't the original that was running my phone, i got 4.2.2 out of the box, now i will indtsll thst ROM because is 4.4.2 & i will not brick or have problems, the fastboot that you attached doesn't work with the comands ''mfastboot'' i use just ''fastboot''?

i did it!
GUYS! THANK YOU A LOT! i did it, mi moto X is alive, thanks @KidJoe, @danger2u & @kj2112, you helped me without even knowing me.
I used the comands that @KidJoe gave me, but using just ''fastboot'' everything is working fine, even the 4G connection.
Thanks, really, really thanks... Now i feel i'm a real XDA member & i wish my post help people.

Ota updates on unlocked bootloader? Please help

I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?

why nobody answered my questions yet? Plz reply soon

sandy1636 said:
I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?
Click to expand...
Click to collapse
Unlocked bootloader, doesn't matter with updates, or system flash..only when one needs Root, then the bootloader needs unlocked, unless a Root exploit is used..
sent by my
5.0_22.11.6 Lollipop (Rooted)
TWRP v2.8.0.1-titan
UPDATE-SuperSU-v2.16
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!

Try this:
Flash Stock firmware using these commands in this order:
Code:
[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot
Hope this helps

KrishnaSagar said:
Flash Stock firmware using these commands in this order:
Code:
[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot
Hope this helps
Click to expand...
Click to collapse
i have already entered all these commands and successfully flashed stock rom. But when i enter mfastboot.exe oem lock, its shows as (bootloader) sst lock failure.

That is the standard procedure, but if you are getting errors then please refer to this thread:
http://forum.xda-developers.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827

KrishnaSagar said:
That is the standard procedure, but if you are getting errors then please refer to this thread:
http://forum.xda-developers.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827
Click to expand...
Click to collapse
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.
But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery. Is that true?

sandy1636 said:
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.
But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery. Is that true?
Click to expand...
Click to collapse
Yes. OTA updates are available on Unlocked Bootloader as long as you dont Root or change the recovery.

Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?
I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.

grayme said:
Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?
I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.
Click to expand...
Click to collapse
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.
If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.

rufflove said:
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.
If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.
Click to expand...
Click to collapse
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.

grayme said:
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.
Click to expand...
Click to collapse
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.

rufflove said:
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.
Click to expand...
Click to collapse
I used to understand these phones, but everything just seems so much more complicated these days!
I'm getting old.

Stock image for XT1097?

Hi,
I have a Brazilan version XT1097, bootloader unlocked but no root yet.
I cannot install anything from play store because I get an error that does not say much.
All I did was trying to root using a guide I found that tells you to use CF-Autoroot, but it just did not work.
Then I installed TWRP to see if there was any ROMs available since I came from the Nexus 5 and was used to see tons of ROMs on xda to grab and flash.
To my surprise, none is available so far.
Now I am trying to find the original 1097 images to flash on my device and go back to stock.
Might even give up on root, if necessary, but I need the phone back
Any ideas on how to proceed?

A different problem now
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!

leandroqm said:
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
Click to expand...
Click to collapse
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
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 (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.

seco2004 said:
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
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 (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
Click to expand...
Click to collapse
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!

leandroqm said:
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
Click to expand...
Click to collapse
Did you get it working?
Sent from my XT1097 using Tapatalk

seco2004 said:
Did you get it working?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Yes, absolutely!
I upgraded it to lollipop and rooted right afterwards

How did you get a 1097 stock Lollipop image?

TheAquanox said:
How did you get a 1097 stock Lollipop image?
Click to expand...
Click to collapse
secco2004 shared me his backups

But is it 1097 lollipop or 1095 with the módem from 1097? Can you share dais backup? I'm Being unable to tether and would like to find out if it is the rom or the phone.
Greetings !

It was actually the KK 4.4.4 original images.
I had to update to lollipop right after via OTA.
IDK if secco2004 allows me to share it. Could you PM him, please?
He posted recently on the topic.

Yeah, it was actually the 4.4.4 Brazilian firmware, feel free to share it. For lollipop I have just the flasheable zip.
Sent from my XT1097 using Tapatalk

Since secco2004 said it is ok to share, tell me if you want me to sent it somewhere...
It is the XT1097 4.4.4 brazilian original images.

hey, can I have XT1097 stock images please?

I also need it
I flashed NX CM12.1 v3.0 rom and lost gps.
Someone in the thread said that i have to go back to stock, verify gps is working properly... blah, blah, blah.....
So the thing is that i don´t know what stock image to use on my phone and where to get it.
It is a XT1097.
Can any of you guys help me?

Need help please
I've flashed ATT_XT1097_5.0.2_system_ ext4_ root.zip using Mofo.exe and followed directions to the T but soon as its done flashing I reboot back into fastboot mode to wipe the cache but gives me error hab check failed for recovery failed to validate recovery image boot up failed. Please any help would be a life savor i'm lost. Anyone know where to find recovery.img file for Moto X XT1097 stock image file maybe I can flash in fastboot mode? I just hope I Dont have a bricked device. I am stuck in bootloop mode and can't wipe cache.

Thanks!
I really thank you, it worked for me! :good:

[Q] lollipop to kit kat?

Is it possible to downgrade from lollipop to KitKat? Is there any guide out there?
I have a simfree uk motox 2014 from Motorola, currently unrooted
Please let me know!
Thanks and happy holidays

If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Edit: You can't just flash factory image to downgrade. See my post below.

_MetalHead_ said:
If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Click to expand...
Click to collapse
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L

varignet said:
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L
Click to expand...
Click to collapse
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.

_MetalHead_ said:
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.
Click to expand...
Click to collapse
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks

fbiryujin said:
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks
Click to expand...
Click to collapse
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.

_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Edit: Also I take it that I should use mfastboot?

fbiryujin said:
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Click to expand...
Click to collapse
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.

Huh, I had never heard of RSD Lite before... I have just been using mfastboot.

_MetalHead_ said:
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.
Click to expand...
Click to collapse
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it

fbiryujin said:
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it
Click to expand...
Click to collapse
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.

_MetalHead_ said:
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.
Click to expand...
Click to collapse
Thanks. I'll use mfastboot just to be sure (If I even need to downgrade). Now to wait for that Walnut Finish to come back in stock :/

mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04

NWKENT said:
mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
Click to expand...
Click to collapse
I wonder why they stopped including XML files...

_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.

divergens said:
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.
Click to expand...
Click to collapse
So you skipped "fastboot flash boot boot.img"?

No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img

divergens said:
No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.

fbiryujin said:
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.
Click to expand...
Click to collapse
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.

divergens said:
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.
Click to expand...
Click to collapse
Haha my main device is sadly an iPhone 6 right now, and that's too big. I prefer the size of the iPhone 5S or the first gen Moto X. I want to be able to use the entire device with one hand while being secure in the fact that a movement or gesture won't loosen my grip on it. Sadly the world is just making bigger phones now, and the few smaller ones out there are "cheap" low budget/power options.