XT1952-1 boot.img issues

Search This thread

danheg

New member
Apr 13, 2021
4
0
Hi!

I'm new here, and some threads have been helpful already. However, I wonder if trying other different approaches might make the issue more complicated than it needs to be. Also, this isn't urgent, and I'd rather do it right than fudge around more than I already have..

I'm currently stuck with a "bad key" in the top left corner when booting the phone. I can still boot into bootloader and fastboot detects the device. I've tried overwriting the boot.img with a variety of variants, hoping it would work out, but alas it has not. I can boot into TWRP (phone wouldn't accept TWRP install from the start, but that's okay) but when I attempt to flash a LOS zip via sideload, it returns some errors.

I had originally installed a LOS + MicroG variant, which was working great, and then wanted to lock the bootloader. Well, and here I am.. :ROFLMAO:

From what I can tell, I shouldn't have to blankflash just yet. However, I'm not quite sure what the easiest path out of this pickle is. Thoughts?

Edit: I should add LMSA returns an issue when attempting to download software for the device. I tried setting it to a different XT variant, and it correctly recognizes the device, but then returns an "improper settings" message, if I remember right.

This is what getvar returns:

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-channel_retail-a5c9d71-190702
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVTB
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: D6D709D800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 03-28-2019
(bootloader) sku: XT1952-1
(bootloader) carrier_sku: XT1952-1
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 13 21:45: 9 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/channel_reteu/channel:9/P
(bootloader) ro.build.fingerprint[1]: PY29.105-134/e13ed:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.156.channel_r
(bootloader) ro.build.version.full[1]: eteu.retail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband[0]: M632_26.100.01.120.01R CHANNEL_SUPERDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf ([email protected]
(bootloader) kernel.version[1]: lbld71) (gcc version 4.9.x 20150123 (pre
(bootloader) kernel.version[2]: release) (GCC) ) #1 SMP PREEMPT Tue Jul
(bootloader) kernel.version[3]: 2 04:04:07 CDT 2019
(bootloader) sbl1.git: MBM-2.1-channel_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-channel_retail-a5c9d71-190702
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timit
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 6

Thanks for any help in advance! :D
 
Last edited:

sd_shadow

