Database Info

bricked my moto g while downgrading lollipop to kitkat / corrupted data partition?

i was using moto g xt1033 asian retail, i changed it to 4.4.4 brazilian retail and then updated to lollipop 5.0 brazilian following a thread on xda. all worked well. i came across a thread which had an ota update for 5.0 to 5.0.1 it was a 10mb file. i put it in pendrive and flashed it via twrp. since then the phone never went past the warning bootloader unlocked page.
when i power it off, it automatically reopens but gets stuck on the warning bootloader unlocked page.
usb debugging is enabled, i can access bootloader, can use fastboot commands, it recognizes adb commands and can flash recoveries on it.
the only thing that doesnt work is that it doesnt get past the warning page.
so i went to twrp, cleared all- dalvick cache, data, internal storage, cache and system.
it gives wipe complete, FAILED
see image 1.
so i flashed the original 4.4.4 rom and it again gives the same errors and now i get waves on twrp, but still doesnt go past the warning bootloader unlocked screen.
updating partition details-
E : unable to mount '/data'
E : unable to mount '/cache'
E : unable to mount internal storage
see image 2.
basically, every time i try to wipe it or install a new rom it gives problems about partition.
so i wiped it again and installed cm11 snapshot on it.
again the same unmounting problems, but now it goes past the warning bootloader screen but always stays on the arrow rotating about the cm logo.
i searched a lot online , and i think the problem is corrupted partition.
so i followed this thread http://forum.xda-developers.com/showthread.php?t=2683787 .
first he shows a way by using terminal command from trwp . when i goto command terminal, it shows browse to starting folder i chose any folder like sdcard and enter this code
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
. it gives this
see image 3 and image 4.
i try the next alternative that is using adb and this code
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
and it gives this
see image 5.
please help me to clear this partiton problem. thank you in advance :')

I suggest you be very careful about what you do next.
It sounds like you should fastboot flash the Lollipop gpt.bin (partition table) - I believe the KitKat gpt.bin will cause you serious problems.

lost101 said:
I suggest you be very careful about what you do next.
It sounds like you should fastboot flash the Lollipop gpt.bin (partition table) - I believe the KitKat gpt.bin will cause you serious problems.
Click to expand...
Click to collapse
hey thank you for the quick reply
but could you guide me where to get the appropriate lollipop rom
and sorry for this noob question, but will installing lollipop gpt fix up the partition?

SemiNoob314 said:
hey thank you for the quick reply
but could you guide me where to get the appropriate lollipop rom
and sorry for this noob question, but will installing lollipop gpt fix up the partition?
Click to expand...
Click to collapse
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.

lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
Thank you!
Will download and proceed as you said, though the download may take some time.
Will reply with the result.

lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
Man you are a freaking lifesaver!!
Cannot thank you enough!! everything is working now!!
Thank you again!!

how to restore to lollipop or kitkat
i have bricked my moto g xt1033 asia firmware in a process to downgrade it from lollipop 5.0.2 to kitkat 4.4.4 i was badly struck and as the bootloader is unlocked it only shows the "WARNING bootloader unlocked " can anyone help me with what to do now to make my phone work in lollipop or kitkat any version

i want to say
---------- Post added at 08:36 AM ---------- Previous post was at 08:29 AM ----------
lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
https://labs-dl.xda-cdn.com/apks/01e697
---------- Post added at 08:43 AM ---------- Previous post was at 08:36 AM ----------
lost101 said:
I've attached the gpt.bin included with Lollipop 5.0.2. I am not responsible if this goes wrong, but this seems to me what you should do.
The command is: fastboot flash partition gpt.bin
Don't use any other commands for now.
Afterwards, try flashing the ROM zips you have on the phone, or this: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Flashing that gpt.bin may wipe internal storage.
Click to expand...
Click to collapse
last week i flashed motorola stock rom kitkat 4.4 on falcon using TWRP it flashed sucessfully...but after flashing i m not able to install any other custom rom like mokee,lineage,resurrection...it always stucks at boot... before flashing stock rom i flashed many rom but since the day flashing stock rom not able to flash any other looks like ROM changed the internal storage type as it says sometimes in twrp "unable to mount storage"

[Q] Stuck on Bootloader Locked Screen

