Related
need help [urgent]
here I post command from CMD :
++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
++++++++++++++++
C:\android>fastboot flash hboot vivo_downgrade.img
sending 'hboot' (1024 KB)...
OKAY [ 0.421s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.546s
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.172s]
finished. total time: 0.172s
++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
+++++++++++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.16.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.707.1
(bootloader) serialno: HT155TD00844
(bootloader) imei: 355301044806969
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3a3895d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++
I cant access RECOVERY MODE
I cant access My ROM/Stock ROM
Help me
wesly.btm said:
need help [urgent]
here I post command from CMD :
++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
++++++++++++++++
C:\android>fastboot flash hboot vivo_downgrade.img
sending 'hboot' (1024 KB)...
OKAY [ 0.421s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.546s
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.172s]
finished. total time: 0.172s
++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
+++++++++++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.16.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.707.1
(bootloader) serialno: HT155TD00844
(bootloader) imei: 355301044806969
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3a3895d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++
I cant access RECOVERY MODE
I cant access My ROM/Stock ROM
Help me
Click to expand...
Click to collapse
What are you trying to accomplish? The vivo_downgrade.img is only used when you have Revolutionary S-OFF HBOOT installed. Also, you will only be able to use the 'fastboot flash' command when the bootloader is in the UNLOCKED state. The fact that you LOCKED it before the attempting the 'fastboot flash hboot' command probably saved you from making a huge mistake.
You have 2 options to get your phone operational again.
1. You need to UNLOCK your bootloader again then flash a custom Recovery and then flash a custom ROM.
2. Since you are now RELOCKED, you can take the 2.30.707.1 RUU and run it to return to stock.
You have 2 options to get your phone operational again.
1. You need to UNLOCK your bootloader again then flash a custom Recovery and then flash a custom ROM.
2. Since you are now RELOCKED, you can take the 2.30.707.1 RUU and run it to return to stock.
+++++++++++
pls advise, the link for Item 1 & 2?
thanks,
how to I get S-OFF,
since I cant load to Menu HTC forgot to check Setting > Developer Option > USB Debug
I cant access recovery mode.
wesly.btm said:
You have 2 options to get your phone operational again.
1. You need to UNLOCK your bootloader again then flash a custom Recovery and then flash a custom ROM.
2. Since you are now RELOCKED, you can take the 2.30.707.1 RUU and run it to return to stock.
+++++++++++
pls advise, the link for Item 1 & 2?
thanks,
Click to expand...
Click to collapse
wesly.btm said:
how to I get S-OFF,
since I cant load to Menu HTC forgot to check Setting > Developer Option > USB Debug
I cant access recovery mode.
Click to expand...
Click to collapse
If you want to gain S-OFF, you first will need to do option 1 and then use the Downgrade script.
If you need links, you should search this forum and read the sticky posts. If you have never unlocked the bootloader, then you need to use the procedure at HTCDEV.com. If you have used that procedure, then you can simply use the same unlock_token.bin again to unlock it.
tpbklake said:
If you want to gain S-OFF, you first will need to do option 1 and then use the Downgrade script.
If you need links, you should search this forum and read the sticky posts. If you have never unlocked the bootloader, then you need to use the procedure at HTCDEV.com. If you have used that procedure, then you can simply use the same unlock_token.bin again to unlock it.
Click to expand...
Click to collapse
I need help
short story:
Error when flashing RUU? ERROR [110]: FILE OPEN ERROR
Now, I know the problem was my Desire was S-OFF.
When pull out the USB cable:
[1]SPLASH 1 – OK
[2]USERDATA - OK
[3]SYSTEM - FAIL-PU
[4]RECOVERY - OK
[5]RADIO_CUST - OK
[6]RADIO_V2 - OK
[7]BOOTLOADER - Bypassed
[8]BOOT - OK
Partition update fail!
Update fail!
HTC logo when I turn on the phone with four figures on the squares
After that I tried to flash recovery with fastboot, but I can’t install my backup and the all custom room was frozen on the first boot.
My nandroid beckup:
system: 254MB
data: 128 MB
cache: 2,6 MB
First I tried to flash bravo_alpharev.img but it dosn’t work. The RUU flash was error as well.
I heard that:
flash- fastboot- bravo_downgrader.img
Now the error massege: RUU? ERROR [132]: SIGNATURE ERROR
http://forum.xda-developers.com/showthread.php?t=2214309
Fastboot flash:
[Q] Fastboot 'FAILED (remote: signature verify fail)
http://forum.xda-developers.com/showthread.php?t=1357625
+++++++++++++++++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
++++++++++++++++++++++++++++++++++++++
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
++++++++++++++++
++++++++++++++++++++++++
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: SetRuuNbhUpdate
(bootloader) serialno: SH0C4PL02400
(bootloader) imei: 355302049055073
(bootloader) product: Bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0 I have no displayed this last line
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++++++++
Now I can’t turn on the phone. I can charging the buttery and if I connect the USB cable and my PC , I can use some base function but I can’t flashing.
So put something on the SD an turn on fastboot mode or any other mode is not working for my phone. If I try to turn on I have no nothing on the screen at the moment. Black screen….
I heard maybe I locked the bootloader so….
bootloader (bootloader lock) I try to unlock and I used HTCdev
Windows fail process stopped ect.
What can I do now?
Is there any solution for me?
GeriW said:
I need help
short story:
Error when flashing RUU? ERROR [110]: FILE OPEN ERROR
Now, I know the problem was my Desire was S-OFF.
When pull out the USB cable:
[1]SPLASH 1 – OK
[2]USERDATA - OK
[3]SYSTEM - FAIL-PU
[4]RECOVERY - OK
[5]RADIO_CUST - OK
[6]RADIO_V2 - OK
[7]BOOTLOADER - Bypassed
[8]BOOT - OK
Partition update fail!
Update fail!
HTC logo when I turn on the phone with four figures on the squares
After that I tried to flash recovery with fastboot, but I can’t install my backup and the all custom room was frozen on the first boot.
My nandroid beckup:
system: 254MB
data: 128 MB
cache: 2,6 MB
First I tried to flash bravo_alpharev.img but it dosn’t work. The RUU flash was error as well.
I heard that:
flash- fastboot- bravo_downgrader.img
Now the error massege: RUU? ERROR [132]: SIGNATURE ERROR
http://forum.xda-developers.com/showthread.php?t=2214309
Fastboot flash:
[Q] Fastboot 'FAILED (remote: signature verify fail)
http://forum.xda-developers.com/showthread.php?t=1357625
+++++++++++++++++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
++++++++++++++++++++++++++++++++++++++
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
++++++++++++++++
++++++++++++++++++++++++
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: SetRuuNbhUpdate
(bootloader) serialno: SH0C4PL02400
(bootloader) imei: 355302049055073
(bootloader) product: Bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0 I have no displayed this last line
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++++++++
Now I can’t turn on the phone. I can charging the buttery and if I connect the USB cable and my PC , I can use some base function but I can’t flashing.
So put something on the SD an turn on fastboot mode or any other mode is not working for my phone. If I try to turn on I have no nothing on the screen at the moment. Black screen….
I heard maybe I locked the bootloader so….
bootloader (bootloader lock)I try to unlock and I used HTCdev
Windows fail process stopped ect.
What can I do now?
Is there any solution for me?
Click to expand...
Click to collapse
Why do you reply to a thread that is more than a year old?
As well as this, you have posted in the wrong device forum. This is for the HTC Incredible S, not the HTC Desire xD
You may have better luck in the Desire forum
Sent from my Nexus 5
Hi all,
So I have well and truly hardbricked my XT1803. Most probably arose as I foolishly flashed a Potter firmware to my Sanders phone. Teaches me for not reading everything carefully before going ahead to flash firmware.
Anyway, I'm now in the situation where I have hard bricked my device completely. No OS, no recovery, no bootloader. Strangely the device can be found if install the device on my PC as "Android ADB interface" and I can run fastboot commands in cmd (however nothing appears on the phones screen). I've detailed my getvar all details below if that helps!
I've tried re-flashing NPS26.116-61 on the device and this gives me an error at the first hurdle as per the below.
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.096s
I've tried blank flash based on the G5 forums to see if this can boot some life into it, however the phone is not recognising as QUALCOMM HS-USB QDLoader 9008
If I force install of the QUALCOMM HS-USB QDLoader 9008 drivers, this just gives me the < waiting for device > if I run blank flash.
Fastboot getvar all as per the below - I've added some in bold as these have been purposely hidden.
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: XXXXXXXXX
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3xxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 01-08-2018
(bootloader) sku: XT1803
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 2:46 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPS26.116-61/74:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.231.74.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-Resurrected-Kernel
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x 2
(bootloader) kernel.version[2]: 0150123 (prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: MPT Thu Jan 11 23:42:06 EST 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.07-0-g3b15bb0
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=283f623
(bootloader) devcfg.git: git=283f623
(bootloader) keymaster.git: git=283f623
(bootloader) cmnlib.git: git=283f623
(bootloader) cmnlib64.git: git=283f623
(bootloader) prov.git: git=283f623
(bootloader) aboot.git: git=MBM-NG-VC1.07-0-g9d7f987
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.211s
If anyone has any thoughts on bringing this back to life I'd great appreciate it!
Bro try flashing this firmware
https://androidfilehost.com/?fid=673956719939831738
Ur using old version
Hi there,
Thanks for your advice. I tried this and got the following errors on flashing the firmware. All steps were successful other than the below.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot 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 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
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.101s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.143s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.445s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot 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.457s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.428s]
finished. total time: 0.888s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.609s
i have same problem please give me the solution please
kooljim45 said:
Hi there,
Thanks for your advice. I tried this and got the following errors on flashing the firmware. All steps were successful other than the below.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot 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 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
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.101s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.143s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.445s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot 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.457s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.428s]
finished. total time: 0.888s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.579s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.609s
Click to expand...
Click to collapse
u need to download new firmware or try skipping gpt if ur bootloader is unlocked
Try flash twrp and flashable stock
When 61-5 no work
Sent from my Moto G5S Plus using XDA Labs
Adi5 said:
Try flash twrp and flashable stock
When 61-5 no work
Sent from my Moto G5S Plus using XDA Labs
Click to expand...
Click to collapse
Seriously? How can he flash twrp flashable zip without accessing twrp
Sri Datta said:
Seriously? How can he flash twrp flashable zip without accessing twrp
Click to expand...
Click to collapse
My bad
I didn't say error while flashing recovery
Fastboot boot twrp.img maybe will work but it won't help
Sent from my Moto G5S Plus using XDA Labs
I have tried the latest firmware. The biggest issue is that my PC can see the device through fastboot, however nothing appears on the phone screen.
Do ...U have twrp . Working???..try a custom ROM bro ....
TWRP is not working. The bootloader doesn't start. There is no recovery mode.
Fast boot mode??
Bro try unlocking bootloader then flash bootloader
Image primary_gpt failed validation
Hi! Sorry about my language, im from Argentina. I'm trying to flash a rom on Moto G5S Plus, and i catch this error:
Image primary_gpt failed validation.
Log is here:
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' (45 KB)...
OKAY [ 0.016s]
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.154s
I'm Flashing: SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Anybody can help me please? I cant install Magisk anyway!
XT1800. Nougat 7.1.1
Thks
damansilla said:
Hi! Sorry about my language, im from Argentina. I'm trying to flash a rom on Moto G5S Plus, and i catch this error:
Image primary_gpt failed validation.
Log is here:
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' (45 KB)...
OKAY [ 0.016s]
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.154s
I'm Flashing: SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Anybody can help me please? I cant install Magisk anyway!
XT1800. Nougat 7.1.1
Thks
Click to expand...
Click to collapse
U need flash newest software..... Which software channel u have?
Adi5 said:
U need flash newest software..... Which software channel u have?
Click to expand...
Click to collapse
Hi! What do you refer with software channel? Sorry i dont understand.
I did some research on this.. Your out of luck. Best is to sell it for parts not working. Or take it to a shop that specialize in phone repair.. Might cost you a $100, but it is better than buying a new one, which is costly.
damansilla said:
Hi! What do you refer with software channel? Sorry i dont understand.
Click to expand...
Click to collapse
Every region has a Software channel, you can check the name of your region's channel in the About Phone section
thippu46 said:
Every region has a Software channel, you can check the name of your region's channel in the About Phone section
Click to expand...
Click to collapse
Hi! My channel Is retar.
Thanks!
damansilla said:
Hi! My channel Is retar.
Thanks!
Click to expand...
Click to collapse
Which version u have now?
so here i am, after 2 days of scrutinizing every corner of the internet, looking for solution. i had my moto g6 on pie but out of curiosity i wanted try out different roms and here is what happened:
- after ive successfully unlocked the oem lock, installed twrp and tried to install different roms just to run into error 255 and such i gave up and thought **** it lets go back to original rom, so i fired up fastboot and put back oreo that i downloaded from here, the splashscreen however was still bearing the 'device has been unlocked and cant be trusted' message, so i thought i would put back the oem lock and then formatted the device... ooops and thats when i started having these problems.
- since then i cant install any rom - stock or mod (i was however successful in flashing twrp back on the phone)
- fastboot says FLASHING_LOCKED and having tried maybe 6 different stock roms i noticed that i can flash these two lines without problems:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
but anything after that is giving me (bootloader) flash permission denied FAILED (remote failure) in powershell
so to sum it up: i can boot into fastboot or twrp but i cant do much anything else
ive seemed to exhaust every remote advice out there and really dont know what to do anymore
any of you guys could point me in the right direction? or is the phone done and done?
here is the fastboot var list
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) meid:
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 26 14: 4:32 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(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
thx
Peter
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
najjannajS650 said:
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
Click to expand...
Click to collapse
thanks, i think ive already tried that already before,
here is a recap of what happens when i type in fastboot flashing unlock
- (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue.
- (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer (bootloader) Options.
i dont have any rom installed so i cant get into developers options and allow OEM unlock
edited: and if i try ./fastboot oem unlock
i get
... (bootloader) invalid boot state
:crying:
nobody has solution to this? really????
delosanto said:
nobody has solution to this? really????
Click to expand...
Click to collapse
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Spaceminer said:
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Click to expand...
Click to collapse
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
delosanto said:
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
Click to expand...
Click to collapse
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Spaceminer said:
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Click to expand...
Click to collapse
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(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
delosanto said:
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: son[email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(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
Click to expand...
Click to collapse
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Spaceminer said:
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Click to expand...
Click to collapse
im in the uk, please dont say there is still hope
delosanto said:
im in the uk, please dont say there is still hope
Click to expand...
Click to collapse
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
i tried to flashed the files exactly in the order they appear in .info file
./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 flash dsp adspso.bin
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash system system.img_sparsechunk.8
./fastboot flash system system.img_sparsechunk.9
./fastboot flash vendor vendor.img_sparsechunk.0
./fastboot flash vendor vendor.img_sparsechunk.1
./fastboot flash oem oem.img
./fastboot erase cache
./fastboot erase userdata
./fastboot erase ddr
./fastboot oem fb_mode_clear
./fastboot reboot
delosanto said:
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
Click to expand...
Click to collapse
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
---------- Post added at 07:09 PM ---------- Previous post was at 06:57 PM ----------
@delosanto
Are you able to boot or flash twrp?
Spaceminer said:
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
Click to expand...
Click to collapse
thank you! i think i must have read and tried everything there is out there trying to bring the poor little fella back to life.. ive tried different ports, methods, ROMs, different cables, tomorrow im gonna try what youre suggesting - the older cmd but i doubt it will make any difference, since i was able to flash and re-flash this phone just fine before i somehow managed to **** up the oem lock with no possibility to unlock it since there is no OS.
yes, im able to totally erase twrp (pic of android with red triangle and NO COMMAND) and then bring it back by booting twrp and consequently flashing twrp so it's there back under recovery mode
Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Ragarianok said:
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Click to expand...
Click to collapse
the last OS that was successfully flashed was Oreo
delosanto said:
the last OS that was successfully flashed was Oreo
Click to expand...
Click to collapse
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Spaceminer said:
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Click to expand...
Click to collapse
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
delosanto said:
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
Click to expand...
Click to collapse
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Spaceminer said:
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Click to expand...
Click to collapse
but when i try to flash the stock rom, again i get past the first two files gpt.bin and bootloader.bit but the rest is giving me the same error
(bootloader) flash permission denied
FAILED (remote failure)
but then it crashes back to fastboot
and i even did a clean windows installation today
I have the z3 play and when I try to re-install any rom I have this error, I think that at some point I damaged the bootloader or installed a different model, could someone help me tell me how to fix it?
I just solved a problem where I had lost the IMEI, I re-installed a rom from a pay site and I got it back, this error appeared to me before I installed that rom so I don't think that was the problem, these are the commands I use to install the rom
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.142s]
Finished. Total time: 0.161s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.397s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth_a: not found
Sending 'bluetooth_a' (400 KB) OKAY [ 0.014s]
Writing 'bluetooth_a' OKAY [ 0.012s]
Finished. Total time: 0.057s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash dsp dspso.bin
(bootloader) is-logical:dsp_a: not found
Sending 'dsp_a' (16384 KB) OKAY [ 0.585s]
Writing 'dsp_a' OKAY [ 0.129s]
Finished. Total time: 0.754s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash logo logo.bin
(bootloader) is-logical:logo_a: not found
Sending 'logo_a' (2393 KB) OKAY [ 0.088s]
Writing 'logo_a' OKAY [ 0.025s]
Finished. Total time: 0.658s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24177 KB) OKAY [ 0.836s]
Writing 'boot_a' OKAY [ 0.673s]
Finished. Total time: 2.059s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system_a: not found
Sending 'system_a' (524284 KB) OKAY [ 17.904s]
Writing 'system_a' OKAY [ 3.695s]
Finished. Total time: 21.665s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system_a: not found
Sending 'system_a' (524284 KB) OKAY [ 17.820s]
Writing 'system_a' OKAY [ 3.645s]
Finished. Total time: 22.072s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system_a: not found
Sending 'system_a' (524284 KB) OKAY [ 17.577s]
Writing 'system_a' OKAY [ 3.673s]
Finished. Total time: 21.790s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system_a: not found
Sending 'system_a' (489540 KB) OKAY [ 16.312s]
Writing 'system_a' OKAY [ 3.463s]
Finished. Total time: 20.299s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system_a: not found
Sending 'system_a' (524284 KB) OKAY [ 17.369s]
Writing 'system_a' OKAY [ 3.642s]
Finished. Total time: 21.532s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system_a: not found
Sending 'system_a' (119052 KB) OKAY [ 4.134s]
Writing 'system_a' OKAY [ 0.874s]
Finished. Total time: 5.544s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash system_b system_other.img
(bootloader) is-logical:system_b: not found
Sending 'system_b' (380212 KB) OKAY [ 12.788s]
Writing 'system_b' OKAY [ 2.694s]
Finished. Total time: 15.527s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash oem oem.img
(bootloader) is-logicalem_a: not found
Sending 'oem_a' (136204 KB) OKAY [ 4.656s]
Writing 'oem_a' OKAY [ 1.007s]
Finished. Total time: 5.706s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash oem_b oem_other.img
(bootloader) is-logicalem_b: not found
Sending 'oem_b' (20384 KB) OKAY [ 0.733s]
Writing 'oem_b' OKAY [ 0.194s]
Finished. Total time: 0.960s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot flash vendor vendor.img_sparsechunk.0
(bootloader) is-logical:vendor_a: not found
Sending 'vendor_a' (524284 KB) OKAY [ 18.155s]
Writing 'vendor_a' OKAY [ 3.639s]
Finished. Total time: 21.847s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot erase carrier
Erasing 'carrier' OKAY [ 0.005s]
Finished. Total time: 0.009s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot erase cache
Erasing 'cache' OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot erase userdata
Erasing 'userdata' OKAY [ 1.123s]
Finished. Total time: 1.126s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot erase ddr
Erasing 'ddr' OKAY [ 0.007s]
Finished. Total time: 0.009s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml>
and I get this with fastboot getvar all
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml> .\fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-d3390b3-200106
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY2
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 5512D6C9
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 35410
(bootloader) meid:
(bootloader) date: 11-12-2018
(bootloader) sku: XT1929-6
(bootloader) carrier_sku: XT1929-6
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-25/b6ca4:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.31.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: M636_30.77.01.101R BECKHAM_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8c2d809fa9ac
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x
(bootloader) kernel.version[2]: 20150123 (prerelease) (GCC) ) #1 SMP PR
(bootloader) kernel.version[3]: EEMPT Thu Apr 30 13:37:10 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_retail-d3390b3-200106
(bootloader) git:xbl: MBM-3.0-beckham_retail-56c771b-200106
(bootloader) gitmic: MBM-3.0-beckham_retail-56c771b-200106
(bootloader) git:rpm: MBM-3.0-beckham_retail-33b79ec-200106
(bootloader) git:tz: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) git:hyp: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) git:devcfg: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) git:keymaster: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) gitrov: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) git:storsec: MBM-3.0-beckham_retail-98f8832-200106
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.136s
PS D:\Users\Yonathan\Desktop\BECKHAM_PPWS29.131_27_1_25_subsidy_IUSMXLA_regulatory_XT1929_6_CFC.xml>
Did you ever solve this issue? I'm having the same problem and having no luck.
Reznor7 said:
Did you ever solve this issue? I'm having the same problem and having no luck.
Click to expand...
Click to collapse
I haven't solved it yet.
I have an XT1924-3, and days ago it stopped booting and it's only on the motorola logo, I tried to reinstall the original rom, but without success.
below is the getvar all of the device and the failures during the installation of the rom.
device info:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BF.55
(bootloader) product: hannah
(bootloader) board: hannah
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZF6223JFW4
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A0AF6D1500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355528098100150
(bootloader) meid:
(bootloader) date: 02-14-2019
(bootloader) sku: XT1924-3
(bootloader) carrier_sku: XT1924-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Mar 10 8: 4:28 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ahannah/ahannah:8.0.0/OPP
(bootloader) ro.build.fingerprint[1]: S27.91-179-8-2/2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.271.2.ahannah.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8937_31.39.05.92R HANNAH_APDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gf653212 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Jul 12 04:53:01 CD
(bootloader) kernel.version[3]: T 2019
(bootloader) sbl1.git: git=MBM-NG-VBF.55-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=abe1c91-dirty
(bootloader) devcfg.git: git=abe1c91-dirty
(bootloader) keymaster.git: git=abe1c91
(bootloader) cmnlib.git: git=abe1c91
(bootloader) cmnlib64.git: git=abe1c91
(bootloader) prov.git: git=abe1c91-dirty
(bootloader) aboot.git: git=MBM-NG-VBF.55-0-g4e3d3ac
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Click to expand...
Click to collapse
Installation:
C:\Users\Kathellen\Desktop\Ferramenta XML para Bat\XT1924-3_AHANNAH_RETIN_8.0.0_OPPS27.91-179-8-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
Finished. Total time: 0.000s
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical: partition: not found
Sending 'partition' (45 KB) OKAY [ 0.156s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7483 KB) OKAY [ 0.453s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(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 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.469s]
Finished. Total time: 1.031s
(bootloader) is-logical:modem: not found
Sending 'modem' (68722 KB) OKAY [ 2.686s]
Writing 'modem' OKAY [ 0.547s]
Finished. Total time: 3.358s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (5668 KB) OKAY [ 0.375s]
Writing 'fsg' OKAY [ 0.062s]
Finished. Total time: 0.484s
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.766s]
Writing 'dsp' OKAY [ 0.156s]
Finished. Total time: 0.953s
(bootloader) is-logical:logo: not found
Sending 'logo' (1423 KB) OKAY [ 0.219s]
Writing 'logo' OKAY [ 0.047s]
Finished. Total time: 0.297s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.609s]
Writing 'boot' OKAY [ 0.313s]
Finished. Total time: 1.125s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (24576 KB) OKAY [ 1.078s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.547s
(bootloader) is-logical:system: not found
Sending 'system' (512413 KB) OKAY [ 19.709s]
Writing 'system' OKAY [ 8.994s]
Finished. Total time: 29.158s
(bootloader) is-logical:system: not found
Sending 'system' (521403 KB) OKAY [ 19.497s]
Writing 'system' OKAY [ 9.452s]
Finished. Total time: 29.175s
(bootloader) is-logical:system: not found
Sending 'system' (491282 KB) OKAY [ 18.315s]
Writing 'system' OKAY [ 8.082s]
Finished. Total time: 26.581s
(bootloader) is-logical:system: not found
Sending 'system' (510457 KB) OKAY [ 18.897s]
Writing 'system' OKAY [ 8.998s]
Finished. Total time: 28.437s
(bootloader) is-logical:system: not found
Sending 'system' (186815 KB) OKAY [ 11.196s]
Writing 'system' OKAY [ 3.421s]
Finished. Total time: 15.170s
(bootloader) is-logical:vendor: not found
Sending 'vendor' (238952 KB) OKAY [ 9.487s]
Writing 'vendor' OKAY [ 6.392s]
Finished. Total time: 16.728s
(bootloader) is-logical: oem: not found
Sending 'oem' (91253 KB) OKAY [ 6.189s]
Writing 'oem' OKAY [ 3.413s]
Finished. Total time: 9.879s
Erasing 'modemst1' OKAY [ 0.016s]
Finished. Total time: 0.026s
Erasing 'modemst2' OKAY [ 0.017s]
Finished. Total time: 0.026s
Erasing 'cache' OKAY [ 0.003s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.037s]
Finished. Total time: 0.046s
Erasing 'DDR' OKAY [ 0.002s]
Finished. Total time: 0.010s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (5668 KB) OKAY [ 0.382s]
Writing 'fsg' OKAY [ 0.076s]
Finished. Total time: 0.484s
OKAY [ 0.002s]
Finished. Total time: 0.005s
Click to expand...
Click to collapse
the device doesn't is unlocked bootloader