fix moto x4 xt1900-7 ro.carrier - Moto X4 Questions & Answers

my moto has stopped working properly. it gets stuck in the logo screen and won't start. not even the backup solved the problem. I can access to the recovery and the bootloader but if I install a rom, nothing change and remain stuck. Rescue and Smart Assistant does not detect the device and tells me that ro.carrier is missing and to contact the seller to rewrite it. This the log of my device
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224KPP39
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 3A32ECCB
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356516081801693
(bootloader) meid:
(bootloader) date: 08-10-2018
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4298
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 7
all: listed above
finished. total time: 0.436s
I try this buy not change
fastboot oem config carrier retail
...
(bootloader) <UTAG name="carrier" type="str" protected="FALSE">
(bootloader) <value>
(bootloader) retail
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see (bere Is link buy i can post for now)
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.031s]
finished. total time: 0.031s

CyberrPK said:
my moto has stopped working properly. it gets stuck in the logo screen and won't start. not even the backup solved the problem. I can access to the recovery and the bootloader but if I install a rom, nothing change and remain stuck. Rescue and Smart Assistant does not detect the device and tells me that ro.carrier is missing and to contact the seller to rewrite it. This the log of my device
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224KPP39
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 3A32ECCB
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356516081801693
(bootloader) meid:
(bootloader) date: 08-10-2018
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4298
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 7
all: listed above
finished. total time: 0.436s
I try this buy not change
fastboot oem config carrier retail
...
(bootloader) <UTAG name="carrier" type="str" protected="FALSE">
(bootloader) <value>
(bootloader) retail
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see (bere Is link buy i can post for now)
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.031s]
finished. total time: 0.031s
Click to expand...
Click to collapse
Try
Code:
fastboot oem fb_mode_clear
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try
Code:
fastboot oem fb_mode_clear
I tried it and it worked. Meanwhile, I tried to install a custom rom, the Superior OS 10 and it starts up correctly. unfortunately with the installation I lost TWRP in favor of the recovery of the rom and the classic method does not make it install again (I will look at how to install it again). unfortunately LMAS does not login (until yesterday work so it will be a momentary disservice of lenovo) and I cannot check if the ro.carrier is working now
Click to expand...
Click to collapse

sd_shadow said:
Try
Code:
fastboot oem fb_mode_clear
I'm a little confused. the installation of the custom rom was successful, but in theory the recovery partition is gone. I say this because if I try to flash TWRP I get this message
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (33432 KB)...
OKAY [ 1.400s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 1.416s
I would think it is a kernel problem, but I can access to the recovery from the bootloader. at this point I think that the recovery partition has been replaced with a partition with a different name. I enclose images of the bootloader, recovery, OS started. I hope you can help me
https://freeimage.host/i/2qZQIe
https://freeimage.host/i/2qZik7
https://freeimage.host/i/2qZsp9
https://freeimage.host/i/img-20200913-194310.2qtEy7
Click to expand...
Click to collapse

You have to download both twrp.img and twrp-installer.zip from twrp.me site. Try "fastboot boot twrp.img" and next install twrp.zip.

unbelievable is a whole day that I have tried that exact command line and I always had error. I restarted the pc and then everything was fine :/
I tried to re-launch LMSA but i always get the same error. with an stock rom should you delete?
https://freeimage.host/i/2qb2sa

Do you have qcn or efs backup , if you have then can you provide that , do it fast

Related

Your device is corrupt. It cannot be trusted and will not boot Moto X4 (help me bro)

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0039062204
(bootloader) cid: 0x0032
(bootloader) channelid: 0x01
(bootloader) uid: 9EB17BE5
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *************************
(bootloader) meid:
(bootloader) date: 10-10-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3942
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-25/32:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.32.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g18bb7f8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 18 11:48:40 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.219s
This whole problem happened after I had the idea of running software (PAYTON_OPWS27.57-40-14_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
I can not unlock the bootloader and access the system, something to do? Thanks in advance!
if you can boot to fast boot you might be able to download the factory rom for your device and reinstall it. if you go to the havocos xda page there is a link to download the factory roms
I was able to find the rom looking at the command of fastboot getvar all and gave to fix the error, the problem now and that the WIFI and the network signal do not work, thanks more for the tip of friend
Blur_Version.27.301.32.payton.ret
if you haven't already, i recommend trying a factory reset. if that don't work reinstall the factory rom again. I had this happen with mine with an ulocked bootloader and Ireformated the device, reinstalled the modem files fron pie, flashed Twrp, then reflashed havocos and everything worked again. I don't know if you want to or use custom roms.

Fastboot requested download size is more than max allowed

[update/edit] I should confirm here that I obtained the most recent firmware from Motorola and checked the MD5s of all the images before flashing. I followed the flashing order in the factory xml service file (which is the same as the flashfile, except it doesn't wipe userdata). Still, getting a bootloop that kicks me into AP fastboot flash mode. Error is that there's no bootable A/B slot. No idea why. Admittedly, I haven't updated ADB or fastboot in three months, but I can't imagine that's the problem.
TL;DR I installed RETAIL OTA firmware onto a RETUS device. It's possible that I murked something else up along the way. Fortunately I can still get into a bootloader (although it's different than the usual one, no cute android dude, just centered text) and fastboot still recognizes it. Here's the getvar all:
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-d3390b3-191110
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX6DMB RV=08 PV=03 FV=0000000000000003
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZY226B4K7X
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: D92406D9
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from recovery boot mode
(bootloader) imei: 351886091464377
(bootloader) meid:
(bootloader) date: 09-08-2019
(bootloader) sku: XT1929-4
(bootloader) carrier_sku: XT1929-4
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4294
(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]: 183-29-1-6/814a8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.471.9.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05900-sdm660.0
(bootloader) version-baseband: M636_29.59.01.96R BECKHAM_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gb5f80f1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Mon Sep 23 23:07:34 CDT 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-d3390b3-191110
(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) gitrov: gitrov
(bootloader) git:storsec: git:storsec
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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.254s
Click to expand...
Click to collapse
I used Lenovo smart assistant to download the correct firmware, but I'd like to flash stuff individually instead of using LMSA, so I don't delete all my user data. However, when I try to flash the bootloader I get the title error. If I try to flash gpt.img to the partition, it just hangs. Any idea what's going on?
After much searching, I found that simply plugging into a USB port can fix the title error. Unfortunately, after flashing everything from the package I downloaded through the smart assistant, I'm still having trouble booting. I get booted into recovery with yellow and red text about not being able to load the android system, my data may be corrupt, etc. HOWEVER, the entire flashing process seemed to go swimmingly. All I can think is that I messed up the A/B partitioning somehow and it doesn't know to boot into one or something. Any ideas? Here's the new getvar:
(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: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX6DMB RV=08 PV=03 FV=0000000000000003
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZY226B4K7X
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: D92406D9
(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: 351886091464377
(bootloader) meid:
(bootloader) date: 09-08-2019
(bootloader) sku: XT1929-4
(bootloader) carrier_sku: XT1929-4
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4265
(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]: 183-29-1-6/814a8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.471.9.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05900-sdm660.0
(bootloader) version-baseband: M636_29.59.01.96R BECKHAM_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gb5f80f1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Mon Sep 23 23:07:34 CDT 2019
(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 (144)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.064s
Click to expand...
Click to collapse
The error I'm getting is No bootable A/B Slot. I went through and checked the MD5s of everything I flashed, it all checks out. I have no idea what's going on.
Fixed the problem by flashing 183.29-1-6. Apparently the issue is with the update from what I see elsewhere.

Big problem on moto X4 XT1900-6

Hi guys, my the moto X4 of my girl friend has briked and just start to fasboot.
The bootloader was not unlocked, and it's not possible unlock withou boot the sytem :crying:
c:\adb>fastboot oem unlock *********************************
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.003s]
Finished. Total time: 0.011s
Here is the get var all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-181117
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0039986521
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: F7A5D56C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359552082099232
(bootloader) meid:
(bootloader) date: 10-28-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4242
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband[0]: M660_7045.36.01.100R PAYTON_LATAMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (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]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-181117
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-181117
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-181117
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-181117
(bootloader) git:tz: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) git:hyp: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) git:devcfg: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) git:cmnlib: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) git:keymaster: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) gitrov: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) git:storsec: MBM-3.0-payton_retail-7023e53-dirty-181117
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.186s
Click to expand...
Click to collapse
No one room i can find on internet (at least for free), can be flashed
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (22245 KB) OKAY [ 0.476s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
I found this version in some paid sites XT1900-6-DS-(93014LYESAF5)-PAYTON_PPW29.69-40-4_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEMST_CFC.xml - Blur_Version.29.421.17.payton.retail.en.US (Brasil) that maybe works but the price to access is to expensive for me
I cant enter in Qualcomm to make a blankflash, i already tried but with reboot-edl, but the device just shows motorola logo (or somethimes bolt charging logo) and keeps restarting.
try download and run:
https://www.motorola.com/us/rescue-and-smart-assistant/p
You should find what you need here:
https://mirrors.lolinet.com/firmware/moto/payton/
they have proper blankflash there.
I have that firmware file for your RETBR Moto X4. I know that is a old post but if you are still interested I can upload it
mvsv said:
I have that firmware file for your RETBR Moto X4. I know that is a old post but if you are still interested I can upload it
Click to expand...
Click to collapse
Hello Friend!
Today I came across the same problem as the creator of the post and this file can help me.
Could you make this firmeware available to me, please?
This is the getvar of my Moto X4:
C:\WINDOWS\system32>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0039361419
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) meid:
(bootloader) date: 10-17-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4186
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband[0]: M660_7045.36.01.100R PAYTON_LATAMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (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]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190305
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190305
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190305
(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) gitrov: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-190305
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.232s
Click to expand...
Click to collapse

