Fastboot requested download size is more than max allowed - Moto Z3 Play Questions & Answers

[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.

Related

Unlocking Bootloader - After it has been relocked (by unknown powers)

Hello XDA! My first post, and I need a bunch of help. My boot loader was unlocked for almost a year. I've installed countless roms, and rooted it several times. However, today I downloaded an app that required screen usage to be enabled. I enabled it, my phone froze, and then it powered off. (Maximo Driver, for rideshare app switching). I always try really hard to find my own information.
Issues:
Will not boot into non-stock rom
Cannot boot into Recovery
Displaying "oem_locked" When It's been unlocked
Nerd Numbers:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-2d29a27-181010
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5430304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY22576XJ4
(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: Volume down key pressed
(bootloader) imei: 356484083039509
(bootloader) meid:
(bootloader) date: 09-19-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4107
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.1.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 8.46-21-16/d00e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.24.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-06900-8x98.0
(bootloader) version-baseband: M660_7042.27.01.74.02R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gb658a68 (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]: Wed Jan 31 06:08:05 CST 2018
(bootloader) git:abl: MBM-3.0-uefi-2d29a27-181010
(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 (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot: _b
(bootloader) running-bl-slot: unknown/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: unknown
(bootloader) slot-successful:_b: unknown
(bootloader) slot-unbootable:_a: unknown
(bootloader) slot-unbootable:_b: unknown
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.748s
PLZ SEND HELP!

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.

No celluar signal and unreliable wifi after switching back to stock

I recently bought a plan at Boostmobile. The plan would not work, and dialing the ##72786# code wouldn't work on my custom rom. I switched to stock via the lolinet mirror & fastboot. Now the code works, but my wifi is not staying connected, and I have no signal what so ever. I have no clue what to do, would appreciate some help. Thanks!
dev1334 said:
I recently bought a plan at Boostmobile. The plan would not work, and dialing the ##72786# code wouldn't work on my custom rom. I switched to stock via the lolinet mirror & fastboot. Now the code works, but my wifi is not staying connected, and I have no signal what so ever. I have no clue what to do, would appreciate some help. Thanks!
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
And post the results here, after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Hi. I ended up fixing the phone calls and texts late last night with the method from https://forum.xda-developers.com/showpost.php?p=81199035&postcount=28. The only thing I did differently was installing my custom from back on after the steps listed as it still refused to work for me after that. The data was not working though, so I had to reinstall stock to do a PRL update, but it won't update, and now nothing is working again...
Here's my getvar output:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-171214
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(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 (2)
(bootloader) serialno: ZY2258ZTFD
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 50569AF6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 12-14-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4285
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:8
(bootloader) ro.build.fingerprint[1]: .0.0/OPW27.57-25-2/2:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.2.payton_fi.go
(bootloader) ro.build.version.full[1]: ogle_fi.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0d9dbc8-00001
(bootloader) kernel.version[1]: -g01d2530 ([email protected]) (gcc vers
(bootloader) kernel.version[2]: ion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Thu Dec 14 09:42:35 CST 2
(bootloader) kernel.version[4]: 017
(bootloader) git:abl: MBM-3.0-uefi-641a15b-171214
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-171214
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-171214
(bootloader) git:rpm: MBM-3.0-uefi-245b046-171214
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.371s
dev1334 said:
Hi. I ended up fixing the phone calls and texts late last night with the method from https://forum.xda-developers.com/showpost.php?p=81199035&postcount=28. The only thing I did differently was installing my custom from back on after the steps listed as it still refused to work for me after that. The data was not working though, so I had to reinstall stock to do a PRL update, but it won't update, and now nothing is working again...
Here's my getvar output:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-171214
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(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 (2)
(bootloader) serialno: ZY2258ZTFD
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 50569AF6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 12-14-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4285
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:8
(bootloader) ro.build.fingerprint[1]: .0.0/OPW27.57-25-2/2:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.2.payton_fi.go
(bootloader) ro.build.version.full[1]: ogle_fi.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0d9dbc8-00001
(bootloader) kernel.version[1]: -g01d2530 ([email protected]) (gcc vers
(bootloader) kernel.version[2]: ion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Thu Dec 14 09:42:35 CST 2
(bootloader) kernel.version[4]: 017
(bootloader) git:abl: MBM-3.0-uefi-641a15b-171214
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-171214
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-171214
(bootloader) git:rpm: MBM-3.0-uefi-245b046-171214
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-171214
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.371s
Click to expand...
Click to collapse
Which firmware are you using
it says
Blur_Version.27.21.2.payton_fi.go
Motorola Blur 27.xxx.xx is Android 8.0
RETUS/XT1900-1_PAYTON_RETUS_9.0_PPWS29.69-39-6-4
is the newest on
https://mirrors.lolinet.com/firmware/moto/payton/RETUS
Android 9 = Motorola Blur 29.xxx.xx
from getvar software version ro.carrier: retus
I would just use LMSA's Flash/Update or Flash/rescue options
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
or you could try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
but I see
Code:
slot-successful:_b: no
which LMSA should fix
Sent from my jerry_cheets using XDA Labs
I'm using the FI Firmware since my moto x4 is the android one variant.
Is the moto x4 the Moto (4th gen)? edit: nevermind it is, looked it up
Thanks! Trying lmsa now
It worked! Though after flashing stock I had to flash copy-partition.zip (From https://androidfilehost.com/?fid=11410963190603885202) to get it to work.
Thanks so much, shadow!
If it cuts out again within a few hours I'll post here, but it seems stable right now.
dev1334 said:
It worked! Though after flashing stock I had to flash copy-partition.zip (From https://androidfilehost.com/?fid=11410963190603885202) to get it to work.
Thanks so much, shadow!
If it cuts out again within a few hours I'll post here, but it seems stable right now.
Click to expand...
Click to collapse
Great, if you can please post the new getvar all?
I'm curious.
Sent from my jerry_cheets using XDA Labs
Sure! Here it is:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056-200126
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(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 (2)
(bootloader) serialno: ZY2258ZTFD
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 50569AF6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 12-14-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4345
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:9
(bootloader) ro.build.fingerprint[1]: /PPWS29.69-39-6-5/44949:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.31.payton_fi.
(bootloader) ro.build.version.full[1]: google_fi.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gca8dc87 (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 Sun Jan 26 23:06:42 CST 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056-200126
(bootloader) git:xbl: MBM-3.0-payton_fi-dec7b7c-200126
(bootloader) gitmic: MBM-3.0-payton_fi-dec7b7c-200126
(bootloader) git:rpm: MBM-3.0-payton_fi-b0c6622-200126
(bootloader) git:tz: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:hyp: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:devcfg: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:cmnlib: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:keymaster: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) gitrov: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:storsec: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) frp-state: no protection (77)
(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: yes
(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.476s
Thanks again!
dev1334 said:
Sure! Here it is:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056-200126
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(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 (2)
(bootloader) serialno: ZY2258ZTFD
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 50569AF6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 12-14-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4345
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:9
(bootloader) ro.build.fingerprint[1]: /PPWS29.69-39-6-5/44949:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.31.payton_fi.
(bootloader) ro.build.version.full[1]: google_fi.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gca8dc87 (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 Sun Jan 26 23:06:42 CST 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056-200126
(bootloader) git:xbl: MBM-3.0-payton_fi-dec7b7c-200126
(bootloader) gitmic: MBM-3.0-payton_fi-dec7b7c-200126
(bootloader) git:rpm: MBM-3.0-payton_fi-b0c6622-200126
(bootloader) git:tz: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:hyp: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:devcfg: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:cmnlib: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:keymaster: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) gitrov: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) git:storsec: MBM-3.0-payton_fi-fa205ea-dirty-200126
(bootloader) frp-state: no protection (77)
(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: yes
(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.476s
Thanks again!
Click to expand...
Click to collapse
This line
(bootloader) running-bl-slot: _a/_a
Should be
(bootloader) running-bl-slot: _a/_b
I don't know what that means
Maybe from the copy partitions.zip ?
Sent from my ali using XDA Labs
---------- Post added at 01:41 AM ---------- Previous post was at 01:38 AM ----------
Nevermind it's probably correct.
Sent from my ali using XDA Labs

Unable to solve. I made the mistake of blocking the bootloader before finishing installing the Stock ROM on the Moto Z3 Play

Hello everyone, everything good?
I bricked my Z3 bike stupidly. I was doing the procedure to install the stock ROM again. But I accidentally blocked the botloader before finishing the process. Now, my phone is running Havoc OS and I can't unlock the bootloader. The option is only available at Stock rom.
What are the alternatives for me to perform the procedure.
Is it still possible or have I lost my Moto Z3 forever?
D:\Celulares\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-71699b6-191109
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(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: SDM636 1.0 (1)
(bootloader) serialno: 0052543606
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: DAAC0870
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 354106094264857
(bootloader) meid:
(bootloader) date: 01-17-2019
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4223
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-15/4d8b92:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.261.22.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: M636_29.59.01.96R BECKHAM_BRAZILDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gd4c7d20 (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]: Sat Nov 9 23:51:39 CST 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-71699b6-191109
(bootloader) git:xbl: MBM-3.0-beckham_retail-56c771b-191110
(bootloader) gitmic: MBM-3.0-beckham_retail-56c771b-191110
(bootloader) git:rpm: MBM-3.0-beckham_retail-4696e9e-191109
(bootloader) git:tz: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) git:hyp: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) git:devcfg: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) git:keymaster: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) gitrov: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) git:storsec: MBM-3.0-beckham_retail-3b6f96d-191109
(bootloader) frp-state: no protection (0)
(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: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.568s
D:\Celulares\Minimal ADB and Fastboot>
Thanks
Josenil Santana

It still not find baseband

My moto x4 baseband dont work. After made an clean install with SuperiorOS rom, it dosent find the mobile network. Wifi works prefect, after flashed the modem after an guide.
Still it says not found when I go into fastboot mode. But adb flashing works, no errors. I looked up the EU version xt1900-7 and rom works nice.
Still no contact with the simcard. Do I miss something? I read about EDL in here, but I got confused.
Plus each time I boot, it comes after frusted momemnt "Verity mode is set to disabled".
Here is the code after fastboot getvar:
(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: ZY22******
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 88462E8D
(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: ***************
(bootloader) meid:
(bootloader) date: 10-21-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4268
(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: <not found>
(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: reteu
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(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
all: listed above
Finished. Total time: 0.132s
Click to expand...
Click to collapse
Try going back to stock with this

Categories

Resources