Database Develop

Q|XT1097 ATT Wont boot

Hey, Ive received the device from a friend after he tried to unlock frp lock. For some reason he flashed a different firmware and now the device is in a bootloop.
Getvar all:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 6020
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: ***********
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 64BF660E0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: **********
(bootloader) meid:
(bootloader) date: 10-30-2014
(bootloader) sku: XT1097
(bootloader) iccid: *********
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Sep 13 18:56:47 UTC 2016"
[B](bootloader) ro.build.fingerprint[0]: motorola/victara_att/victara:5.1/L
(bootloader) ro.build.fingerprint[1]: PES23.32-21.9-8/5:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.23.221.8.victara_att[/B]
(bootloader) ro.build.version.full[1]: .att.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8974BP_42352121.25.09.24R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.4.42-gdc3b1f6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Wed Sep 14 04:43:25 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.20-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.20-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.20-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.20-0-gc8cfdbe
(bootloader) aboot.git: git=MBM-NG-V60.20-0-g78a2c4f
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.075s
After some reading and trying I understand that I cant downgrade or flash other cid.
The only firmware that does not give any error is :
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-8_cid1_CFC
with this script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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
pause
fastboot reboot
but even with this one the phone does not boot.
what else can I try ?

The bootloader is locked.
I think you cant flash via fastboot.
Have you try factory rest from recovery?

try to unlock bootloader via motorola website. flash TWRP

Bootloader cannot be unlocked so no custom solution, also cant boot to any mode except bootloader (recovery,qcom etc.. )

deadwolf666 said:
Bootloader cannot be unlocked so no custom solution, also cant boot to any mode except bootloader (recovery,qcom etc.. )
Click to expand...
Click to collapse
You cant see recovery?
If run motorola official app on windows hels you maybe.
Is your windows drivers ok?
I cant think something else.

papsr6 said:
You cant see recovery?
If run motorola official app on windows hels you maybe.
Is your windows drivers ok?
I cant think something else.
Click to expand...
Click to collapse
I can only see boot loader if I try to boot to recovery or normal I get bootloop.
Drivers are ok because the firmware did flash without errors.

Any thing I could try to boot the phone ?

Super Mega Hard Bricked

Guys
I had unlocked the bootloader and was using the Ressuration Remix a few days ago.
Yesterday i went to install the Stock PAYTON_OPW28.46-13. I made fastboot -w and run the script.
But there was an error and my script had the command: oem lock.
It happened that he did not pass the rom and blocked the bootloader. After that I can not install any ROMs.
I tried them all.
PAYTON_OPWS27.57-25-6-10
PAYTON_OPWS27.57-40-14
PAYTON_OPW28.46-13
PAYTON_OPWS27.57-40-17
I did not succeed. The message I have is:
sending 'bootloader' (9520 KB) ...
OKAY [0.278s]
writing 'bootloader' ...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0
I noticed something different in the bootloader.
The message is: flashing_locked.
- I do not have access to TWRP
- I do not have access to recovery stock
- I do not have access to the previous ROM (deleted everything)
I have access to fastboot
I have access to the option to unlock the bootloader, but when I put the code, the following message is:
Enable USB USB debbuguing <in development option> but I can not do it because I do not have a system!
https://drive.google.com/open?id=1SuJjDUcSPgfy7uzxkcTQYRA4jhQU2TL4
Anyone know what to do?

see if this helps.
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472

What about reapplying for an unlock code, and re-unlocking the bootloader? I did that on my z2 Force when it happened.

slaytanic said:
What about reapplying for an unlock code, and re-unlocking the bootloader? I did that on my z2 Force when it happened.
Click to expand...
Click to collapse
When I try to unlock it, it asks me to enable the USb Debugging option in the developer settings ...

munchy_cool said:
see if this helps.
https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472
Click to expand...
Click to collapse
It sounds a bit tricky but what I realized is that my phone is recognized as Fastboot Payton S and I can not install it as a Qualcomm driver

IVANWB said:
It sounds a bit tricky but what I realized is that my phone is recognized as Fastboot Payton S and I can not install it as a Qualcomm driver
Click to expand...
Click to collapse
try flashing factory firmware from fastboot?

