Database Users

Moto X Pure Edition 2015 FACTORY IMAGES Fastboot help!!!

When click the power button i launch on screen with the Fastboot Flash Mode. I tried all the options but nothing happens.
Select Normal Powerup then also nothing happens.
Select Factory nothing happens. I am stuck on fastboot when starting phone.
I tried to flash factory images and install again using steps mentioned by moto but receive error when below command is entered:
fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.095s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.266s
On mobile i see this:
cmd: getvar;partion-type;partion
cmd: getvar:max-download-size
cmd: download:0008000
cmd: flash;partition
hab check failed for primary_gpt
Failed to verify hab image primary.gpt
When doing motoboot.img I get this:
fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2022 KB)...
OKAY [ 0.115s]
writing 'motoboot'...
(bootloader) Motoboot;Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on mobile I see this:
cmd: getvar;partion-type:motoboot
cmd: getvar:max-download-size
cmd: download:001f9a00
cmd: flash:motoboot
Mismatched partition size (tz)
If you have any information about this please do in the quickest way possible.

What factory images? Are you unlocked?

lafester said:
What factory images? Are you unlocked?
Click to expand...
Click to collapse
I ment the Flash stoke images when using the bootloader thing

ymx75 said:
I ment the Flash stoke images when using the bootloader thing
Click to expand...
Click to collapse
ignore that one. I ment to say the Flash images when using the bootloader and yes I am unlocked

I would download the return to stock zip and run flash all .bat. Then use twrp to make a backup so you don't have to do this again.

lafester said:
I would download the return to stock zip and run flash all .bat. Then use twrp to make a backup so you don't have to do this again.
Click to expand...
Click to collapse
thanks for the info. the thing is, I feel stupid, but I deleted the zip and can't remember wat website I got it from. if you could help me find it, it would mean the world to me

ymx75 said:
thanks for the info. the thing is, I feel stupid, but I deleted the zip and can't remember wat website I got it from. if you could help me find it, it would mean the world to me
Click to expand...
Click to collapse
Here is the thread with the "return to stock" zip file.

ymx75 said:
thanks for the info. the thing is, I feel stupid, but I deleted the zip and can't remember wat website I got it from. if you could help me find it, it would mean the world to me
Click to expand...
Click to collapse
Under Android development or original development
Sent from my XT1575 using Tapatalk

Bricked phone trying to root, now unable to flash stock rom

So I successfully installed TWRP recovery.
I then tried to flash SuperSU, but that gave me a boot loop, so I wanted to try and flash the stock rom again.
I wiped my phone with TWRP.
I wasn't totally sure what the correct version of the ROM was to download. I can't check because the phone is already wiped. It's a UK Moto X Play "lux XT1562 16GB P2C" single sim slot. I had installed an OTA update yesterday. I downloaded XT1562_LUX_RETEU_6.0.1_MPD24.107-52.xml.zip, would that be the correct version? Is there any way to know for sure?
So when I tried to flash the stock rom I ran into problems.
I ran "fastboot flash partition gpt.bin" and I got "(bootloader) Preflash validation failed".
I saw someone say that this could be because you need to flash the correct version of the bootloader first, so I did "fastboot flash bootloader bootloader.img" which was successful, but even after restarting "fastboot flash partition gpt.bin" still failed.
I'm really confused as to what I'm doing wrong. Am I having problems because I'm trying to flash the wrong version of the bootloader, or a version older then that which I had on my phone before wiping? Is this the kind of error you'd get if you were trying to downgrade, or should that work fine?
Help greatly appreciated!
Edit: Should I possibly try flashing 5.1.1 X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip or is flashing an older version a bad idea?

Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen

tavares_one said:
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
Click to expand...
Click to collapse
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
It fails when I try and flash gpt.bin
Code:
❯ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.143s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.740s
and on the bootloader logs is says
Code:
cmd: getvar:partition-type:partition
cmd: getvar:max-download-size
cmd: download 00008000
cmd: flash:partition
version downgraded for primary_gpt

johtso said:
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
Click to expand...
Click to collapse
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Dio-Genes said:
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
Click to expand...
Click to collapse
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.

johtso said:
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
Click to expand...
Click to collapse
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot

fablebreton said:
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
...
Click to expand...
Click to collapse
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s

johtso said:
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
Click to expand...
Click to collapse
Your bootloader is unlocked ?

fablebreton said:
Your bootloader is unlocked ?
Click to expand...
Click to collapse
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"

johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.

johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
if impossible with stock and if Twrp ok why not flash a custom rom

minimale_ldz said:
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
Click to expand...
Click to collapse
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU

johtso said:
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
Click to expand...
Click to collapse
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says

minimale_ldz said:
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
Click to expand...
Click to collapse
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Edit: It worked! You're an absolute life saver! So confusing that those two ROM are named so similarly..

johtso said:
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Click to expand...
Click to collapse
No idea what it means, but both your getvar info and linked firmware are MPDS. Anyway - good luck.

XT1563 - boot loop

I have Moto X play XT1563. It was stuck in a boot loop - moto logo->circle and "erasing"->reboot
Fastboot and ADB works
I tried to flash new firmware (stock image) - failed:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
based on that and research I decided to unlock bootloader, which ended up with:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
since phone is unalbe to boot I cannot go to dev options. Is there any way to have it done using adb or fastboot? even low level linux way to change something in the config?
or (easier way) - anyone aware where can I find new Bell firmware? now I have M8936_2020632.44.03.21.57R LUX_BELLCA_CUST
Appreciate any suggestions

