So i wanted to install the pixel experience rom onto my moto g6 play, i followed a guide on the motorola website and successfully unlocked the bootloader and it say "flashing_unlocked". i then flashed twrp to the recovery and it worked however i got some bad key and N/A boots when going into twrp. From TWRP i factory wiped the phone and forgot to back it up... then i installed the pixel experience .img as a software image and then the magisk.zip. They both installed successfully . However now when i clicked reboot, i got a long key at the top (80012A99-86FDA48-4E357816-0E549F1B-B067FD5) and it would not boot. i then attempted to uninstall magisk by installing a magisk module unistaller as a zip but i get the error 1. Now i can't unistall magisk or boot the phone, how can i fix this?
flashboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BF.55
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL52236SS8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 4E616BB100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351861090413642
(bootloader) meid:
(bootloader) date: 04-25-2018
(bootloader) sku: XT1922-2
(bootloader) carrier_sku: XT1922-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Feb 7 22:40:13 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter_n/aljeter_n:8.0.0
(bootloader) ro.build.fingerprint[1]: /OPP27.91-177/189:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.189.aljeter.r
(bootloader) ro.build.version.full[1]: etail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8937_26.30.05.75R JETER_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gc1d4a26-0000
(bootloader) kernel.version[1]: 3-gddc540d ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Nov
(bootloader) kernel.version[3]: 26 02:24:30 CST 2018
(bootloader) sbl1.git: git=MBM-NG-VBF.55-0-g8ffb6ee
(bootloader) rpm.git: git=MBM-NG-VBF.15-0-g02a0726-dirty
(bootloader) tz.git: git=1d24c88-dirty
(bootloader) devcfg.git: git=1d24c88-dirty
(bootloader) keymaster.git: git=1d24c88
(bootloader) cmnlib.git: git=1d24c88
(bootloader) cmnlib64.git: git=1d24c88
(bootloader) prov.git: git=1d24c88-dirty
(bootloader) aboot.git: git=MBM-NG-VBF.55-0-g4e3d3ac
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
N/A, bad key = completely normal after bootloader unlock
(80012A99-86FDA48-4E357816-0E549F1B-B067FD5) = normal after installing forcenc/verity disabler.
I guess the easiest way out is to flash stock firmware and try reinstalling your rom again. Magisk and forcenc/verity disabler will cause bootloop on any android 10 based rom as far as I know.
gyro_rayo said:
N/A, bad key = completely normal after bootloader unlock
(80012A99-86FDA48-4E357816-0E549F1B-B067FD5) = normal after installing forcenc/verity disabler.
I guess the easiest way out is to flash stock firmware and try reinstalling your rom again. Magisk and forcenc/verity disabler will cause bootloop on any android 10 based rom as far as I know.
Click to expand...
Click to collapse
I guess i can try that, problem is i cant find any of the retgb stock firmware. could i just use another carriers?
OrphicNinja said:
I guess i can try that, problem is i cant find any of the retgb stock firmware. could i just use another carriers?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETGB/
gyro_rayo said:
N/A, bad key = completely normal after bootloader unlock
(80012A99-86FDA48-4E357816-0E549F1B-B067FD5) = normal after installing forcenc/verity disabler.
I guess the easiest way out is to flash stock firmware and try reinstalling your rom again. Magisk and forcenc/verity disabler will cause bootloop on any android 10 based rom as far as I know.
Click to expand...
Click to collapse
Thanks for that, I kept searching for N/A and bad key, as I thought it was the root of my encryption problems, good to know it's normal
Related
Hey guys,
So I bough the latest G5S version, the Green Pomelo aka XT 1799-2. It's a wonderful phone for the price, but I am stuck with stock ROM and locked features such as camera2.api. Decided to root and followed this guide to the letter https://forum.xda-developers.com/moto-g5s/how-to/guide-unlock-bootloader-moto-g5s-t3691200 , but hit a block. When I obtained the phone, my boot loader was already indicating following warning:
"Your device failed verification and may not work properly". I assumed it was already flashed by reseller. Neverthless, I tried to unlock the bootloader using official Motorola key anyway just to receive following:
C:\Minimal ADB and Fastboot>fastboot oem unlock EG2Q6NB37LSZ2RHIX6KZ
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
I assume they locked the bootloader again, but due that I am hopeless now. I contacted their technical support, but they can only offer either full refund or replacement, which will leave me a month without a phone. Thus I am turning on you guys. Is there a way to unlock the bootloader somehow anyway? And if, could you state how?
Here is the full getvar:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX64MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322D4JM7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: AC71A4BE00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359565080402695
(bootloader) meid:
(bootloader) date: 10-08-2017
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Dec 21 19:25:12 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-108/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Thu Mar
(bootloader) kernel.version[3]: 1 20:32:27 CST 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
Cheers
Six
sixtheninth said:
C:\Minimal ADB and Fastboot>fastboot oem unlock EG2Q6NB37LSZ2RHIX6KZ
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
Click to expand...
Click to collapse
In my also gave this same error when I tried to unlock the bootloader, is giving this error because this phone already comes with the unlocked bootloader, it is blocked to flash
Try unlocking using this command
Code:
fastboot flashing unlock
Oh man, thanks a lot for that! That worked. So shall I normally proceed to root now without problems?
how to root now
jvfigueredo said:
In my also gave this same error when I tried to unlock the bootloader, is giving this error because this phone already comes with the unlocked bootloader, it is blocked to flash
Try unlocking using this command
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
Would you tell me how did you root the phone afterwards? I am trying to flash TWRP Recovery twrp-montana-3.2.3-r1.img but getting error.
sixtheninth said:
Would you tell me how did you root the phone afterwards? I am trying to flash TWRP Recovery twrp-montana-3.2.3-r1.img but getting error.
Click to expand...
Click to collapse
I don't root my phone but this twrp works fine, others releases of twrp screen bug rotate 180°, its sucks
Flash Twrp recovery
Code:
fastboot flash recovery twrp.img
I installed TWRP a long time ago, for xposed ad other things, in one instalation of a rom or a kernel my phone started to boot directly to TWRP and not to system, y tried to flash stock but the problem kept going, then i realized that if i boot to bootlader with volume- and power, then hit start the phone will boot normally, so every time i restart the phone i had to boot in bootloader and then hit start. recently i installed the official nougat rom via adb and TWRP, and i still have the problem, i am going to sell the phone now, so i need to give it as stock as possible, so i need to fix the boot issue and relock the bootloader.
I apologize for my english, i did my best to explain the situation.
Thanks
Juanes2070 said:
I installed TWRP a long time ago, for xposed ad other things, in one instalation of a rom or a kernel my phone started to boot directly to TWRP and not to system, y tried to flash stock but the problem kept going, then i realized that if i boot to bootlader with volume- and power, then hit start the phone will boot normally, so every time i restart the phone i had to boot in bootloader and then hit start. recently i installed the official nougat rom via adb and TWRP, and i still have the problem, i am going to sell the phone now, so i need to give it as stock as possible, so i need to fix the boot issue and relock the bootloader.
I apologize for my english, i did my best to explain the situation.
Thanks
Click to expand...
Click to collapse
Please connect your phone in bootloader and write command "fastboot getvar all" and share data so status can be checked for solution.
Actually you need to flash same Bootloader version again to resolve the issue
Data
zahidm said:
Please connect your phone in bootloader and write command "fastboot getvar all" and share data so status can be checked for solution.
Actually you need to flash same Bootloader version again to resolve the issue
Click to expand...
Click to collapse
Hi, i'm sorry i took so long to get the data, here it is, can you still help me out ? thanks for the reply
version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322KZMMJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 34153EE200000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355662082344936
(bootloader) meid:
(bootloader) date: 01-28-2018
(bootloader) sku: XT1791
(bootloader) carrier_sku:
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-2/e71c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.2.mon.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_37.13.03.64R MONTANA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g784476b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 12:38:10 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=9a0b157
(bootloader) devcfg.git: git=9a0b157
(bootloader) keymaster.git: git=7b4297f
(bootloader) cmnlib.git: git=7b4297f
(bootloader) cmnlib64.git: git=7b4297f
(bootloader) prov.git: git=7b4297f
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Juanes2070 said:
Hi, i'm sorry i took so long to get the data, here it is, can you still help me out ? thanks for the reply
version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322KZMMJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 34153EE200000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355662082344936
(bootloader) meid:
(bootloader) date: 01-28-2018
(bootloader) sku: XT1791
(bootloader) carrier_sku:
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-2/e71c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.2.mon.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_37.13.03.64R MONTANA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g784476b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 12:38:10 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=9a0b157
(bootloader) devcfg.git: git=9a0b157
(bootloader) keymaster.git: git=7b4297f
(bootloader) cmnlib.git: git=7b4297f
(bootloader) cmnlib64.git: git=7b4297f
(bootloader) prov.git: git=7b4297f
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Click to expand...
Click to collapse
I sold Montana but let me check solution for you
Need help, tried to downgrade a Moto G6 Play, unlocked bootloader then flashed, after this the phone service stopped working, and it isn't recognizing the Sim card.
Reflashed the stock rom to no avail.
Trying to see imei and getting no answer, and in the fastboot baseband is described has not found. Wifi is working fine.
getvar all returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 0047501565
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 35EA128F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355568092781837
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 29 18:37:43 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPP29.5
(bootloader) ro.build.fingerprint[1]: 5-25/08c6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.26.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g90c1846 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Tue Jan 29 12:40:44 CST 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190129
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Thank you all in advance.
Mount persist in TWRP. From adb shell type
chmod 0700 /persist/rfs/msm/mpss/datablock/id_00
Reboot. Give it a few minutes to provision
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Avakin said:
Need help, tried to downgrade a Moto G6 Play, unlocked bootloader then flashed, after this the phone service stopped working, and it isn't recognizing the Sim card.
Reflashed the stock rom to no avail.
Trying to see imei and getting no answer, and in the fastboot baseband is described has not found. Wifi is working fine.
getvar all returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 0047501565
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 35EA128F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355568092781837
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 29 18:37:43 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPP29.5
(bootloader) ro.build.fingerprint[1]: 5-25/08c6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.26.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g90c1846 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Tue Jan 29 12:40:44 CST 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190129
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Thank you all in advance.
Click to expand...
Click to collapse
Also, you need to reflash your bootloader
Double
Starkiller2 said:
Mount persist in TWRP. From adb shell type
chmod 0700 /persist/rfs/msm/mpss/datablock/id_00
Reboot. Give it a few minutes to provision
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Also, you need to reflash your bootloader
Click to expand...
Click to collapse
Can you guide through the persist process?
Also, every time I flash the bootloadeer it gives me a bad image error.
Then you're flashing the wrong bootloader
In twrp hit the mount button, you should see persist listed.
Check the box, that should mount it.
And are you flashing the boot image or the bootloader? What's your model, and what firmware are you flashing?
Wait, it's not reading the iccid through fastboot. Check the Sim tray. Even without service it should still see it in fastboot
Starkiller2 said:
Then you're flashing the wrong bootloader
In twrp hit the mount button, you should see persist listed.
Check the box, that should mount it.
And are you flashing the boot image or the bootloader? What's your model, and what firmware are you flashing?
Wait, it's not reading the iccid through fastboot. Check the Sim tray. Even without service it should still see it in fastboot
Click to expand...
Click to collapse
Getvar all with the sim inserted:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 0047501565
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 35EA128F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355568092781837
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 28 19: 0:39 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPP29.5
(bootloader) ro.build.fingerprint[1]: 5-25/08c6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.26.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g90c1846 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Tue Jan 29 12:40:44 CST 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190129
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190129
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190129
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
The persist folder doesn't exist, how should I proceed?
Avakin said:
Getvar all with the sim inserted:
The persist folder doesn't exist, how should I proceed?
Click to expand...
Click to collapse
Flash the same firmware your were last on for the aljeter, or one that's later. Your bootloader says this is your firmware. It also says your carrier is Brazil. So, if that first one doesn't work then try this one. If the firmware you flashed was too old the sim card won't be read properly. I've been through this before.
Spaceminer said:
Flash the same firmware your were last on for the aljeter, or one that's later. Your bootloader says this is your firmware. It also says your carrier is Brazil. So, if that first one doesn't work then try this one. If the firmware you flashed was too old the sim card won't be read properly. I've been through this before.
Click to expand...
Click to collapse
I've got some errors during the flash:
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
writing 'boot'...
(bootloader) Image signed with key bad key
And I have the bad key error while turning it on, when I try to lock the bootloader, it tells me to allow unlock on dev settings, there it doesn't let me, telling its already unlocked. This happened with the first link, should I try with the other one?
Avakin said:
I've got some errors during the flash:
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
writing 'boot'...
(bootloader) Image signed with key bad key
And I have the bad key error while turning it on, when I try to lock the bootloader, it tells me to allow unlock on dev settings, there it doesn't let me, telling its already unlocked. This happened with the first link, should I try with the other one?
Click to expand...
Click to collapse
Bad key is normal, it'll say that even if the firmware is correct. That just happens because the bootloader is unlocked. The flash errors you encountered are also normal. It just means the bootloader and gpt.bin you're flashing are older than your current one. That's not a problem. You can just skips those. If everything on your phone is working correctly, then you don't need to try any other firmware.
You don't need to relock your bootloader to do anything, or take an OTA update. Why are you trying to?
Edit: You can hide the bad key message by flashing any of my boot logos in twrp. All of them will hide it except the original one. There's also a couple a few posts down. If you plan on taking an OTA, don't do this until after taking the update. Otherwise the ota will fail since you've modified the stock firmware.
Spaceminer said:
Bad key is normal, it'll say that even if the firmware is correct. That just happens because the bootloader is unlocked. The flash errors you encountered are also normal. It just means the bootloader and gpt.bin you're flashing are older than your current one. That's not a problem. You can just skips those. If everything on your phone is working correctly, then you don't need to try any other firmware.
You don't need to relock your bootloader to do anything, or take an OTA update. Why are you trying to?
Edit: You can hide the bad key message by flashing any of my boot logos in twrp. All of them will hide it except the original one. There's also a couple a few posts down. If you plan on taking an OTA, don't do this until after taking the update. Otherwise the ota will fail since you've modified the stock firmware.
Click to expand...
Click to collapse
Neither firmwares worked, even the signal symbol doesn't appear when the phone is on. What more can I do?
Avakin said:
Neither firmwares worked, even the signal symbol doesn't appear when the phone is on. What more can I do?
Click to expand...
Click to collapse
1. Did you follow all the commands in the flash file of the firmware, such as wipe modemst1, cache, userdata?
2. Can you navigate to settings > Network & Internet > mobile network > Preferred Network Type? If so are there any options.
3. Can you also send me screen shot? I just need to see the status bar. It helps if I can see what you see.
Where are you from my guy? are you from USA or Brazil? And where did you buy your phone.
---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------
Your sku says xt1922-5 that means you more than likely have retbr. Here is your stock firmware. https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETBR/ just follow my guide and reflash and you should be good. If you don't remember what firmware you were on before just flash the most recent Oreo firmware if you want to be on Oreo. if it says anything like security downgrade then start from the first 9.0 firmware until one works with Mobile data working.
---------- Post added at 11:15 PM ---------- Previous post was at 11:04 PM ----------
Also to just avoid the security downgrade stuff please DO NOT use these following adb commands while flashing the firmwares. it will be easier for us sort of
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
Remember DO NOT not use these while flashing lol
Here's the story:
Got an used G6 Play from my cousin today, decided to do a Hard Reset, after the hard reset here it was the FRP, so i asked him the last Pattern lock and then i proceeded.
So i decided to: install twrp, root and then try Custom Roms
I unlocked the bootloader, everything ok, then i installed the decrypt script, also ok, installed Magisk through twrp, also ok.
Then i proceeded with trying custom roms: first the RessurectionRemix, i failed, because no matter which gapps i did, it said that system space was not enough
THen, i proceded to Lineage, than i downloaded the image and the gapps, after installed, it rebooted and the logo screen was "Blinking", like the logo appeared and then black screen, then again appeared and black scree. It keep like this forever, like a bootloop but i never got one blinking like this before, actually very strange.
Now, no matter what i do, it simply dont come back, i tried flashing stock rom 5 times already, and after the process, it goes like this:
It shows the Motorola logo, with some codes above (i guess the unlocked bootloader), then it shows N/a, then it goes to a brief TWRP logo and reboots. Then it starts all over again
I DON'T KNOW WHAT TO DO, THE PHONE IS DEAD, SOMEBODY HELP ME PLEASE
riquemonteiro said:
Here's the story:
Got an used G6 Play from my cousin today, decided to do a Hard Reset, after the hard reset here it was the FRP, so i asked him the last Pattern lock and then i proceeded.
So i decided to: install twrp, root and then try Custom Roms
I unlocked the bootloader, everything ok, then i installed the decrypt script, also ok, installed Magisk through twrp, also ok.
Then i proceeded with trying custom roms: first the RessurectionRemix, i failed, because no matter which gapps i did, it said that system space was not enough
THen, i proceded to Lineage, than i downloaded the image and the gapps, after installed, it rebooted and the logo screen was "Blinking", like the logo appeared and then black screen, then again appeared and black scree. It keep like this forever, like a bootloop but i never got one blinking like this before, actually very strange.
Now, no matter what i do, it simply dont come back, i tried flashing stock rom 5 times already, and after the process, it goes like this:
It shows the Motorola logo, with some codes above (i guess the unlocked bootloader), then it shows N/a, then it goes to a brief TWRP logo and reboots. Then it starts all over again
I DON'T KNOW WHAT TO DO, THE PHONE IS DEAD, SOMEBODY HELP ME PLEASE
Click to expand...
Click to collapse
Code:
fastboot getvar all
To make sure you have the correct codename and software channel for the firmware
Sent from my Moto E (4) using Tapatalk
me too
C:\_Android\Motorola\mg6>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 0047220008
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 62A7DC6800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3555XXXXXXXX
(bootloader) meid:
(bootloader) date: 05-29-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jun 24 0:45:34 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPPS29.
(bootloader) ro.build.fingerprint[1]: 55-35-18-7/6a0d0:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.7.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: M8937_34.42.05.98R JETER_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g3e480e17e11
(bootloader) kernel.version[1]: f-04280-g407726838ebf ([email protected]
(bootloader) kernel.version[2]: 8) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Sat Apr 4 12:
(bootloader) kernel.version[4]: 24:37 CDT 2020
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d6b9-200404
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6ae-200404
(bootloader) tz.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) prov.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.184s
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..
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!
danheg said:
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..
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!
Click to expand...
Click to collapse
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.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
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.
danheg said:
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.
Click to expand...
Click to collapse
Bad key is pretty common for moto devices with unlocked bootloader, usually just means the boot.img isn't signed the way it expected.
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.
danheg said:
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.
Click to expand...
Click to collapse
Moto's must be completely stock to Relock the bootloader, and even then it can be tricky.
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?
danheg said:
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?
Click to expand...
Click to collapse
Do not lock a moto device with a custom rom, unless you don't want it to work ever again.