munchy_cool said:
try flashing factory firmware from fastboot?
Click to expand...
Click to collapse
I've tried all the images, I always receive (bootloader) flash permission denied
success when installing the qualcomm drivers.
When I run blank-flash script, i get the message:
"Waiting for device"

If I try,
fastboot flashing unlock
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.013s]
finished. total time: 0.014s

I dont know what else to say.
you locked the bootloader with developer settings turned off.
I personally dont have a solution for this. let's hope someone else has.

you locked the bootloader with developer settings turned off.[/QUOTE said:
Exactly, I've tried everything ...
Click to expand...
Click to collapse

munchy_cool said:
I dont know what else to say.
you locked the bootloader with developer settings turned off.
I personally dont have a solution for this. let's hope someone else has.
Click to expand...
Click to collapse
Exactly, I've tried everything ...

IVANWB said:
I've tried all the images, I always receive (bootloader) flash permission denied
success when installing the qualcomm drivers.
When I run blank-flash script, i get the message:
"Waiting for device"
Click to expand...
Click to collapse
Have you already tried the emergency fastboot?
This worked for me when my x4 bricked.

jonathangrag said:
Have you already tried the emergency fastboot?
This worked for me when my x4 bricked.
Click to expand...
Click to collapse
Hello everyone, friend what are the commands to enter this mode?

pauloreducinobr said:
Hello everyone, friend what are the commands to enter this mode?
Click to expand...
Click to collapse
It's the same mode, but you use a different software version. Here it is.

try entering in the "cmd" command console this:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot bluetooth flash BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
If the error still appears remove "mfastboot flash oem oem.img"..who knows, maybe it works !

I sent my device yesterday for the warranty.
They said it was necessary to change the plate and the guarantee will cover.
Thanks for the help.

IVANWB said:
I sent my device yesterday for the warranty.
They said it was necessary to change the plate and the guarantee will cover.
Thanks for the help.
Click to expand...
Click to collapse
Wow, they will really cover it? Que sorte! I would not expect that
(saw your post on G+ haha)

Daaaaniel said:
try entering in the "cmd" command console this:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot bluetooth flash BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
If the error still appears remove "mfastboot flash oem oem.img"..who knows, maybe it works !
Click to expand...
Click to collapse
Can you send me the stock boot.img? I need it to examine how it works, and the full firmware will take ages to download. Thank you.
Broadcasted from Zeta Reticuli

Softbricked
So, I have a similar problem, but I can't access anything, because Motorola says "untrusted device" and this bla bla bla. The problem is the ROM, I can't found the original ROM of this phone is in use (XT1900-6). The flashing state is set to locked, and is no possible to unlock OEM. The Qualcomm drivers don't worked here, maybe I need a fresh install of Windows 10.
Anybody have a ideia to fix that?
variables:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-171216
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 004294------
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0E141779
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: --------------------------
(bootloader) meid:
(bootloader) date: 01-25-2018
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3843
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPW27
(bootloader) ro.build.fingerprint[1]: .57-40/52:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.31.52.payton.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7036.16.01.69R PAYTON_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-ge3f7ffe (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Sat Dec 16 07:34:49 CST 2017
(bootloader) git:abl: MBM-3.0-uefi-641a15b-171216
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-171216
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-171216
(bootloader) git:rpm: MBM-3.0-uefi-245b046-171216
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-171216
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (343)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Edit: Removed smiles on text.

Always boots to recovery... Any known fix?

Hi,
I could use some help... One of my G5S Plus phones boots into stock recovery "No command" screen every time I power on. I work around this by entering the stock recovery (Power + Vol Up) and selecting bootloader. Once bootloader loads, I simply hit start and the phone boots properly. All else seems fine -- operation is good.
I've had this issue ever since I unlocked/rooted/TWRP/magisk when I first got the phone. To be honest, I'm not sure I got the mods installed correctly, which is why I have given up and returned to stock. So, I recently flashed the stock Oreo via fastboot and relocked the bootloader. Again, all works fine except for the boot to recovery mode after powering up.
I researched the forum on this issue, but didn't find any solution, though it seems many others have the issue. I'm hoping there is a guru here that knows how to fix this. Examples of others with similar issues:
HTML:
https://forum.xda-developers.com/android/help/moto-g5s-plus-twrp-recovery-boot-loop-t3762077
HTML:
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-recovery-boot-loop-t3772621
HTML:
https://forum.xda-developers.com/moto-g4/help/moto-g4-recovery-boot-loop-t3608348
One thing I did find here on the forums... but it was related to the G5 -- Something to do with the misc partition???:
HTML:
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
Here's my Getvar all...
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: Deleted
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: E3DC2DC800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: Deleted
(bootloader) meid:
(bootloader) date: 09-17-2017
(bootloader) sku: XT1806
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 11 10: 8:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders/sanders:8.1.0/OPS
(bootloader) ro.build.fingerprint[1]: 28.65-36/9fea:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.31.40.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.79R SANDERS_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gd0e0d1a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Aug 10 22:52:41 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=MBM-NG-VC2.11-0-g92e5e21-dirty
(bootloader) tz.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) devcfg.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) keymaster.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) cmnlib.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) cmnlib64.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) prov.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Here are the commands I used to flash -- I tried to erase DDR, but permission was denied:
Code:
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 dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Followed by these commands to relock the bootloader
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock

