Help recovering xt1941-3 - Motorola One Questions & Answers

Hi there, I'm trying to recovery a Moto One xt1941-3 but even after a successful flash, I get the following message:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
Tried multiple firmwares, with RSD Lite or Lenovo Moto Smart Assistant but always getting the same error.
Any thoughts? I'm really desperate right now.

No one?

DogDorgs said:
No one?
Click to expand...
Click to collapse
I doubt I have a fix, but what do you get with
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs

sd_shadow said:
I doubt I have a fix, but what do you get with
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for the response.
So I've tested and I get different results of the getvar-all. I'll explain:
If I enter the fastboot mode manually (without trying to boot normally) I get this result
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0053993482
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 508356F900000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 02-04-2019
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 13 13:11:54 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-20/e4a64:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.426.30.deen.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_01.02.04.02R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-g91db513 (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 Thu Jan 23 05:01:46 CST 2020
(bootloader) sbl1.git: MBM-2.1-deen_retail-b314434-200123
(bootloader) rpm.git: MBM-2.1-deen_retail-80327a1-200123
(bootloader) tz.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) devcfg.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) keymaster.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) cmnlib.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) cmnlib64.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) prov.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) aboot.git: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 5
all: listed above
Finished. Total time: 0.225s
And If I try to boot and fall back to fastboot I get this message
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0053993482
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 508356F900000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 02-04-2019
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 13 13:15:59 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-20/e4a64:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.426.30.deen.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_01.02.04.02R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-g91db513 (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 Thu Jan 23 05:01:46 CST 2020
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
Finished. Total time: 0.217s
It's interesting because if I don't try to boot to the system, it says that the slot B is bootable.

DogDorgs said:
I doubt I have a fix, but what do you get with
Hey, thanks for the response.
So I've tested and I get different results of the getvar-all. I'll explain:
If I enter the fastboot mode manually (without trying to boot normally) I get this result
And If I try to boot and fall back to fastboot I get this message
It's interesting because if I don't try to boot to the system, it says that the slot B is bootable.
Click to expand...
Click to collapse
I don't suppose you checked
Oem lock Developer option before it stopped working?
If you did likely the bootloader could be unlocked.
You would have had to enable dev options first.
If none of those sound familiar you didn't do it.
Other than that I don't think there's a solution.
You can try
Fastboot wipe all
Or
Fastboot wipe misc
LMSA saves the firmware it downloaded.
Was that blur version 29.xxx.xx or 30.xxx?
Sent from my ali using XDA Labs
---------- Post added at 02:37 AM ---------- Previous post was at 02:31 AM ----------
Are these the firmware versions you used with RSD Lite?
https://mirrors.lolinet.com/firmware/moto/deen/official/RETBR/
XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Or
XT1941-3_DEEN_RETBR_9.0_PPKS29.68-16-21-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Sent from my ali using XDA Labs

sd_shadow said:
I don't suppose you checked
Oem lock Developer option before it stopped working?
If you did likely the bootloader could be unlocked.
You would have had to enable dev options first.
If none of those sound familiar you didn't do it.
Other than that I don't think there's a solution.
You can try
Fastboot wipe all
Or
Fastboot wipe misc
LMSA saves the firmware it downloaded.
Was that blur version 29.xxx.xx or 30.xxx?
Sent from my ali using XDA Labs
---------- Post added at 02:37 AM ---------- Previous post was at 02:31 AM ----------
Are these the firmware versions you used with RSD Lite?
https://mirrors.lolinet.com/firmware/moto/deen/official/RETBR/
XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Or
XT1941-3_DEEN_RETBR_9.0_PPKS29.68-16-21-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hi, so the version LMSA downloaded first was a 29.xxx and then downloaded the 30.xxx, with both of them installing flawlessly. I've tried to unlock the bootloader but nope, the OEM unlock was not enabled.
Another thing that I've tried was bricking the phone by installing an older Oreo rom, and then I've performed a blankflash in order to flash another time. The flash was a success but the phone still not booting.
And about those commands, seems like my fastboot is not recognizing it, when I try to boot I get this message:
Code:
fastboot wipe all
fastboot: usage: unknown command wipe
Thanks for the attention!
EDIT: Yeah, I've tried some roms from this site you've linked, included those two.

DogDorgs said:
Hi, so the version LMSA downloaded first was a 29.xxx and then downloaded the 30.xxx, with both of them installing flawlessly. I've tried to unlock the bootloader but nope, the OEM unlock was not enabled.
Another thing that I've tried was bricking the phone by installing an older Oreo rom, and then I've performed a blankflash in order to flash another time. The flash was a success but the phone still not booting.
And about those commands, seems like my fastboot is not recognizing it, when I try to boot I get this message:
Code:
fastboot wipe all
fastboot: usage: unknown command wipe
Thanks for the attention!
EDIT: Yeah, I've tried some roms from this site you've linked, included those two.
Click to expand...
Click to collapse
Sorry wrong commands
It should have been
Fastboot erase misc
Or
Fastboot erase all
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Sorry wrong commands
It should have been
Fastboot erase misc
Or
Fastboot erase all
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
So I've tried to run those commands, the misc says "access denied" and the "erase all" did work. I've run those two commands and re-flashed the last rom. No lucky thought. :/

Same
I have exactly the same problem... I can't toggle the option "Allow OEM unlock" because my phone suddenly bricked. One day it was working perfectly and the next day it shows "boot up failed". I've already try flashing several roms but nothing changes in "fastboot getvar all". My warranty isn't valid because my phone is from another country.

DogDorgs said:
So I've tried to run those commands, the misc says "access denied" and the "erase all" did work. I've run those two commands and re-flashed the last rom. No lucky thought. :/
Click to expand...
Click to collapse
did u found a solution?

Related

NEED HELP!!! Bricked XT1650-03 sheridan after flashing 8.0.0 RETUS

Please I need help. I flashed a RETUS oreo firmware over my RETEU 7.0 april 2017 update.
The upgrade was successful using the official full firmware but it gets to the stage where it encrypts the phone then it reboots and constantly gets in a reboot loop. I really need help as I have been searching for hours with no solution.
I downloaded and flashed XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Device is locked and I enabled oem unlock prior to update but i didn't unlock bootloader. I wish I had. Now I'm stuck.
I know I made mistake and I really need help. I would appreciate any help rendered
The flashing was successful. I think I shouldn't have flashed the gpt.bin file. Maybe thats the cause of the problem?
Please I am in desperate need for solution.
I got this using fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223MT6CR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AAA5AE1400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-17-2016
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:30:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: 27.76-51/58:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.58.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g72b40d5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Feb 26 05:47:32 CST 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.02-0-g722a114
(bootloader) tz.git: git=b5f954a-dirty
(bootloader) hyp.git: git=b5f954a-dirty
(bootloader) devcfg.git: git=b5f954a-dirty
(bootloader) keymaster.git: git=b5f954a-dirty
(bootloader) cmnlib.git: git=b5f954a-dirty
(bootloader) cmnlib64.git: git=b5f954a-dirty
(bootloader) prov.git: git=b5f954a-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.164s
Click to expand...
Click to collapse
FINALLY FIXED AFTER 12HOURS.
I was lucky because the phone came on and I quickly enabled "oem unlock" and unlocked bootloader then flashed stock 7.1.1 suing fastboot
It worked like a charm afterwards. Maybe the software 8.0.0 is too much for the phone.
Thanks for the support.
http://erfanoabdi.000webhostapp.com....11.58.griffin.retail.en.US&carrier=reteu&sn= there is for you phone, try flashing that
eLaDiio said:
http://erfanoabdi.000webhostapp.com....11.58.griffin.retail.en.US&carrier=reteu&sn= there is for you phone, try flashing that
Click to expand...
Click to collapse
This is a 94.4mb update file. Please how is it going to work because the phone doesn't boot up?
I am in bigger trouble now. I flashed the zip and I have qhusb_bulk
sorry my bad, and try to reflash all again?
eLaDiio said:
sorry my bad, and try to reflash all again?
Click to expand...
Click to collapse
I have just flashed oreo blankflash to restore the device but still the same issue. It stays in a reboot loop. and sometimes the modem will disappear in the fastboot mode. I cant get the device to boot up. Please any help?

help regarding flashing stock rom to Moto one

I need help regarding flashing stock rom to Moto one which is No bootable A/B Slot and OEM locked,
I have bootloader unlock key but can't unlock as it ask to enable oem unlock in setting but phone is in bootloop.
I have flashed different stock roms via fastboot, rsd lite, LMSA, all goes well but phone returns to startup failed screen. Latest rom i have tried is DEEN_PPKS29.68_16_21_20_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT1941-3_DEEN_RETUS_9.0_PPKS29.68-16-21-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is their anything that can be done to bring it to life.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-4658d8b-191103
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(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: ZY*******F9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 9A8FF06400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 35**********6
(bootloader) meid:
(bootloader) date: 10-29-2018
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri May 24 7:29:24 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-8/2414:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.371.9.deen.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_16.15.02.19R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-ga0ecad3 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Wed May 22 19:17:07 CDT 2019
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-4658d8b-191103
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
finished. total time: 0.179s
@gsm420
With the bootloader locked, I don't think so.
Sent from my ali using XDA Labs
---------- Post added at 09:08 PM ---------- Previous post was at 08:55 PM ----------
If you can force it into EDM, you can could try the blankflash
https://forum.xda-developers.com/showpost.php?p=77613798&postcount=2
This may boot it to EDM
Code:
fastboot oem blankflash
Unlikely to work with locked bootloader, but worth trying
Sent from my ali using XDA Labs
sd_shadow said:
@gsm420
With the bootloader locked, I don't think so.
Sent from my ali using XDA Labs
---------- Post added at 09:08 PM ---------- Previous post was at 08:55 PM ----------
If you can force it into EDM, you can could try the blankflash
https://forum.xda-developers.com/showpost.php?p=77613798&postcount=2
This may boot it to EDM
Code:
fastboot oem blankflash
Unlikely to work with locked bootloader, but worth trying
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Thanks for replying, but not able to put in edm
gsm420 said:
I need help regarding flashing stock rom to Moto one which is No bootable A/B Slot and OEM locked,
I have bootloader unlock key but can't unlock as it ask to enable oem unlock in setting but phone is in bootloop.
I have flashed different stock roms via fastboot, rsd lite, LMSA, all goes well but phone returns to startup failed screen. Latest rom i have tried is DEEN_PPKS29.68_16_21_20_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT1941-3_DEEN_RETUS_9.0_PPKS29.68-16-21-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is their anything that can be done to bring it to life.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-4658d8b-191103
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(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: ZY*******F9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 9A8FF06400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 35**********6
(bootloader) meid:
(bootloader) date: 10-29-2018
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri May 24 7:29:24 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-8/2414:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.371.9.deen.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_16.15.02.19R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-ga0ecad3 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Wed May 22 19:17:07 CDT 2019
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-4658d8b-191103
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
finished. total time: 0.179s
Click to expand...
Click to collapse
Did you solved your problem? I'm living the same situation. Tried to update via LMSA and now the moto one is stucked on bootloader. I flashed using fastboot commands and nothing seems to work.
sd_shadow said:
@gsm420
With the bootloader locked, I don't think so.
Sent from my ali using XDA Labs
---------- Post added at 09:08 PM ---------- Previous post was at 08:55 PM ----------
If you can force it into EDM, you can could try the blankflash
https://forum.xda-developers.com/showpost.php?p=77613798&postcount=2
This may boot it to EDM
Code:
fastboot oem blankflash
Unlikely to work with locked bootloader, but worth trying
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
How to send the phone into EDL?
claudiusuflea said:
How to send the phone into EDL?
Click to expand...
Click to collapse
Cannot unless bootloader is unlocked
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Cannot unless bootloader is unlocked
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
then, there's no hope, no way to unbrick the phone?
claudiusuflea said:
then, there's no hope, no way to unbrick the phone?
Click to expand...
Click to collapse
see my reply in
https://forum.xda-developers.com/mo...-lite-x-1941-4-fastboot-t4085913#post82354355

Motorola One Lite (X 1941-4) fastboot brick

Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 CST 2020
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
finished. total time: 0.180s
Thank you!
claudiusuflea said:
Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 CST 2020
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
finished. total time: 0.180s
Thank you!
Click to expand...
Click to collapse
You cannot downgrade firmware with a locked bootloader.
There is no Android 10 for Dean/RetEU
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
There will be no fix until there is Android 10 firmware for your device.
sd_shadow said:
You cannot downgrade firmware with a locked bootloader.
There is no Android 10 for Dean/RetEU
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
There will be no fix until there is Android 10 firmware for your device.
Click to expand...
Click to collapse
Also tried the beta for android 10 for deen-reteu, retail, retbr, and everything I found on the internet, didn't work, once android 10 stable for reteu would roll out is this phone fixable by the fastboot flashing method?
Also LMSA deleted my ro.build.version.full, it appears null on the getvar
claudiusuflea said:
Also tried the beta for android 10 for deen-reteu, retail, retbr, and everything I found on the internet, didn't work, once android 10 stable for reteu would roll out is this phone fixable by the fastboot flashing method?
Also LMSA deleted my ro.build.version.full, it appears null on the getvar
Click to expand...
Click to collapse
You may have flashed so many incompatible versions there is no fixing
Sent from my ocean using XDA Labs
sd_shadow said:
You may have flashed so many incompatible versions there is no fixing
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
I guess i have to wait or take it to a technician if the stable android 10 won't work, my wrong I didn't unlock the bootloader. Thank you very much!
sd_shadow said:
you cannot downgrade firmware with a locked bootloader.
There is no android 10 for dean/reteu
https://mirrors.lolinet.com/firmware/moto/deen/official/reteu/
there will be no fix until there is android 10 firmware for your device.
Click to expand...
Click to collapse
reteu got 10
there was 1 more ota after that for march update
n1kolaa said:
reteu got 10
there was 1 more ota after that for march update
Click to expand...
Click to collapse
Ok, do you have a copy of the firmware?
I haven't seen it.
Sent from my ali using XDA Labs
sd_shadow said:
Ok, do you have a copy of the firmware?
I haven't seen it.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Didnt saved it, can provide fw id.
edit:
n1kolaa said:
Didnt saved it, can provide fw id.
edit:
Click to expand...
Click to collapse
also new LSMA version, it did recognise my phone now, but still after rescue it would have the same error
also we have android 10 roms on lolinet
trying the reteu android 10 from lolinet as last try
claudiusuflea said:
also new LSMA version, it did recognise my phone now, but still after rescue it would have the same error
also we have android 10 roms on lolinet
trying the reteu android 10 from lolinet as last try
Click to expand...
Click to collapse
Dead. Nothing worked again. So the phone is doomed, I will try once I can to take it to a gsm. It's the emmc partition which causes this problem.
Always unlock bootloader or at least enable oem unlock in developer settings before messing with firmwares (specially when downgrading). You got a really expensive papper weight.

Bootloader Unlockable: cid: 0x0000 -- plz assist!

Hi, please help me to obtain my oem get_unlock_data,
or show me another way to unlock my Moto Z!
Thank you.
Code:
# fastboot devices
ZY223----- fastboot
# fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.058s]
# fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223TK---
(bootloader) cid: 0x0000
(bootloader) channelid: 0x40
(bootloader) uid: 038F8B1700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 01-16-2019
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 2:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: 27.76-71-2-3/3:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.271.3.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R SRS
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g63fe64c-0006
(bootloader) kernel.version[1]: 2-gdf10a01 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Tue Sep 25 04:27:10 CDT
(bootloader) kernel.version[4]: 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=5b45243-dirty
(bootloader) hyp.git: git=5b45243-dirty
(bootloader) devcfg.git: git=5b45243-dirty
(bootloader) keymaster.git: git=5b45243-dirty
(bootloader) cmnlib.git: git=5b45243-dirty
(bootloader) cmnlib64.git: git=5b45243-dirty
(bootloader) prov.git: git=5b45243-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe:
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Addendum:
I noticed, that in Settings > System > Developer options > OEM unlocking is not set to 'On'!
After each Restart the set to 'On' gets lost!
This could explain mentioned result:
# fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
How can I keep my OEM unlocking setting, or is there a way to enter Fastboot without restart?
Thank you!
[email protected] said:
Addendum:
I noticed, that in Settings > System > Developer options > OEM unlocking is not set to 'On'!
After each Restart the set to 'On' gets lost!
This could explain mentioned result:
# fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
How can I keep my OEM unlocking setting, or is there a way to enter Fastboot without restart?
Thank you!
Click to expand...
Click to collapse
You can try a factory reset or LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Sorry, it took a while, since I first had to obtain another phone; btw. Moto Z play, meanwhile rooted.
Factory reset didn't work.
I need to see, whether LMSA exe can run on Ubuntu. Never had a Windoze PC.
Thanks anyway.
[email protected] said:
Sorry, it took a while, since I first had to obtain another phone; btw. Moto Z play, meanwhile rooted.
Factory reset didn't work.
I need to see, whether LMSA exe can run on Ubuntu. Never had a Windoze PC.
Thanks anyway.
Click to expand...
Click to collapse
What software channel is it on?
It should be in getvar all as carrier:
And in settings/about phone
Something like RetUS or RetLA or Att
Sorry it's RetEU
Code:
ro.carrier: reteu
Which should be good for unlocking.
Have you tried leaving it connected to wifi to see if there is an update?
Sometimes there is a time delay for the OEM unlock toggle.
the device may need to connect to Wifi during that time.

Unlock bootloader as a device that does not start the system

Hello people, I have a problem with my moto g power, my bootloader is blocked and my device is only in fastboot mode, I can't boot the system to activate the OEM option in the settings, I've tried the original rom but it doesn't install due to the bootloader is blocked, how can I do anything?
need help !
jhonn2700 said:
Hello people, I have a problem with my moto g power, my bootloader is blocked and my device is only in fastboot mode, I can't boot the system to activate the OEM option in the settings, I've tried the original rom but it doesn't install due to the bootloader is blocked, how can I do anything?
need help !
Click to expand...
Click to collapse
Use Lenovo rescue (LMSA) and restore
and if LMSA is not able to fix it, there might be a hardware issue , maybe corrupted ram? so i'd say return it for warranty.
the system should not suddenly stop working without manually breaking some stuff
does not work, fastboot single partition error
The LMSA does not work, a single partition fastboot error appears and new updated rom's stock. someone help me!
I have the same problem. Tried to install a stock rom, then i did "fastboot oem lock", now i get the message "your device is corrupted. It cannot be trusted and will not boot". In the Fastboot Flash Mode it shows "Flashing... Locked".
Tried to run Fastboot oem unlock <Code Provided>, but i get the error:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.011s
Tried to boot most recent Stock Rom, but get "Permission Denied" errors.
Tried Lenovo Resue but it fails at 50%. Log shows access denied errors.
Below, the result for getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-rav_retail-dfa2a6b4b2-201028
(bootloader) product: rav
(bootloader) board: rav
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF5232L9LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 2A2B3EA1
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805259264
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-18-2020
(bootloader) sku: XT2045-1
(bootloader) carrier_sku: XT2045-1
(bootloader) battid: SB18C55376
(bootloader) battery-voltage: 4257
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30.
(bootloader) ro.build.fingerprint[1]: 63-35-1-15/37df17:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R RAV_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Wed Oct 28 19:
(bootloader) kernel.version[3]: 22:27 CDT 2020
(bootloader) git:xbl: MBM-3.0-rav_retail-60f322a3b-201028
(bootloader) git:xbl_config: MBM-3.0-rav_retail-60f322a3b-201028
(bootloader) git:rpm: MBM-3.0-rav_retail-ffcccb0-201028
(bootloader) git:tz: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:hyp: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:devcfg: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:cmnlib: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:cmnlib64: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:keymaster: MBM-3.0-rav_retail-056b6062-201028
(bootloader) gitrov: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:abl: MBM-3.0-rav_retail-dfa2a6b4b2-201028
(bootloader) git:qupfw: MBM-3.0-rav_retail-f848623-201028
(bootloader) git:uefisecapp: MBM-3.0-rav_retail-056b6062-201028
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 5
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C73901
all: listed above
did you manage to solve it in any way?
I still have this problem
jhonn2700 said:
did you manage to solve it in any way?
I still have this problem
Click to expand...
Click to collapse
I took it to the Motorola technical assistance and they replaced the Logic Board. Coudn't find another solution.

Categories

Resources