Hey guys
First of all: I think, I ****ed up.
So I was on a custom 5.0.2 Rom and it was really buggy (forceclose, lowmemory, etc.) and so I decided,
that it would be a good idea to go back to stock and flash Slimrom. As far, as I remember, I did the following:
1. Go into my custom recovery and delete everything (I know, I'm an idiot :crying: )
2. Go into fastboot and flash 4.4.4 via a script on my PC
3. Get problems, which I somehow resolve (pls don't ask me, how. I was pretty drunk last night.)
4. 4.4.4 is up and running. I download the stock 5.0.2 OTA files form XDA and try to flash them with TWM.
5. Everything is super buggy under 5.0.2, so I decide to flash back 4.4.4 and use the stock recovery.
6. 5.0.2 runs just fine and I begin to prepare for the custom Slimrom.
7. Install custom recovery, download Slimrom and GApps.
8. Flash Slimrom and get some weird error, that /system and /date can't be mounted. Everything ****ed up from there on...
9. Try to flash the stock 4.4.4 from before (using the script). Doesn't work, gets stuck on bootloader unlocked messege.
10. Try random **** (literally everything, I can find on the web.)
11. Write this post.
Some information, you could need:
XT1032
Fastboot version: 41.18
Unlocked (Status Code: 3)
Boots into recovery
Recovery is TWM 2.8.6.0
Things, I've tried: Flash the stock 4.4.4 system and then flash a custom rom, using TWM Didn't work
Reflash the stock "Kernel Module", found under /showthread.php?t=2649763 Didn't work
Flash an alternate "bootloader unlocked" Screen Didn't work
Please help me, guys :fingers-crossed:

Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.

audit13 said:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
Click to expand...
Click to collapse
First of all, thank you for your quick response!
I was able to flash everything without any errors, but unfortunately, it is still stuck on the Warning screen.

Did you erase cache and userdata in fastboot?

audit13 said:
Did you erase cache and userdata in fastboot?
Click to expand...
Click to collapse
Yes, but it did not help
Edit: it gives me an error, when flashing gpt.bin.
it says:
(bootloader) Preflash validation failed
FAILED (remote failure)

So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?

audit13 said:
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
Click to expand...
Click to collapse
When trying to flash the motoboot.img, it says "permission denied" and when trying to flash the gpt.bin, it says "(bootloader) Preflash validation failed FAILED (remote failure)".
The 5.0.2 ROM was the OTA update, which in my case, is the normal motorola one. I did convert my device to a GPE, when Lollipop for the moto G GPE became availible (arround december),
but went back to the normal ROM to get the 5.0.2 OTA.
Thank you for your help :laugh:
Ok, I have used this: http://forum.xda-developers.com/moto-g/development/rom-4-4-4-stock-eu-1-click-easy-flash-t2879757 and i'm back in Stock 4.4.4. I have got no idea, how that worked but it's done

That's great that it worked.
If you want to get 5.02 OTA update, be sure to update Motorola Update Services app in the Play store before checking for updates.

I give up on life (I tried everything to fix the god forsaken phone and loosing hope)

This is a tangent to the issue I had Situated HERE. I am seriously giving up on hope and want help for the love of god. Semester is approaching and I need a functioning mobile
After "fixing" my isssue and being on Lolipop 5.0.2, I realised that my SU binary wasn't present, So I reboot into recovery to realise that CWM isn't present anymore.
Not a big issue, I plug it in and flash TWRP onto it using fasboot commands.
Now i go into recovery and Install Superuser.zip trough TWRP. Then I decide to make a backup of everything. Afterwards I rebooted
The boot logo (The logo in which it normally mentions that Bootloader is unlocked and blablabla) Apears. But then it closes. Apears again but then closes once more. It keep doing than until I boot it into bootloader and close it once arrived there.
If I try to get into TWRP again it closes and continue the cycle.
So I flashed in CWM recovery with the intention to Flash the Stock lolipop ZIP that I done before (which fixed it).
When I boot CWM however, I am presented with a bunch of command lines at the bottom saying
"E: can't mount cache/logs"
and other lines (If you want the exact command lines say so and I will go get them). I didn't flinched to it (sometimes weird **** happens like that and I got used to it) so I go into the install from sdcard. I get this amazing message:
E: cannot mount sdcard
And all gui is not even present. I close the phone and start panicking
################################################################
In other words I need help. I will be checking this thread all the time looking for any help. I am giving up. faced such a problem in my life. I am scared that I bricked the phone for good.
Here is all I know about said phone:
KITKAT MOTO G 4.4.4 from canada (obtained from WIND mobile) most likely XT1034 (Its a mono sim)
The bootloader is 41.18
I used TWRP 2.8.6.2 for xt1032 (This is probably why everything exploded. I didn't realised it was for xt1032)
And I used CWM touch 6.4.0.7 falcon
MORE INFO WILL BE COMING, But I am extremely stressed right now to the idea that I might killed it.
#######################################################################################
#######################################################################################
Here are the CWM error messages
ClockworkMod Recovery v6.0.4.7
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_Install
- Install ZIP
- Choose zip from /sdcard
E: can't mount /sdcard
-Choose zip from /sdcard
##CWM gui closes## only the command lines are showing.

################
Update 1. I calmed down. I searched the error message and found out that it could either be an issue with CWM being currupted. I will reflash it and bring details. If it doesn't work I will format cache (Wiping the cache seems to not work)
Formatting the cache seems to fix all the cache error messages. But the mounting of /sdcard still present an obstacle
################

Why not flash stock firmware?
motofirmware.center
Sent from my XT1031

#######################
Update 2
I did some research and found out that my sdcard might be on logical and not primary and a way to fix it is to use mini partition tool on it. I am hesitant to do this so I will search for other possible issues
############################################

ATTACK said:
Why not flash stock firmware?
motofirmware.center
Sent from my XT1031
Click to expand...
Click to collapse
Because I can't find it.
try to find a 4.4.4, xt1034 canada stock firmware, Not easy. I've look for around 3 hours without success.
I however found a flashable zip for it, so I need to make recovery work, Because to my knowledge you can't flash an entire zip from adb/fastboot
The site you provided doesn't contain the right firmware. I highly appreciate the help though.

####################################
update 3
I decided to try and sideload stock rom lolipop. Seems to be working. Will be updating the results.
Here are the result:
ON MOTO G
-Install zip from sideload
nothing unusual happens
ON ADB
- adb sideload "lolipop stock rom".zip
Loads.....
Sends.....
"*failed to write data 'protocolt fault <Coudn't read status: invalid argument'* "
BACK TO MOTO G
- cancel sideload
Restarting adbd....
status 0
finding update package.....
opening update package.....
E: Can't open /tmp/update.zip
(bad)
installation aborted.
Click to expand...
Click to collapse
So it doesn't work but I found that last bit interesting. I feel like things are clearing up even though no ones is helping me (except for ATTACK, thanks but I will need a lot more help than that ) So help is apreciated
######################################

What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034

Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031

k-kuchen said:
What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034
Click to expand...
Click to collapse
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
ATTACK said:
Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031
Click to expand...
Click to collapse
YES, Omg I didn't knew lost posted Firmwares. Prase the mighty lost god. The first one is exactly it.
I don't mind waiting 1 or 2 hours. as long as I got it nicely set up for september 1 I'm a-ok
If it boots properly I owe you sir.

thegamerchunk1 said:
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
Click to expand...
Click to collapse
The 4.4.4 is also in this thread
Edit: Hosted on AFH -> https://www.androidfilehost.com/?fid=24052804347795180

##############################
Update 4
I tried to restore stock firmware. Back to square 1.
Cache issues.... I fixed it
Can't mount /sdcard.... Can't fix it.
The logo is the only thing I see and whenever I try to close it by pressing the power button, it reboots into the logo screen.
The only way I can truly close it is by opening fastboot menu and closing it there.
WHY IS THIS HAPPENING IM LOOSING MY MIND
I beg someone, anyone, Help me...
######################################################################

##################################
Update 5 Final ****ing update ****
I wiped and formatted /sdcard with philz touch recovery.
It seems that I can mount the sdcard now but I can't flash any roms because it
"Failed to set up expected mounts for install"
I am seriously in the most depressed mood ever. I worked for 4 years in computer development and I never had this much trouble ever. I ****ing give up everything. If someone ever encounter this issue:
you are ****ed throw the moto g in the garbage its dead nada done.
If someone thinks the contrary tell me how I am supposed to fix this. I will check it in about 12 hours.

I will do anything that someone thinks is going to fix it.

So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031

kinda urgent
@lost101 can you help him brother. He is in dire need.....

@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.

ATTACK said:
So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031
Click to expand...
Click to collapse
I flashed it using fastboot. here are the commands I used
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.

lost101 said:
@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.
Click to expand...
Click to collapse
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.

thegamerchunk1 said:
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.
Click to expand...
Click to collapse
Make sure to include the command: fastboot erase userdata

thegamerchunk1 said:
I flashed it using fastboot. here are the commands I used
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.
Click to expand...
Click to collapse
Ok - after you retry flashing, please post those errors. May want to try using mfastboot instead of fastboot as well.
Also you could 'adb push ROM.zip' with a custom recovery, bypassing the sd card altogether, but I think you should get your device to boot first.
Sent from my XT1031

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Unable to flash stock rom on moto g turbo (XT1557).

I'm unable to flash stock rom on my moto g turbo xt1557, with the fastboot method,
the actual problem is when i try to flash gpt.bin in the command getting the error
preflash validation failed remote failure.
since i've flashed this rom earlier it was succesfull at that time then i have installed twrp to try lineage os.
as now i want to revert back to stock , im unable due to the following error.
i'm trying the latest version of the stock rom which is availables\ still getting the error.
Please help.:crying :crying::crying:
Thanks :good::good::good:

vishal4950 said:
I'm unable to flash stock rom on my moto g turbo xt1557, with the fastboot method,
the actual problem is when i try to flash gpt.bin in the command getting the error
preflash validation failed remote failure.
since i've flashed this rom earlier it was succesfull at that time then i have installed twrp to try lineage os.
as now i want to revert back to stock , im unable due to the following error.
i'm trying the latest version of the stock rom which is availables\ still getting the error.
Please help.:crying :crying::crying:
Thanks :good::good::good:
Click to expand...
Click to collapse
Just skip that and do all commands,

Ojas25.8 said:
Just skip that and do all commands,
Click to expand...
Click to collapse
Dude. You mean to skip the flashing of gpt.bin
I have tried that too. Skipping the gpt.bin makes firmware flashing successful.
But after that problem is that phone get stuck on boot logo. Waited untill 30mins still no response.

vishal4950 said:
Dude. You mean to skip the flashing of gpt.bin
I have tried that too. Skipping the gpt.bin makes firmware flashing successful.
But after that problem is that phone get stuck on boot logo. Waited untill 30mins still no response.
Click to expand...
Click to collapse
Did you factory reset in stock recovery first? It's essential...