Moto g9 plus totally hardbricked no edl stuck fastboot - Moto G9 Plus Guides, News, & Discussion

Hi good day, i flashed pixelExperience UNOFFICIAL ROM last week but i found a bug that wifi kept disconnecting so I wanted to return back to stock so I did the process to go back to stock, and everything was fine until i decided to relock the bootloader, the phone got stuck at a screen that said "Operating system not valid this device wont boot" <--- it was something like that, i dont remember so I inmediately went to fastboot mode and try to reflash the rom but everything I tried to do didn't work because it kept asking me that my bootloader needed to be unlock by going to system usb debugging etc, but how would I do that if the phone was already stuck at fastboot, then i thought I don't know twhy I got the stupid idea that running "fastboot erase all" command would help me, so yes I ran that command and guess what the phone got much worse than it already was
now i can't do anything I've searched on a lot of forums and nothing seems to work I heard that using a blankflash would help me the thing is no matter the command i run it will always sends me back to fastboot mode I tried moto rescue and didn't work as well I've heard that EDL mode but phone keeps going to fastboot or maybe I'm doing something wrong, please help me!!!!
this is what fastboot getvar all shows
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) product: odessa
(bootloader) board: odessa
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRLAP
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GASAO4U21 FV=0106 WB=0
(bootloader) ram: 4GB MICRON LP4 DIE=32Gb M5-M8=FF 06 00 18
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZY22CRQG7F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: D2DE5AB3
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 355537115810642
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-29-2021
(bootloader) sku: XT2087-1
(bootloader) carrier_sku: XT2087-1
(bootloader) battid: SB18C98040
(bootloader) battery-voltage: 3914
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: amxmx
(bootloader) ro.build.fingerprint[0]: motorola/odessa_retail/odessa:11/R
(bootloader) ro.build.fingerprint[1]: PAS31.Q2-59-17-4-3-2/37446:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-09100-SMxxx0.0
(bootloader) version-baseband: M7150_22.31.04.72R ODESSA_BRLAP_CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[4]: an 5 04:57:51 CST 2022
(bootloader) git:xbl: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:xbl_config: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:aop: MBM-3.0-odessa_retail-9817cf3-220105
(bootloader) git:tz: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:hyp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:devcfg: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:cmnlib: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:keymaster: MBM-3.0-odessa_retail-db27bc4-220105
(bootloader) git:storsec: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) gitrov: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:abl: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) git:uefisecapp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(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
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D02302
(bootloader) primary-display: txd_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.041s

Edgar Pione said:
Hi good day, i flashed pixelExperience UNOFFICIAL ROM last week but i found a bug that wifi kept disconnecting so I wanted to return back to stock so I did the process to go back to stock, and everything was fine until i decided to relock the bootloader, the phone got stuck at a screen that said "Operating system not valid this device wont boot" <--- it was something like that, i dont remember so I inmediately went to fastboot mode and try to reflash the rom but everything I tried to do didn't work because it kept asking me that my bootloader needed to be unlock by going to system usb debugging etc, but how would I do that if the phone was already stuck at fastboot, then i thought I don't know twhy I got the stupid idea that running "fastboot erase all" command would help me, so yes I ran that command and guess what the phone got much worse than it already was
now i can't do anything I've searched on a lot of forums and nothing seems to work I heard that using a blankflash would help me the thing is no matter the command i run it will always sends me back to fastboot mode I tried moto rescue and didn't work as well I've heard that EDL mode but phone keeps going to fastboot or maybe I'm doing something wrong, please help me!!!!
this is what fastboot getvar all shows
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) product: odessa
(bootloader) board: odessa
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRLAP
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GASAO4U21 FV=0106 WB=0
(bootloader) ram: 4GB MICRON LP4 DIE=32Gb M5-M8=FF 06 00 18
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZY22CRQG7F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: D2DE5AB3
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 355537115810642
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-29-2021
(bootloader) sku: XT2087-1
(bootloader) carrier_sku: XT2087-1
(bootloader) battid: SB18C98040
(bootloader) battery-voltage: 3914
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: amxmx
(bootloader) ro.build.fingerprint[0]: motorola/odessa_retail/odessa:11/R
(bootloader) ro.build.fingerprint[1]: PAS31.Q2-59-17-4-3-2/37446:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-09100-SMxxx0.0
(bootloader) version-baseband: M7150_22.31.04.72R ODESSA_BRLAP_CUST
(bootloader) kernel.version[0]: Linux version 4.14.190-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[4]: an 5 04:57:51 CST 2022
(bootloader) git:xbl: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:xbl_config: MBM-3.0-odessa_retail-ce4c20166-220105
(bootloader) git:aop: MBM-3.0-odessa_retail-9817cf3-220105
(bootloader) git:tz: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:hyp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:devcfg: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:cmnlib: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:keymaster: MBM-3.0-odessa_retail-db27bc4-220105
(bootloader) git:storsec: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) gitrov: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) git:abl: MBM-3.0-odessa_retail-e69c40c38d-220105
(bootloader) git:uefisecapp: MBM-3.0-odessa_retail-c8525e1a1-220105
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(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
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D02302
(bootloader) primary-display: txd_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.041s
Click to expand...
Click to collapse
How to boot into EDL Mode

Related

BootLooping/recovery booting Motorola Z2 Play Xt1710-02

I am at my limit. I have the phone able to be boot in fastboot mode. The phone only can boot in fastboot mode. Trying to get it to recovery mode only makes it blink for an instant and either turns off or goes to a black screen. The phone oem is locked, bootloader is locked, and for some reason I can't seem to find the correct recovery file or stock rom to boot or flash too.
I ran fastboot get-var all and got this:
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB MICRON Q3J97V RV=08 PV=10 FV=00000000000000A7
(bootloader) ram: 3GB MICRON LP3 DIE=6Gb M5=03 M6=00 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224FL3BG
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: C379DE4800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355675081790487
(bootloader) meid:
(bootloader) date: 08-26-2017
(bootloader) sku: XT1710-02
(bootloader) carrier_sku:
(bootloader) battid: SNN5985A
(bootloader) iccid: 89148000003596429824
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 15: 3:57 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus_verizon/albus:8.0.0
(bootloader) ro.build.fingerprint[1]: /ODS27.76-12-36/39:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.221.39.albus_veri
(bootloader) ro.build.version.full[1]: zon.verizon.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8953P_41.50.07.73R ALBUS_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g2879ff4 (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]: Mon Jul 2 18:23:37 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=MBM-NG-VC1.82-0-gbd19194
(bootloader) tz.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) devcfg.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) keymaster.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) prov.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: vzw
(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.211s
Any help at all is greatly appreciated. Well i'd like to change an earlier statement. Now when I try booting it it goes to recovery mode for a split second and turns off. It's only when I go to fastboot mode and try starting it from there does it constantly loop.
not sure but try this command, it may help:-
fastboot continue
This happened to me flashing the latest firmware. Not sure what fixed it exactly but I flashed a few different firmwares and the problem was gone.
xt1710-02 is a Verizon version. If you can get to fastboot, try the software assistance from Verizon: https://www.verizonwireless.com/support/knowledge-base-209216/
It will restore back to factory.
Edit: nvm. If you can't get it to boot then this won't help you. What about this firmware? https://mirrors.lolinet.com/firmware/moto/albus/official/VZW/

XT 1789-04 Can't Get Passed Bootloader

Hey all,
Okay. I have (apparently) the 1789-04 version of the Z2 Force. However, the phone insists, for the most part, internally, that it is an AT&T phone, not the TMO variant, which would be the variant indicated by the model number. This has lately become an issue due to the fact that the other day I was in camera mode on the phone, and POOF it bricked all over me, and I've tried to flash all kinds of stock firmware onto the phone. ATT firmwares flash successfully across the board, but just end up doing a bootloader boot loop, sometimes asking me to factory data reset the phone. TMO stock firmware fails at the point where the boot image flashes with the error "Preflash validation error". I've tried all kinds of firwmares, the most recent, slightly older ones.
The device shows in the bootloader as OEM locked, but when I flash the TMO bootloader, it starts off with the bootloader unlocked warning. Total bonkers. When the ATT is flashed, it never boots, so no point. I only get as far as the Motorola screen. I cannot get the phone to go to blankflash, as the command fastboot oem blankflash (no quotes) produces an error that says something along the the lines of that not being authorized. I would LOVE for my phone to be forced into a spot where I could use blankflash and go from there. Anyway, here's the getvar, if you guys have any suggestions, that would be great.
C:\Users\zacha>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY2249JTJC
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 3D66704C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080795291
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3695
(bootloader) iccid: 89014103270252934039
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(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]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) git:storsec: git:storsec
(bootloader) gitrov: gitrov
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.206s
zjcook23 said:
Hey all,
Okay. I have (apparently) the 1789-04 version of the Z2 Force. However, the phone insists, for the most part, internally, that it is an AT&T phone, not the TMO variant, which would be the variant indicated by the model number. This has lately become an issue due to the fact that the other day I was in camera mode on the phone, and POOF it bricked all over me, and I've tried to flash all kinds of stock firmware onto the phone. ATT firmwares flash successfully across the board, but just end up doing a bootloader boot loop, sometimes asking me to factory data reset the phone. TMO stock firmware fails at the point where the boot image flashes with the error "Preflash validation error". I've tried all kinds of firwmares, the most recent, slightly older ones.
The device shows in the bootloader as OEM locked, but when I flash the TMO bootloader, it starts off with the bootloader unlocked warning. Total bonkers. When the ATT is flashed, it never boots, so no point. I only get as far as the Motorola screen. I cannot get the phone to go to blankflash, as the command fastboot oem blankflash (no quotes) produces an error that says something along the the lines of that not being authorized. I would LOVE for my phone to be forced into a spot where I could use blankflash and go from there. Anyway, here's the getvar, if you guys have any suggestions, that would be great.
C:\Users\zacha>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY2249JTJC
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 3D66704C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080795291
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3695
(bootloader) iccid: 89014103270252934039
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(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]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) git:storsec: git:storsec
(bootloader) gitrov: gitrov
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.206s
Click to expand...
Click to collapse
Try Flash/rescue option in
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Another note is that both att and tmo models are xt 1789-04, so the if your phone is telling you it's an att then there is no way to unlock the bootloader.
Sent from my moto z4 using XDA Labs
sd_shadow said:
Try Flash/rescue option in
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
Tried this multiple times but my phone can't get past fastboot so I can't check the USB debugging or even have the phone detected by the LMSA. when i manually tell the program that it's an xt-1789-04, it will get as far as cmd: getvar:serialno before saying it can't match the product with the model number.

