Database Develop

[Q] Trying to flash back to stock

I formatted system in recovery and i dont have a ROM to flash...am i SOL or is there a way to get out of this mess?

You started another thread? here's the rsdlite thread
http://forum.xda-developers.com/showthread.php?t=2446515
Sent on my Moto X

flashallthetime said:
You started another thread? here's the rsdlite thread
http://forum.xda-developers.com/showthread.php?t=2446515
Sent on my Moto X
Click to expand...
Click to collapse
THANK GOD. Someone to help. I need my phone for tomorrow been like this ALL DAY

Prestige_DOPE said:
THANK GOD. Someone to help. I need my phone for tomorrow been like this ALL DAY
Click to expand...
Click to collapse
Just pick the kitkat sbf firmware for your carrier just to make it easy
Sent on my Moto X

Prestige_DOPE said:
THANK GOD. Someone to help. I need my phone for tomorrow been like this ALL DAY
Click to expand...
Click to collapse
follow the steps below
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache

dray_jr said:
follow the steps below
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Click to expand...
Click to collapse
Thank You for your help man. Everything is up and working. Felt like i had a paper weight on my hands

Why flash back to the 4.2.2 camera OTA with an unlocked bootloader?

[Q] xt1056 Sprint, wont connect to network please help

while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.

I attempted the slapmymoto method in the motoxtool kit and selected verizon

bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root

dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?

bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device

i restored completely to stock and am still having the same issue. please help

bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in

dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.

bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.

dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash

bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734

dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.

dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.

I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied

ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.

dray_jr said:
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this

Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.

Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old

sorry but how do I remove the var line?

ive got it figured out thank you for your help

[HELP] Moto X bricked. How to unbrick it?

let me explain what exactly happened. l was running LiquidSmooth v3.2 on my Moto X. I have flashed few roms previously as well. I was facing no issues whatsoever but still wanted to upgrade to LiquidSmooth v4.0. So this time when I got on fastboot menu
and chose recovery, I got invalid kernel/ ramdisk size error. I was not able to enter recovery menu and this has happened to me for the first time. I chose normal reboot and then even the phone was working fine. But now, things have gone worse. I entered fastboot menu again and by mistake chose factory option instead of recovery. Phone started rebooting i think. As i had installed LiveLog app on my phone all I could see was logs on the screen. I waited for around 45 minutes but phone didnt boot up. I switched off and restarted again but same result. I think it is bricked. Is there any way I can get my phone back to working state? Any kind of help would be appreciated.
Thanks.

Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy

crazyworm said:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
Click to expand...
Click to collapse
you can def do that but if you want to try to bring it back to life without going to stock you can try this.
Flash your custom recovery again threw fastboot. then after that if you can boot into it just reinstall LS rom and try and boot your phone up if no luck then just follow the above guide from my thread and return to stock and redo everything

Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app

d1nesh said:
Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yes Root Romoved, don't use last command "fastboot oem lock" if you want bootloader still unlocked

Sound advice above... Except there's no reason to lock your bootloader again. I'd skip that part. And remain unlocked. ?

Thanks a lot. I will try this method today and then flash LiquidSmooth v4.0. Just in case if I face any problem, I'll be back.
Sent from my GT-S5360 using xda app-developers app

I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app

d1nesh said:
I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
what carrier is your phone from i will try and find a good like for the stock firmware.
but like i said i would try to just flash the custom recovery and see if you can boot into it. if you can you might not have to go back to completely stock from the recovery you can iinstall liquid smooth rom. it has its own kernel so it should fix the kernel issue and system issues. if not then you can go back to flashing everything to stock.

It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Also, can you please guide me through the steps so that I do not make any mistakes this time. I'm really scared this time and I don't wanna hard brick my phone. I'd be really very thankful.
Sent from my GT-S5360 using xda app-developers app

Thank you for your help, guys.
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA

d1nesh said:
It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Click to expand...
Click to collapse
No. USB Debugging does not need to be on when using RSDLite or mFastboot.
d1nesh said:
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA
Click to expand...
Click to collapse
At this point, I would consider redoing the steps outlined by @dray_jr earlier in this thread.. with a few tweaks...
its important to be using the correct ROM for your phone. Is there fine print on the back of your phone, does it say XT1052? If so, the link to the Asia XT1052 4.4.4 rom should be correct.
Next... use mfastboot for ALL parts, not just system.img, and follow these steps.. Yes, the are very similar to what you did already, and yes, i know some are repeated, that is intentional.
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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 reboot
OPTIONAL, but in your case might be necessary: just before the final mfastboot reboot command, issue... mfastboot erase userdata this will erase your apps and data.
If any of these commands fail, please make sure you capture it and post it. (NOTE: there is a way to select and copy on the text from the CMD Prompt window, please do that, rather than screen shot)
Once your phone boots up properly, it will be back to stock, unrooted, but as long as you don't do the "oem lock" command with mfastboot or fastboot, your bootloader will remain unlocked. You can then flash TWRP or other custom recovery and re-root.

My XT1072 stuck on fastboot flash screen - Help needed

Hi,
I have an XT1072 which was rooted and running CM. Since I wanted to install stock ROM, I used the Windows Tool from this forum to restore stock Android. By doing so, I was stuck with Bootloader locked screen.
Since then I am stuck on Fastboot Flash Mode screen (see pic attached).
When I try to connect my device to the same PC or any other PC and try mfastboot or fastboot or any command, it just says Waiting for device. I have all the required drivers installed in all the PCs I tested.
Using the volume buttoms, I am able to select any option, but it wont open any option (such as Normal Powerup or Recovery)
Can someone help?
Thanks

