Related
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
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.
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
reno55 said:
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
Click to expand...
Click to collapse
Try using Titanium Backup to freeze MotorolaOTA
samwathegreat said:
Try using Titanium Backup to freeze MotorolaOTA
Click to expand...
Click to collapse
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
reno55 said:
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
Click to expand...
Click to collapse
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
samwathegreat said:
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
Click to expand...
Click to collapse
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
reno55 said:
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
Click to expand...
Click to collapse
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
samwathegreat said:
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Click to expand...
Click to collapse
Can I flash philz?
reno55 said:
Can I flash philz?
Click to expand...
Click to collapse
Don't see why not. Just substitute the filename for philz recovery instead.
Get Philz here: http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
I have not used Philz personally...I prefer TWRP, but it looks like (unlike TWRP), that there is a different img for each variant of the Moto X. You will need to be careful to download the correct one.
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup, TWRP and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is there no way to complete the OTA without flashing a stock recovery? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
YES, that is the best way to do it. You can -try- disabling xposed, and un-doing any major modifications you have done (like freezing or removing any system apps). You want it to be as close to stock as possible before you try to accept the OTA, which includes flashing back the stock recovery.
SBFing back to stock 4.4.2 FIRST, and accepting the update, THEN flashing TWRP and rooting, then re-configuring everything and installing your apps is MUCH safer and pretty much guarantees that your filesystem will be 100% intact.
If it were ME, I would SBF first -- for whatever that's worth...
Good Luck
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
reno55 said:
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
Click to expand...
Click to collapse
Sure. It's just slightly more complicated. You'll need the entire 4.4.2 SBF for your carrier.
Do this: Reboot to bootloader
FIRST, JUST flash gpt.bin and motoboot.img:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Now you need to REBOOT back into bootloader (to prevent gpt.bin mis-match -- if you don't reboot here, you will get errors). Do this by typing:
mfastboot reboot-bootloader
Now flash the rest of the files:
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 erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Reboot, and you should be back to stock 4.4.2
And finally the disclaimer: DO NOT TRY TO DOWNGRADE TO ANY VERSION PRIOR TO 4.4.2 .....if you don't want a brick.
It's ok to downgrade 4.4.3 to 4.4.2 because the bootloader version did not change. It is NOT safe to downgrade to anything prior (4.4 or 4.2.2).
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:
hello all right with you, I hope so, I am Brazilian, and I would take a doubt on the bike variant g2 xt1078 of my region (Brazil).
Accidentally I Flashed the ROM xt1068 on my mobile xt1078, and now the first command "mfastboot.exe flash partition gpt.bin" shows the error "GPT Version Downgrade". And then camndo "mfastboot.exe flash system system.img_sparsechunk.0" It also shows the error "Image is too large" with this system partition has been reduced or changed, I wonder if this has repair, and that any suggestion and welcome.
@lost101
@Kamin4ri
@VitaTaf
@parrotgeek1
l.rochas
Is your Bootloader unlocked?
lost101 said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
yes unlocked.
What is the exact name of the XT1078 firmware image your are currently trying to flash?
lost101 said:
What is the exact name of the XT1078 firmware image your are currently trying to flash?
Click to expand...
Click to collapse
this and the image of factory with august patch
XT1078_THEA_RETBR_DS_6.0_MPBS24.65-34-5_cid12_subsidy-DEFAULT_CFC.xml
mfastboot flash partition gpt.bin
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
And the rest of the commands operates normally
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said
lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said
l.rochas said:
@lost101
does not work, same mistakes previously said
Click to expand...
Click to collapse
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
It seems to be a very risky method, but not hurt to try.
l.rochas said:
It seems to be a very risky method, but not hurt to try.
Click to expand...
Click to collapse
You already almost completely destroyed your handset by flashing the wrong bootloader. You don't exactly have many options here.
lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
I've tried this method.
After a backup of all partitions on another default XT1078, the restore process on my phone finished with error only on /system or /data (I don't remember well).
Then I've tried to boot, but it had boot loop, just blinking very fast the Warning screen of unlocked bootloader.
It didn't work. :/
The only working method was merging XT1068 and XT1078 ROMs. Now Wifi and Mobile Data are working.
Now I can't change this ROM. Lineage or the whole XT1078 stock can't be installed.
The problem was that I didn't realize I was applying a XT1068 ROM on a XT1078 phone.
As all partitions were changed by flashing gpt.bin, the correct gpt.bin of XT1078 can't be applied.
Any solution????
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
benjausen said:
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
Click to expand...
Click to collapse
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
peacehope said:
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
Click to expand...
Click to collapse
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
benjausen said:
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
Click to expand...
Click to collapse
I don't have now a LineageOS ROM to check, but if I'm not wrong, it doesn't have each separated file as Stock ROM. Am I wrong?
I've flashed many Stock ROMs manually file by file, but never with custom ROMs.
Can you please provide any link teaching this with custom ROMs? I really want to try this.
Maybe this can be a solution, and if it works we will help many people here.