"Invalid partition name boot" error

I'm currently on a bootloop on a rooted device that was working fine, and trying to flash a firmware so it can reset (tried factory reset to no deal)
When I try to flash the boot.img I get:
C:\adb\update>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.048s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.054s
I also tried to flash lineage 17.1 but get "erase permission denied"
baigun said:
I'm currently on a bootloop on a rooted device that was working fine, and trying to flash a firmware so it can reset (tried factory reset to no deal)
When I try to flash the boot.img I get:
C:\adb\update>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.048s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 1.054s
I also tried to flash lineage 17.1 but get "erase permission denied"
Click to expand...
Click to collapse
What does getvar all say? (remove the imei before posting)
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say? (remove the imei before posting)
Code:
fastboot getvar all
Click to expand...
Click to collapse
C:\Users\Kon>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-613092d79-210317
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB UNKNOWN LP4 DIE=4Gb M5=00 M6=00 M7=00 M8=00
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: 0066225513
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: C4BECDAB9137B413000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355555112592799
(bootloader) imei2: 355555112592807
(bootloader) meid:
(bootloader) date: 05-13-2020
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 2 21:46:38 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:10/QMDS30.47
(bootloader) ro.build.fingerprint[1]: -19-4/71fae:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-q0.mp1.tc2sp-V1.53
(bootloader) version-baseband: MT6771_V70.02.01.108R
(bootloader) kernel.version[0]: Linux version 4.14.141+ ([email protected]
(bootloader) kernel.version[1]: build) (gcc version 4.9.x 20150123 (prer
(bootloader) kernel.version[2]: elease) (GCC)) #1 SMP PREEMPT Mon Jan 25
(bootloader) kernel.version[3]: 04:26:14 CST 2021
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: yes
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C73269
all: listed above
finished. total time: 0.126s
baigun said:
C:\Users\Kon>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-613092d79-210317
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB UNKNOWN LP4 DIE=4Gb M5=00 M6=00 M7=00 M8=00
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: 0066225513
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: C4BECDAB9137B413000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 05-13-2020
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 2 21:46:38 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:10/QMDS30.47
(bootloader) ro.build.fingerprint[1]: -19-4/71fae:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-q0.mp1.tc2sp-V1.53
(bootloader) version-baseband: MT6771_V70.02.01.108R
(bootloader) kernel.version[0]: Linux version 4.14.141+ ([email protected]
(bootloader) kernel.version[1]: build) (gcc version 4.9.x 20150123 (prer
(bootloader) kernel.version[2]: elease) (GCC)) #1 SMP PREEMPT Mon Jan 25
(bootloader) kernel.version[3]: 04:26:14 CST 2021
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: yes
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C73269
all: listed above
finished. total time: 0.126s
Click to expand...
Click to collapse
I don't see anything wrong there.
Try a different USB port or PC
See if there is an update to the SDK platform-tools
Tried an older stock rom, android 9, it worked, tried to update and now I get
"dm-verity corruption
This device can't be trusted,
please press the power button to boot or the phone will power off in 5s."
Did I brick my phone? :c
new getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-190906
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB UNKNOWN LP4 DIE=4Gb M5=00 M6=00 M7=00 M8=00
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: 0066225513
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: C4BECDAB9137B413000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355555112592799
(bootloader) imei2: 355555112592807
(bootloader) meid:
(bootloader) date: 05-13-2020
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jun 14 1: 4:28 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMD29.70-3
(bootloader) ro.build.fingerprint[1]: 7-1/5022a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.41.1.lima_32.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V9.04.01.79R
(bootloader) kernel.version[0]: Linux version 4.4.146 ([email protected]
(bootloader) kernel.version[1]: 54) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Fri Sep 6 07
(bootloader) kernel.version[3]: :50:09 CDT 2019
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: yes
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C73269
all: listed above
finished. total time: 0.129s
baigun said:
Tried an older stock rom, android 9, it worked, tried to update and now I get
"dm-verity corruption
This device can't be trusted,
please press the power button to boot or the phone will power off in 5s."
Did I brick my phone? :c
new getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-190906
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB UNKNOWN LP4 DIE=4Gb M5=00 M6=00 M7=00 M8=00
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: 0066225513
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: C4BECDAB9137B413000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355555112592799
(bootloader) imei2: 355555112592807
(bootloader) meid:
(bootloader) date: 05-13-2020
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jun 14 1: 4:28 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMD29.70-3
(bootloader) ro.build.fingerprint[1]: 7-1/5022a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.41.1.lima_32.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V9.04.01.79R
(bootloader) kernel.version[0]: Linux version 4.4.146 ([email protected]
(bootloader) kernel.version[1]: 54) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Fri Sep 6 07
(bootloader) kernel.version[3]: :50:09 CDT 2019
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: yes
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C73269
all: listed above
finished. total time: 0.129s
Click to expand...
Click to collapse
It's never a good idea to downgrade a Moto and then install an OTA update.
Try LMSA's Rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
I used an up to date stock and it resolved, thank you sd_shadow for the support, I dunno what exactly was causing both problems, but it went good eventually

