yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] TechBurner:
Get a list of the mount points of your phone and than just format system,boot,data and cache partition after using the command "fastboot OEM format". Than flash everything through fastboot again or flash a recovery than flash using that recovery.

Just try flashing a ROM through recovery because you can specify the mount points in the script.
[Moto G Q&A, Help & Troubleshooting] TechBurner:
Can you open recovery? are you able to flash recovery?

I restored my stock firmware without any problems on my moto g.

I had a cmw backup and there was no problem in restoring.

The problem you have specified occurs when you flash a rom or something in the wrong partition(other mount point)

You must have downloaded the wrong file i suppose but i am sure it can be fixed , you just need to contact someone who knows about this more
[Moto G Q&A, Help & Troubleshooting] hansdepaula:
i not can enter in recovery..

fastboot dnt write nothing..

nothing change on my phone..

my recovery stay black and my custom logo stay,

and i try flash more that 15 versions of stock's firmware

and all versions of recoverys

nothing change..

my device say on layout of bootloader

"AP Fastboot Flash Mode (s)

41.11 (sha=7d46a5a, 20014-05-25 09:28:38)

CPU: MSM8226 CS

eMMc: 16gb Samdisk RV=06 PV=07 TY=17

DRAM: 1024MB Samsung S4 SDRAM DIE=4GB

Battery OK

Device is UNLOCKED. Status Code: 3

Transfer Mode: USB Connected"
[Moto G Q&A, Help & Troubleshooting] hansdepaula:
i try use one blankscript but 'downgrade' mensage stay show on my device and log:

if you want to broke your bootloader push one key
Pressione qualquer tecla para continuar. . .
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.016s]
writing 'fsg'...
OKAY [ 3.141s]
finished. total time: 3.172s
target max-sparse-size: 256MB
sending 'rpm' (200 KB)...
OKAY [ 0.016s]
writing 'rpm'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.312s
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.047s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.078s
target max-sparse-size: 256MB
sending 'sdi' (32 KB)...
OKAY [ 0.047s]
writing 'sdi'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
target max-sparse-size: 256MB
sending 'tz' (400 KB)...
OKAY [ 0.078s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.406s
Bootloader broken YAY!
Pressione qualquer tecla para continuar. . .

i cant try another options like 'qualcomm_boot_tool' because it dont show my device:

from Boss442 to XDA
< waiting for device >

fastboot dont write nothing on my phone..

everything stay like before flash,

cutombootlogo and breakrecovery dont change..

getvar show a CMkenel.. (first post)

:/

if try use another version of firmware it say 'downgrade failed'..

on 4.4.3 firmware everithing say OK

but dont change nothing..

what i can do?

some one can help, give me a idea or option?
[Moto G Q&A, Help & Troubleshooting] TechBurner:
you would probably have to wait for some time untill someone figures out a fix, many people are having this problem so its very likely to get fixed . Stay tuned and dont worry
[Moto G Q&A, Help & Troubleshooting] hansdepaula:
thanks for attention Shlok..

you really give me a hope..

see people and thread's with 'same' problem..

read suposed fixes also, but then consistes on enter in recovery mode.

or flash gpi.bin / recovery.img

and can not do it..

think my fastboot as corrupted..

and then cant write nothing.. :/

more logs, maybe help:

C:\Users\Hans\Desktop\443>mfastboot erase system
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.018s]
finished. total time: 0.019s

C:\Users\Hans\Desktop\443>mfastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.049s]
finished. total time: 0.051s

C:\Users\Hans\Desktop\443>mfastboot erase boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.038s]
finished. total time: 0.039s

C:\Users\Hans\Desktop\443>mfastboot erase logo
erasing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.031s

C:\Users\Hans\Desktop\443>mfastboot erase modem
erasing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.013s

C:\Users\Hans\Desktop\443>

yeah

i have unlocked phone..

my cid say '0x0000C', on getvar all (first post)
[Moto G Q&A, Help & Troubleshooting] hansdepaula:
my hopes die..

i really hope if i as the 4.4.4 firmware i will can revive my device..

but at some minutes i try flash parts of 4.4.4 ota (Blur_Version.210.12.32.falcon_umtsds.Brasil.en.BR) version for my device..

in zip i take the files:

gpt.bin
fsg.mbn
rpm.mbn
sbl1.mbn
sbl1_8226.mbn
sdi.mbn
tz.mbn

