Moto G4 Play issue. NEED HELP! (Permission denied boot loader cid: 0xDEAD ) - Moto G4 Play Questions & Answers

Hello Everyone!
Well.. I managed to hard brick my moto g4 play.
I was able to blankflash my device back to the bootloader... however I am now having another issue.
I attempted the following based off other guides here. bellow is everything I have attempted to unlock my boot loader and try to reflash ROM
moto g4 play XT1601
link for blankflash for those who are looking : https://forum.xda-developers.com/g4-play/help/hardbrik-moto-g4-play-xt1603-blankflash-t3745245/page2
Code:
.\fastboot.exe oem fb_mode_set
.\fastboot.exe flash partition gpt.bin
.\fastboot.exe flash logo logo.bin
.\fastboot.exe flash boot boot.img
.\fastboot.exe flash recovery recovery.img
.\fastboot.exe flash system system.img_sparsechunk.0
.\fastboot.exe flash system system.img_sparsechunk.1
.\fastboot.exe flash system system.img_sparsechunk.2
.\fastboot.exe flash system system.img_sparsechunk.3
.\fastboot.exe flash system system.img_sparsechunk.4
.\fastboot.exe flash system system.img_sparsechunk.5
.\fastboot.exe flash system system.img_sparsechunk.6
.\fastboot.exe flash system system.img_sparsechunk.7
.\fastboot.exe flash oem oem.img
.\fastboot.exe flash modem NON-HLOS.bin
.\fastboot.exe erase modemst1
.\fastboot.exe erase modemst2
.\fastboot.exe flash fsg fsg.mbn
.\fastboot.exe erase cache
.\fastboot.exe erase userdata
.\fastboot.exe erase customize
.\fastboot.exe erase clogo
.\fastboot.exe erase DDR
.\fastboot.exe oem fb_mode_clear
.\fastboot.exe reboot
this is the output.
Code:
PS C:\Users\giuse\Desktop\XT1601_HARPIA_BELL_MPIS24.241-15.3-7_cid50_subsidy-BELLCA_regulatory-DEFAULT_CFC.xml> .\fastbo
ot.exe flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.458s
PS C:\Users\giuse\Desktop\XT1601_HARPIA_BELL_MPIS24.241-15.3-7_cid50_subsidy-BELLCA_regulatory-DEFAULT_CFC.xml> .\fastbo
ot.exe flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 268435456 bytes
sending 'logo' (1216 KB)...
OKAY [ 0.045s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.058s
When I attempt to unlock the bootloader
Code:
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.213s
PS C:\Users\giuse\Desktop\platform-tools> .\fastboot.exe oem unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.204s
Code:
PS C:\Users\-\Desktop\platform-tools> .\fastboot.exe oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
Code:
PS C:\Users\\Desktop\platform-tools> .\fastboot.exe getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-81.12(*)
(bootloader) product: harpia
(bootloader) board: harpia
(bootloader) secure: yes
(bootloader) hwrev: 0x81B0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=08 PRV=07 TYPE=57
(bootloader) ram: 2GB Samsung S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: d432e4d1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: CAEE1A1F00000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 268435456
(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) aboot.git: git=MBM-NG-V81.12-0-gf9417da
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.469s

Same problem
Zep2 said:
Hello Everyone!
Well.. I managed to hard brick my moto g4 play.
I was able to blankflash my device back to the bootloader... however I am now having another issue.
I attempted the following based off other guides here. bellow is everything I have attempted to unlock my boot loader and try to reflash ROM
moto g4 play XT1601
link for blankflash for those who are looking : https://forum.xda-developers.com/g4-play/help/hardbrik-moto-g4-play-xt1603-blankflash-t3745245/page2
Code:
.\fastboot.exe oem fb_mode_set
.\fastboot.exe flash partition gpt.bin
.\fastboot.exe flash logo logo.bin
.\fastboot.exe flash boot boot.img
.\fastboot.exe flash recovery recovery.img
.\fastboot.exe flash system system.img_sparsechunk.0
.\fastboot.exe flash system system.img_sparsechunk.1
.\fastboot.exe flash system system.img_sparsechunk.2
.\fastboot.exe flash system system.img_sparsechunk.3
.\fastboot.exe flash system system.img_sparsechunk.4
.\fastboot.exe flash system system.img_sparsechunk.5
.\fastboot.exe flash system system.img_sparsechunk.6
.\fastboot.exe flash system system.img_sparsechunk.7
.\fastboot.exe flash oem oem.img
.\fastboot.exe flash modem NON-HLOS.bin
.\fastboot.exe erase modemst1
.\fastboot.exe erase modemst2
.\fastboot.exe flash fsg fsg.mbn
.\fastboot.exe erase cache
.\fastboot.exe erase userdata
.\fastboot.exe erase customize
.\fastboot.exe erase clogo
.\fastboot.exe erase DDR
.\fastboot.exe oem fb_mode_clear
.\fastboot.exe reboot
this is the output.
Code:
PS C:\Users\giuse\Desktop\XT1601_HARPIA_BELL_MPIS24.241-15.3-7_cid50_subsidy-BELLCA_regulatory-DEFAULT_CFC.xml> .\fastbo
ot.exe flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.458s
PS C:\Users\giuse\Desktop\XT1601_HARPIA_BELL_MPIS24.241-15.3-7_cid50_subsidy-BELLCA_regulatory-DEFAULT_CFC.xml> .\fastbo
ot.exe flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 268435456 bytes
sending 'logo' (1216 KB)...
OKAY [ 0.045s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.058s
When I attempt to unlock the bootloader
Code:
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.213s
PS C:\Users\giuse\Desktop\platform-tools> .\fastboot.exe oem unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.204s
Code:
PS C:\Users\-\Desktop\platform-tools> .\fastboot.exe oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
Code:
PS C:\Users\\Desktop\platform-tools> .\fastboot.exe getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-81.12(*)
(bootloader) product: harpia
(bootloader) board: harpia
(bootloader) secure: yes
(bootloader) hwrev: 0x81B0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=08 PRV=07 TYPE=57
(bootloader) ram: 2GB Samsung S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: d432e4d1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: CAEE1A1F00000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 268435456
(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) aboot.git: git=MBM-NG-V81.12-0-gf9417da
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.469s
Click to expand...
Click to collapse
Well Iam also facing the same problem. Its showing Preflash Validation Failure.

no fix currently
V Bala Krishnan said:
Well Iam also facing the same problem. Its showing Preflash Validation Failure.
Click to expand...
Click to collapse
no fix currently still waiting to hear back from some community memebers.

UP

same fault
sorry for my bad english, I have the same fault, waiting for a solution

hey, i was exactly at ur position. after a month research i found it.try this https://www.youtube.com/watch?v=IRa97F14RKE&app=desktop make use of the files in the description not the video. just flash it like u flash a stock rom. and it'd be good to go. the reason for it is we need to find the exact stock nougat rom and roms available on the internet doesn't work except this!

keerthi perumal said:
hey, i was exactly at ur position. after a month research i found it.try this https://www.youtube.com/watch?v=IRa97F14RKE&app=desktop make use of the files in the description not the video. just flash it like u flash a stock rom. and it'd be good to go. the reason for it is we need to find the exact stock nougat rom and roms available on the internet doesn't work except this!
Click to expand...
Click to collapse
Can we recover the Hardbricked Moto G4 play from it ?

Yes u can

keerthi perumal said:
hey, i was exactly at ur position. after a month research i found it.try this https://www.youtube.com/watch?v=IRa97F14RKE&app=desktop make use of the files in the description not the video. just flash it like u flash a stock rom. and it'd be good to go. the reason for it is we need to find the exact stock nougat rom and roms available on the internet doesn't work except this!
Click to expand...
Click to collapse
Hey Superb It worked for me. Thanks a lot yar

keerthi perumal said:
hey, i was exactly at ur position. after a month research i found it.try this https://www.youtube.com/watch?v=IRa97F14RKE&app=desktop make use of the files in the description not the video. just flash it like u flash a stock rom. and it'd be good to go. the reason for it is we need to find the exact stock nougat rom and roms available on the internet doesn't work except this!
Click to expand...
Click to collapse
Not work for me:crying:

elandaetam said:
Not work for me:crying:
Click to expand...
Click to collapse
So what exactly the problem was ? What's does it showing ?

V Bala Krishnan said:
So what exactly the problem was ? What's does it showing ?
Click to expand...
Click to collapse
The errors are: preflash validation, when loading any bootloader.img or gpt.bin
o Permission denied bootloader, in addition to having CID: 0xdead

Same error for me
elandaetam said:
The errors are: preflash validation, when loading any bootloader.img or gpt.bin
o Permission denied bootloader, in addition to having CID: 0xdead
Click to expand...
Click to collapse
I have the same error when flashing using the "flash rom nougat.bat" file inside the video's description, also i couldn't flash the blankflash because qualcomm driver not detects the phone.

Related

xt1575 invalid cid status 0x69 flash failed

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

Stuck in fastboot, unable to flash stock firmware

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.

Flashing back to Stock, Trying to understand Errors

So I ran into some issues installing LOS15 and flashed back to stock using POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Being paranoid I am concerned about the errors I have gotten, mainly because if the ROM messed with my system and I cannot replace it, well, who know what nefarious actions might be taking place.
I have booted the system and it works fine, but again, just being cautious.
Here are the errors:
Code:
[B]fastboot flash partition gpt.bin[/B]
sending 'partition' (45 KB)...
OKAY [ 0.005s]
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.074s
[B]fastboot flash bootloader bootloader.img[/B]
sending 'bootloader' (5115 KB)...
OKAY [ 0.233s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.510s
[B]sudo fastboot flash boot boot.img [/B]
ending 'boot' (16384 KB)...
OKAY [ 0.771s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.442s]
finished. total time: 1.213s
[B]sudo fastboot flash recovery recovery.img [/B]
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.973s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.532s]
[B]
sudo fastboot erase customize[/B]
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
[B]sudo fastboot erase clogo [/B]
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
Is your moto g5 plus reteu?
InsaneNexuS said:
Is your moto g5 plus reteu?
Click to expand...
Click to collapse
I guess you meant retail? Yeah, it is retail. No amazon ads.
Well I need to know if it was reteu software channel. Otherwise it wont work for you. Maybe because your not flashing the right files? Mine was RETEU, which means its a european model.
No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.
Well then you need to find the right firmware for you US model. And start with locking the bootloader. And flash every line one by one (copy paste). Dont copy all of them and paste them otherwise it wont work. You really have to do it one by one.
Bootloader relock commands:
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 boot boot.img
fastboot oem lock
After you locked the bootloader start flashing the firmware. Use this site to find the right firmware:https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I gues you should try the one that says RETAIL in the name.
---------- Post added at 23:01 ---------- Previous post was at 22:59 ----------
NODE06 said:
No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.
Click to expand...
Click to collapse
Well if you have done it before then I guess I don't really know what the problem is
Here's what happened putting in that code:
Code:
sudo fastboot oem lock
[sudo] password for user:
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
sudo fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.012s]
finished. total time: 0.012s
sudo fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75638 KB)...
OKAY [ 3.432s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.499s
I guess I would just like to know why this is happening. like what does "(bootloader) Security version downgrade" even mean?
Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).
acejavelin said:
Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).
Click to expand...
Click to collapse
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s
NODE06 said:
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s
Click to expand...
Click to collapse
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.
acejavelin said:
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.
Click to expand...
Click to collapse
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?
NODE06 said:
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?
Click to expand...
Click to collapse
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.
acejavelin said:
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.
Click to expand...
Click to collapse
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.
NODE06 said:
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.
Click to expand...
Click to collapse
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.
acejavelin said:
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.
Click to expand...
Click to collapse
He's flashing a stock.zip I believe.
aaronrw said:
He's flashing a stock.zip I believe.
Click to expand...
Click to collapse
Not with fastboot...
@NODE06 What exactly are you flashing and how?
acejavelin said:
Not with fastboot...
@NODE06 What exactly are you flashing and how?
Click to expand...
Click to collapse
I am flashing
POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
on Linux using ADB, yes, fastboot. I have done it often enough on this phone and used to do it on my G4.
I am wondering, looking at the flashfile.xml, if I should flash them in the same order they are listed in that file. But again, it does not make sense since the only think I did was install Lineage 15 when I was running Resurrection. I will try again to repair with TWRP, maybe I am missing something.
I am back on Resurrection and things are running fine, but I am concerned now that Lineage 15 might be doing some really weird stuff.
I notice the flashfile.xml has
Code:
<sparsing enabled="true" max-sparse-size="536870912"/>
<step operation="getvar" var="max-sparse-size"/>
in it.
Do they matter at all?
When I run the fastboot command I get a different number
Code:
sudo fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.008s
So, I fixed it. And yeah, you need to fastboot stock in the same order as the flashfile.xml and include the getvar max-sparse-size. Here is what worked for me. I got no errors besides the "bad key" for boot and recovery images.
Code:
sudo fastboot getvar max-sparse-size
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash oem oem.img
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase DDR
sudo fastboot oem fb_mode_clear
sudo fastboot reboot