Recognized Contributor
  • Sep 21, 2011
    17,540
    1
    8,180
    South Dakota
    goo.gl
    Moto X4
    Moto G7 Power
    Hi!

    I'm new here, and some threads have been helpful already. However, I wonder if trying other different approaches might make the issue more complicated than it needs to be. Also, this isn't urgent, and I'd rather do it right than fudge around more than I already have..

    I'm currently stuck with a "bad key" in the top left corner when booting the phone. I can still boot into bootloader and fastboot detects the device. I've tried overwriting the boot.img with a variety of variants, hoping it would work out, but alas it has not. I can boot into TWRP (phone wouldn't accept TWRP install from the start, but that's okay) but when I attempt to flash a LOS zip via sideload, it returns some errors.

    I had originally installed a LOS + MicroG variant, which was working great, and then wanted to lock the bootloader. Well, and here I am.. :ROFLMAO:

    From what I can tell, I shouldn't have to blankflash just yet. However, I'm not quite sure what the easiest path out of this pickle is. Thoughts?

    Edit: I should add LMSA returns an issue when attempting to download software for the device. I tried setting it to a different XT variant, and it correctly recognizes the device, but then returns an "improper settings" message, if I remember right.

    This is what getvar returns:

    (bootloader) version: 0.5
    (bootloader) version-bootloader: MBM-2.1-channel_retail-a5c9d71-190702
    (bootloader) product: channel
    (bootloader) board: channel
    (bootloader) secure: yes
    (bootloader) hwrev: PVTB
    (bootloader) radio: 2
    (bootloader) storage-type: emmc
    (bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
    (bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
    (bootloader) cpu: SDM632
    (bootloader) serialno: [redacted]
    (bootloader) cid: 0x0032
    (bootloader) channelid: 0x00
    (bootloader) uid: D6D709D800000000000000000000
    (bootloader) securestate: flashing_unlocked
    (bootloader) iswarrantyvoid: yes
    (bootloader) max-download-size: 536870912
    (bootloader) reason: Volume down key pressed
    (bootloader) imei: [redacted]
    (bootloader) meid:
    (bootloader) date: 03-28-2019
    (bootloader) sku: XT1952-1
    (bootloader) carrier_sku: XT1952-1
    (bootloader) battid: SB18C30734
    (bootloader) iccid:
    (bootloader) cust_md5:
    (bootloader) max-sparse-size: 268435456
    (bootloader) current-time: "Tue Apr 13 21:45: 9 UTC 2021"
    (bootloader) ro.build.fingerprint[0]: motorola/channel_reteu/channel:9/P
    (bootloader) ro.build.fingerprint[1]: PY29.105-134/e13ed:user/release-ke
    (bootloader) ro.build.fingerprint[2]: ys
    (bootloader) poweroffalarm: 0
    (bootloader) ro.build.version.full[0]: Blur_Version.29.251.156.channel_r
    (bootloader) ro.build.version.full[1]: eteu.retail.en.US
    (bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
    (bootloader) version-baseband[0]: M632_26.100.01.120.01R CHANNEL_SUPERDS
    (bootloader) version-baseband[1]: DS_CUST
    (bootloader) kernel.version[0]: Linux version 4.9.112-perf ([email protected]
    (bootloader) kernel.version[1]: lbld71) (gcc version 4.9.x 20150123 (pre
    (bootloader) kernel.version[2]: release) (GCC) ) #1 SMP PREEMPT Tue Jul
    (bootloader) kernel.version[3]: 2 04:04:07 CDT 2019
    (bootloader) sbl1.git: MBM-2.1-channel_retail-b508f3a-190702
    (bootloader) rpm.git: MBM-2.1-channel_retail-22daab3-190702
    (bootloader) tz.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
    (bootloader) devcfg.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
    (bootloader) keymaster.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
    (bootloader) cmnlib.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
    (bootloader) cmnlib64.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
    (bootloader) prov.git: MBM-2.1-channel_retail-8798b8e-dirty-190702
    (bootloader) aboot.git: MBM-2.1-channel_retail-a5c9d71-190702
    (bootloader) frp-state: no protection (0)
    (bootloader) ro.carrier: timit
    (bootloader) current-slot: a
    (bootloader) running-boot-lun: 0
    (bootloader) running-slot: _a
    (bootloader) slot-suffixes: _a,_b
    (bootloader) slot-count: 2
    (bootloader) slot-successful:_a: No
    (bootloader) slot-successful:_b: Yes
    (bootloader) slot-bootable:_a: Yes
    (bootloader) slot-bootable:_b: Yes
    (bootloader) slot-retry-count:_a: 5
    (bootloader) slot-retry-count:_b: 6

    Thanks for any help in advance! :D
    This should be your firmware
    https://mirrors.lolinet.com/firmware/moto/channel/official/TIMIT/
    XT1952-1_CHANNEL_TIMIT_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

    There are newer versions like this Android 10
    XT1952-1_CHANNEL_TIMIT_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

    I would start with the version you have.
    Download the firmware, unzip, find the flash.file.xml, open it with a text editor, copy, and paste into the online flash.file convertor, link in my thread.
     

    danheg

    New member
    Apr 13, 2021
    4
    0
    Thanks! I'm trying it now.

    I do get "(bootlaoder) is-logical:system_a: not found" (or a corresponding similarity) for almost every line. Also, boot.img still returns a "bad key" during flash.

    Device reboots, and I get a "bad key," but it reboots into the operating system.

    That should allow me to reinstall LOS, or at least I can try and see if it'll do so.
     

    sd_shadow

    Recognized Contributor
  • Sep 21, 2011
    17,540
    1
    8,180
    South Dakota
    goo.gl
    Moto X4
    Moto G7 Power
    Thanks! I'm trying it now.

    I do get "(bootlaoder) is-logical:system_a: not found" (or a corresponding similarity) for almost every line. Also, boot.img still returns a "bad key" during flash.

    Device reboots, and I get a "bad key," but it reboots into the operating system.

    That should allow me to reinstall LOS, or at least I can try and see if it'll do so.
    Bad key is pretty common for moto devices with unlocked bootloader, usually just means the boot.img isn't signed the way it expected.
     

    danheg

    New member
    Apr 13, 2021
    4
    0
    Okay. 18.1 + MicroG running again. I'm also getting the N/A on boot again, as I did last time.

    Big thanks for that! I had been plucking the boot.img out of of zips in the expectation that it would eventually work. Didn't realize I needed to flash the whole system.

    I found myself in this mess because I wasn't able to properly lock the bootloader. Unless there are specific suggestions on what I should try or do better, I'd just leave it open. It bugs me a little, but it's not a huge issue.
     

    sd_shadow

    Recognized Contributor
  • Sep 21, 2011
    17,540
    1
    8,180
    South Dakota
    goo.gl
    Moto X4
    Moto G7 Power
    Okay. 18.1 + MicroG running again. I'm also getting the N/A on boot again, as I did last time.

    Big thanks for that! I had been plucking the boot.img out of of zips in the expectation that it would eventually work. Didn't realize I needed to flash the whole system.

    I found myself in this mess because I wasn't able to properly lock the bootloader. Unless there are specific suggestions on what I should try or do better, I'd just leave it open. It bugs me a little, but it's not a huge issue.
    Moto's must be completely stock to Relock the bootloader, and even then it can be tricky.
     

    danheg

    New member
    Apr 13, 2021
    4
    0
    Okay. What I take away from that is that it's difficult, if not impossible, to re-lock the bootloader of a Motorola loaded with Lineage?
     
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone