Database Develop

Bricked Phone.. Please Help

I downloaded XT1924-7_HANNAH_TMO_8.0.0_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip from the fourms because my cell was bricked. Now it is not detecting the SIM card. Could you please help me with this?
Getvar below
bootloader) version: 0.5
bootloader) version-bootloader: moto-msm8940-BF.C3
bootloader) product: hannah
bootloader) board: hannah
bootloader) secure: yes
bootloader) hwrev: P3
bootloader) radio: 6
bootloader) storage-type: emmc
bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
bootloader) cpu: MSM8940
bootloader) serialno: ZL5224NLRP
bootloader) cid: 0x0015
bootloader) channelid: 0x85
bootloader) uid: 4FE4194800000000000000000000
bootloader) securestate: flashing_unlocked
bootloader) iswarrantyvoid: yes
bootloader) max-download-size: 535822336
bootloader) reason: Volume down key pressed
bootloader) imei: 351883090514278
bootloader) meid:
bootloader) date: 06-07-2018
bootloader) sku: XT1924-7
bootloader) carrier_sku: XT1924-7
bootloader) battid:
bootloader) iccid:
bootloader) cust_md5:
bootloader) max-sparse-size: 268435456
bootloader) current-time: "Thu Jan 1 16:27:17 UTC 1970"
bootloader) ro.build.fingerprint[0]: motorola/hannah_t/hannah:8.0.0/OCP
bootloader) ro.build.fingerprint[1]: 27.91-51-4/5:user/release-keys
bootloader) poweroffalarm: 0
bootloader) ro.build.version.full[0]: Blur_Version.27.261.5.hannah_t.t.
bootloader) ro.build.version.full[1]: 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-g5480efb-0001
bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
bootloader) kernel.version[3]: 20 09:40:55 CDT 2018
bootloader) sbl1.git: git=MBM-NG-VBF.C3-0-geb7a3e0
bootloader) rpm.git: git=02a0726-dirty
bootloader) tz.git: git=MBM-NG-VBF.C8-0-g5fefee4-dirty
bootloader) devcfg.git: git=MBM-NG-VBF.C8-0-g5fefee4-dirty
bootloader) keymaster.git: git=MBM-NG-VBF.C8-0-g5fefee4
bootloader) cmnlib.git: git=MBM-NG-VBF.C8-0-g5fefee4
bootloader) cmnlib64.git: git=MBM-NG-VBF.C8-0-g5fefee4
bootloader) prov.git: git=MBM-NG-VBF.C8-0-g5fefee4-dirty
bootloader) aboot.git: git=MBM-NG-VBF.C3-0-gff56367
bootloader) frp-state: no protection (77)
bootloader) ro.carrier: tmo
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
ll: listed above
Thanks!
burntkid