files..

and try, with sucess flash then using a bat script like:

mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
mfastboot flash rpm rpm.mbn
mfastboot flash sdi sdi.mbn
mfastboot flash sbl1 sbl1_8226.mbn
mfastboot flash tz tz.mbn

i recive ok for all (no one 'downgrade' msg)

but nothing change again..

i also try flash the logo.bin and recovery.img for 4.4.3 before this comands..

try also custonsrecoverys.img and logo.bin

try another variations of this, and other fastboot flash's..

and nothing change again..

i really think my fastboot as corrupted, i try use [MENTION=1946177]Boos442[/MENTION] tools, http://xdaforums.com/showthread.php?p=53921401.

but i dont have a qualcomm drivers for my device (VID_05C6&PID_9025)

:/

i'll stay waiting for something..

someone have a idea about what i can try do..?
[Moto G Q&A, Help & Troubleshooting] hansdepaula:
today, before waste my day sheaching..

i have see me device on ADB :)

but, it say "unathorized", and my device stay on bootlogoloop

see:

C:\Users\Hans\Desktop\443>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\Users\Hans\Desktop\443>adb devices
List of devices attached
0425016712 unauthorized

C:\Users\Hans\Desktop\443>adb shell
error: device unauthorized. Please check the confirmation dialog on your device.

C:\Users\Hans\Desktop\443>adb kill-server

C:\Users\Hans\Desktop\443>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\Users\Hans\Desktop\443>adb devices
List of devices attached
0425016712 unauthorized

C:\Users\Hans\Desktop\443>

"error: device unauthorized. Please check the confirmation dialog on your device."

i cant see dialog, my device stay in bootloop.. :/

have a some comand i can use in unauthorized mode?
[Moto G Q&A, Help & Troubleshooting] SbM_:
What does "fastboot devices" say?
[Moto G Q&A, Help & Troubleshooting] hansdepaula:
fastboot show me device like charm..

C:\androidsdk\sdk\platform-tools>fastboot devices
0425016712 fastboot

see all logs, and getvar all on first post.

all fastboot flash report OK..

but nothing change on phone, recovery say OK on flash but before restart o direct click on recovery mode, then dont work..

same on logo.bin, say OK on fastboot but on restart i stay see a custombootlogo i use before bricked..

i try format some partition but not work..

i think my sd card/eMMC or/and partitions was break, like 'bad disk'

fastboot say "RAW" dont format..

please, waste a time for read my first and other posts, i put some important logs, and all posts have moreover ..

maybe you can help me, or give me a good idea. :)
[Moto G Q&A, Help & Troubleshooting] okaryn:
Hello,

I've you resolved your problem ? I have exactly the same problem, fastboot say ok for all command, but do nothing in reality
[Moto G Q&A, Help & Troubleshooting] lost101:
4.3 kernel is not compatible with latest Bootloader. If you update to 4.4.4 via OTA update or firmware image - you cannot boot 4.3 ever again.
[Moto G Q&A, Help & Troubleshooting] okaryn:
Yes, but we can't flash anything.

For me, I have a 4.4.4 GPE, only access to Fastboot. Fastboot flash say OK to all commands but do nothing (no recovery, no new logo... nothing).

the tools for refresh or corrupt then bootloader doesn't work to...
[Moto G Q&A, Help & Troubleshooting] lost101:
Are you using fastboot or mfastboot? What commands have you used? Do the 'flash system system.img' commands actually match the filenames of the firmware you have downloaded?
[Moto G Q&A, Help & Troubleshooting] lost101:
Whenever you get a 'max download size' message - flashing was not successful.

