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] Lollipop update failing. How do I troubleshoot?

I have a stock pure edition Moto X 2014, I received the update today. It downloads fine, but when it tries to install, it Error, and then reboots, and tells me the install is unsuccessful. This has happened 3 times. I'm rooted, but everything else is stock. How do I troubleshoot or attempt to resolve. I don't even know where to go from here. Thanks for any help!

Can't be rooted. You need a stock system partition.

crap, thanks for the reply. I was worried that was the case. Can I go back?

randyklein said:
crap, thanks for the reply. I was worried that was the case. Can I go back?
Click to expand...
Click to collapse
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ 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 erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.

bradley26 said:
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ 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 erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
Click to expand...
Click to collapse
Thanks so much! You are awesome.

For anyone else with this issue, here is how I solved this.
-Download mfastboot v2 from here, extract into your ADB folder.
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Reboot and the update should now work. Good luck.

I am at encryption unsuccessful... No fastboot, no recovery.. not adb or mfastboot foes not recognize my device. But computer device managerr shows device...
Any workaround to get mfastboot detect my moto x xt1053.
Thanks

affineer said:
I am at encryption unsuccessful... No fastboot, no recovery.. not adb or mfastboot foes not recognize my device. But computer device managerr shows device...
Any workaround to get mfastboot detect my moto x xt1053.
Thanks
Click to expand...
Click to collapse
If you cant access bootloader fastboot and the device is only black screen and the green light notification you have HARD BRICK.
this means you have downgread the device and you try to update ota to newer version.
If you do this you bricked your phone and there is no solution.
If not try to charge your battery for long time and after try to boot on fastboot mode.
Oh sorry you have xt1053?
This is not moto x 2014.
What device do you have?
Moto g,moto x1 ?
The tread is for moto x2.

papsr6 said:
If you cant access bootloader fastboot and the device is only black screen and the green light notification you have HARD BRICK.
this means you have downgread the device and you try to update ota to newer version.
If you do this you bricked your phone and there is no solution.
If not try to charge your battery for long time and after try to boot on fastboot mode.
Oh sorry you have xt1053?
This is not moto x 2014.
What device do you have?
Moto g,moto x1 ?
The tread is for moto x2.
Click to expand...
Click to collapse
sorry for wrong posting,
my device can boot. run boot up animation after bootloader unlocked warning. and stays at ENCRYPTION UNSUCCESSFUL. Reset button does not work.
Power button works fine. but key combination does not help booting to fastboot or recovery. Have tried "mfastboot reboot bootloader" but it does not sense device.
Device manager detects it as MTP device.
Any help.
I will continue seeking help in xt1053 forum till I get it working.

affineer said:
sorry for wrong posting,
my device can boot. run boot up animation after bootloader unlocked warning. and stays at ENCRYPTION UNSUCCESSFUL. Reset button does not work.
Power button works fine. but key combination does not help booting to fastboot or recovery. Have tried "mfastboot reboot bootloader" but it does not sense device.
Device manager detects it as MTP device.
Any help.
I will continue seeking help in xt1053 forum till I get it working.
Click to expand...
Click to collapse
First time i hear this.
Youmust ask in xt1053 tread if someone know what can you do.
Moto x2 not showing this problem i think.
You are sour you use the right combination of buttons for fastboot mode?
Hold power and volume up for turn off the device first and afte try combination buttons for fastboot bootloader mode.

Managed to screw up phone, but bootloader still works.... what to do??

Okay, guys...
I have a big, big, big issue and If it's possible, I'd like all the help in the world.
I unlocked my bootloader, upgraded to mm 6.0 and decided to root and install TWRP because bloatware, right?
Anyways, I did a big no-no and after a series of unfortunate events, I don't have a recovery and I can only boot into the bootloader.
Don't ask HOW I got here, I couldn't tell you with a gun to my forehead.
Now, I have tried ways to get myself out of this:
Installed an earlier TWRP recovery - doesn't work
Installed CM recovery - Doesn't work
Looked on motorola.ca for stock images - doesn't work
I can boot my phone with TWRP but I can't install it. (the inapropriate partition size error in pink)
whatever. Whenever I boot into twrp, I see all my partitions and with modifications on, I cannot format my /sdcard/ partition (internal memory)
it was being detected by my pc a few times and after a few more tries to flash ANY rom compatible with my phone, I simply have no luck.
Any advice right now is more than appreciated!
Awaiting answers with impatience.
EDIT: Forgot to mention the model number is the XT1097 canadian Moto X 2014 (Telus mobility)
Thanks for the help in advance

Have you tried this? Put ROM/gapps on internal storage. Fastboot boot twrp, then flash ROM/gapps with twrp. Once booted you should be able to install twrp via playstore without the partition mismatch issue. I had to go this route to get twrp to stick on my XT1096

I cannot access the internal memory for some reason!
I hear my pc make a sound for connected but it doesn't show up in explorer

Have you tried ADB sideload? Try flashing the stock MM Rom Zip located in the Moto X 2014 XDA Thread. It might work, if it doesn't, I can send you a toolkit that might fix the phone.

I did try to sideload and I get the following:
Installation failed: unable to mount (all the partitions are listed)
E: Failed to mount
E: Can't mount
And if you're talking about RDS Lite, I am completely unable to find my phone with it.

What I really need is a tool that will fix the partition table.
I don't know how, but I messed it up REAL GOOD!

also, for some reason I Have 2 recoveries atm.
When I completely power off my phone and then power on, I boot into the CyanogenMod Recovery.
THEN, when I reboot into recovery, I go into the TWRP recovery.
And every time afterwards I Reboot to recovery, I come back to the TWRP

Install Motorola USB Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download and keep full firmware VICTARA_RETCA_XT1097_6.0
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
If you are able to flash with fastboot, maybe you can go back to stock, then go on from there.
Try these, one by one:
fastboot getvar max-sparse-size
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
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

I know you wouldn't, but hope you do. But if you could tell me how you got here, I could assist you better.

Thank you, Mate!
This restored my phone to retail!
I am in your debt!

You're welcome. We are all here to help each other.

Hi, I am in the exact same situation right now. I tried the fastboot method to flash all the files for the XT1096 VZW version. Every time I boot up after flashing everything, the dead andy with read exclamation point 'No Command' logo pops up and blinks every 5 seconds or so. Any help please? Thanks!

So I managed to get TWRP to install. Now I can't flash anything. All the partitions are somehow corrupted and I can't mount anything. Any ideas on how to fix the partitions?

OK

My apologies, Gus. I just posted a new QA thread on here. Can we discuss there? Thanks.

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

Moto x stuck at bootloader warning screen and won't go anywhere else.

So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.

Slupvee said:
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Click to expand...
Click to collapse
It's always a good idea to put your phone in bootloader mode and do:
fastboot getvar all
So you get all the specs of your phone, and copy the info into a Notepad file.
Did you try reflashing TWRP (twrp-3.0.2-1-victara.img)?
If that's not working, you may be able to reflash stock firmware.
https://firmware.center:8081/firmware/Motorola/
Something like this:
fastboot getvar max-sparse-size
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
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
fastboot reboot

thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.

Slupvee said:
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Click to expand...
Click to collapse
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?

Gus Ghanem said:
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Click to expand...
Click to collapse
Verizon moto x 2014 5.1

Hey did u fixed it?