Database Develop

Flash LMY47E and Preserve Data

I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.

Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery

From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up

y2whisper said:
From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up
Click to expand...
Click to collapse
Only if you boot android before rooting. Install-recovery.sh is suppled with the ROM that upon boot will install stock recovery. However flashing SuperSU hijacks this script for its own purposes, removing its ability to flash recovery. So trick is flash the ROM, boot straight to recovery and flash SuperSU

Ah. Good to know

rootSU said:
Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery
Click to expand...
Click to collapse
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
EDIT: See your post above (I took too long typing). Thanks for clarifying.

ManHands said:
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
Click to expand...
Click to collapse
Have a look above.

I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot

Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed

moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
rootSU said:
Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed
Click to expand...
Click to collapse
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.

ManHands said:
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.
Click to expand...
Click to collapse
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.

Look at the op on Franco's thread and you'll have your answer

holeindalip said:
Look at the op on Franco's thread and you'll have your answer
Click to expand...
Click to collapse
If he looks in the Franco thread, it will answer his question about having to flash a stock boot.img?

moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?

rootSU said:
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.
Click to expand...
Click to collapse
Brain fart, for future reference Franco r1-r19 is 5.0,5.0.1,5.0.2 and r20+ is for 5.1

Thanks for the input everyone. To follow-up, I took the steps just as I planned in OP. No need to flash boot.img as frano-r20 is what I'm running and is compatible with 5.1 (despite the build # difference). I also didn't want to encrypt as the factory boot.img will force encrypt.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
And just as @rootSU pointed out, prior to booting system, go into TWRP from bootloader to install su.zip first (otherwise factory recovery will overwrite TWRP). Then boot system, and you're back in business. Just had to re-do a couple build.prop edits, but everything else was as it was before.

If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?

lamenting said:
If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?
Click to expand...
Click to collapse
That, or you can wait for 47E factory boot.img that's non-enforcable. But, from the sounds of it people are still able to use the 47D boot.img linked in the post you provided. I'd imagine there's not much difference between the two.

Forerunner326 said:
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?
Click to expand...
Click to collapse
I have no idea honestly, I saw someone else post it that way. It is probably not necessary.

ManHands said:
I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.
Click to expand...
Click to collapse
After flashing the files in fastboot you said to use the hardware buttons to boot into TWRP. How exactly did you go from fastboot to TWRP? Did you just power off while in fastboot or something else?

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.

MOB30I Swap Partition.

Anyone else noticing that the device now shows a swap partition? I used diskinfo (https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en) for this, and before updating to MOB30I, this swap partition wasn't there, it was included in my normal RAM.
EDIT: Here's a screenshot. http://i.imgur.com/GoLG6EP.jpg

Mine doesn't. Only flashed bootloader & system though.

Strange. I did a flashboot flash-all install of 30i and don't have a swap partition.
Sent from my Nexus 6 using XDA Labs

No swap partition here either. Also on MOB30I

Wow that's really strange. I flashed all of the img files one by one. And then noticed the swap partition. I didn't do anything out of the ordinary. ._.

H4X0R46 said:
Wow that's really strange. I flashed all of the img files one by one. And then noticed the swap partition. I didn't do anything out of the ordinary. ._.
Click to expand...
Click to collapse
What order maybe that matters

DR3W5K1 said:
What order maybe that matters
Click to expand...
Click to collapse
My exact steps.
fastboot flash bootloader bootloader[tab]
fastboot reboot-bootloader
fastboot flash radio radio[tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
then I rebooted, installed elite kernel, went back into bootloader and ran fastboot format userdata again to unencreypt, systemless rooted, and installed xposed. Those are my exact steps, this swap partition caught me by surprise.

H4X0R46 said:
My exact steps.
fastboot flash bootloader bootloader[tab]
fastboot reboot-bootloader
fastboot flash radio radio[tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
then I rebooted, installed elite kernel, went back into bootloader and ran fastboot format userdata again to unencreypt, systemless rooted, and installed xposed. Those are my exact steps, this swap partition caught me by surprise.
Click to expand...
Click to collapse
It's probably from elite having swap default. Or maybe you turned or on with kernel auditor

Could that mean possible Ubuntu touch support with Multi ROM?
Sent from my Nexus 6 using XDA-Developers mobile app

DR3W5K1 said:
It's probably from elite having swap default. Or maybe you turned or on with kernel auditor
Click to expand...
Click to collapse
I got with the dev for elite and he said it was in a recent update to the kernel, so it's the kernel that does this. Thanks guys!

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

Restoring to stock now has blinking green android blinking at bootup. What to do?

After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!

D.A.N. said:
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
Click to expand...
Click to collapse
You need to be more specific. Hopefully you didn't downgrade the bootloader or partition table. Can you put the phone in bootloader mode and type this?
fastboot getvar all
You need to find the latest stock firmware for your variant and region, and flash it like this (example from my variant):
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

Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?

D.A.N. said:
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
Click to expand...
Click to collapse
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all

Gus Ghanem said:
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Click to expand...
Click to collapse
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.

D.A.N. said:
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
Click to expand...
Click to collapse
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/

Gus Ghanem said:
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Click to expand...
Click to collapse
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.

D.A.N. said:
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
Click to expand...
Click to collapse
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.

Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.

D.A.N. said:
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
Click to expand...
Click to collapse
What storage type should i have?EXT4 or something else?

D.A.N. said:
What storage type should i have?EXT4 or something else?
Click to expand...
Click to collapse
I think it's normally ext4, not sure if it's for all partitions. Data might be f2fs.

Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.

D.A.N. said:
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
Click to expand...
Click to collapse
Even if you reboot TWRP?
Is your stock firmware MPES24.49-18-7

Gus Ghanem said:
Even if you reboot TWRP?
Click to expand...
Click to collapse
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.

D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
Your stock firmware files, are they MPES24.49-18-7
I have a XT1097 RETCA
You could try reflashing the partition table and bootloader if you're absoluitely sure you have the latest firmware.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img

D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?

D.A.N. said:
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
Click to expand...
Click to collapse
It is ext4 except data, which is f2fs

File system

\
Gus Ghanem said:
It is ext4 except data, which is f2fs
Click to expand...
Click to collapse
it was the file system types. I changed them to what you said and it wiped them. attempting to reinstall rom and if it works i can try to go to stock again i guess. Thank you Gus for taking time to help.

Gus Ghanem said:
File system
Click to expand...
Click to collapse
I installed stock rooted rom. It booted backed into recovery. I had to reboot into bootloader, rebooted from there and it is turning on. I think something is still screwed up though because it always boots back into recovery.