I have resolved this issue by installing TWRP on my Moto E5 plus phone and wiping the whole phone. Than I fastboot all the files on the system and loaded up the phone. It is now working fully. If anyone has issues please feel free to contact me.
Thanks,
burntkid
burntkid said:
I downloaded XT1924-7_HANNAH_TMO_8.0.0_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip from the fourms because my cell was bricked. Now it is not detecting the SIM card. Could you please help me with this?
Getvar below
bootloader) version: 0.5
bootloader) version-bootloader: moto-msm8940-BF.C3
bootloader) product: hannah
bootloader) board: hannah
bootloader) secure: yes
bootloader) hwrev: P3
bootloader) radio: 6
bootloader) storage-type: emmc
bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
bootloader) cpu: MSM8940
bootloader) serialno: ZL5224NLRP
bootloader) cid: 0x0015
bootloader) channelid: 0x85
bootloader) uid: 4FE4194800000000000000000000
bootloader) securestate: flashing_unlocked
bootloader) iswarrantyvoid: yes
bootloader) max-download-size: 535822336
bootloader) reason: Volume down key pressed
bootloader) imei: 351883090514278
bootloader) meid:
bootloader) date: 06-07-2018
bootloader) sku: XT1924-7
bootloader) carrier_sku: XT1924-7
bootloader) battid:
bootloader) iccid:
bootloader) cust_md5:
bootloader) max-sparse-size: 268435456
bootloader) current-time: "Thu Jan 1 16:27:17 UTC 1970"
bootloader) ro.build.fingerprint[0]: motorola/hannah_t/hannah:8.0.0/OCP
bootloader) ro.build.fingerprint[1]: 27.91-51-4/5:user/release-keys
bootloader) poweroffalarm: 0
bootloader) ro.build.version.full[0]: Blur_Version.27.261.5.hannah_t.t.
bootloader) ro.build.version.full[1]: 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-g5480efb-0001
bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
bootloader) kernel.version[3]: 20 09:40:55 CDT 2018
bootloader) sbl1.git: git=MBM-NG-VBF.C3-0-geb7a3e0
bootloader) rpm.git: git=02a0726-dirty
bootloader) tz.git: git=MBM-NG-VBF.C8-0-g5fefee4-dirty
bootloader) devcfg.git: git=MBM-NG-VBF.C8-0-g5fefee4-dirty
bootloader) keymaster.git: git=MBM-NG-VBF.C8-0-g5fefee4
bootloader) cmnlib.git: git=MBM-NG-VBF.C8-0-g5fefee4
bootloader) cmnlib64.git: git=MBM-NG-VBF.C8-0-g5fefee4
bootloader) prov.git: git=MBM-NG-VBF.C8-0-g5fefee4-dirty
bootloader) aboot.git: git=MBM-NG-VBF.C3-0-gff56367
bootloader) frp-state: no protection (77)
bootloader) ro.carrier: tmo
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
ll: listed above
Thanks!
burntkid
Click to expand...
Click to collapse

burntkid said:
I have resolved this issue by installing TWRP on my Moto E5 plus phone and wiping the whole phone. Than I fastboot all the files on the system and loaded up the phone. It is now working fully. If anyone has issues please feel free to contact me.
Thanks,
burntkid
Click to expand...
Click to collapse
Should go here follow this guide so if u brick again u can boot to fastboot via sd and flash all stock fw with out all the work arounds https://www.google.com/amp/s/forum..../android/tool-mmcblk0-extractor-t3306883/amp/

XT1802 remove TWRP for write Stock Recovery ,but power on in recovery mode.

