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
Related
I've been trying to root and install Lineage 16.0 on my Z2 force TMO XT1789-04 for a few weeks now.
I was able to unlock the bootloader on Motorola's website no problem.
The phone has been updated to OCXS 27.1.7.
When I run getprop ro.bootloader, MBM-3.0-nash_tmo-1f35305-190705 is my result. This didn't verify if my bootloader was OCSX, so I ran the getvar all command in fastboot, and the output said I was running MBM-3.0-nash_tmo-1f35305-190705 in slot _b. I will post all the info at the end of the post.
Earlier I made the mistake of moving ahead to set the bootloader partition to slot _a. Luckilly I didn't brick my phone. I used the following commands with no luck .
fastboot set_active other
fastboot set_active a
fastboot –set-active=_aslot
fastboot –set-active=_a
What am I doing wrong? Should I give up? I'd rather sell my phone than brick it.
If someone could point me in the right direction I'd appreciate it!!!.
Thanks!
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224B9BP4
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 14905111
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ****(deleted)
(bootloader) meid:
(bootloader) date: 07-26-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4379
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) gitrov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
Why do u have to do all of this to just install lineage 16?
I'm on T-Mobile too and I just simply:
1- fastboot flashed the pre-los zip
2- follow the normal procedure for flashing Los (although it took time to find the right twrp version actually working, many didn't flashed successfully) + magisk for root
3- mind my tmo Z2 force was already on Oreo...
Use twrp 3.3.0.0.img to flash with, I wouldn't worry about installing twrp since the updater uses Los recovery. If you must insstall twrp 3.3.1.0.zip is solid I believe. Not sure why 3..3.0.0.zip isn't there, but I have the zip if needed.
I tried to install TWRP 3.3.0-0 using fastboot flash boot (path to) twrp.img
I wasn't able to get TWRP installed. Am I using the wrong commands or twrp image?
Google_is_Watching said:
I tried to install TWRP 3.3.0-0 using fastboot flash boot (path to) twrp.img
I wasn't able to get TWRP installed. Am I using the wrong commands or twrp image?
Click to expand...
Click to collapse
You'll need to run fastboot boot twrp.img once it boots to TWRP you can use the install option within TWRP to install the twrp.zip file
rcmaehl said:
You'll need to run fastboot boot twrp.img once it boots to TWRP you can use the install option within TWRP to install the twrp.zip file
Click to expand...
Click to collapse
It worked!!! I feel dumb but grateful. Thank you!
Hello,
i need help trying to revive this motog8 play, i can do everything with the old models, but at the first time i tried to root those A/B systems, i bricked it and i think its ded.
Tried revive with rds, but doesnt recognice the xml file and the usb port, LSMA doesnt have the model yet, and by the fastboot still the same.
The server looks pretty empty, if no one can help i think its going to the thrash, cuz the techs here in my city doesnt flash devices, just change screens haha :')
Start Up Failed:
AP Fastboot Flash Mode (Secure)
No Bootable A/B Solt
Please, help, since i buy this stupid device i tried to install magisk and it died haha
Matiasfh01 said:
Hello,
i need help trying to revive this motog8 play, i can do everything with the old models, but at the first time i tried to root those A/B systems, i bricked it and i think its ded.
Tried revive with rds, but doesnt recognice the xml file and the usb port, LSMA doesnt have the model yet, and by the fastboot still the same.
The server looks pretty empty, if no one can help i think its going to the thrash, cuz the techs here in my city doesnt flash devices, just change screens haha :')
Start Up Failed:
AP Fastboot Flash Mode (Secure)
No Bootable A/B Solt
Please, help, since i buy this stupid device i tried to install magisk and it died haha
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
and post it here (remove the IMEI line)
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
sd_shadow said:
Run
Code:
fastboot getvar all
and post it here (remove the IMEI line)
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
I want to follow this close. This is 2nd or 3rd thread I have seen this failed to boot problem. It makes me second guess my choice to purchase one of these devices.
I have wondered if this phone, being Mtk soc, opens possibly to use sp flash tool for flashing and repair. This would be my first Moto device, but definitely not first Mtk. I am familiar and comfortable with sp flash tool. .
mrmazak said:
I want to follow this close. This is 2nd or 3rd thread I have seen this failed to boot problem. It makes me second guess my choice to purchase one of these devices.
I have wondered if this phone, being Mtk soc, opens possibly to use sp flash tool for flashing and repair. This would be my first Moto device, but definitely not first Mtk. I am familiar and comfortable with sp flash tool. .
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-d6ab3f7-190816
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326QRN5Q
(bootloader) cid: 0x0032
(bootloader) channelid: 0x04
(bootloader) uid: 5F9D600C3FE92E5C000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-23-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 1 22: 6: 0 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32_amx/lima:9/PMDS29
(bootloader) ro.build.fingerprint[1]: .70-70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32_amx
(bootloader) ro.build.version.full[1]: .amx.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: amxcl
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C56212
all: listed above
Matiasfh01 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-d6ab3f7-190816
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326QRN5Q
(bootloader) cid: 0x0032
(bootloader) channelid: 0x04
(bootloader) uid: 5F9D600C3FE92E5C000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-23-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 1 22: 6: 0 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32_amx/lima:9/PMDS29
(bootloader) ro.build.fingerprint[1]: .70-70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32_amx
(bootloader) ro.build.version.full[1]: .amx.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: amxcl
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C56212
all: listed above
Click to expand...
Click to collapse
So, based on what has been told. And the information in your post here. You need to use the boot.img from this firmware.
mirrors.lolinet.com >firmware >moto >lima_32 >official >AMXCL >XT2015-2_LIMA_32_AMX_9.0_PMDS29.70-70-2_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmwar...ubsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
mrmazak said:
So, based on what has been told. And the information in your post here. You need to use the boot.img from this firmware.
mirrors.lolinet.com >firmware >moto >lima_32 >official >AMXCL >XT2015-2_LIMA_32_AMX_9.0_PMDS29.70-70-2_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmwar...ubsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Doesnt work, or should i just flash the boot.img ?
Matiasfh01 said:
Doesnt work, or should i just flash the boot.img ?
Click to expand...
Click to collapse
Carefully, I have no experience with Moto. All I can say is from other device experience.
Based on the guide you quoted as followed. You downloaded firmware. Extracted the boot.img, patched that boot.img. then flashed it to slot_a and slot_b.
Then you had boot loop.
Was the firmware you downloaded the correct one that matches getvar output.(from before , not now). The firmware I linked matches getvar output from now.
And back to the question, yes try to just flash the boot.img from linked firmware to both boot_a and boot_b. Just like from the root guide, but with the stock images.
Matiasfh01 said:
Doesnt work, or should i just flash the boot.img ?
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
You want to flash the same
Blur Software version
If not sure you could just
Flash the full firmware.
Edit
Sent from my ali using XDA Labs
sd_shadow said:
Code:
fastboot flash boot boot.img
You want to flash the same
Blur Software version
If not sure you could just
Flash the full firmware.
Edit
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
did both and didnt work, and no, the lsma doesnt support the device yet
(bootloader) is-logical:boot_a
(bootloader) : not found
Sending 'boot_a' (32768 KB) OKAY [ 0.720s]
Writing 'boot_a' OKAY [ 0.589s]
Finished. Total time: 1.362s
what does the not found mean?
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
I've never tried to unlock/root my z2 play (this one is my wife's), but it is now stuck in bootloader.
Selecting the options START, RECOVERY MODE, FACTORY MODE, BP TOOLS, and QCOM all fail with the same message:
Code:
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Since we never expected this issue to happen, usb debugging and allow oem unlock hasn't been enabled. We tried to use the "Rescue and Smart Assistant" from motorola, but it fails with:
Code:
Flashboot Flash Single Partition
Flash failed. Please try again
We are using the "ALBUS_C_OPSS27.76_12_28_20_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml" motorola suggested.
I've tried using fastboot and looking through various threads on using fastboot commands to flash stock firmware, but haven't found any success. Also tried doing the steps in the firmware's servicefile.xml with no success.
Here's the output from "fastboot getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224WBXTH
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: B4C8C53E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: --REMOVED--
(bootloader) meid:
(bootloader) date: 03-19-2018
(bootloader) sku: XT1710-01
(bootloader) carrier_sku:
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:47:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus_c/albus:8.0.0/OPSS2
(bootloader) ro.build.fingerprint[1]: 7.76-12-28-20/19:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.461.19.albus_c.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8953P_41.50.07.67.03R ALBUS_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gd304391 (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]: Tue Jun 18 07:23:48 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=20bded9-dirty
(bootloader) devcfg.git: git=20bded9-dirty
(bootloader) keymaster.git: git=20bded9-dirty
(bootloader) cmnlib.git: git=20bded9-dirty
(bootloader) cmnlib64.git: git=20bded9-dirty
(bootloader) prov.git: git=20bded9-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: retus
(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
(Sorry if I forgot to remove some private info... I only remember threads telling other people to remove IMEI)
edit:
We don't care about recovering any data, just want to get the phone working again. I got the bootloader unlock code from motorola, but it doesn't work. It says:
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
Tried to use 2 different albus TWRP for recovery, but it can't validate (probably because I can't unlock bootloader)
bump
bump
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.