Question Unable to unlock bootloader of motog60

I am trying to unlock the bootloader of my device but it dosent work on the motorola website the steps to unlock bootloader are:
1) reboot to bootloader
2) connect your phone to pc
3) then in cmd type fasboot oem get_unlock_data
After this we should get a string that we have to copy and paste on the website but, every time i run the command in step 3 i get an error saying (bootloader) FAILED
I dont understand what am i doing wrong ? I have unlocked the oem from developer options too.
Please help!
Xplo!t_A said:
I am trying to unlock the bootloader of my device but it dosent work on the motorola website the steps to unlock bootloader are:
1) reboot to bootloader
2) connect your phone to pc
3) then in cmd type fasboot oem get_unlock_data
After this we should get a string that we have to copy and paste on the website but, every time i run the command in step 3 i get an error saying (bootloader) FAILED
I dont understand what am i doing wrong ? I have unlocked the oem from developer options too.
Please help!
Click to expand...
Click to collapse
Try a different usb port, cable and pc
These can all cause this error.
sd_shadow said:
Try a different usb port, cable and pc
These can all cause this error.
Click to expand...
Click to collapse
tried on a WIN7 pc with all drivers installed properly and used a different cable. Here is my console output:
C:\Users\awadh>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.047s]
finished. total time: 0.047s
Xplo!t_A said:
tried on a WIN7 pc with all drivers installed properly and used a different cable. Here is my console output:
C:\Users\awadh>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.047s]
finished. total time: 0.047s
Click to expand...
Click to collapse
Try a factory reset
sd_shadow said:
Try a factory reset
Click to expand...
Click to collapse
Did a factory reset still no change.
Did you enable OEM unlock in developer settings? I was just wondering if unlocking this device could be difficult because of ThinkShield security
vatsalc said:
Did you enable OEM unlock in developer settings? I was just wondering if unlocking this device could be difficult because of ThinkShield security
Click to expand...
Click to collapse
Did that too form the dev settings. Still the problem persists
Here is the output of "fastboot get_var all" of my device if it helps.
C:\Users\awadh>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_r
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SKhynix H9HQ15AECMBDAR FV
(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5-M8
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZF6526V5GC
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 3B77226B
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 05-12-2021
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18D01687
(bootloader) battery-voltage: 3821
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retin
(bootloader) ro.build.fingerprint[0]: motorola/ha
(bootloader) ro.build.fingerprint[1]: /RRI31.Q1-4
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-
(bootloader) version-baseband[0]: M7150_09.297.01
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.1
(bootloader) kernel.version[1]: roid-build) (clan
(bootloader) kernel.version[2]: droid NDK, GNU ld
(bootloader) kernel.version[3]: f) 2.27.0.2017031
(bootloader) kernel.version[4]: un 11 07:59:53 CD
(bootloader) git:xbl: MBM-3.0-hanoip_retail-e9068
(bootloader) git:xbl_config: MBM-3.0-hanoip_retai
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5
(bootloader) git:tz: MBM-3.0-hanoip_retail-994049
(bootloader) git:hyp: MBM-3.0-hanoip_retail-99404
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-99
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-99
(bootloader) git:keymaster: MBM-3.0-hanoip_retail
(bootloader) git:storsec: MBM-3.0-hanoip_retail-9
(bootloader) gitrov: MBM-3.0-hanoip_retail-9940
(bootloader) git:abl: MBM-3.0-hanoip_retail-aea4f
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-6ac
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retai
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03162
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
all: listed above
finished. total time: 1.217s
Xplo!t_A said:
Here is the output of "fastboot get_var all" of my device if it helps.
C:\Users\awadh>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_r
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SKhynix H9HQ15AECMBDAR FV
(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5-M8
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ZF6526V5GC
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 3B77226B
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 05-12-2021
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18D01687
(bootloader) battery-voltage: 3821
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retin
(bootloader) ro.build.fingerprint[0]: motorola/ha
(bootloader) ro.build.fingerprint[1]: /RRI31.Q1-4
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-
(bootloader) version-baseband[0]: M7150_09.297.01
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.1
(bootloader) kernel.version[1]: roid-build) (clan
(bootloader) kernel.version[2]: droid NDK, GNU ld
(bootloader) kernel.version[3]: f) 2.27.0.2017031
(bootloader) kernel.version[4]: un 11 07:59:53 CD
(bootloader) git:xbl: MBM-3.0-hanoip_retail-e9068
(bootloader) git:xbl_config: MBM-3.0-hanoip_retai
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5
(bootloader) git:tz: MBM-3.0-hanoip_retail-994049
(bootloader) git:hyp: MBM-3.0-hanoip_retail-99404
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-99
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-99
(bootloader) git:keymaster: MBM-3.0-hanoip_retail
(bootloader) git:storsec: MBM-3.0-hanoip_retail-9
(bootloader) gitrov: MBM-3.0-hanoip_retail-9940
(bootloader) git:abl: MBM-3.0-hanoip_retail-aea4f
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-6ac
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retai
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03162
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
all: listed above
finished. total time: 1.217s
Click to expand...
Click to collapse
CID should be good
Code:
(bootloader) cid: 0x0032
You're not using a VPN or something else that would alter your internet access?
sd_shadow said:
CID should be good
Code:
(bootloader) cid: 0x0032
You're not using a VPN or something else that would alter your internet access?
Click to expand...
Click to collapse
Nope
finally after the latest security patch update some how i was able to get unlock data for bootloader
Hi! I have a Motorola G60, I opened the bootloader, but couldn't find any modified ROMs for it. I didn't change anything, I didn't root.
How to lock the bootloader?
Fastboot oem lock?