Hello. I have here one XT1802. This device had the bootloader unlocked and installed the TWRP for ROOT. A few days ago, i'm write the firmware SANDERS_RETAIL_8.1.0_OPSS28.65-36-9 and relock bootloader fine and remove TWRP, but the device power on in Recovery Mode (show No command) and i make the process ( HOLD power and Vol + button) and select Reboot to Bootloader (for enter in Fastboot mode) and click in Start , Oh yeah, after that all the device turns on normal..
The device, download the OPS28.65-36-11 (OTA) but not update. I'm update for OPS28.65-36-11 using Fastboot comand and complete Firmware.
But, the device It still has the same difficulty to turn on completely. So I wanted to know if anyone has any tips on how to solve this problem and the device will turn on normally.
See down Fastboot log:
version: 0.5
version-bootloader: moto-msm8953-C2.12
product: sanders
board: sanders
secure: yes
hwrev: P4
radio: 4
storage-type: emmc
emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
cpu: MSM8953
serialno: 0043028527
cid: 0x0032
channelid: 0x19
uid: E9B4BAAC00000000000000000000
securestate: oem_locked
iswarrantyvoid: yes
max-download-size: 534773760
reason: Reboot mode set to fastboot
imei: 35411509*******
meid:
date: 01-19-2018
sku: XT1802
carrier_sku:
battid: SB18C18457
iccid:
cust_md5:
max-sparse-size: 268435456
current-time:
ro.build.fingerprint[0]: motorola/sanders_nt/sanders_nt:8.1
ro.build.fingerprint[1]: .0/OPS28.65-36-11/431cb:user/relea
ro.build.fingerprint[2]: se-keys poweroffalarm: 0
ro.build.version.full[0]: Blur_Version.28.241.8.sanders.ret
ro.build.version.full[1]: ail.en.US
ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
version-baseband[0]: M8953_41.50.07.79.01R SANDERS_BRAZILDS
version-baseband[1]: DS_CUST
kernel.version[0]: Linux version 3.18.71-perf-g810c3e8 (hud
kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
kernel.version[3]: Fri Apr 26 14:05:39 CDT 2019
sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
rpm.git: git=92e5e21-dirty
tz.git: git=e619e20
devcfg.git: git=e619e20
keymaster.git: git=e619e20
cmnlib.git: git=e619e20
cmnlib64.git: git=e619e20
prov.git: git=e619e20
aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
frp-state: no protection (0)
ro.carrier: retbr
current-slot:
slot-suffixes: _a
slot-count: 1
slot-successful:_a: INVALID
slot-successful:_b: INVALID
slot-bootable:_a: INVALID
slot-bootable:_b: INVALID
slot-retry-count:_a: unknown
slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.017s
Click to expand...
Click to collapse

Moto x4 1900-4 Brick (Lineage OS 16 stock base)

I unlock the bootloader of my moto x4 and i flash Lineage OS 16 ...all ok...but i erase all the system and by mistake i reunlock the bootloader but whitout system...
I cant start sistem because not exist! I cant reflash because bootloader is lock...
I try to flash stock rom, i tried with all stock retail roms on lolinet, i downloaded about 70Gb of stock roms and all say (Bootloader) Permison denied...
I believe the only stock can flash is the stock base of lineage os 16 , but i dont know in what stock version based lineage os 16 for motorola x4 ...
Someone in xda say the only stock rom can flash is the stock whit the same Bootloader version, but i cant find stock whit my bootloader version...And repit, i downloaded all retail stock roms exist since 2017 in this link mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
My getvar...
HTML:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-181231
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224QT2VT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x29
(bootloader) uid: AB7DEE02
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356486081004948
(bootloader) meid:
(bootloader) date: 01-11-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3846
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -26-4/a2a2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.211.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g6448940 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Dec 31 10:17:24 CST 2018
(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-181231
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:pmic: MBM-3.0-payton_retail-6b0c3d7-181231
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-181231
(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:prov: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-181231
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 5.939s

llue45 said:
I unlock the bootloader of my moto x4 and i flash Lineage OS 16 ...all ok...but i erase all the system and by mistake i reunlock the bootloader but whitout system...
I cant start sistem because not exist! I cant reflash because bootloader is lock...
I try to flash stock rom, i tried with all stock retail roms on lolinet, i downloaded about 70Gb of stock roms and all say (Bootloader) Permison denied...
I believe the only stock can flash is the stock base of lineage os 16 , but i dont know in what stock version based lineage os 16 for motorola x4 ...
Someone in xda say the only stock rom can flash is the stock whit the same Bootloader version, but i cant find stock whit my bootloader version...And repit, i downloaded all retail stock roms exist since 2017 in this link mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
My getvar...
(bootloader) kernel: uefi(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-181231(bootloader) product: payton(bootloader) board: payton(bootloader) secure: yes(bootloader) hwrev: P4(bootloader) radio: LATAM(bootloader) storage-type: eMMC(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002(bootloader) ufs: N/A(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E(bootloader) cpu: SDM630 1.0 (6)(bootloader) serialno: ZY224QT2VT(bootloader) cid: 0x0032(bootloader) channelid: 0x29(bootloader) uid: AB7DEE02(bootloader) securestate: flashing_locked(bootloader) verity-state: disabled (0)(bootloader) iswarrantyvoid: yes(bootloader) max-download-size: 536870912(bootloader) reason: UTAG bootmode configured as fastboot(bootloader) imei: 356486081004948(bootloader) meidbootloader) date: 01-11-2018(bootloader) sku: XT1900-4(bootloader) carrier_skubootloader) battid: SNN5995A(bootloader) battery-voltage: 3846(bootloader) iccidbootloader) cust_md5bootloader) max-sparse-size: 268435456(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69(bootloader) ro.build.fingerprint[1]: -26-4/a2a2:user/release-keys(bootloader) poweroffalarm: 0(bootloader) ro.build.version.full[0]: Blur_Version.29.211.11.payton.ret(bootloader) ro.build.version.full[1]: ail.en.US(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0(bootloader) version-baseband: <not found>(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g6448940 (hud(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT(bootloader) kernel.version[3]: Mon Dec 31 10:17:24 CST 2018(bootloader) git:abl: MBM-3.0-payton_retail-0e6e7ce-181231(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-181231(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-181231(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-181231(bootloader) git:tz: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) git:hyp: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) git:devcfg: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) git:cmnlib: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) git:cmnlib64: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) git:keymaster: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) gitrov: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) git:storsec: MBM-3.0-payton_retail-c593123-dirty-181231(bootloader) frp-state: no protection (0)(bootloader) ro.carrier: openmx(bootloader) current-slot: a(bootloader) running-bl-slot: _a/_a(bootloader) running-boot-lun: 0(bootloader) slot-count: 2(bootloader) slot-successful:_a: no(bootloader) slot-successful:_b: no(bootloader) slot-unbootable:_a: no(bootloader) slot-unbootable:_b: no(bootloader) slot-retry-count:_a: 6(bootloader) slot-retry-count:_b: 0all: listed abovefinished. total time: 5.939s
Click to expand...
Click to collapse
You could try
Code:
fastboot oem blankflash
Which should put the device in to
Emergency download mode
And try the blankflash post in
https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
Sent from my mata using XDA Labs

@sd_shadow thanks for looking in at these!

Not found
sd_shadow said:
You could try
Code:
fastboot oem blankflash
Which should put the device in to
Emergency download mode
And try the blankflash post in
https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Im try the comand but it say (bootloader) Command Restricted
:crying::crying::crying::crying::crying::crying::crying::crying:

llue45 said:
You could try
Im try the comand but it say (bootloader) Command Restricted
:crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
See
https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
Sent from my mata using XDA Labs

sd_shadow said:
See
https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Thanks bro i see all post, but motorola hasnt edl mode!
Thanks for your support

why is my phone stuck on boot loop

can someone explain to me why this phone is stuck on bootloop from this output. system model motorola one power xt-1942-1
kernel: uefi
version-bootloader: MBM-3.0-chef_retail-0e6e7ce-190528
product: chef
board: chef
secure: yes
hwrev: PVT
radio: PRC
storage-type: eMMC
emmc: 64GB SAMSUNG 3H6CAB RV=08 PV=02 FV=0000000000000002
ufs: N/A
ram: 6GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
cpu: SDM636 1.0 (0)
serialno:
cid: 0x0017
channelid: 0xc1
uid: 89BC3483
securestate: flashing_locked
verity-state: disabled (0)
iswarrantyvoid: yes
max-download-size: 536870912
reason: Volume down key pressed
imei:
meid:
date: 09-23-2018
sku: XT1942-1
carrier_sku: XT1942-1
battid: SB18C28957
battery-voltage: 3816
iccid:
cust_md5:
max-sparse-size: 268435456
ro.build.fingerprint[0]: motorola/chef/chef_sprout:10/QPTS3
ro.build.fingerprint[1]: 0.61-18-3/9514c:user/release-keys
poweroffalarm: 0
ro.build.version.full: <not found>
ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
version-baseband: <not found>
kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
kernel.version[3]: an 22 03:40:15 CST 2020
git:abl: MBM-3.0-chef_retail-0e6e7ce-190528
git:xbl: MBM-3.0-chef_retail-7e6e70e-190528
gitmic: MBM-3.0-chef_retail-7e6e70e-190528
git:rpm: MBM-3.0-chef_retail-881c582-190528
git:tz: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:hyp: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:devcfg: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:cmnlib: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:cmnlib64: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:keymaster: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
gitrov: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:storsec: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
frp-state: no protection (0)
ro.carrier: retcn
current-slot: b
running-bl-slot: _b/_b
running-boot-lun: 0
slot-count: 2
slot-successful:_a: no
slot-successful:_b: no
slot-unbootable:_a: yes
slot-unbootable:_b: no
slot-retry-count:_a: 0
slot-retry-count:_b: 6
all: listed above

yudestar said:
can someone explain to me why this phone is stuck on bootloop from this output. system model motorola one power xt-1942-1
kernel: uefi
version-bootloader: MBM-3.0-chef_retail-0e6e7ce-190528
product: chef
board: chef
secure: yes
hwrev: PVT
radio: PRC
storage-type: eMMC
emmc: 64GB SAMSUNG 3H6CAB RV=08 PV=02 FV=0000000000000002
ufs: N/A
ram: 6GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
cpu: SDM636 1.0 (0)
serialno:
cid: 0x0017
channelid: 0xc1
uid: 89BC3483
securestate: flashing_locked
verity-state: disabled (0)
iswarrantyvoid: yes
max-download-size: 536870912
reason: Volume down key pressed
imei:
meid:
date: 09-23-2018
sku: XT1942-1
carrier_sku: XT1942-1
battid: SB18C28957
battery-voltage: 3816
iccid:
cust_md5:
max-sparse-size: 268435456
ro.build.fingerprint[0]: motorola/chef/chef_sprout:10/QPTS3
ro.build.fingerprint[1]: 0.61-18-3/9514c:user/release-keys
poweroffalarm: 0
ro.build.version.full: <not found>
ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
version-baseband: <not found>
kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
kernel.version[3]: an 22 03:40:15 CST 2020
git:abl: MBM-3.0-chef_retail-0e6e7ce-190528
git:xbl: MBM-3.0-chef_retail-7e6e70e-190528
gitmic: MBM-3.0-chef_retail-7e6e70e-190528
git:rpm: MBM-3.0-chef_retail-881c582-190528
git:tz: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:hyp: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:devcfg: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:cmnlib: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:cmnlib64: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:keymaster: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
gitrov: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
git:storsec: MBM-3.0-chef_retail-c7b1e8b-dirty-190528
frp-state: no protection (0)
ro.carrier: retcn
current-slot: b
running-bl-slot: _b/_b
running-boot-lun: 0
slot-count: 2
slot-successful:_a: no
slot-successful:_b: no
slot-unbootable:_a: yes
slot-unbootable:_b: no
slot-retry-count:_a: 0
slot-retry-count:_b: 6
all: listed above
Click to expand...
Click to collapse
Don't know, has it worked since you relocked the bootloader?
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Don't know, has it worked since you relocked the bootloader?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
No it hasn't. I had unlocked the bootloader and flashed linage os with an aim to get to android 10. the phone was booting up and working ok other than bluetooth which had problems and it was always popping up an error message when using the phone and was irritating. So I decided to flash stock rom based on android 8 using the flash file which I wish I had opened and read after which the device was bricked and the boot loader was locked coz the flash file had an oem lock command in it. After going through the internet I now know the brick was caused by the downgrade but i need an explanation on exactly what happens.

yudestar said:
No it hasn't. I had unlocked the bootloader and flashed linage os with an aim to get to android 10. the phone was booting up and working ok other than bluetooth which had problems and it was always popping up an error message when using the phone and was irritating. So I decided to flash stock rom based on android 8 using the flash file which I wish I had opened and read after which the device was bricked and the boot loader was locked coz the flash file had an oem lock command in it. After going through the internet I now know the brick was caused by the downgrade but i need an explanation on exactly what happens.
Click to expand...
Click to collapse
Try using the unlocking code again
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try using the unlocking code again
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
It says Check 'OEM unlocking' in Android Settings > Developer
Options. It can't boot or go to recovery. I tried flashing TWRP and since then recovery is lost.

No IMEI after flashing the Stock from, Unable to Unlock the Bootloader

I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (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 Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s

hamhaingaurav said:
I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (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 Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
Click to expand...
Click to collapse
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.

riyan65 said:
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
Click to expand...
Click to collapse
Yes, I knwo there is an hope if i can unlock the bootloader, but the service center guy messed my device, I do not know how they flashed my device, they were flashing my device and said it is not turning on, i said okay return my device, i will flash it my self and after taking from them, i was trying to unlock the bootloader and I was getting the error "Code validation failure with status 7". I am also unable to get Unlock data.
What can i do now, is there any solution to it. Do i need to take my device to service center again ???

Try flashing april stock....then do the OTA update till August..

vivek1310yadav said:
Try flashing april stock....then do the OTA update till August..
Click to expand...
Click to collapse
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.

hamhaingaurav said:
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
Click to expand...
Click to collapse
PM me..