anyone?

ram11 said:
anyone?
Click to expand...
Click to collapse
Your system image is signed using incorrect key. Reflash system partition with factory image.

LuK1337 said:
Your system image is signed using incorrect key. Reflash system partition with factory image.
Click to expand...
Click to collapse
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?

ram11 said:
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
Click to expand...
Click to collapse
You need to get fastboot drivers...

LuK1337 said:
You need to get fastboot drivers...
Click to expand...
Click to collapse
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.

ram11 said:
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
Click to expand...
Click to collapse
Join #titandev at freenode in 20 mins, I'll try to help you out.
Sent from my Moto G 2014 LTE using Tapatalk

Any luck?
Hi Guys,
I know this is a long shot as this is an old thread but did you get anywhere with a resolution to this?
I'm in the exact same position.
Tried flashing with different factory roms and "fastboot boot" to try force it to boot a twrp image

I'm also stuck here, anyone has had any luck?

Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
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 system system.img_sparsechunk.5
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
Click to expand...
Click to collapse
This will flash the fw, factory reset and reboot the phone.

I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it
dr.nic said:
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
This will flash the fw, factory reset and reboot the phone.
Click to expand...
Click to collapse
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!

Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
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 system system.img_sparsechunk.5
mfastboot reboot
Click to expand...
Click to collapse
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks

dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
Bootloader should check if boot and system images are correct otherwise it should send user back to bootloader.

dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
I gave this a shot as suggested and I'm getting this error:
C:\Users\Nick\Downloads\New folder>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259279 KB)...
OKAY [ 9.742s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.131s
Also getting the error:
version downgraded for system
Invalid PIV signed system image

Out of tricks stock flash + factory reset always worked for me sorry.
I noted my phone model/region before doing anything (xt1072-thea-reteu) got the right fw and it worked fine, maybe was another problem giving the same error "failed to validate system image" unable to boot and stuck in bootloader, weird.... :\

Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?

nickkk93 said:
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
Click to expand...
Click to collapse
My phone is in a drawer I'd love to be able to fix it because I really miss Android now but it there doesn't seem to be a solution... I am no giving up hope entirely though!

I tink that I have similar problem with my X1072.
After unroot with Kingroot and install AdAway and TWRP from Google Play I even noticed that I hadn't unlock bootolader.
Now I can't reboot my phone without entering in Bootloader and reseting to factory defaults. After some reboots no data has been deleted.
I have tried to reflash the entire phone but In bootloader mode the phone is not detected by the computer, so I can't flash. I'm stucked. by now

josepmanel said:
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Click to expand...
Click to collapse
Have you had any luck at all? My phone has been in a drawer for a couple of months now...

Guys try flashing the latest MM stock i discovered an error too in my old update script /sniff.
Run the *.bat as admin .
Stock zip for XT1072:
MEGA Mirror 1
MEGA Mirror 2
Fastboot+mfastbootv2
BAT File
MM Flash BAT said:
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_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
Click to expand...
Click to collapse
Also remember if you are on another model and not XT1072 you should dl the correct image for your phone from HERE Look if Android 6 is available for your country, if you have gb-de-fr-es you can use the EU stock image.
Unpack everything in the same folder and launch the *.BAT as admin

No OS Can't Boot

So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.

Speedy712 said:
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Click to expand...
Click to collapse
So you have the Motorola USB drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Recent versions of ADB/Fastboot.
Latest stock firmware:
firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1096/
Probably VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Extract the firmware and put the 4 ADB/Fastboot files in the folder with the firmware files.
Boot into Bootloader Mode and connect the phone, make sure the phone says "connected..."
Shift + right-click inside that folder, Open command window here... Paste these commands, BUT CHECK THE NUMBER of sparsechunks your firmware has:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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 fb_mode_clear

Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!

Speedy712 said:
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Click to expand...
Click to collapse
You're welcome, glad it worked!
If you want to try custom roms again, I've been using TWRP 3.0.2-1 and it seems to have no issues so far (and I'm running the latest CM Nightlies).

Gus Ghanem said:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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 fb_mode_clear
Click to expand...
Click to collapse
so with this method you dont have to use the motofastboot?

fakieskr8333 said:
so with this method you dont have to use the motofastboot?
Click to expand...
Click to collapse
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.

Gus Ghanem said:
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Click to expand...
Click to collapse
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.

fakieskr8333 said:
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
Click to expand...
Click to collapse
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?

Gus Ghanem said:
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Click to expand...
Click to collapse
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?

fakieskr8333 said:
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
Click to expand...
Click to collapse
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.

Gus Ghanem said:
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Click to expand...
Click to collapse
Thanks, I am at work now but as soon as I get home I will give it a go. I have been on iOS for over a year now and my moto has been dead since about a month after moto allowed us to unlock the verizon variant. Stupid thing lol.

how do I check the amount of sparsechunks that I have. Sorry for the dumb question
---------- Post added at 02:04 PM ---------- Previous post was at 01:44 PM ----------
I just finished doing this. I am kind of a noob at this so bear with me. I tried this and I get this message that says "Boot up failed" when I try normal powerup. I'm kind of scared..

ABSOLUTE LEGEND
i was stuck since almost 36 hours, good i dint lose hope and smash the x against the wall
YOUR A LIFE SAVER Fakieskr