• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE][Osprey] Fastboot Flashing Factory Firmware Images

Search This thread

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
Did factory data reset in stock recovery first before following fastboot flash procedure. Did my lads Vodafone UK branded phone to 5.1.1 EU Retail 3 days ago and its perfect.

Though this on which is Tesco Uk is not right. Done it again but it will not boot to recovery as just displays green android and No command so can't wipe in recovery now. Can't go back to 5.1.1 either as it fails on flashing boot probably due to MM partitioning is different. Still makes system hang if facebook is installed too.
Are you including the following command: fastboot erase userdata?
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
Yeah, following every step as per the flash by fastboot thread.
Please don't cross-post. The issue is either (a) phone is not being wiped, or (b) firmware image is not flashing. Provide a log of the fastboot flashing process - copy and paste command prompt. Take screenshots if necessary. You may need to try different flashing scenarios - different PC (or in Linux), different usb cable.
 

waj1234

Senior Member
Mar 5, 2010
502
54
Leeds
Please don't cross-post. The issue is either (a) phone is not being wiped, or (b) firmware image is not flashing. Provide a log of the fastboot flashing process - copy and paste command prompt. Take screenshots if necessary. You may need to try different flashing scenarios - different PC (or in Linux), different usb cable.

Not got another pc to try unfortunately. Is there no way of going back to 5.1.1? If not its off back in box and I will buy something else lol. Only got the 8g as I thought MM would play nice with sd card which it dont do any better than any android version before.

When flashing 6.0 every step says Okay so assume its working correct, done it twice with same outcome. It works ok and is working now but facebook apps make playstore hang as it just sits on installing. Doing a factory reset within android just hangs on Erasing and entering recovery mode just says no command under mr green android.

Flashing 5.1.1 retail uk on my sons vodafone uk handset on same laptop went perfect though not tried putting MM on his yet and doubt I will try now.
 

Kunu11

Member
Jan 17, 2016
11
0
fastboot boot recovery.img​


Such issues indicate you have not flashed the MM Firmware image correctly. Factory data reset in Stock Recovery before flashing.

@lost1010 I did that and get:
C:\MM>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
FAILED (remote failure)
finished. total time: 0.527s

Just some thoughts here...is E: the SD Card? Can it be that it is looking for the cache on my SD card and it is not finding it? Is there an image for the cache I can flash?
 

waj1234

Senior Member
Mar 5, 2010
502
54
Leeds
Just add too that I have this micro sd car - 32GB MicroSDHC Card, Lexar Professional 1000X, C10, UHS-II, U3, 150MB/s and any apps installed to it are un useable and it even states that its a slow card. But its a fat card and genuine so this MM update is far from a finished product. I did get facebook apps installed but it takes 5 mins plus before they install.
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
Just add too that I have this micro sd car - 32GB MicroSDHC Card, Lexar Professional 1000X, C10, UHS-II, U3, 150MB/s and any apps installed to it are un useable and it even states that its a slow card. But its a fat card and genuine so this MM update is far from a finished product. I did get facebook apps installed but it takes 5 mins plus before they install.
That SDCARD may be the source of all your sorrow.

Everyone: Do not report issues unless you have removed SDCARD, flashed firmware image and tested ROM fully. Installing apps to SDCARD is above and beyond what this tutorial is about.
 
  • Like
Reactions: kiekeboeboe

waj1234

Senior Member
Mar 5, 2010
502
54
Leeds
That SDCARD may be the source of all your sorrow.

Everyone: Do not report issues unless you have removed SDCARD, flashed firmware image and tested ROM fully. Installing apps to SDCARD is above and beyond what this tutorial is about.

The sd card was not inserted at any point during my issues listed. Just tried it now and moved a few apps to test. removed immediately and put it in my sons phone with 5.1.1 installed and tried same apps moved and its perfect.

Just hope there will be a way to go back to 5.1.1 as mine is not the same phone. Still takes an age to factory restore and still no command message in recovery mode. Tried again to fastboot 6.0, no errors at any stage but still same. I could not even sell it as it is at the moment.
 

jakeflake

New member
Feb 4, 2016
2
0
Hey,
Does anyone know how to do the stuff operating on a mac? I got Android Studio, but I am not sure if this works, Im pretty clueless. Thanks!
 

jakeflake

New member
Feb 4, 2016
2
0
I think you can use the files included here on Mac:


To test:
./adb devices
./fastboot devices​