Question Moto e 2020 XT2052-1 Startup Fail

Hello, I have this device with problems booting android 10. A red legend appears showing "
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fail-through from factory boot mode "
I have tried to flash it with various tools like RSD Lite, Odin(NOT shown), and Lenovo User Assistant, all efforts have failed the device always shows the same red legend or sometimes it goes completely black with the charging indicator led blinking. Recovery mode is not accessible.
Please help. Thanks in advance
Rainwod said:
Hello, I have this device with problems booting android 10. A red legend appears showing "
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fail-through from factory boot mode "
I have tried to flash it with various tools like RSD Lite, Odin(NOT shown), and Lenovo User Assistant, all efforts have failed the device always shows the same red legend or sometimes it goes completely black with the charging indicator led blinking. Recovery mode is not accessible.
Please help. Thanks in advance
Click to expand...
Click to collapse
What does getvar all say? Remove imei before posting
Code:
fastboot getvar all
thanks sd_shadow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY22BLLKRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 96F6A8B300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from factory boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-18-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66368
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 9 8:41:56 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-135-7/c2ede:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.02R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[3]: un 9 05:43:55 CDT 2021
(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: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 1.609s
i downloaded and try to flash this ROMs:
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
GINNA_RETAIL_QPGS30.82_135_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
the variable (bootloader) ro.build.fingerprint[1] does not change its value, it always shows S30.82-135-7/c2ede:user/release-ke even after flashing with RSD Lite.
Thanks a lot
Rainwod said:
thanks sd_shadow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY22BLLKRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 96F6A8B300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from factory boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-18-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66368
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 9 8:41:56 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-135-7/c2ede:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.02R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[3]: un 9 05:43:55 CDT 2021
(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: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 1.609s
i downloaded and try to flash this ROMs:
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
GINNA_RETAIL_QPGS30.82_135_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
the variable (bootloader) ro.build.fingerprint[1] does not change its value, it always shows S30.82-135-7/c2ede:user/release-ke even after flashing with RSD Lite.
Thanks a lot
Click to expand...
Click to collapse
Rsd lite may not work with Windows 10.
Use Windows 7 or xp with rsd lite.
Sometimes this works flash this.
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then retry LMSA if you have Windows 10 or RSD Lite if you have Windows 7 or XP
sd_shadow said:
(...)
Then retry LMSA if you have Windows 10 or RSD Lite if you have Windows 7 or XP
Click to expand...
Click to collapse
I have tried both methods that you have indicated, in both cases ( RSD lite with Windows XP ) the process ends normally without failures but the result is the same, red Startup Fail legend. Thanks for the help, do you have any other ideas?
Rainwod said:
I have tried both methods that you have indicated, in both cases ( RSD lite with Windows XP ) the process ends normally without failures but the result is the same, red Startup Fail legend. Thanks for the help, do you have any other ideas?
Click to expand...
Click to collapse
It's possible the issue is related to the Persist Partition or other secure partition.
There is a good thread in the Moto G5 Plus forum.
I don't know if any of that discussion applies to the Moto E though.
Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements
I have created this thread in order to have one thread that details just the solution to fixing your persist, identifying whether or not you have an issue with your persist, and how you can restore your IMEI without hacks. This guide is written...
forum.xda-developers.com
Honestly looks like a cross flash to retus, followed by a bootloader lock. I don't think you can trust any fastboot variables if that's the case. You'd just have to flash boot.img for every model and variant of the E 2020 until you find the one that is allowed to boot.

Categories

Resources