Database Develop

Lost 40GB Disk-Space after flashing 5.1

Hi Friends,
i lost after flashing to 5.1 nearly 40GB of storage.
i flashed via fastboot.
Any idea to fix this?

Just do a factory reset it happen .after flashing . don't worry when u do a factory reset it will show the storage .

Dont help.
i started from the beginning again and uses this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
Click to expand...
Click to collapse
and when i try to get into the stock recovery, i see just a dead android-guy with a red alarm-sign

Hold power and press up once while that is showing.

Muchas Gracias.. it worked.

pauernet said:
Dont help.
i started from the beginning again and uses this:
and when i try to get into the stock recovery, i see just a dead android-guy with a red alarm-sign
Click to expand...
Click to collapse
That is because those are NOT the right commands.
You should be using this (assuming you want to start fresh):
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot format userdata
fastboot reboot
Or this if you want to keep your data:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot reboot
Both of these methods will not reduce your reported storage space.

I had similar issue i have the 32 GB variant and before I flashed the update 5.1 I had 25.89 or and now I only have 23.03 gbs what gives

beachbum40 said:
I had similar issue i have the 32 GB variant and before I flashed the update 5.1 I had 25.89 or and now I only have 23.03 gbs what gives
Click to expand...
Click to collapse
Same thing happens to me. In fastboot the command "fastboot -w" will fix it. You lose all your data though since it formats everything.

Evo_Shift said:
Same thing happens to me. In fastboot the command "fastboot -w" will fix it. You lose all your data though since it formats everything.
Click to expand...
Click to collapse
How do u do that fastboot w- thing I had to fastboot each IMG one by one when updating.

I dont believe that fastboot -w will work in this instance......pretty sure you need to format the partition.
I have had this happen twice now after flashing the factory images....huge PITA if you dont catch it immediately before loading up your apps and data.

beachbum40 said:
How do u do that fastboot w- thing I had to fastboot each IMG one by one when updating.
Click to expand...
Click to collapse
Yeah, I meant I flashed each image one by one to update to 5.1. Then the first time I booted up I noticed I had 23.03GB available. Then I went back into fastboot and did fastboot -w, it formats everything or whatever, and the next time I boot up it acts like you just did a factory reset but the memory lists 25.98 now. I think fastboot -w must do more than simply reformat the space listed. It spits out a ton of information after you do it like it is creating the proper amount of space rather than simply reformatting what is being displayed.

Evo_Shift said:
Yeah, I meant I flashed each image one by one to update to 5.1. Then the first time I booted up I noticed I had 23.03GB available. Then I went back into fastboot and did fastboot -w, it formats everything or whatever, and the next time I boot up it acts like you just did a factory reset but the memory lists 25.98 now. I think fastboot -w must do more than simply reformat the space listed. It spits out a ton of information after you do it like it is creating the proper amount of space rather than simply reformatting what is being displayed.
Click to expand...
Click to collapse
Ohh OK gotcha yeah I'll give that a shot and see what happens. Thank

Evo_Shift said:
Yeah, I meant I flashed each image one by one to update to 5.1. Then the first time I booted up I noticed I had 23.03GB available. Then I went back into fastboot and did fastboot -w, it formats everything or whatever, and the next time I boot up it acts like you just did a factory reset but the memory lists 25.98 now. I think fastboot -w must do more than simply reformat the space listed. It spits out a ton of information after you do it like it is creating the proper amount of space rather than simply reformatting what is being displayed.
Click to expand...
Click to collapse
Yeah I did what you said and all is back to normal. I have 25.98 gbs like I'm supposed to now.! ? Thanks for your help

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?

Stock restore

I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes

hollywood_jack said:
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
Click to expand...
Click to collapse
Or do it manualy with adb, look here as a guide http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504 method 2. Toolkits will always bite you in the ass at some point in the future

gee2012 said:
Toolkits will always bite you in the ass at some point in the future
Click to expand...
Click to collapse
Sorry but I not have understood this

hollywood_jack said:
Sorry but I not have understood this
Click to expand...
Click to collapse
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong

gee2012 said:
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
Click to expand...
Click to collapse
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?

hollywood_jack said:
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
Click to expand...
Click to collapse
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.

gee2012 said:
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
Click to expand...
Click to collapse
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel

hollywood_jack said:
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
Click to expand...
Click to collapse
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img

gee2012 said:
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
Click to expand...
Click to collapse
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?

hollywood_jack said:
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
Click to expand...
Click to collapse
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.

gee2012 said:
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
Click to expand...
Click to collapse
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop with the following flash (always method 2)?

hollywood_jack said:
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop?
Click to expand...
Click to collapse
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.

gee2012 said:
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
Click to expand...
Click to collapse
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?

hollywood_jack said:
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
Click to expand...
Click to collapse
Extract the rom and flash the bootloader first (fastboot flash bootloader namebootloader.img) and fastboot reboot-bootloader, then the radio and also reboot and then the rest in one go. Good luck an if you have doubts/problems post it here. Plenty of helpfull members around

But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk

hollywood_jack said:
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
Click to expand...
Click to collapse
Once you unlock the BL it stays unlocked unless you lock it manualy. Even if you flash a new bootloader.

Thanks my friend...thanks alot
with my Nexus 6

hollywood_jack said:
Thanks my friend...thanks alot
with my Nexus 6
Click to expand...
Click to collapse
Good luck, its only a bit stressfull the first time

gee2012 said:
Good luck, its only a bit stressfull the first time
Click to expand...
Click to collapse
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?

hollywood_jack said:
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
Click to expand...
Click to collapse
- You don`t have to erase boot and recovery
- Yes you can flash a non encryped kernel but you`ll have to factory reset after you flashed and the N6 is booting or your storage will say its 32GB.
- Rooting is easiest by placing the latest 2.8.7.1 TWRP recovery in the sdk-platform-tools folder, reboot in bootloadermode and fastboot boot namerecovery.img and boot up and flash the latest superSU.zip (Beta 2.49 afaik) or use a toolkit if want to.

How to root N6F26Q 7.1.1?

Hey, how do I root the Nexus 6 on 7.1.1 and the Build Number is N6F26Q? Thanks.

I use Magisk

But how do I root? A link to a tutorial would be helpful.

php111 said:
But how do I root? A link to a tutorial would be helpful.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Go here and you should be fine? Is this your 1st time rooting the nexus ?

php111 said:
But how do I root? A link to a tutorial would be helpful.
Click to expand...
Click to collapse
Step-1
https://www.youtube.com/watch?v=29U7X4NgoUY
Look up Shamu Latest TWRP
Step-2
https://www.youtube.com/watch?v=84D2-UnUIA4
Look for the latest stable SuperSU
Done

Or this way which is longer.
Make sure the phone is in fastboot mode.
Than:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
First, delete the recovery file or replace with the TWRP recovery (just rename the TWRP recovery to recovery.img and yes, to replace when copy/paste, that should do the job).
Now reboot again and boot into recovery and than wipe cache and dalvik and flash SuperSU and wipe cache and dalvik again.
Someone above asked me is this my first root? No, my first root was on a Galaxy S3 which I do not have the S3 anymore. What made me to lose the root on the S3 was I took an OTA update and it KNOX the device so I could not root.
Yes, this is my first root on Nexus. No, it is not my first root in regards to Android

Wugs toolkit does it fine in one click
Sent from my EVA-L09 using Tapatalk

I just flashed supersu 2.78 in twrp, that worked

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.