So Its basically the same procedure, and i just add ./ in front of every command?
And a last question, I know it sounds stupid but how do I navigate to the path where the files are? It just shows me that its in mydrivesname>motog(thats the folder name). How do I write that in the terminal?
Thanks for the quick answer!
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
So Its basically the same procedure, and i just add ./ in front of every command?
And a last question, I know it sounds stupid but how do I navigate to the path where the files are? It just shows me that its in mydrivesname>motog(thats the folder name). How do I write that in the terminal?
Please use Google to answer such questions.
 

waj1234

Senior Member
Mar 5, 2010
502
54
Leeds
To anyone unable to access recovery options, these are the official instructions: (Scroll down the 'External Reset')

The following command may be required:
fastboot erase cache​

Thanks for posting that link. I wiped mine that way and installed 6.0 again as cant go back to 5.1.1 then wiped it again in recovery before first boot and its a different phone. Though both Facebook and facebook groups took a while to install compared to all the other apps byt did eventually. Maybe they need an update for MM, who knows. It is now running smooth though almost no space left. Shame sd cards are useless still but next time I will get a larger memory.:good:
 
  • Like
Reactions: lost101

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
Thanks for posting that link. I wiped mine that way and installed 6.0 again as cant go back to 5.1.1 then wiped it again in recovery before first boot and its a different phone. Though both Facebook and facebook groups took a while to install compared to all the other apps byt did eventually. Maybe they need an update for MM, who knows. It is now running smooth though almost no space left. Shame sd cards are useless still but next time I will get a larger memory.:good:
Glad to hear that resolved it.
 

willygoodboy

Senior Member
Dec 10, 2012
74
10
Lons le Saunier
Hello guys i followed this tuto with the "XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7" firmware and now the phone says start up failed, your device didnt start up successfully. Use the software repair assistant on your computer......

My phone is a XT1541, all the flash steps was okay.

What's wrong

Please help
 
Last edited:

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
Hello guys i followed this tuto with the "XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7" firmware and now the phone says start up failed, your device didnt start up successfully. Use the software repair assistant on your computer......

My phone is a XT1541, all the flash steps was okay.

What's wrong

Please help
Did you do a "Factory Data Reset" in Android Settings prior to flashing? See post above about how to do this in Stock Recovery:
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,335
Yes i did this before.

I forgot to say that The bootloader say "failed to validate system image"

Thanks
Check the names of the files in the firmware folder. Do not simply copy and paste commands from the tutorial. You need to flash all sparsechunks. Provide a log. Show me the contents of command prompt. Take screenshots if necessary.
 
  • Like
Reactions: kiekeboeboe