By seeing "(bootloader) imei: Deleted" and "(bootloader) serialno: Deleted" i can tell that the phone is really messed up.
I've found this guide, but it says you need STOCK NOUGAT but you're on OREO, but it might help you.

It seems the latest OTA fixed the issue. It complained about the recovery partition during install, but appears to have overwritten it/fixed it during the upgrade. Wife hasn't complained since the update.

Coala990 said:
By seeing "(bootloader) imei: Deleted" and "(bootloader) serialno: Deleted" i can tell that the phone is really messed up.
I've found this guide, but it says you need STOCK NOUGAT but you're on OREO, but it might help you.
Click to expand...
Click to collapse
LOL. I manually deleted them before posting the text. I should have been more clear about that.
The wife is running Oreo just fine and getting OTA updates. The only issue is that the phone cold boots to stock recovery. Easy workaround... Power + Vol Down on cold boot into bootloader, then press power to select "start" directly from bootloader. Then, it boots just fine.

Flashed incorrect region firmware - Not able to lock the bootloader again - Bricked?

Hi guys,
I have Moto G5S Plus Indian variant phone - XT1804. I was trying to unlock the bootloader and root the phone. The phone already had stock firmware 8.1. During the process, I used the following firmware - SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
The phone was able to unlock successfully, but during the boot, it is giving the following message:
Your device has been unlocked and can't be trusted again.
ID: bad key
Your device will boot in 5 seconds.
Although it says your device will boot in 5 seconds, nothing happens after 5 seconds. I am not to boot into the OS, but can into the fastboot mode by pressing volume down and power button. Below are my current getvar details:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: DC7B4C3F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 10-17-2017
(bootloader) sku: XT1804
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 12 16:16:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36/9fea:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.31.40.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_27.36.07.41R SANDERS_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gd0e0d1a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Aug 10 22:52:41 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=MBM-NG-VC2.11-0-g92e5e21-dirty
(bootloader) tz.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) devcfg.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) keymaster.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) cmnlib.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) cmnlib64.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) prov.git: git=MBM-NG-VC2.11-1-g9a0b157
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
I need help with three things.
1. Relock the bootloader and get back to Indian stock oreo 8.1 firmware. If you can provide the correct download link to restore stock firmware to Oreo 8.1.
2. Unlock the bootloader again with the correct stock ROM to get rid of the bad key message.
3. Possibly install twrp (not able to flash it right now) and PixelExperience ROM
I have tried the restore process with following commands on below firmwares, but does not help with locking the bootloader again.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
I have tried with following steps to lock the bootloader with following commands, but still not working.
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
I tried the above steps with the following firmware - SANDERS_RETAIL_8.1.0_OPSS28.65-36-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, none of the steps are producing any errors except last. It is giving the following error in the last step.
(bootloader) Still require signed system.img and/or oem.img
Please help. :crying:

Did you give it 10 minutes?
---------- Post added at 05:43 AM ---------- Previous post was at 05:43 AM ----------
jacecrobinson said:
Did you give it 10 minutes?
Click to expand...
Click to collapse
It's quite normaly for it to say that but take up to five minutes on the first boot
---------- Post added at 05:45 AM ---------- Previous post was at 05:43 AM ----------
jacecrobinson said:
Did you give it 10 minutes?
Click to expand...
Click to collapse
It's quite normaly for it to say that but take up to five minutes on the first boot