Check here
https://github.com/motoxplay/stock
there is a bell firmware but is tagged with a BELL? so, don´t know if will it work
Cheers.

Thanks - checked that before - this one is 6.0.1 and I need 7.1.1
Version NPD26.48-21-1 to be exact

I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s

stingu said:
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
Do you have an unlocked bootloader?

Did you try to install TWRP ? It's not bootloader unlocked, is it ?

Bootloader is locked, while trying to unlock it I get:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Flashing and booting fails, for stock and TWRP

Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?

Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?

Cannot flash TWRP (failed to load kernel)

I'm trying to root my Moto X Pure following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
I was able to unlock the bootloader. In fastboot mode, it says "Device is UNLOCKED. Status Code: 3"
But so far I am unable to flash TWRP on it.
The serial comes up when I type: "adb devices," or "fastboot devices" in the command prompt. I attempt to flash with the following:
HTML:
C:\root>fastboot flash recovery C:\root\twrp-3.2.1-0-twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.109s]
writing 'recovery'...
OKAY [ 0.623s]
finished. total time: 0.736s
Then, when I go to "Recovery Mode" on the phone, I get a screen that says this...
Star Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get
the Software Repair Assistant
..... (several more lines)...
Error: failed to load kernel!
Boot up failed
Click to expand...
Click to collapse
I've tried these versions of TWRP:
twrp-2.8.5.0-twrp
twrp-2.8.7.0-clark
twrp-3.0.2-0-twrp
twrp-3.1.0-0-twrp
twrp-3.2.1-0-twrp
Same result every time.
Any ideas to help? Thanks!

Twrp for clark is ~37MB, you are flashing wrong file(4690kb).
Download again 3.+, place it in adb, fastboot.exe folder and flash:
fastboot flash recovery TwrpName.img
or boot only
fastboot boot TwrpName.img @thejukes

The bootloader has changed and phone is bricked; what should I do?

So I have run CandyOS for a while, but since it got bricked for some reason (possibly something to do with magisk modules) I decided to run another ROM instead. This is what I've done, keep in mind my bootloader has been unlocked the whole time:
1. booted into TWRP
2. flashed LOS 17.1 (gave error 18)
3. booted into bootloader in order to boot into LOS native recovery which I here realized existed (although their installation page says to use TWRP)
4. phone reboots into a changed bootloader which now claims "oem_locked"
The bootloader:
Code:
(in the middle of screen) Power off
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-river_retail-0ff2095b20-200404
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
oem_locked
I've tried a couple of things, results below:
I tried to unlock the bootloader (I have the unlock code saved):
Code:
fastboot oem unlock XXXXXXXX (bootloader) feature disabled
OKAY [ 0.003s]
Finished. Total time: 0.008s
Tried to flash a recovery:
Code:
fastboot flash recovery lineage-17.1-20200719-recovery-river.img
target reported max download size of 536870912 bytes
sending 'recovery' (20318 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.701s
..boot into recovery:
Code:
fastboot boot lineage-17.1-20200719-recovery-river.img
downloading 'boot.img'...
OKAY [ 0.702s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
The exact same things happens with TWRP
I have also tried the Lenovo recovery program with no success, it refuses to recognize my device.
So what would be my next steps? Any help would be appreciated as I've tried to ask in a couple of places with no success

Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:

Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
No this actually didn't occur to me, I'll try it as soon as I get home and see what happens. Thank you!

Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
It didn't work:
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.093s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.125s
Code:
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.365s
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies

yarnbomb said:
It didn't work:
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies
Click to expand...
Click to collapse
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs

sd_shadow said:
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Oh, didn't know that. What would be my options with this?

yarnbomb said:
Oh, didn't know that. What would be my options with this?
Click to expand...
Click to collapse
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The former didn't recognize my device, the latter I didn't know about, I'll try it asap

yarnbomb said:
The former didn't recognize my device, the latter I didn't know about, I'll try it asap
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7 if you can.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs

timba123 said:
You need blankflash
Click to expand...
Click to collapse
Not if it's in fastboot mode.
Sent from my ali using XDA Labs

timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Fastboot OEM blankflash doesn't work if bootloader is locked.

timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Timba, can you hook me up with the Telegram group for the G7?
Wondering if they have a blankflash for Android 10 or something.

timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
you are absolute about this because same issue happen to me and all has failed this definitely did the fix on my moto g7 power I just want to Thank You for this really appreciate it

timba123 said:
He stated he unlocked bootloader already. I did too and had same problem. Its saying oem locked due to a bad flash or didnt flash copypartitions zip in twrp. Can we contact him and try it? I bet it will work. I'm on XT1955-5 but it's the same issue I and many others have been in and fixed.
Click to expand...
Click to collapse
yes worked on mine xt1955-5 and yes was cause on flashing a custom rom thought was brick for good till had to came arcoss this fix and the only fix that got it out of that ap fastboot bullshits and yes had oem lock before it happen and when it bricked oem say's it's lock which got me thinking how in the hell going get out of this tryed all other method mention non work glad this did again thanks