Top Liked Posts

  • There are no posts matching your filters.
  • 135
    Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.

    Based on existing tutorial by @t-bon3. This guide has been created as a hard-brick occurred using the old Moto G (1st Gen) tutorial. Please exercise extreme care with Fastboot, and only use the commands mentioned here. Experimenting with Fastboot commands can seriously damage your phone.


    How to Fastboot Flash Moto G (3rd Gen) Factory Firmware Images

    Required Files:
    Motorola Drivers: Download
    Latest Fastboot | ADB (Windows | Linux): Download (Windows 10 users may need this pack for Drivers to work.)
    Factory Firmware Images: [INDEX][Osprey] Moto G Factory Firmware Images

    WARNING: You must perform a 'Factory data reset' in Stock Recovery before flashing any Firmware Image - instructions here.


    Instructions:

    1) Extracting Fastboot and Firmware Images:
    Extract zip for chosen Firmware Image to a folder with a simple directory structure. For example: C:\motog_firmware\
    Extract the adb-fastboot-latest_win_linux.zip into this folder.​

    2) Reboot the phone into 'Bootloader mode' and preparing PC for flashing

    Windows:
    Entering Fastboot mode:
    ------------------------------------
    i) The 'hardware' way.

    a) Unplug the USB cable and power off the phone.
    b) Press and hold 'Volume down' then power on the phone.
    c) Connect USB cable to your computer.

    ii) The 'software' way.

    a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
    b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
    c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
    d) Open Command Prompt, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:

    Code:
    adb reboot-bootloader
    Linux:
    Entering Fastboot mode:
    ------------------------------------
    i) The 'hardware' way.

    a) Unplug the USB cable and power off the phone.
    b) Press and hold 'Volume down' then power on the phone.
    c) Connect USB cable to your computer.

    ii) The 'software' way. (Requires ADB to be already installed - see below)

    a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
    b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
    c) Connect phone to computer via USB
    d) Navigate to the Firmware folder, right-click and open terminal and type:

    Code:
    adb reboot-bootloader

    Installing ADB / Fastboot:
    -------------------------------------
    Flashing via Linux LiveCD: (Put factory firmware files on an external usb drive / pen)
    --------------------------------
    a) Download Ubuntu LiveCD
    b) Burn to DVD or write to USB pen
    c) Restart PC, Boot from DVD into Ubuntu
    d) Open Terminal and type the following:
    sudo add-apt-repository ppa:nilarimogard/webupd8
    sudo apt-get update
    sudo apt-get install android-tools-adb android-tools-fastboot​

    e) Test fastboot by typing: sudo fastboot devices
    You should see:
    <serial number> fastboot​
    f) You are now ready to flash the fastboot files


    3) Fastboot Commands:

    Do commands manually, one at a time - checking that each one returns an [OKAY].​

    NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
    Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.

    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.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 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
    fastboot reboot​

    ALWAYS CHECK YOUR MODEL
    FLASHING WRONG FIRMWARE CAN DESTROY A PHONE
    31
    Frequently Asked Questions:

    Can I restore Factory Firmware if my Bootloader is locked?
    Yes. However attempting to downgrade to an older version of Android may fail - 'Preflash validation' error. Even with an unlocked Bootloader, downgrading cannot be guaranteed. It's also important to be aware that flashing the wrong Bootloader (bootloader.img) for your model can have serious consequences. Always establish your model of Moto G before flashing.

    I get a 'Preflash validation' error when flashing a Firmware Image
    The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.

    After flashing Firmware Image files phone gets stuck during boot-up | will not load Android?
    Check you are naming the files correctly, and make sure you are flashing all of the 'sparsechunk' files - not just those mentioned in the tutorial. The 'sparsechunk' commands listed there are not to be copied exactly, different firmware images may have different files.

    How to flash Radio Firmware only?
    Use the following fastboot commands:
    fastboot flash modem NON-HLOS.bin
    fastboot erase modemst1
    fastboot erase modemst2
    fastboot flash fsg fsg.mbn​

    How do I downgrade to an older Firmware?
    Downgrading carries risks, and may result in constant nagging notifications to update Android. Decide carefully if this is really what you want. With earlier generations of Moto G flashing bootloader.img and gpt.bin has resulted in a hard-brick. Avoid flashing these files if you are trying to downgrade. The safer option is to find a custom Stock ROM with OTA Updates disabled.

    Fastboot in Linux is not working?
    In Linux, root access is required for Fastboot and/or ADB to work.
    sudo fastboot devices​
    20
    Factory data reset via Stock Recovery:
    (1) Flash via fastboot stock recovery.img (found in firmware image zip)
    (2) Turn your phone off.
    (3) Press and hold Volume DOWN + POWER.
    (4) In recovery menu press Volume down twice.
    (5) Press power. You will see a red exclamation mark.
    (6) Hold power down, then tap Volume UP.
    (7) Go to Wipe data / Factory reset and press power button.
    (8) Scroll to Yes - delete all user data and press power.​
    4
    Yes and no.
    I mean reflashing same firmware.
    If I reflash same firmware, but only system partition (or all files), I think it could work (to unroot) without erasing anything.
    In nexus 7, reflashing same firmware without erasing user data is the right way to unroot.

    Three days ago I upgraded from 5.1 to 6.0 without performing 'Factory data reset' and Android boots ok
    With Moto G (3rd Gen) in particular - not doing a 'factory data reset' has prevented Android booting for many people. It's also my experience with Moto G generally that not erasing userdata can introduce a wide range of issues, from very minor to very serious. I am now of the opinion that if you have not done a 'Factory data reset' in Android and erased userdata during fastboot flashing - you have not flashed Android properly. For best performance / experience, do what I say.
    3
    @lost101, do you think the downgrade could result if we flash only gtp.bin and bootloader (it will flash the old bootloader), reboot to bootloader (the old one now) and then flash the other partitions?
    Sorry if this is a stupid question.
    The last thing you should ever do is touch the Bootloader on a device. It's completely unnecessary and stupidly dangerous.

    These are the only commands required:
    fastboot flash boot boot.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 modem NON-HLOS.bin
    fastboot erase modemst1
    fastboot erase modemst2
    fastboot flash fsg fsg.mbn
    fastboot erase cache
    fastboot erase userdata
    fastboot reboot​

    If not booting, add the following command at the beginning of list:
    fastboot flash partition gpt.bin​