Yesterday morning my phone stuck on dummy bootloader and showing oem locked ..
I can't flash any stock rom
And twrp coz oem is locked
When I want to flash stock rom via fastboot it shows
Unable to initialise partition table remote failure ..
I checked barcode .. there I see my imie no gone 000000..
Please help ..
I think my bootloader is bricked ... ..
If anyone developed blank flash zip for our xt1804 please help me...
Motocare says u have to change motherboard cost around 14 k
Please help me ...
Thank you in advance

jacecrobinson said:
Did you give it 10 minutes?
It's quite normaly for it to say that but take up to five minutes on the first boot
Click to expand...
Click to collapse
Thank you so much for the tip. I am now able to boot into the OS now, but then I am stuck with the following:
1. Unlocked bootloader - I would to relock it and unlock properly in order to install twrp bootloader
2. I am stuck with non-Indian firmware, hence will not receive OTA updates
3. I would like to install custom ROMs, which I can't since #1 - not able to install twrp.
Any workarounds or solutions are highly appreciated.

chiaotzu said:
Thank you so much for the tip. I am now able to boot into the OS now, but then I am stuck with the following:
1. Unlocked bootloader - I would to relock it and unlock properly in order to install twrp bootloader
2. I am stuck with non-Indian firmware, hence will not receive OTA updates
3. I would like to install custom ROMs, which I can't since #1 - not able to install twrp.
Any workarounds or solutions are highly appreciated.
Click to expand...
Click to collapse
You can't receive ota to my knowledge with a unlocked and modified boot..also if you relock your loader you have to be back to stock which defeats the port pose of a unlocked boot.
What version of twrp did you try and install? Did you use fast boot?and do you have USB dev enabled in settings before trying

Solved the issue, thanks.

chiaotzu said:
Solved the issue, thanks.
Click to expand...
Click to collapse
Please document your solution, in case other users have this problem
Sent from my Alcatel 5041C using XDA Labs

chiaotzu said:
Solved the issue, thanks.
Click to expand...
Click to collapse
have xt1802, I installed the firmware SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
but when using adb commands it presents error writing 'partition' ...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6
target reported max download size of 534773760 bytes
sending 'system' (262139 KB) ...
OKAY [5.623s]
is left without infinite loop, how to solve?

incorrect firmware Moto G5S Plus
chiaotzu said:
Solved the issue, thanks.
Click to expand...
Click to collapse
What you do it for solve??
I have the same poblem here

Unable to flash any file, or go anywhere past Fastboot on Moto G5s Plus XT1800

Hi guys, this is my first post here in XDA, and i'm kinda desperate... a couple of weeks ago my Moto G5s Plus (rooted, but with official Nougat firmware) turned itself off overnight, and ever since won't turn on except on Fastboot mode. Every time I try to Start the device normally, the Bootloader Logs appear with the message "Start up failed; failed to validate boot image". The same thing happens when I try to go into Factory or even Recovery mode (instead of failed to validate boot image, it says, failed to validate recovery image).
When I plug it into my PC, it is recognized but only as Android Bootloader Mode. I've tried different files of official firmware in order to flash them via fastboot, but it's no use... it just says "Preflash validation failed", and so on.
When I enter the command getvar_all, this is what it shows:
C:\Users\IVAN\Sanders\Stock\Third>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: 229d978d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 881733DA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.06-0-g1e22c44
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
Finished. Total time: 0.250s
I've noticed that both the CID and the IMEI are gonners, but as I can't flash anything, there's no way of trying the "Validus" method to restore the IMEI (which I've already done a couple of months ago, after the first root).
I've tried by setting my PC into Test Mode, so as to "skip" the validation of the flash images, but it shows the exact same message. RSD Lite won't even show my device when plugged. I couldn't erase user data, cache or even system partitions, because it says "Permission denied".
These are some of the fastboot commands i've tried to reflash stock (I looked for the latest Oreo firmware, so as to be sure that I wasn't downgrading):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
exit
...always answering "REMOTE failure". I've tried to describe the problem as thoroughly as I could; I hope someone can gimme a hand :good:

Iv_Milh said:
Hi guys, this is my first post here in XDA, and i'm kinda desperate... a couple of weeks ago my Moto G5s Plus (rooted, but with official Nougat firmware) turned itself off overnight, and ever since won't turn on except on Fastboot mode. Every time I try to Start the device normally, the Bootloader Logs appear with the message "Start up failed; failed to validate boot image". The same thing happens when I try to go into Factory or even Recovery mode (instead of failed to validate boot image, it says, failed to validate recovery image).
When I plug it into my PC, it is recognized but only as Android Bootloader Mode. I've tried different files of official firmware in order to flash them via fastboot, but it's no use... it just says "Preflash validation failed", and so on.
When I enter the command getvar_all, this is what it shows:
C:\Users\IVAN\Sanders\Stock\Third>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: 229d978d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 881733DA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.06-0-g1e22c44
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
Finished. Total time: 0.250s
I've noticed that both the CID and the IMEI are gonners, but as I can't flash anything, there's no way of trying the "Validus" method to restore the IMEI (which I've already done a couple of months ago, after the first root).
I've tried by setting my PC into Test Mode, so as to "skip" the validation of the flash images, but it shows the exact same message. RSD Lite won't even show my device when plugged. I couldn't erase user data, cache or even system partitions, because it says "Permission denied".
These are some of the fastboot commands i've tried to reflash stock (I looked for the latest Oreo firmware, so as to be sure that I wasn't downgrading):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
exit
...always answering "REMOTE failure". I've tried to describe the problem as thoroughly as I could; I hope someone can gimme a hand :good:
Click to expand...
Click to collapse
friend I have the same problem, I think it is the firmware that is used, the one that should be used is the NPSS26.116-26-4

Matiasnck said:
friend I have the same problem, I think it is the firmware that is used, the one that should be used is the NPSS26.116-26-4
Click to expand...
Click to collapse
Hi Matias, thanks for answering. I've already tried with several firmware files, the latest one being SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, always getting the same errors. Do you think that by using a specific file, the "Preflash valitation failed" errors should stop? I'll try again with that file you suggested, and see what happens... I hope it works; I'm not sure, but I think I've already tried that one.
The Moto drivers are allegedly ok, and I've downloaded again Minimal ADB, so I'm trying to convince myself those aren't the ones keeping me from reflashing.

Iv_Milh said:
Hi Matias, thanks for answering. I've already tried with several firmware files, the latest one being SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, always getting the same errors. Do you think that by using a specific file, the "Preflash valitation failed" errors should stop? I'll try again with that file you suggested, and see what happens... I hope it works; I'm not sure, but I think I've already tried that one.
The Moto drivers are allegedly ok, and I've downloaded again Minimal ADB, so I'm trying to convince myself those aren't the ones keeping me from reflashing.
Click to expand...
Click to collapse
I still have the same problem, I will try a new computer, maybe that's it?

Matiasnck said:
I still have the same problem, I will try a new computer, maybe that's it?
Click to expand...
Click to collapse
The only way that by using another computer the error would stop, would be that the drivers in your current pc aren't the ones you're supposed to have, in my opinion. Try it, anyways... there's nothing to lose.

Hi , please try this and let me know if it works or not, thanks
https://github.com/laginimaineb/Alohamora?files=1

whodat711 said:
Hi , please try this and let me know if it works or not, thanks
https://github.com/laginimaineb/Alohamora?files=1
Click to expand...
Click to collapse
Can you explain what I should do with that?

Could you solve it?

Try lenovo smart assistant
https://support.lenovo.com/us/en/downloads/ds101291

whodat711 said:
Try lenovo smart assistant
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
I am new to this thread, but I found this and THANK YOU! I hope this will save my day!

whodat711 said:
Hi , please try this and let me know if it works or not, thanks
https://github.com/laginimaineb/Alohamora?files=1
Click to expand...
Click to collapse
Hi, thanks for the reply; could you please explain what I should do with that? I see the python files, but i'm not sure on how to use them.

whodat711 said:
Try lenovo smart assistant
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
I've already tried it, but so far it has failed to whether recognize my device, or just got stuck in the process of reading it. Motorola Device Manager, Software Upgrade Assistant, RSD Lite, Wondershare... none of them have worked for me.