Simple Moto G4 Question

Motorola G4 XT1625
Minor Problem: Phone will not start normally, only boots into Fastboot mode.
Minor Problem: Phone is oem Locked
Major Problem: I never went into "settings" on the phone and ENABLED OEM UNLOCKING.
Question: Is it possible to recover this phone or am I spinning my wheels here?
A little background. Not a developer, just trying to get my phone running again. I have installed Moto tools on my PC, requested and received an unlock code, connected to the phone and can send commands via command line. I understand what the issue is, and hindsight says I should have enabled the phone for development on day 1 based on the risk of an OTA update failure. I've read nearly every forum post regarding this topic, just haven't got clear answer as to if this phone is recoverable.
Oh, and if this looks slightly familiar, its a repost of a thread I started in the general Android help and Q&A forum. I received an email from Brandon, chief admin, letting me know I may receive more info from the MOTO G4 forum.
Thanks in advance.....
Hello there, if the phone boots only into fastboot mode it may be that Stock OS has been wiped, therefore having no OS would reboot the phone every time. When you unlock the bootloader the user data gets erased and the phone goes into factory reset, however, you didn't have OEM unlocked. I don't see if it should be an issue right now.
What I would do is trying to find the stock ROM of your G4, and re flashing it. What I also would do is just try to flash recovery thru fastboot and see if it works.
Quick question, do you see the unlocked boot loader message when you boot your phone ? (this phone cannot be trusted blah blah)
Let me know if it works either way. I don't think OEM lock should be an issue if the system partition has been erased. You got an unlock code and used it.
Good luck!
If you can remember what firmware you had before attempting to unlock your bootloader, you can find a lot of the athene firmwares here: https://androidfilehost.com/?a=show&w=files&flid=72578
For US Nougat devices, I recall the latest build is NPJ25.93-14.7 (though there are reports that there is a newer build being deployed).
That's an odd issue to experience though - can you remember what happened to your device? Was there a factory reset or an erase command issued? A locked bootloader normally should not permit you to erase the system.
With OEM unlocking disabled, you likely would have been blocked from being able to unlock your bootloader. However, by requesting the unlock key, Motorola has a record of the request against your IMEI, so may refuse to service your device under the now voided warranty. Perhaps the best bet at this moment in time is to try a stock ROM reflash.
If you can't remember what stock firmware you had, or want a confirmation, then I'd like to see your getvar info please:
1)Boot to bootloader, connect your device to your computer.
2)In the ADB terminal, type 'fastboot getvar all' without quotes, press Enter on your keyboard.
3)Paste the output into a post here, you may wish to remove your IMEI. This output should be a list of your device variables and give us an idea of the state of your device.
Thank you both for help here.
Quick question, do you see the unlocked boot loader message when you boot your phone ? (this phone cannot be trusted blah blah)
No, the phone will not boot in any mode, factory,recovery,etc, and comes back with
Start Up Failed:
AP Fastboot Flash Mode (secure)
Fastboot reason : UTAG "bootmode" configured as fastboot
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
As to the pre-failure status, the phone was fine after the last upgrade, I believe in late December or early January. I also noticed that the internal storage was running thin so I uninstalled some unused apps as well as using the storage/apps/ clear cache method to get the unused space back to about 3GB unused. No problems after that either. The problem started with the phone doing one of two things, it either shut down such that I had to hold the power button down for 30 sec to start/reboot the phone, or would it simply do a full reboot on its own. The period between these events varied, sometimes a matter of minutes, other times a day or two. It did this for about a week until it booted into the mode I described earlier.
The following is the requested data from the phone,
Thanks again for your help
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(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: 1
(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: ********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: ***********
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: ***********
(bootloader) meid:
(bootloader) date: 01-11-2017
(bootloader) sku: XT1625
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 24 17:32:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:7.0/NPJS25.
(bootloader) ro.build.fingerprint[1]: 93-14.7-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.246.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.64R ATHENE_RETUSA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcb2b19d (hudsoncm
(bootloader) kernel.version[1]: @ilclbld30) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Nov 23 16:36:43 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=a970ead
(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 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.280s
Thank you for your patience, I'm starting to come up the learning curve a little bit.
I did go to the AndroidFileHost site and downloaded what looked like the most recent Athene set of files, based on its upload date and version number.
My limited knowledge tells me that this is older than the firmware loaded on the phone and will not load (see errors below)(security version downgrade)
I've only included 2 of the failures, I assume that is enough info....
****************************
fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.051s
fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.554s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.727s
*******************************************
I was following these instructions, adapting to fit the files that came in the down load
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
fastboot reboot
Makettle said:
Thank you for your patience, I'm starting to come up the learning curve a little bit.
I did go to the AndroidFileHost site and downloaded what looked like the most recent Athene set of files, based on its upload date and version number.
My limited knowledge tells me that this is older than the firmware loaded on the phone and will not load (see errors below)(security version downgrade)
I've only included 2 of the failures, I assume that is enough info....
****************************
fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.051s
fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.554s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.727s
*******************************************
I was following these instructions, adapting to fit the files that came in the down load
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
fastboot reboot
Click to expand...
Click to collapse
Thanks for the getvar info. That suggests you have the NPJ25.93-14.7-3 US retail firmware (December 2017 security patch). Unfortunately, we don't have that firmware leaked to us yet - hopefully someone can capture the correct firmware from Motorola.
As you've correctly surmised, the firmwares we've got are too old for your device, and particularly as your bootloader is locked, the locked bootloader is rejecting any firmware that is older than the current version (as locked bootloaders do not permit firmware downgrades).
You could refer your device to a service centre and see if they can flash the latest firmware onto your device (and hopefully not charge you), or wait for a retail NPJ25.93-14.7-3 stock firmware to 'unofficially' appear.
Thanks Echo92, the help has been greatly appreciated.
It was an Ah Ha moment with your last message when I realized I could see the version of firmware from the getvar info, like I said I'm coming up the learning curve, just been a slow climb.......
I have contacted Motorola service about the phone, the response I received was that the G4 is not repairable, I could purchase a replacement for $90, which when you think about it is not a bad deal, but they only offered it with a 90 day warranty. I did not specifically ask about them simply re-flashing it, so I'm not sure if that was an option or not.
In case your curious, I've since replaced the phone, different brand, but will keep this one as a backup if I can eventually get the firmware re-loaded (hoping that it is not hardware related problem)
Thanks again

Need help my Moto g5plus hard brick dead solution

Hi everybody today I want to flash pixel rom pie 9
but Why I don't know my phone to have hardbrick,
I can try to unlock bootloader again, but I still the code on CMD
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
Can help me pls
Sorry for my language
terawoot said:
Hi everybody today I want to flash pixel rom pie 9
but Why I don't know my phone to have hardbrick,
I can try to unlock bootloader again, but I still the code on CMD
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
Can help me pls
Sorry for my language
Click to expand...
Click to collapse
PS C:\Users\Skincat\Desktop\motog5+\mfastboot> fastboot getvar all
(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: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB 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: 5f9fd45e
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 8B55166800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(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.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.078s
terawoot said:
PS C:\Users\Skincat\Desktop\motog5+\mfastboot> fastboot getvar all
(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: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB 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: 5f9fd45e
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 8B55166800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(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.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.078s
Click to expand...
Click to collapse
then now I still only this
(bootloader) Not in unlocked state
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
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.088s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.366s
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.055s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.098s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.378s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.564s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.464s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.689s
target reported max download size of 534773760 bytes
sending 'system' (256557 KB)...
OKAY [ 5.579s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.641s
target reported max download size of 534773760 bytes
sending 'system' (256617 KB)...
OKAY [ 5.564s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.599s
target reported max download size of 534773760 bytes
sending 'system' (253985 KB)...
OKAY [ 5.563s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.596s
target reported max download size of 534773760 bytes
sending 'system' (256710 KB)...
OKAY [ 5.563s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.589s
target reported max download size of 534773760 bytes
sending 'system' (256912 KB)...
OKAY [ 5.573s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.579s
target reported max download size of 534773760 bytes
sending 'system' (257861 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.609s
target reported max download size of 534773760 bytes
sending 'system' (260027 KB)...
OKAY [ 5.639s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.679s
target reported max download size of 534773760 bytes
sending 'system' (257785 KB)...
OKAY [ 5.567s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.610s
target reported max download size of 534773760 bytes
sending 'system' (257830 KB)...
OKAY [ 5.563s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.600s
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 1.555s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.583s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.004s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.019s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.111s
error: cannot load 'BTFM.bin'
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.008s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
...
(bootloader) Not in unlocked state
OKAY [ 0.086s]
finished. total time: 0.087s
rebooting...
Are you trying to flash a firmware or unlock the bootloader? Anyways the firmware you are trying to flash isn't the latest. It won't downgrade. Try the latest firmware.
Your bootloader seems to be locked.
You need to unlock that first. Try turning on OEM unlock from developer settings and then try the unlock data command.
And please follow guides or chances are you won't be able to recover the phone.
debdeep98 said:
Are you trying to flash a firmware or unlock the bootloader? Anyways the firmware you are trying to flash isn't the latest. It won't downgrade. Try the latest firmware.
Your bootloader seems to be locked.
You need to unlock that first. Try turning on OEM unlock from developer settings and then try the unlock data command.
And please follow guides or chances are you won't be able to recover the phone.
Click to expand...
Click to collapse
But I can't not start up my phone. so I think the bootloader is broken.
terawoot said:
But I can't not start up my phone. so I think the bootloader is broken.
Click to expand...
Click to collapse
Are you able to bring the device in bootloader/stock recovery mode?
If yes boot to bootloader mode with the key combination (I think it was power and vol down or power and vol up) and fastboot flash the latest stock firmware for your region:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
You don't need an unlocked bootloader for that.
terawoot said:
But I can't not start up my phone. so I think the bootloader is broken.
Click to expand...
Click to collapse
No it's not broken. If you are flashing oreo fimware there are 9 system sparse chunks(0-8). Make sure u flash them all.
terawoot said:
But I can't not start up my phone. so I think the bootloader is broken.
Click to expand...
Click to collapse
debdeep98 said:
No it's not broken. If you are flashing oreo fimware there are 9 system sparse chunks(0-8). Make sure u flash them all.
Click to expand...
Click to collapse
For Oreo the whole sets of commands are for
Locking:
-----------------
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 boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
-----------------------------------
The same commands for Nougat:
Flashing:
-----------------------------------
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 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
--------------------------
Locking:
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 boot boot.img
fastboot oem lock

Categories

Resources