[Moto G Q&A, Help & Troubleshooting] jamiethomaswhite:
Issues with fastboot commands

Okay, firstly I have just got to stop and thank you for your speedy, well written and understandable posts. Thank you, thank you, thank you. A million times over :)

So for everyone's reference I had my phone plugged in via USB to my PC and that's how it went flat. So as forgotter said I plugged it into a wall socket. Here's where it gets irritating again. I left it on charge all night and it still wouldn't work. I realised I was using my USB to wall plug adapted charger that came with my Moto G. So instead I plugged it into my gf's Samsung AC plug on a hunch, lo and behold only this charger worked. Just so you guys know.

So I charged it up and I've taken a stab at it again this morning.

I followed your instructions to try everything in Post #7 on Page 1 but got stuck at "fastboot push C:/adb\system /system/".

First, I thought it was because I was using a different directory and had amended the "C:/adb\system" part incorrectly. So I moved it all to C:/adb anyway for clarities sake. Still it wouldn't work and instead posts all available commands back to me as I used the help command (see bottom of post for copy of raw output).

On another hunch that trying to reflash stock firmware (as almost all the other guides have said) screwed something up, I found out how to flash a rom from fastboot, followed your steps in Post #5 to get CWM back in its original state and then flashed the CM11 M4 rom through fastboot. That all worked fine and I can now flick between fast boot mode and recovery (which I couldn't get to last time).

The only issue is I'm still getting the same response from the "fastboot push C:/adb\system /system/" command and adb commands themselves i.e. "adb reboot-bootloader" etc don't work. I'm running this on a high end Windows 8 PC through admin CMD from a portable ADB installation if any of that helps.

I'm lost without my Moto G D: I got so used to my Samsung Galaxy S i9000 being an absolute breeze to unlock and rom >_<

P.S. I forgot to mention but no matter which recovery I use they're complaining about SU needing to be reinstalled/reapplied. Is this normal? Am I still rooted?

Here's the raw output from CMD for "fastboot push C:/adb\system /system/" :

C:\adb>fastboot push C:/adb\system /system/

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format <partition> format a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache (and format

if supported by partition type)

-u do not first erase partition before

formatting

-s <specific device> specify device serial number

or path to device port

-l with "devices", lists device paths

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address.

default: 0x10000000

-n <page size> specify the nand page size. default:

2048

-S <size>[K|M|G] automatically sparse files greater th

an

size. 0 to disable

C:\adb>