What model Moto G do you have?
[Moto G Q&A, Help & Troubleshooting] okaryn:
XT1032 with french operator SFR, convert to GPE 4.4.4 with fastboot. The GPE was flash 2 times with success (always after a tentative to flash a custom rom). The problem appear after flashing Cyanogen with TWRP (20 minutes to boot with the CM Circle, battery off, and after the can't do anything else).

It's not my phone, it's for a friend who sent me his phone.
[Moto G Q&A, Help & Troubleshooting] lost101:
Having looked over this thread, two things need to be said:

(1) Fastboot is not user-friendly because it is meant for use by engineers. You will not be given helpful error messages. You should not randomly try fastboot commands.

(2) The worst thing you can do to your phone is run the command: fastboot erase all

Which is exactly what the OP did. Certain partitions contain persistent data, intended to survive even flashing a firmware image and erasing of the userdata partition. Once these partitions have been erased -

they cannot be restored

. This is why people loose their IMEI when they run the above command.

The only commands you need to concern yourself with are those mentioned in the tutorial. fastboot format at your peril.

Having said that, even those that have run 'erase all' can still use their phone as a tablet. I suspect you are not running the correct commands.

Try all three versions of fastboot in this zip: https://www.androidfilehost.com/?fid=23578570567719065

Use the following commands: (in this order)

mfastboot.exe flash partition gpt.bin

mfastboot.exe flash motoboot motoboot.img

mfastboot.exe flash logo logo.bin

mfastboot.exe flash boot boot.img

mfastboot.exe flash recovery recovery.img

mfastboot.exe flash system system.img_sparsechunk.0

mfastboot.exe flash system system.img_sparsechunk.1

mfastboot.exe flash system system.img_sparsechunk.2

mfastboot.exe flash modem NON-HLOS.bin

mfastboot.exe erase modemst1

mfastboot.exe erase modemst2

mfastboot.exe flash fsg fsg.mbn

mfastboot.exe erase cache

mfastboot.exe erase userdata​

NB. Are system.img_sparsechunk.0 / .1 / .2 the actual file-names? Some firmware images include a forth sparsechunk.
[Moto G Q&A, Help & Troubleshooting] lost101:
They are different file-sizes - likely different versions, which is why I include both. One version may work where the other does not.

I would try Retail France next: (converting back to non-GPe might be the solution)

http://xdaforums.com/showthread.php?p=54872143
[Moto G Q&A, Help & Troubleshooting] lost101:
Before you do anything else, are you absolutely sure this is a non-LTE Moto G?
[Moto G Q&A, Help & Troubleshooting] okaryn:
Yes , it was bought before the Moto 4G was released. If I remove the back, I can seen a sticker on the battery with :

model : XT1032

FCC ID : IHDT56PF1

Type : MODEB

It's a 16GB model
[Moto G Q&A, Help & Troubleshooting] lost101:
Someone else who was getting the ''WARNING: System partition size" message, was able to boot into Android despite it.

http://xdaforums.com/moto-g/help/brick-sytem-partition-t2871452​

When you flash the gpt.bin (partition table) the phone's partitions should be set to the correct size. Could you provide the output for the following ADB commands:

adb shell

df​
[Moto G Q&A, Help & Troubleshooting] okaryn:
I saw this thread before, but the gpt.bin don't resolve the problem for me :(

D:\moto>adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

ADB work under fastboot ? I'm trying with my functionnal moto-g and it's the same thing.
[Moto G Q&A, Help & Troubleshooting] lost101:
I forgot you can't boot into Android. You can boot into a custom recovery using the the fastboot command:

mfastboot boot recovery_name.img​

Both Philz Touch and TWRP (Mount > Enable MTP) gave me access to ADB - at least in Ubuntu.

BTW, "cat /proc/partitions" is a better command to use.
[Moto G Q&A, Help & Troubleshooting] okaryn:
This is doesn't work since 4.4 :( With a good phone, the command is OK but after reboot the screen show strange colors.

I still retried and I noticed a strange thing : actually, I have the Warning unlock logo. With the command to reboot on recovery, I see the Motorola logo but after some second the phone reboot with the warning unlock logo (I don't see the strange colors). On the reboot, I don't have the vibration (with my phone I have it)

I try with the 2 recoveries, the GPE recovery, the stock recovery and the CM recovery, all with fastboot and mfastboot :(
[Moto G Q&A, Help & Troubleshooting] lost101:
I tested the command before posting, on a 4.4.4 phone. It works fine.
[Moto G Q&A, Help & Troubleshooting] okaryn:
Strange, don't work on my 2 Moto G. What version of bootloader do you have ? I have 41.05 on my working phone and 41.13 on the break phone.
[Moto G Q&A, Help & Troubleshooting] lost101:
bootloader version: 41.13
[Moto G Q&A, Help & Troubleshooting] okaryn:
Strange, I can't reboot to recovery with my working phone too :(

I can reboot only with the stock KOT49H GPE recovery but without any screen... The recovery is not load but phone don't reboot immediatly and I got a vibration.

I'm searching something like the Nexus 4 "fastboot -c “lge.kcal=0|0|0|x” boot recovery.img"...

[Edit]

I've tried all this Phil'z version :

recovery_6.13.3.img

recovery_6.25.0.img

recovery_6.41.6.img

recovery_6.50.6.img

recovery_6.54.9.img

recovery_6.55.0.img

recovery_6.57.9.img

and...

openrecovery-twrp-2.6.3.0-falcon_umts.img

openrecovery-twrp-2.7.0.0-xt1032.img

openrecovery-twrp-2.7.1.0-xt1032.img

openrecovery-twrp-2.7.1.1-xt1032.img

openrecovery-twrp-2.8.0.1-xt1032.img
[Moto G Q&A, Help & Troubleshooting] lost101:
I've attached the bootloader (motoboot.img) and partition table (gpt.bin) from the Retail EU 4.4.4 firmware image. See if that makes any difference in being able to boot into Recovery from .img.
[Moto G Q&A, Help & Troubleshooting] okaryn:
That's change nothing, no error but can't boot to recovery :crying: I see the Motorola logo, but after that the phone reboot with the unlock warning logo. It's strange the boot logo it's not the same between normal boot and the "boot recovery.img" command.

I try all this firmwares (full, or just gpt/motoboot+recovery) :

4.4.4_KTU84P GPE

4.4.4_KXB21.14 AS

4.4.4_KXB21.14 BR

4.4.4_KXB21.14 EU

4.4.4_KXB21.14 FR

4.4.4_KXB21.14 FR Vodafone

4.4.4_KXB21.14 GB Vodafone

4.4.4_KXB21.14 US Verizon
[Moto G Q&A, Help & Troubleshooting] lost101:
As I've already said, even if 'fastboot format all' has been done on the phone - you still should be able to boot. I'm starting to think disk corruption or hardware fault.

The Android L Motorola firmware image will include a new Bootloader - so there might still be a chance to fix it without sending the phone to Mororola.
[Moto G Q&A, Help & Troubleshooting] okaryn:
My friend don't remember to have use the format all command, only the .cmd with the firmware...

I also think it's a hardware problem, I'm not the only one who had this problem, I found lot of thread with this problem after a firmware flash, no one with a solution...

hope the L firmware can resolve it.

Thanks for time you spend with me :)
[Moto G Q&A, Help & Troubleshooting] RajuMon:
LOST IMEI

I run fastboot erase all &

I lost my imei , my all imei is 0 any solution fro this ?
[Moto G Q&A, Help & Troubleshooting] os_man:
http://www.androidbrick.com/qualcomm-snapdragon-imei-tamiri-ders-4-qualcomm-snapdragon-imei-repair/
[Moto G Q&A, Help & Troubleshooting] cxxxx:
Hello,

was a solution found for this in the meantime?

I am experiencing nearly the same situation on my 2nd gen Moto G, I cannot flash anything using fastboot and cannot lock again.

C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.

Differences: My device was never rooted and still locked before the problem occured, what happened after the battery was totally empty. My IMEI is still valid and I did not run "fastboot erase all".
[Moto G Q&A, Help & Troubleshooting] agucollado:
Same issue with my XT1063

Anybody get a fix for this?, I'm running in the same issue with my XT1063 RETUGLB version

HELP!!!
[Moto G Q&A, Help & Troubleshooting] electrictimes:
Any updates on this? I'm in the exact same predicament. The only error I get trying to flash everything again is the flash partition gpt.bin. Everything else seems to flash fine, but I don't if mfastboot is actually doing anything. I also get the "File system type raw not supported." when trying to wipe. I have tried multiple roms/recoveries, can't get this thing to start to save my life.

In my case, the problems started with a failed encryption effort. Last time I checked the encryption progress it said 30 min remaining then it remained on the GPE bootlogo (with flying Google colored circles) and was stuck on it for 8 hours. Nothing happened. I tried rebooting and only got to the same boot animation over and over again. I guess the filesystem is totally hosed...
[Moto G Q&A, Help & Troubleshooting] andrefv:
Same problem here. But my device was rooted, and this was not a problem... Dont know what to do anymore....
[Moto G Q&A, Help & Troubleshooting] agucollado:
Request to the Gods

I implore the gods of this forum to enlighten us.

Possible solutions that come to my mind are:

1. Format partitions and load their corresponding images (don't know how)

2. Make note that the cell is completely bricked and it doesn't boot and perform some magic procedure to resurrect him from the dead (Nor doesn't know how)

Help!!!!:crying::crying:
[Moto G Q&A, Help & Troubleshooting] Darksl1der:
What if we will try to write partition images with "dd"?

To push images from working device, for example or empty images.

Else - what if we will try to format partitions manualy, maybe force to change filesystem?

osman, the link you've provided - requires password.

http://www.androidbrick.com/qualcomm-snapdragon-imei-tamiri-ders-4-qualcomm-snapdragon-imei-repair/

Btw I have TWRP backups of PDS and everything else, but not sure I can use it without twrp.
[Moto G Q&A, Help & Troubleshooting] andrefv:
What is "dd"?

I've tried (almost) everything. Every change I've try to make via TWRP or Fastboot there's no effect. In TWRP when I try to format DATA, the device restarts.
[Moto G Q&A, Help & Troubleshooting] Darksl1der:
"dd" is adb command to work with partitions. kind of low level, since working not with files and folders, but partitions.

I have another idea. What if we will switch mounting point of sdcard to sdcard1.

I mean - to edit bootloader-startup-script stored inside boot.img file.

We can't flash it, due to an read-only issue. But at least we can run it. "Fastboot boot FileName.img".

Since bl is unlocked - it will accept modified bootloader file and will run our modified startup script.
[Moto G Q&A, Help & Troubleshooting] andrefv:
I dont know how to do it. You could write a step by step?
[Moto G Q&A, Help & Troubleshooting] Darksl1der:
Well, at first we need to find out how to disassemble boot.img file - I used imgRePacker for it.

There are lots of scripts, settings, etc.

Open sctipts with notepad and search for sd mounting point to edit.

Then we'll need to complete all the files back to boot.img (did not even tried to do that at this moment)
[Moto G Q&A, Help & Troubleshooting] Oliverrlh:
nobody have found a solution to this problem? I am facing the same issues (cant format any partitions due to raw format). We need help!. Tried flash another recovey, tried adb shell to flash rom, tried flash rom from fastboot commands, tried format data, tried wipes, tried fix partitios (from recovey) and ABSOLUTY NO CHANGES. I can boot to system but I get FORCE CLOSES to all apps, I can boot bootloader and recovey but raw partitions dont let me makes changes. I have a Moto G 2014 Xt1063 using Lollipop 5.0.2.
[Moto G Q&A, Help & Troubleshooting] WiCiO_MeDi:
hi, it appears i'm stuck with you guys :/

i have working /user /cache /system but /sdcard is offlimit and I'm stuck at bootlogo.

as mentioned before, fastboot doesn't help..

how this happened?

i flashed stock 5.0.2 through fastboot - everything works

i flashed twrp and cm12 - everything works except gps (forgot to get a fix)

so i repeated the process with fastboot stock - everything went to hell!

phone: xt1032 - my wife's phone...
[Moto G Q&A, Help & Troubleshooting] WiCiO_MeDi:
ok, i've managed to sort it out ;)

what i did:

1. on bootloader, command fastboot -w, wchich formats /data and /cache even if they are raw

2. flash twrp recovery: fastboot flash recovery twrp.img

3. enter recovery from fastboot and change filesystem of /system partition: Wipe->Repair of Change Filesystem, select /system and ext4

4. then go to fastboot again and flash only system (all sparsechunks) [probably you can skip this step]

5. enter recovery and flash CM (mine was 12.1) and gapps. the installer spills some errors but whatever, thank god it gets through!

6. reboot system

it should boot to CM!

give it a try ;)
[Moto G Q&A, Help & Troubleshooting] GKentaurus:
And it Works? It's a solution for this problem? or the pone keep bricked? :confused::confused:

I've the same problem with a phone from a friend... and I flash everything.... but the pone has no changes.... Please... Help me :crying::eek:
[Moto G Q&A, Help & Troubleshooting] WiCiO_MeDi:
yep, it helped, did you try this method on "your" moto?
[Moto G Q&A, Help & Troubleshooting] patil.ketan:
I have a same problem with moto e, by booting into recovery, it is stuck at teamwin logo ANY IDEAS?
[Moto G Q&A, Help & Troubleshooting] lost101:
Use the fastboot command: fastboot erase userdata