i have one xt1575 moto x pure in bricked state fastboot doesn't except any command
following error on fastboot
start 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 software repair assistant
here is the getvar all info
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.1C(*)
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: b3deb886
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 295D7A001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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) 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) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.1C-0-ge29f91e
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.047s
Click to expand...
Click to collapse
can anyone help with this issue bootloader was locked and get_unlock_data command also not success
mfastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.005s
Click to expand...
Click to collapse
mfastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.003s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (40960 KB)...
OKAY [ 1.434s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.452s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash bootlaoder bootloader.img
target max-sparse-size: 256MB
sending 'bootlaoder' (2699 KB)...
OKAY [ 0.135s]
writing 'bootlaoder'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.190s
E:\motorola\X_Pure_XT1575_CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml>mfastboot flash modem non-hlos.bin
target max-sparse-size: 256MB
sending 'modem' (41675 KB)...
OKAY [ 1.369s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.383s
Click to expand...
Click to collapse
device start up failed
What Android version did you have before the trouble occurred? It looks like you are trying to downgrade, which isn't possible with a locked bootloader. When your bootloader is locked you must flash the same or newer Android version, all others will fail.
Thanks For Your Reply.
I returned this phone to customer but I receive one more moto x pure xt1575 with imei 0 issue i tried all modem but still imei 0
I also erased the modemst1 and modemst2 and then flash the correct fsg then still imei 0. In this phone bootloader status is engineering. How to solve this issue?
Shabby The Dev said:
Thanks For Your Reply.
I returned this phone to customer but I receive one more moto x pure xt1575 with imei 0 issue i tried all modem but still imei 0
I also erased the modemst1 and modemst2 and then flash the correct fsg then still imei 0. In this phone bootloader status is engineering. How to solve this issue?
Click to expand...
Click to collapse
Any phone with bootloader status "Engineering" should be returned to Motorola... It is not in a fully unlocked state and it is not intended for normal use (and no, it is not some "special" unlock above a regular bootloader unlock as some people say)
https://forums.lenovo.com/t5/MOTORO...g-and-Unlocked-bootloader-status/td-p/3420219
Recently acquired a bricked moto x pure. No way of knowing for sure how it was bricked but I'm guessing attempted downgrade. When starting up the Bootloader logs say:
AP fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from charger boot mode
CID read failure
Invalid CID status 0x69
Click to expand...
Click to collapse
fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48(*)
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA084034CW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 3862CC001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 10-07-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 9 14:23:32 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6898f68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Sat Jan 30 14:35:02 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.422s
Click to expand...
Click to collapse
I attempted to flash the CLARK_RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml stock firmware but got the following error:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.094s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.953s
Click to expand...
Click to collapse
I also tried using mfastboot, with the same results. Anybody know how to fix this?
Is your bootloader locked?
thebaconbox said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yes it is. Tried to unlock it already but I get:
>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
acejavelin said:
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
Click to expand...
Click to collapse
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.961s
>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.141s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.234s
Click to expand...
Click to collapse
I get the same errors if I try to flash anything.
jml1290 said:
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
I get the same errors if I try to flash anything.
Click to expand...
Click to collapse
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
acejavelin said:
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
Click to expand...
Click to collapse
Here's what I get:
>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.000s
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.561s
Click to expand...
Click to collapse
jml1290 said:
Here's what I get:
Click to expand...
Click to collapse
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
acejavelin said:
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
Click to expand...
Click to collapse
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
jml1290 said:
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
Click to expand...
Click to collapse
Sorry... But if the bootloader is locked you might be able to register it on your Motorola account and file a warranty claim, couldn't hurt to try.
Hi, Sorry for the bad translation, I'm from Argentina and use an online translator
before posting try several solutions from this and other forums, but do not achieve anything until now.
A friend brought me a moto g4 xt1621 to which I installed a custom rom and made it brick, I was trying to install several stock roms and none worked, the phone turns on but does not pass the warning screen:
Your device has been unlocked and can't be trusted
To learn more visit:
motorola.com/unlockbootloader
ID:bad key
Your device will boot in 5 seconds.
that message is repeated every 5 seconds in an infinite loop and does not pass from there.
I have installed the Motorola drivers, android studio with the SDK, and platform-tools with adb and fastboot
the phone connects well with the pc
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot devices
ZY223FFBZJ fastboot
Click to expand...
Click to collapse
and the fastboot getvar all command throws this
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223FFBZJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: 37E01A0100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: la:
(bootloader) meid:
(bootloader) date: 09-16-2016
(bootloader) sku: XT1621
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 17 18:59:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-23.4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.24.4.athene.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70004.04.03.32R ATHENE_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld30) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sat May 14 20:58:01 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
all: listed above
Finished. Total time: 0.109s
Click to expand...
Click to collapse
this is the last rom I tried to install and it did not work either:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info
and the image of boot and recovery gives me an error key bad key
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.844s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.563s]
Finished. Total time: 1.610s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.828s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.609s]
Finished. Total time: 1.625s
Click to expand...
Click to collapse
can someone please tell me if there is a solution for this or the phone is unrecoverable
thank you very much
Curious did getvar variables change after you tried to flash the NPJ version? What does the getvar all show now?
superceege said:
Curious did getvar variables change after you tried to flash the NPJ version? What does the getvar all show now?
Click to expand...
Click to collapse
thanks x answer
I do not change anything, before and after it shows the same thing, but in the windows console (cmd) and in bootloader log it shows everything well
Those bad key messages are normal when flashing a stock ROM with an unlocked bootloader, if I recall.
Looks like from your getvar log that you have a Marshmallow stock ROM but the Nougat bootloader, at least the Dec 2017 Nougat bootloader (the B1:07 bootloader was on the Dec 2017, Feb 2018 and April 2018 firmwares).
Can we see the log of what happens when you flash the April 2018 NPJS25.93-14-18 firmware please?
Also, which custom ROM did you try to flash and what happened to make the device brick?
thanks for your attention
the flash process seems normal
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot devices
ZY223FFBZJ fastboot
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.004s]
Finished. Total time: 0.006s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
Sending 'partition' (32 KB) OKAY [ 0.013s]
Writing 'partition' (bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.105s]
Finished. Total time: 0.312s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
Sending 'bootloader' (3651 KB) OKAY [ 0.233s]
Writing 'bootloader' (bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.526s]
Finished. Total time: 0.954s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
Sending 'logo' (2186 KB) OKAY [ 0.140s]
Writing 'logo' OKAY [ 0.085s]
Finished. Total time: 0.419s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.976s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.582s]
Finished. Total time: 1.755s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.968s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.616s]
Finished. Total time: 1.778s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.945s]
Writing 'dsp' OKAY [ 0.442s]
Finished. Total time: 1.579s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash oem oem.img
(bootloader) has-slotem: not found
Sending 'oem' (96490 KB) OKAY [ 5.667s]
Writing 'oem' OKAY [ 2.455s]
Finished. Total time: 8.320s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
Sending 'system' (261013 KB) OKAY [ 15.346s]
Writing 'system' OKAY [ 6.736s]
Finished. Total time: 22.274s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
Sending 'system' (250846 KB) OKAY [ 14.594s]
Writing 'system' OKAY [ 6.469s]
Finished. Total time: 21.258s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
Sending 'system' (254613 KB) OKAY [ 14.836s]
Writing 'system' OKAY [ 6.550s]
Finished. Total time: 21.583s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
Sending 'system' (261613 KB) OKAY [ 15.235s]
Writing 'system' OKAY [ 6.376s]
Finished. Total time: 21.805s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
Sending 'system' (260927 KB) OKAY [ 15.228s]
Writing 'system' OKAY [ 6.816s]
Finished. Total time: 22.256s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
Sending 'system' (255614 KB) OKAY [ 14.858s]
Writing 'system' OKAY [ 6.402s]
Finished. Total time: 21.456s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
Sending 'system' (253500 KB) OKAY [ 14.653s]
Writing 'system' OKAY [ 6.875s]
Finished. Total time: 21.724s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
Sending 'system' (82497 KB) OKAY [ 4.786s]
Writing 'system' OKAY [ 2.052s]
Finished. Total time: 7.035s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (76958 KB) OKAY [ 4.440s]
Writing 'modem' OKAY [ 1.960s]
Finished. Total time: 6.597s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.035s]
Finished. Total time: 0.231s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.035s]
Finished. Total time: 0.231s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
Sending 'fsg' (2032 KB) OKAY [ 0.128s]
Writing 'fsg' OKAY [ 0.096s]
Finished. Total time: 0.418s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.023s]
Finished. Total time: 0.219s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 0.076s]
Finished. Total time: 0.273s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot erase customize
(bootloader) has-slot:customize: not found
Erasing 'customize' OKAY [ 0.020s]
Finished. Total time: 0.216s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot erase clogo
(bootloader) has-slot:clogo: not found
Erasing 'clogo' OKAY [ 0.022s]
Finished. Total time: 0.216s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.005s]
Finished. Total time: 0.005s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot rebbot
fastboot: usage: unknown command rebbot
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.007s
C:\Users\Marce\AppData\Local\Android\Sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223FFBZJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: 37E01A0100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358216070360003
(bootloader) meid:
(bootloader) date: 09-16-2016
(bootloader) sku: XT1621
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 24 16: 0:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-23.4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.24.4.athene.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70004.04.03.32R ATHENE_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld30) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sat May 14 20:58:01 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
all: listed above
Finished. Total time: 0.168s
Click to expand...
Click to collapse
here the list of commands
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 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
Click to expand...
Click to collapse
Thanks for the flash log and your getvar logs. It looks like that the flash, despite apparently writing, is not being committed to the flash memory. Despite your bootloader being updated to B1:07 (which is the version expected for the April 2018 security patch firmware), your device is, for some reason, not writing the updated system. Your system version is still 6.0.1 (with the May 2016 security patch?). Unfortunately, that may mean a failing flash memory or other hardware fault, especially if you can't flash stock firmware.
I'd try the flash again with a high quality USB cable (preferably the original USB cable if one was provided) and try to use different USB ports. Else, you may have to consider sending it for repair or ask your friend to possibly return it.
Ok I will try to follow your advice, if I find a solution I will post it and if it does not work I will return it to my friend.
I thought it would be easier to fix it.
But if the phone has any hardware failure they will have to take it to the technical service.
Thanks for the help.
Edit: SOLVED. Flashed 8.1.0 October update before rebooting and everything went fine
First I unlocked the bootloader using this guide.
Then I immediately flashed TWRP using this guide from the TWRP site. After rebooting, I was unable to access "Recovery" in the bootloader as I was shown an error message, "Moto G5 Plus is unlocked and can't be trusted, bad key error", as seen in this post. A user on the post said to flash the stock ROM and then reflash TWRP.
I rebooted into bootloader and flashed the Android 7.1 stock rom. While still in the bootloader, I then realized that I messed up and should've flashed the the 8.1.0 stock ROM as that is what the device initially had. I then download the 8.1.0 ROM from here and flash it in fastboot using this guide.
However, while flashing 8.1.0, the following errors were output (I removed the successful outputs):
HTML:
fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.003s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot f
lash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.006s]
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)
Finished. Total time: 0.079s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot f
lash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.383s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.258s]
Finished. Total time: 0.645s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot f
lash recovery recovery.img
Sending 'recovery' (20580 KB) OKAY [ 0.467s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.350s]
Finished. Total time: 0.823s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot e
rase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.007s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot e
rase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.120s
I'm still sitting in the bootloader as I'm afraid of rebooting in fear of potentially hardbricking the device. The
HTML:
image_primary gpt
error in particular seems kind of scary - Googling it, it seems people only encountered it when hardbricking the device.
Here is an output of my
HTML:
fastboot gervar all
:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(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) serialno: removed
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: removed
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: removed
(bootloader) meid:
(bootloader) date: 03-12-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 16 3:38:17 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:8.1.0/OPSS2
(bootloader) ro.build.fingerprint[1]: 8.85-17-2/945e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0000
(bootloader) kernel.version[1]: 4-g7402761 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Wed Oct 10 09:19:54 CDT
(bootloader) kernel.version[4]: 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=MBM-NG-VC0.91-0-g92e5e21-dirty
(bootloader) tz.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) devcfg.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) keymaster.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) prov.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(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
all: listed above
Finished. Total time: 0.273s
Is my device okay, and am I okay to reboot? If something is wrong, is there anything I can do to fix it? Thanks!
Hi team,
I need help. I have a Moto G5 Plus (XT1687). A few weeks ago, it kept rebooting. Went to shut it down. Never rebooted again... After investigation, I understood it was hard bricked. I then followed some guide and managed to get it softbricked. Now, I don't actually remember which blank flash I used, but I have the feeling I used the wrong one (possibly for model XT1686), because I just can't flash anything else now (like Potter).
I don't need or want to root the phone, I just want to go back to the stock OS. I am not actually quite sure if I had Potter v.7 or 8 (or another version?).
I am far from an expert, so I am just trying to follow guides, but I don't really know what I am doing.
Anyway... I tried again to follow this guide https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but I don't actually go far.
Let me explain what I see...
When booting the phone, I get this screen:
https://drive.google.com/file/d/1dgwGtsSLh3VYOaD6PKJhJ2_Z5DpczY0k/view?usp=sharing
I then move to Recovery mode, and*this is what I see:
https://drive.google.com/file/d/18fPYBMkxU2N9P9zD6UB5ouKZ5w3AebQu/view?usp=sharing
In the Windows command prompt, when I type fasboot devices, I get the result
a58c134 fastboot
though nothing shows up on the phone. But I assume this is correct.
Then, when I start typing the first lines of code, I get errors in the command prompt:
https://drive.google.com/file/d/14t-amwAzANZjroGBgsnzOeE6pQgQCUdL/view?usp=sharing
Now, I do see there is some communication going on with the phone, as the phone displays something. This is what I get with the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
https://drive.google.com/file/d/1pujKmNB0zYrswztGXwJYNGNLPCeD0ZQe/view?usp=sharing
So... That's where I am. Don't really know if I managed to flash anything in the phone, but since I get all those issues, I guess that nothing is transferred. Please help!
Glencoe said:
Hi team,
I need help. I have a Moto G5 Plus (XT1687). A few weeks ago, it kept rebooting. Went to shut it down. Never rebooted again... After investigation, I understood it was hard bricked. I then followed some guide and managed to get it softbricked. Now, I don't actually remember which blank flash I used, but I have the feeling I used the wrong one (possibly for model XT1686), because I just can't flash anything else now (like Potter).
I don't need or want to root the phone, I just want to go back to the stock OS. I am not actually quite sure if I had Potter v.7 or 8 (or another version?).
I am far from an expert, so I am just trying to follow guides, but I don't really know what I am doing.
Anyway... I tried again to follow this guide https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but I don't actually go far.
Let me explain what I see...
When booting the phone, I get this screen:
https://drive.google.com/file/d/1dgwGtsSLh3VYOaD6PKJhJ2_Z5DpczY0k/view?usp=sharing
I then move to Recovery mode, and*this is what I see:
https://drive.google.com/file/d/18fPYBMkxU2N9P9zD6UB5ouKZ5w3AebQu/view?usp=sharing
In the Windows command prompt, when I type fasboot devices, I get the result
a58c134 fastboot
though nothing shows up on the phone. But I assume this is correct.
Then, when I start typing the first lines of code, I get errors in the command prompt:
https://drive.google.com/file/d/14t-amwAzANZjroGBgsnzOeE6pQgQCUdL/view?usp=sharing
Now, I do see there is some communication going on with the phone, as the phone displays something. This is what I get with the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
https://drive.google.com/file/d/1pujKmNB0zYrswztGXwJYNGNLPCeD0ZQe/view?usp=sharing
So... That's where I am. Don't really know if I managed to flash anything in the phone, but since I get all those issues, I guess that nothing is transferred. Please help!
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Click to expand...
Click to collapse
Thanks sd_shadow! So this is what I get:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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: 0
(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-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.178s
What should I do know?
Glencoe said:
run
Thanks sd_shadow! So this is what I get:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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: 0
(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-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.178s
What should I do know?
Click to expand...
Click to collapse
Don't suppose you know which software channel it was on?
Verizon, Retail, RetEU...
I would try LMSA'S Flash rescue
Unlikely that will work though.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If you are in the USA and not sure which software channel try RetUS
https://mirrors.lolinet.com/firmware/moto/potter/official
Maybe try mfastboot.exe
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
sd_shadow said:
Don't suppose you know which software channel it was on?
Verizon, Retail, RetEU...
Click to expand...
Click to collapse
I am from Canada, and my carrier is Videotron, though we bougth the (unlocked) phone from Target, in the US, so I'd think the channel may be RetUS indeed.
sd_shadow said:
I would try LMSA'S Flash rescue
Unlikely that will work though.
Click to expand...
Click to collapse
I should have mentioned I had already tried it, and it didn't work indeed. Just checked again, and all it says is "Failed to match the connected device..."
sd_shadow said:
Maybe try mfastboot.exe
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
I followed your guide (my, I realise you are a guru on here!), and tried flashing with mfastboot (while sending each system.img chunck separately, as I have 8 system.img_sparsechunck.* files)... Looks like it failed again!
This is what I get from the Command prompt:
C:\adb\mfastboot-v2>mfastboot devices
a58c134 fastboot
C:\adb\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 2.055s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.076s
C:\adb\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258396 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.388s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256514 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.399s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (246302 KB)...
OKAY [ 7.090s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.104s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.494s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.518s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.507s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.530s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.504s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.524s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (250531 KB)...
OKAY [ 7.203s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.232s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (262059 KB)...
OKAY [ 7.509s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.538s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (254142 KB)...
OKAY [ 7.289s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.318s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.522s
C:\adb\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.643s
C:\adb\mfastboot-v2>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.038s
C:\adb\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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: 0
(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-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.152s
I will try to uninstall all drivers and try again, just in case, but if you see anything else, let me know! I really appreciate your help!
Glencoe said:
I am from Canada, and my carrier is Videotron, though we bougth the (unlocked) phone from Target, in the US, so I'd think the channel may be RetUS indeed.
I should have mentioned I had already tried it, and it didn't work indeed. Just checked again, and all it says is "Failed to match the connected device..."
I followed your guide (my, I realise you are a guru on here!), and tried flashing with mfastboot (while sending each system.img chunck separately, as I have 8 system.img_sparsechunck.* files)... Looks like it failed again!
This is what I get from the Command prompt:
C:\adb\mfastboot-v2>mfastboot devices
a58c134 fastboot
C:\adb\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 2.055s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.076s
C:\adb\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258396 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.388s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256514 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.399s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (246302 KB)...
OKAY [ 7.090s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.104s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.494s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.518s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.507s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.530s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.504s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.524s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (250531 KB)...
OKAY [ 7.203s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.232s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (262059 KB)...
OKAY [ 7.509s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.538s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (254142 KB)...
OKAY [ 7.289s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.318s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.522s
C:\adb\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.643s
C:\adb\mfastboot-v2>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.038s
C:\adb\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(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: 0
(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-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.152s
I will try to uninstall all drivers and try again, just in case, but if you see anything else, let me know! I really appreciate your help!
Click to expand...
Click to collapse
Well I'm not hopeful.
You could try
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
Sent from my jerry_cheets using XDA Labs
sd_shadow said:
Well I'm not hopeful.
You could try
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
Click to expand...
Click to collapse
This is something I had already tried... Without luck!
C:\adb\mfastboot-v2>mfastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.025s]
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.137s
C:\adb\mfastboot-v2>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (5115 KB)...
OKAY [ 0.153s]
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.284s
C:\adb\mfastboot-v2>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2186 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.102s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.509s
Am I using the right firmware? I tried with the Potter RETUS 8.1.0...
Could it be that the bootloader is locked? If so, how do I unlock it?
Should I try to flash a blank file again? If so, how?
Or should I try to flash a bootable image on an SD card?
I am willing to try anything you can think of. This phone is already useless as is, so I have nothing to lose... I like challenges, but this one is very frustrating! But it is also a great learning experience!
Glencoe said:
T
Am I using the right firmware? I tried with the Potter RETUS 8.1.0...
Click to expand...
Click to collapse
I don't know, getvar isn't giving enough info to tell.
Do you remember where you found the blankflash?
Could you upload it somewhere? Drive, Mega, ...
Could it be that the bootloader is locked? If so, how do I unlock it?
Click to expand...
Click to collapse
bootloader is locked
Code:
(bootloader) securestate: oem_locked
Very unlikely you could unlock the bootloader as
OEM unlocking must be allowed in Dev options
which requires the phone to boot normally
but you could try
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Should I try to flash a blank file again? If so, how?
Or should I try to flash a bootable image on an SD card?
Click to expand...
Click to collapse
Unfortunately, these are not options
The device needs to be in emergency download mode (edl)
There is no way to enter edl with a locked bootloader.
I am willing to try anything you can think of. This phone is already useless as is, so I have nothing to lose... I like challenges, but this one is very frustrating! But it is also a great learning experience!
Click to expand...
Click to collapse
sd_shadow said:
I don't know, getvar isn't giving enough info to tell.
Do you remember where you found the blankflash?
Could you upload it somewhere? Drive, Mega, ....
Click to expand...
Click to collapse
I don't actually remember where I got the blankflash, but I know I have 2 files, and I think I used the wrong one (XT1686)... Maybe that's the issue...
Those are the 2 files I have:
Don't remember, possibly XT1687: https://drive.google.com/file/d/1A5fpqO6tVSGJfQynwjlDex0LS4-yuMm9/view?usp=sharing
XT1686: https://drive.google.com/file/d/19pa9aR0j110Yk07wdwQ-AY-yHoH0nvw0/view?usp=sharing
Let me know what you think! If you have a better version, I am willing to try, if there is still a way to flash it...
sd_shadow said:
bootloader is locked
Code:
(bootloader) securestate: oem_locked
Click to expand...
Click to collapse
That's what I thought...
sd_shadow said:
Very unlikely you could unlock the bootloader as
OEM unlocking must be allowed in Dev options
which requires the phone to boot normally
but you could try
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Click to expand...
Click to collapse
I'll give it a try!
sd_shadow said:
Unfortunately, these are not options
The device needs to be in emergency download mode (edl)
There is no way to enter edl with a locked bootloader.
Click to expand...
Click to collapse
In other words, there is no much hope to revive it...
Glencoe said:
I don't actually remember where I got the blankflash, but I know I have 2 files, and I think I used the wrong one (XT1686)... Maybe that's the issue...
Those are the 2 files I have:
Don't remember, possibly XT1687: https://drive.google.com/file/d/1A5fpqO6tVSGJfQynwjlDex0LS4-yuMm9/view?usp=sharing
XT1686: https://drive.google.com/file/d/19pa9aR0j110Yk07wdwQ-AY-yHoH0nvw0/view?usp=sharing
Let me know what you think! If you have a better version, I am willing to try, if there is still a way to flash it...
That's what I thought...
I'll give it a try!
In other words, there is no much hope to revive it...
Click to expand...
Click to collapse
I guess you could try RetIN I think it's the only XT1686 firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETIN/
sd_shadow said:
I guess you could try RetIN I think it's the only XT1686 firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETIN/
Click to expand...
Click to collapse
Really? Knowing my phone is XT1687? Or should I try it if I flashed the XT1686 blankflash?
Glencoe said:
Really? Knowing my phone is XT1687? Or should I try it if I flashed the XT1686 blankflash?
Click to expand...
Click to collapse
At this point I don't think it will hurt anything.
Sent from my ali using XDA Labs
sd_shadow said:
At this point I don't think it will hurt anything.
Click to expand...
Click to collapse
You're right! But I will try you other suggestion to unlock first and see how it goes (hopefully later today). Will let you know the outcome! Thanks for helping me! I really appreciate it!