[GUIDE][Osprey] Fastboot Flashing Factory Firmware Images

Karumbaiah

Senior Member
Feb 17, 2013
82
3
0
Bangalore
Preflash Validation errors mean your using the incorrect factory image, it's older than what's installed (most likely) or for the wrong device. Downgrading is only possible if the bootloader is unlocked, and even then it can be dangerous, so you must use a factory firmware image that is the same or newer version than what's installed... Unfortunately, Lenovo's Moto hasn't been quite as forthcoming with new firmware images as in the past.

I suggest going to the G4 Plus group and asking there, other than basic knowledge most of us can't help you here.
Everyone so far has been suggesting pretty much the same to me. But I'm sure I'm using the latest version of the firmware. It's the one before the latest security patch. However, the boot image and recovery image should remain the same.

Here's the version that I'm trying to flash.
XT1641-XT1643_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC

I came across this version after a lot of research. Please help me if I'm still using the wrong one.
 

acejavelin

Recognized Contributor
Sep 3, 2009
6,835
3,318
0
Lincoln, ND
Everyone so far has been suggesting pretty much the same to me. But I'm sure I'm using the latest version of the firmware. It's the one before the latest security patch. However, the boot image and recovery image should remain the same.

Here's the version that I'm trying to flash.
XT1641-XT1643_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC

I came across this version after a lot of research. Please help me if I'm still using the wrong one.
Wouldn't know anymore than you... But in newer devices there could be a version that is newer only by OTA, if you have taken and there is no same or newer full image, you're basically SOL
 

mahesh ws

New member
Oct 13, 2015
4
0
0
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) Press power + Volume UP.
(7) Go to Wipe data / Factory reset and press power button.
(8) Scroll to Yes - delete all user data and press power.​
my g3 got stuck in the bootloader it shows bootup failed. can you help me out?
 

Nevinyrral

New member
Dec 24, 2016
1
0
0
Hi everyone, I been trying to flash the GPT partition with no success, I followed the flash recovery instructions, applied factory reset; strange thig is that the recovery mode is not working any more any help is appreciated :)

