So I have the same issue that so many here have had. And have yet been able to fix it with the usual methods (going back to stock, flashing non-HLOS.bin, etc.) I've tried every variant of stock I could find for my XT1900-1. I even have a second XT1900-1 that's also on RETUS that I tried flashing EFS from to no avail.
The most recent thing I've done is re-write my IMEI number using an Xposed module. I've successfully got my IMEI back, but running "getvar all" shows me this:
The things that stood out to me is that I still have no MEID, ICCID, cust_md5, radio, or ufs.
I have no idea what cust_md5, radio, or ufs are -- or how to change MEID and ICCID. I still have the box, so I can get my original IDs from that. Can anyone give me info about that, or point me in the direction to do more research?
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-eca8056-191217
(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: (ORIGINAL S/N)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: C7B1C566
(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: (THE IMEI THAT I WROTE WITH XPOSED)
(bootloader) meid:
(bootloader) date: 03-14-2019
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4326
(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]: -39-6-4/4011a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.481.16.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.100a PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g81a5f80 (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 Tue Dec 17 16:30:24 CST 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191217
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191217
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191217
(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-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
Thanks for continuing the fight. I have yet to be able to bring my phone back from No-IMEI status for a second time. You can find in my previous posts a weird way I was able to recover my IMEI. I still have Wifi at least, so I just use the phone as a waterproof device to take with me when I am around water. Moved to a Pixel 3a, which has pathetic safeguards to moisture.
Here are some stuff about
Related
I recently tried loading the stock rom and now my IMEI and MAC are empty. The phone was also always unlockable but is grayed out with connect to the internet or contact your carrier. No Wifi or Mobile network can be accessed, Wifi turns off automatically when attempting to turn on. Is it possible to fix?
VinneyThe2nd said:
I recently tried loading the stock rom and now my IMEI and MAC are empty. The phone was also always unlockable but is grayed out with connect to the internet or contact your carrier. No Wifi or Mobile network can be accessed, Wifi turns off automatically when attempting to turn on. Is it possible to fix?
Click to expand...
Click to collapse
Sounds like wrong firmware or used wrong commands
Post the info from
Code:
fastboot getvar all
Remove the imei line first though.
Sent from my perry_f using XDA Labs
sd_shadow said:
Sounds like wrong firmware or used wrong commands
Post the info from
Code:
fastboot getvar all
Remove the imei line first though.
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-181231
(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: ZY224H9G8X
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 522923E8
(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: 356484080842301
(bootloader) meid:
(bootloader) date: 10-12-2017
(bootloader) sku: XT1900-1
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4257
(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]: -26-4/a2a2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.211.11.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-g6448940 (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 Dec 31 10:17:24 CST 2018
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-181231
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-181231
(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) gitrov: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-181231
(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-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.147s
Looks like you should be using
Payton Retus
https://mirrors.lolinet.com/firmware/moto/payton/official/RETUS/
Sent from my Moto E (4) using Tapatalk
Is there a way load without the ability to unlock bootloader? Everytime I try to ADB an image, it throws an invalid signature in error 21, footer error
I have no recovery, I can't boot into Android and I can not flash anything. I only have fastboot. Can someone please help?
[email protected]:~ $ fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(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: SDM630 1.0 (2)
(bootloader) serialno: ZY2257XJJD
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: E4D6217A
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 10-16-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 3866
(bootloader) iccid: 8901260971114917964
(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-13/badd5:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.55.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_7048.65.01.101R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g097f40be62ed
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x
(bootloader) kernel.version[2]: 20150123 (prerelease) (GCC) ) #1 SMP PR
(bootloader) kernel.version[3]: EEMPT Thu Sep 24 04:43:29 CDT 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) git:xbl: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) gitmic: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) git:rpm: MBM-3.0-payton_fi-f97e5eb-200924
(bootloader) git:tz: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:hyp: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:devcfg: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:keymaster: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) gitrov: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:storsec: MBM-3.0-payton_fi-68ee948c3-200924
(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-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 3
(bootloader) slot-retry-count:_b: 0
all: listed above
[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.
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
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
I used the lenovo rescue assistant to go back to stock after trying out LineageOS (it was unstable for me). everything worked for about 2 days until the phone started freezing on whatever screen it was on at the time (off, home, call, chrome, etc.). When it was not frozen, I also noticed Google Play Services or Moto App Launcher stopped working constantly until a reboot. I also tried to flash stock with the guide video on the forum, with similar results. I was able to get a logcat through adb when it was frozen this morning. Can anyone tell me what I need to do? My getvar all data is below:
Spoiler: getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-eca8056-191217
(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: ZY*********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: C755AD1A
(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-12-2017
(bootloader) sku: XT1900-1
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3907
(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]: -39-6-4/4011a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.481.16.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-g81a5f80 (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 Tue Dec 17 16:30:24 CST 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191217
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) gitmic: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191217
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) gitrov: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191217
(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: 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
EDIT: I tried to attach the logcat but it is not staying attached.