Question Moto G51 - Softbrick

Hello everybody,
I can't find correct subforum for Moto G51. Hope I can get some help here.
I have softbricked my phone by doing two mistakes:
1) Trying to flash the software for XT2171-2 on my XT2171-3
2) Forgetting to switch on "OEM unlocking" in developer options before I have started
After that phone was not starting so I went to Smart Rescue to go back to stock (CYPFQ_CMCC_RRYA31.Q3_56_99_2_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Tried flashing the stock ROM with Smart Rescue and Fastboot but it always fails, and the phone starts but is stuck on "Motorola" logo.
Is there any method to unbrick it when the bootloader is locked?
Error:
flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (21676 KB)...
OKAY [ 0.548s]
writing 'bootloader'...
-> Validating 'default.xml'
-> Preflash validation failed
-> Preflash validation failed
-> Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.764s
Click to expand...
Click to collapse
fastboot getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-51fb89de16b-220616
(bootloader) product: cypfq
(bootloader) board: cypfq
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: PRC
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM8V9001JM-B813 FV=0100 WB=2048
(bootloader) ram: 8GB SAMSUNG LP4x DIE=16Gb M5-M8=01 08 10 52
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZT3228GLP6
(bootloader) cid: 0x000B
(bootloader) channelid: 0x00
(bootloader) uid: 113092FD
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 352662831346094
(bootloader) imei2: 352662831346102
(bootloader) meid:
(bootloader) date: 12-27-2021
(bootloader) sku: XT2171-3
(bootloader) carrier_sku: XT2171-3
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4139
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 1
(bootloader) ro.carrier: cmcc
(bootloader) ro.build.fingerprint[0]: motorola/cypfq_cmcc/cypfq:11/RRYA3
(bootloader) ro.build.fingerprint[1]: 1.Q3-56-79-3/a217ba:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-07400-MANNAR.0
(bootloader) version-baseband[0]: M4350_HI431_37.1032.01.66.06R CYPFG_PR
(bootloader) version-baseband[1]: CDSDS_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g3496d9e83035
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Feb 9 04
(bootloader) kernel.version[9]: :14:24 CST 2022
(bootloader) git:xbl: MBM-3.0-uefi-ff43dd709-220616
(bootloader) git:xbl_config: MBM-3.0-uefi-ff43dd709-220616
(bootloader) git:abl: MBM-3.0-uefi-51fb89de16b-220616
(bootloader) git:rpm: MBM-3.0-uefi-970d74ef-220616
(bootloader) git:tz: MBM-3.0-uefi-45bb97c8-220616
(bootloader) git:hyp: MBM-3.0-uefi-45bb97c8-220616
(bootloader) git:devcfg: MBM-3.0-uefi-45bb97c8-220616
(bootloader) git:keymaster: MBM-3.0-uefi-37f0814b-220616
(bootloader) git:storsec: MBM-3.0-uefi-37f0814b-220616
(bootloader) git:uefisecapp: MBM-3.0-uefi-37f0814b-220616
(bootloader) gitrov: MBM-3.0-uefi-45bb97c8-220616
(bootloader) git:qupfw: MBM-3.0-uefi-6274caa-220616
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PH62
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
Click to expand...
Click to collapse
Only thing u can do is send it to motorola. They can fix it but it costs 150 PLN / 35 USD with Door to Door service. Mine they fixed in two weeks. When you receive back your phone, dont oem lock it. OEM lock is for MTK devices not QCOM. flashing lock and that's it.

Bootloop simply installing Magisk (solved)

Long time member of XDA,first time actually needing to root a phone.
I successfully unlocked the bootloader of my 64Mb dual sim XT1929-8 (EU variant I believe).
Previously unused phone, I all I did was attempt to install Magisk
Installation
The Magic Mask for Android
topjohnwu.github.io
now it won't boot but can I still start the standard recovery/bootloader.
Where did I go wrong?
This was my config before flashing:
C:\cmd\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-180526
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA_APAC
(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 (3)
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 6E5192B0
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 12-15-2018
(bootloader) sku: XT1929-8
(bootloader) carrier_sku: XT1929-8
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4251
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:8.1.0/OPW
(bootloader) ro.build.fingerprint[1]: 28.70-35/8194:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.11.39.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband[0]: M636_10.22.01.65R BECKHAM_EMEA_APACDSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g7821a6b-00003
(bootloader) kernel.version[1]: -ge77904a ([email protected]) (gcc vers
(bootloader) kernel.version[2]: ion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Sat May 26 17:35:37 CDT 2
(bootloader) kernel.version[4]: 018
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-180526
(bootloader) git:xbl: MBM-3.0-uefi-bee28a0-180526
(bootloader) gitmic: MBM-3.0-uefi-bee28a0-180526
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-180526
(bootloader) git:tz: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:hyp: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:devcfg: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib64: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:keymaster: MBM-3.0-uefi-ca80f2d-180526
(bootloader) gitrov: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:storsec: MBM-3.0-uefi-ca80f2d-180526
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.203s
Click to expand...
Click to collapse
I then followed the Magisk instructions, using a boot.img file from BECKHAM_RETAIL_8.1.0_OPWS28.70-56-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for the patch.
I chose the retail one because the phone was still on firmware 8.1.0, rather than use the EU variant, as the only file available for that was version 9.0. This was the output:
C:\cmd\adb>fastboot flash boot magiskboot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24053 KB) OKAY [ 0.874s]
Writing 'boot_a' OKAY [ 0.702s]
Finished. Total time: 1.622s
Click to expand...
Click to collapse
The phone gives the black bootloader unlocked disclaimer, then the blue motorola logo with the Verity overlay. The overlay goes away but then nothing changes further. I guess this is a bootloop?
Looking at the following helpful posts, https://forum.xda-developers.com/t/firmware-8-1-official-moto-z3-play-beckham.3805433/post-78404153
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants) Firmwares the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) =...
forum.xda-developers.com
I tried applying the unpatched boot.img. And I tried applying it to boot_a:
C:\cmd\adb>fastboot flash boot magiskboot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24053 KB) OKAY [ 0.874s]
Writing 'boot_a' OKAY [ 0.702s]
Finished. Total time: 1.622s
Click to expand...
Click to collapse
But no difference in behaviour.
I notice the recovery screen says Baseband: <not found>
I don't know why that would be gone if all I did was replace the boot partition.
This is now the output of getvar:
C:\cmd\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-180526
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA_APAC
(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 (3)
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 6E5192B0
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 12-15-2018
(bootloader) sku: XT1929-8
(bootloader) carrier_sku: XT1929-8
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4194
(bootloader) iccid:
(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.2.r1-07200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gb64b199-02190
(bootloader) kernel.version[1]: -gcdcc31b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Thu Apr 4 12:38:56 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-180526
(bootloader) git:xbl: MBM-3.0-uefi-bee28a0-180526
(bootloader) gitmic: MBM-3.0-uefi-bee28a0-180526
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-180526
(bootloader) git:tz: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:hyp: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:devcfg: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib64: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:keymaster: MBM-3.0-uefi-ca80f2d-180526
(bootloader) gitrov: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:storsec: MBM-3.0-uefi-ca80f2d-180526
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.172s
Click to expand...
Click to collapse
I'm curious also why slot-retry-count:_a would decrement from 7 to 6 ?
I thought I would ask on here before trying too many random things.
Surely it can't be too hard to reverse the flash of a single file.
TL;DR : I found the isssue myself - The firmware image I chose wasn't compatible with my stock rom even though it was for the same hardware.
~~~
Just to help anyone else with this issue in the future:
I installed Lenovo 'Rescue and Smart Assitant' and jumped through their account registration hoops.
It reflashed the entire phone with the RETEU rom upgraded to Android 9 and got it running again.
Of course it was not rooted, but this time Magisk instructions worked - using the boot.img file from the RETEU image.
I still had the following error during install:
C:\cmd\adb>fastboot flash boot magiskboot.img
(bootloader) is-logical:boot_a: not found
Click to expand...
Click to collapse
But the phone booted and is successfully rooted.

Categories

Resources