Code:
C:\MotoPipe\ADB>fastboot.exe flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [  0.127s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.

(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.612s

C:\MotoPipe\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.86
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x6
(bootloader) emmc: 8GB Hynix REV=07 PRV=07 TYPE=57
(bootloader) ram: 1024MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) cid: 0x000C
(bootloader) channelid: 0x1f
(bootloader) uid: 9A69F60C00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) date: 07-17-2015
(bootloader) sku: XT1543
(bootloader) battid: SNN5965A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Oct 19 17:25:47 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_retla_ds/osprey_ud
(bootloader) ro.build.fingerprint[1]: s:5.1.1/LPI23.72-16.4/4:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.36.4.osprey_retla
(bootloader) ro.build.version.full[1]: _ds.retla.en.01
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.49-gef57933 (hudsoncm
(bootloader) kernel.version[1]: [user=387459]@ilc[/user]lbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Jun 11 23:03:51 CDT 2015
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: git=MBM-NG-V80.86-0-g9fa648d
(bootloader) tz.git: git=MBM-NG-V80.86-0-g53215ba
(bootloader) hyp.git: git=MBM-NG-V80.86-0-g53215ba
(bootloader) aboot.git: git=MBM-NG-V80.86-0-g14cfbb2
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:DDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-type:padA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:padB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:persist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:padC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:oem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-size:DDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000177000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:padA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000177000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:padB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-size:persist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:padC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-size:oem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x0000000091000000
(bootloader) partition-size:userdata: 0x0000000121fe0000
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tefunl
all: listed above
finished. total time: 0.633s
I'm using XT1543_OSPREY_RETLA_DS_6.0.1_MPI24.107-55-2_cid12_subsidy-DEFAULT_CFC,

Thanks in advance
 
Last edited:

rizwan.mahai

Senior Member
Jul 2, 2014
231
55
58
Nizamabad, India
Thank You

Flashed 6.0 successfully on MotoG3 from 5.1.1. I lost TWRP, so now I have to flash it and get rid of that bootloader unlocked logo.
One question though, I took a TWRP backup of 5.1.1 before flashing 6.0. I just wanted to know whether after flashing TWRP can I flash that 5.1.1 and roll back to lollipop rom ?
 

acejavelin

Recognized Contributor
Sep 3, 2009
6,835
3,318
0
Lincoln, ND
Flashed 6.0 successfully on MotoG3 from 5.1.1. I lost TWRP, so now I have to flash it and get rid of that bootloader unlocked logo.
One question though, I took a TWRP backup of 5.1.1 before flashing 6.0. I just wanted to know whether after flashing TWRP can I flash that 5.1.1 and roll back to lollipop rom ?
No, although restoring the backup may make the device bootable or not, it would be in a mixed state with parts of the device on Marshmallow and marts on Lollipop... Remember we have 16+ partitions on this device, TWRP only backs up and restores less than half of them.
 

Cookie Ninja

Senior Member
Jan 21, 2010
2,043
699
193
No, although restoring the backup may make the device bootable or not, it would be in a mixed state with parts of the device on Marshmallow and marts on Lollipop... Remember we have 16+ partitions on this device, TWRP only backs up and restores less than half of them.
Wow! 16+ partitions! I never knew this....any source where I can further my knowledge? Thanks....

Dead Cookies leave no trails...
 

acejavelin

Recognized Contributor
Sep 3, 2009
6,835
3,318
0
Lincoln, ND
Wow! 16+ partitions! I never knew this....any source where I can further my knowledge? Thanks....

Dead Cookies leave no trails...
Hopefully you never find out, some phones have as many as 37... Or so I've heard, most partitions are not accessible directly unless your bricked an Qpst modem mode..

If you want an idea of some of what the phone mounting, open a terminal emulator and just do some basic commands like mount and you will see some of tgem
 

acejavelin

Recognized Contributor
Sep 3, 2009
6,835
3,318
0
Lincoln, ND
Can I downgrade from October security firmware to July security firmware
Did you read the second post?

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.
The real question would be why would you want to? There is no significant difference between July and October except the secutiry patches...
 

rizwan.mahai

Senior Member
Jul 2, 2014
231
55
58
Nizamabad, India
I already reverted back

No, although restoring the backup may make the device bootable or not, it would be in a mixed state with parts of the device on Marshmallow and marts on Lollipop... Remember we have 16+ partitions on this device, TWRP only backs up and restores less than half of them.
Before I could read this message, I already reverted back to 5.1.1 using the TWRP I had backed up. To the surprise I didn't face any problem & 5.1.1 is running smoothly (as usual) now.

[Out of topic] One thing I noticed after flashing 6.0 was I got the VOLTE (Reliance Jio, India) icon and could flawlessly connect to call services. The problem in 5.1.1 is there's no VOLTE icon even after enabling Enhanced 4G LTE Services, and the call won't connect & also the Enhanced 4G LTE Services option appears and disappears randomly. (mostly after inserting 2nd sim).
 

zendude

Member
Dec 17, 2015
31
8
28
XT1548 stock rom contents

. . .
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​
. . .
I need to restore the factory firmware image on a Sprint XT1548 and located the stock rom zip file from another thread. I noticed that the flash instruction omits one of the image files in the zip file, carrier.img. Is there a reason why it's left out? flashfile.xml and servicefile.xml seem to indicate that the file is a part of the factory image.

XT1548_OSPREY_SPRINT_6.0.1_MCI24.107-82_cid9_subsidy-DEFAULT_CFC.xml.zip is the stock rom zip file from
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639

Archive: XT1548_OSPREY_SPRINT_6.0.1_MCI24.107-82_cid9_subsidy-DEFAULT_CFC.xml.zip
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
37876520 Defl:N 30235686 20% 2016-06-29 08:04 1c9397ad NON-HLOS.bin
16879616 Defl:N 9799132 42% 2016-06-29 08:04 99fab95e recovery.img
2375680 Defl:N 2117681 11% 2016-06-29 08:04 86ad9570 fsg.mbn
32768 Defl:N 4846 85% 2016-06-29 08:04 ff31e586 gpt.bin
16777216 Defl:N 9206552 45% 2016-06-29 08:04 6d4d63f6 boot.img
268433500 Defl:N 167794464 38% 2016-06-29 14:39 2a7afdc7 system.img_sparsechunk.0
249277352 Defl:N 163616578 34% 2016-06-29 14:39 a4a66670 system.img_sparsechunk.1
256467436 Defl:N 137017050 47% 2016-06-29 14:39 f174d66a system.img_sparsechunk.2
268432908 Defl:N 149034221 45% 2016-06-29 14:39 f16d1152 system.img_sparsechunk.3
94707692 Defl:N 58434324 38% 2016-06-29 14:39 ee3c7733 system.img_sparsechunk.4
53428 Defl:N 3431 94% 2016-06-29 08:04 4bbce907 carrier.img
1384553 Defl:N 521026 62% 2016-06-29 08:04 40720573 logo.bin
2607616 Defl:N 841723 68% 2016-06-29 08:04 9f264b83 bootloader.img
2433 Defl:N 834 66% 2016-06-29 14:39 c51466f8 flashfile.xml
2233 Defl:N 757 66% 2016-06-29 14:39 c674b825 servicefile.xml
1088 Defl:N 51 95% 2016-06-29 14:39 aa4d510c slcf_rev_b_default_v1.0.nvm
806 Defl:N 424 47% 2016-06-29 14:39 55169c15 OSPREY_SPRINT_6.0.1_MCI24.107-82_cid9_subsidy-DEFAULT_CFC.info.txt
-------- ------- --- -------
1215312845 728628780 40% 17 files

Thank you.
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,326
0
@zendude - It's not present for most other firmware images. It may be unnecessary, but if you do flash it - make sure it's to the correct partition.
 

Rocker223

Senior Member
Jul 1, 2016
109
21
0
20
Shimoga
Automated Reset

Resetting your phone is two clicks away You better change your mind!! unless the usb wire is correctly connected to the PC there is going to be no problem. :eek: And I have ran so many tests to make the process of resetting your phone goes smoothly without any interuption while its running!!

You can't expect much from me as I'am still learning, but I will try my level best to make this process easy and keep it updated!

NOTE: This is made for phones with 8 sparsechunk files (0-7)

Tested on: Moto G3 XT1550
Download Here

USAGE:
Place this file in the place of your stock firmware with adb and run this file!!
 
Last edited:

infinite4evr

Senior Member
Sep 20, 2016
223
28
28
New Delhi
infinite4evr.com
hey i am getting PREFLASH VALIDATION FAILURE on bootloader ? CAN SOMEONE HELP PLS? And remote failure -permission denied for every other command.

---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------

@zendude - It's not present for most other firmware images. It may be unnecessary, but if you do flash it - make sure it's to the correct partition.
Lost can ya help me about the above thing i posted? Thanks and am asking about it after so much of research , Read all pages of this thread :(
 

acejavelin

Recognized Contributor
Sep 3, 2009
6,835
3,318
0
Lincoln, ND
hey i am getting PREFLASH VALIDATION FAILURE on bootloader ? CAN SOMEONE HELP PLS? And remote failure -permission denied for every other command.

---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------


Lost can ya help me about the above thing i posted? Thanks and am asking about it after so much of research , Read all pages of this thread :(
Preflash Validation failure means you're using a firmware image that is older than what's installed in the device. You need a newer image, and should read the second posts in the firmware and how to flash firmware threads.
 
  • Like
Reactions: infinite4evr
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone