Database Info

Moto G XT1032 8GB - Completely stock and bootloader locked stuck on Motorola logo

Hello everyone,
last week my Moto G (never unlocked, and completely stock) stopped working. I was on lastest official update, that is Lollipop 5.1, but the problem didn't come up with the update, this was later.
One morning (I have not been shutting down the phone for 1 month I guess) I wake up, it's off. I switch it on and it stays on Motorola logo forever.
If I try to go to fastboot (bootloader version 41.1A) it works, but if I select any option (except the barcode one, the only one working) the phone will go back to the Motorola logo, so I am unable to factory reset and even to go in recovery!
So I tried to erease everything using fastboot and PC: it can communicate with PC, and all commands work EXCEPT the commands that must act on partitions, they ALWAYS return "Remote failure" error.
At that point I tried to unlock the bootloader, maybe that was the problem, but no, same error, always.
Any idea guys? Save my phone please
This is the output for fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CPXQ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: BAAE0F020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Oct 3 15:18:41 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 18:36:22 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.068s

I have the same exact problem!
Nabbolo said:
Hello everyone,
last week my Moto G (never unlocked, and completely stock) stopped working. I was on lastest official update, that is Lollipop 5.1, but the problem didn't come up with the update, this was later.
One morning (I have not been shutting down the phone for 1 month I guess) I wake up, it's off. I switch it on and it stays on Motorola logo forever.
If I try to go to fastboot (bootloader version 41.1A) it works, but if I select any option (except the barcode one, the only one working) the phone will go back to the Motorola logo, so I am unable to factory reset and even to go in recovery!
So I tried to erease everything using fastboot and PC: it can communicate with PC, and all commands work EXCEPT the commands that must act on partitions, they ALWAYS return "Remote failure" error.
At that point I tried to unlock the bootloader, maybe that was the problem, but no, same error, always.
Any idea guys? Save my phone please
This is the output for fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9290CPXQ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: BAAE0F020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Oct 3 15:18:41 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_reteu/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.EURetail.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00R EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 18:36:22 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.068s
Click to expand...
Click to collapse
My phone was stuck on blue logo in a bootloop, unable to access anything even after entering bootloader. I flashed the firmware through amd but the problem still exists! Please help

It sounds like emmc corruption for which there is no cure. Unfortunately, without an unlocked Bootloader - your options are limited. However we can try some things.
Flash the latest XT1032 (try both GPE and Retail) Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
It sounds like emmc corruption for which there is no cure. Unfortunately, without an unlocked Bootloader - your options are limited. However we can try some things.
Flash the latest XT1032 (try both GPE and Retail) Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
What are the chances with having an unlocked Bootloader?

Xephor_EX said:
What are the chances with having an unlocked Bootloader?
Click to expand...
Click to collapse
How do you mean? Is there a question mark over if the Bootloader is locked or Unlocked? Assuming the Bootloader is locked, the flashing the factory firmware image may resolve a partition issue - if one exists - and allow you to then unlock the Bootloader.
Make sure you are following the Bootloader unlocking tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6

lost101 said:
How do you mean? Is there a question mark over if the Bootloader is locked or Unlocked? Assuming the Bootloader is locked, the flashing the factory firmware image may resolve a partition issue - if one exists - and allow you to then unlock the Bootloader.
Make sure you are following the Bootloader unlocking tutorial: http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
No, I mean that my bootloader is unlocked, I tried flashing the stock firmwares but the problem still persists.

Xephor_EX said:
No, I mean that my bootloader is unlocked, I tried flashing the stock firmwares but the problem still persists.
Click to expand...
Click to collapse
fastboot boot twrp.img​
Factory reset (and format data if necessary) and flash a custom ROM.

lost101 said:
fastboot boot twrp.img​
Factory reset (and format data if necessary) and flash a custom ROM.
Click to expand...
Click to collapse
I can't enter recovery. The only option which works is the Barcodes one :/

Xephor_EX said:
I can't enter recovery. The only option which works is the Barcodes one :/
Click to expand...
Click to collapse
I didn't ask you to enter Recovery. Do that command via fastboot.

lost101 said:
I didn't ask you to enter Recovery. Do that command via fastboot.
Click to expand...
Click to collapse
I know, I did that. After the the fastboot flashes twrp, the phone screen goes black and shows the moto logo then re-enters bootloader.

Xephor_EX said:
I know, I did that. After the the fastboot flashes twrp, the phone screen goes black and shows the moto logo then re-enters bootloader.
Click to expand...
Click to collapse
I just need to be clear, you are doing:
fastboot boot twrp.img​
not:
fastboot flash recovery twrp.img​

lost101 said:
I just need to be clear, you are doing:
fastboot boot twrp.img​
not:
fastboot flash recovery twrp.img​
Click to expand...
Click to collapse
Mhm, yes.

It looks bad for you. The only remaining option (in my opinion) is to treat the phone as a hard-brick, and unbrick it. This may be a way to undo whatever corruption has occurred on the phone.
[HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide]​

lost101 said:
It looks bad for you. The only remaining option (in my opinion) is to treat the phone as a hard-brick, and unbrick it. This may be a way to undo whatever corruption has occurred on the phone.
[HOW TO] Unbrick Moto G 2013! [Falcon, Peregrine] [Lollipop guide]​
Click to expand...
Click to collapse
Will try it tomorrow. Thanks for the help man, appreciate it.
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
Xephor_EX said:
Will try it tomorrow. Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
The phone has actually died before in 2015 due to downgrade from 5.1 Brazil to 4.4.4 updating to 5.0.2 through OTA. A lot of people had been waiting for the mbm files for lollipop and I only got it unbricked through that method in June and now this happened :/

[Q] Moto G stuck on "Warning Bootloader unlocked" screen[but RECOVERY, FASTBOOT work]

[Q] Moto G stuck on "Warning Bootloader unlocked" screen[but RECOVERY, FASTBOOT work]
A friend sent the phone(MOTO G XT 1069) for assistance, and I believe they bricked the phone, but they told him the "board is defective" .
I have tried mfastboot + adb with ROM 4.4.4 STOCK(all commands) and others ROM's, but it restarts on the same white screen, it vibrates but does not leave this screen(warning bootloader...) ... and RSD LITE (a failure happens) ...
Ps: it can also receive charge through the charger.
ps¹: Should I really give up?
thanks

LOG fastboot:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4887
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x7
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 0434404824
(bootloader) cid: 0x000C
(bootloader) channelid: 0x19
(bootloader) uid: DFB473060F000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355***********2
(bootloader) meid:
(bootloader) date: 2014-12-11
(bootloader) sku: XT1069
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jul 8 21:38:38 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retbr_dstv/titan_ud
(bootloader) ro.build.fingerprint[1]: stv:6.0/MPB24.65-34-3/3:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.81.3.titan_retbr_
(bootloader) ro.build.version.full[1]: dstv.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g3a1ecea-00026-g0a0
(bootloader) kernel.version[1]: ded4 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Mon Aug 22 14:
(bootloader) kernel.version[3]: 24:06 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.87-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.87-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.87-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.87-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.87-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: 04*******4
(bootloader) sutinfo:
(bootloader) ro.carrier: retbr
all: listed above
finished. total time: 0.069s

Sorry can't help you much as I'm a bit of a novice but think people will need more info.
What recovery are you using ...twrp ?
And is it the latest version ,does it Boot into the bootloader menu OK ?
I'm not even sure which version of moto g that is but presuming its newer than my xt1039 so why try such a old ROM?
Sent from my XT1039 using Tapatalk

steve.loveday said:
Sorry can't help you much as I'm a bit of a novice but think people will need more info.
What recovery are you using ...twrp ?
And is it the latest version ,does it Boot into the bootloader menu OK ?
I'm not even sure which version of moto g that is but presuming its newer than my xt1039 so why try such a old ROM?
Sent from my XT1039 using Tapatalk
Click to expand...
Click to collapse
Recovery: Apparently it is stock, is written "Android Recovery"
Old ROM, was to try to see if he(moto g) would come back ...
thanks and forgive my english

Desmios said:
Recovery: Apparently it is stock, is written "Android Recovery"
Old ROM, was to try to see if he(moto g) would come back ...
thanks and forgive my english
Click to expand...
Click to collapse
Sounds like its just had its bootloader unlocked at that's it
Double check your model is definitely xt1069 and follow this guide to put new recovery and ROM
https://wiki.cyanogenmod.org/w/Install_CM_for_titan
Sent from my XT1039 using Tapatalk

I had exactly the same problem as you on an XT1032. It was a faulty internal storage (faulty hardware). It lets you flash the files and replace recovery and everything, but never boots, always stays at the bootlogo, not even bootanimation.
You can try the following:
a) Download the stock firmware from another source, then flash it again via mfastboot, read carefully the command output in the computer and in the fastboot screen. Both should say OK or report success in some way. Check if some command causes pink/red message lines in the fastboot screen.
b) Maybe you're forgetting some command in mfastboot?
c) Try flashing TWRP, then wiping all partitions from there and then flashing CyanogenMOD or another stable ROM. If there's an IO error, TWRP's verbosity will help you finding it.
Good luck.

moralesnery said:
I had exactly the same problem as you on an XT1032. It was a faulty internal storage (faulty hardware). It lets you flash the files and replace recovery and everything, but never boots, always stays at the bootlogo, not even bootanimation.
You can try the following:
a) Download the stock firmware from another source, then flash it again via mfastboot, read carefully the command output in the computer and in the fastboot screen. Both should say OK or report success in some way. Check if some command causes pink/red message lines in the fastboot screen.
b) Maybe you're forgetting some command in mfastboot?
c) Try flashing TWRP, then wiping all partitions from there and then flashing CyanogenMOD or another stable ROM. If there's an IO error, TWRP's verbosity will help you finding it.
Good luck.
Click to expand...
Click to collapse
Hello
My Moto G is also stuck on the unlocked bootloader screen, i cant even turn my mobile off (only via fastboot-> recover -> turn mobile off ).
I would flash a rom but i went totally wrom it seems.. im a noob with this things..
So, I have cyanogenmod recovery, but ive already tried to factory reset, wipe system partition and cache, but nothing has changed.
My PC dont recognize my MOTO G anymore because USB debugging is probably off.. Thats why i cant use command promt now ...
So.. is my mobile broken forever?
Or is there someone who can fix it?
(I was also wondering if someone is Dutch here, so i can bring the phone to repair it... if he can be repaired)
Im afraid he will never works again
Kind regards
Lauji
UPDATE: Solved by new recovery (twrp) and flashed another rom with GApps Package.

xt1955-5 Null imei

is my first time rooting and i run into some problems with my xt1955-5.
the phone no longer recognizes the sim card and imei null appears when i check for the imei i have my phone rooted so i already check into the modem folder and carrier and there is no files there.
I would appreciate the help
update i fix my problem following this steps
https://forum.xda-developers.com/showpost.php?p=80052655&postcount=117
thanks to sd_shadow for the help

zaxcast said:
is my first time rooting and i run into some problems with my xt1955-5.
the phone no longer recognizes the sim card and imei null appears when i check for the imei i have my phone rooted so i already check into the modem folder and carrier and there is no files there.
I would appreciate the help
Click to expand...
Click to collapse
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs

thanks
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[*][Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
thanks bro i finaly fix it and dindt lost my root thanks

sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Having this same problem I think, I can't check IMEI using *#0606# (Only Serial number appears and some barcode) nor can I see anything on Settings (Both IMEI are blank, MIN, PRL version and MEID are unknown), I can only check IMEI (IMEI1 only) using "fastboot getvar all". I already tried flashing NON-HLOS.bin, erasing modems and flashing fsg, but still doesn't work. It stopped working some time after I had failed installing custom ROMs and went back to stock (I'm almost 100% sure it was working then after a few days it stopped working, it also stopped on an unrooted Moto G7 Play but still works on a Custom ROM+Magisk Moto G5)
https://forum.xda-developers.com/g7-power/help/sim-card-stopped-t4040745
https://forum.xda-developers.com/g7-power/help/lock-bootloader-oem-unlocking-t4051605 (I only ever flashed stock using eraseandupdate.bat and this thread, so it wasn't caused by "fastboot erase all". I did flash RETUS once (my device is RETBR), but that's after it'd stopped working already)

sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
so i am having a similar issue, unknown baseband, IMEI. I did try the flash of NON-HLOS.bin and fsg.mbn but did nothing. and i wasnt able to do a backup before the phone hard bricked. i did use blankflash to recover the phone from the hardbrick. then i found that pp029.114-63_cid50 worked to restore my phone to boot up the system.

crazyc5127 said:
so i am having a similar issue, unknown baseband, IMEI. I did try the flash of NON-HLOS.bin and fsg.mbn but did nothing. and i wasnt able to do a backup before the phone hard bricked. i did use blankflash to recover the phone from the hardbrick. then i found that pp029.114-63_cid50 worked to restore my phone to boot up the system.
Click to expand...
Click to collapse
What does
Code:
fastboot getvar all
Say?

sd_shadow said:
What does
Code:
fastboot getvar all
Say?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(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: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s

crazyc5127 said:
What does
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(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: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s
Click to expand...
Click to collapse
You used the metro pcs firmware?
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
Sent from my perry_f using XDA Labs

sd_shadow said:
You used the metro pcs firmware?
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
i think it was just a blank firm to be honest. which of those firmware should i download and flash? the newest, right?

crazyc5127 said:
i think it was just a blank firm to be honest. which of those firmware should i download and flash? the newest, right?
Click to expand...
Click to collapse
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
just finished the flash, i am able to see all the barcodes with *#06#. thank you for the proper link, searching on my own was close but still off just a little bit.
now, my end goal for this phone is to take it off the Metro network and have it on T-Mobile network directly. i recently upgraded providers, but got a phone that, to me, isnt quite as good as the G7 Power, the REVVlry Plus. its still a great phone, as it is a moto build, but the battery is what has me not wanting to use it. any pointers on going this route? i would like to have root access as well, so i can tune and tinker more.

https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
this is what i ended up using to get my phone back to life. now the phone sits at just having an unlocked bootloader.
my goal for this phone is to remove the Metro firmware and replace it with tmobile firmware. or root to be able to use any sim card.

sd_shadow said:
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
You should never use the firmware to rescue your phone, that was the problem at first place to lose your baseband. Use last known working firmware to rescue

Metro by T-Mobile G7 Power - was hard bricked now no IMEI

So I have a G7 Power from Metro. Bootloader is unlocked, TWRP is not loaded yet, device DOES NOT have an IMEI right now.
I am attaching some screenshots of the main details of my phone. I am at a loss as to what to do next. Someone please help me. I am pretty sure that I need to find a way to put an IMEI on the phone before I can do anything with it, right???
Motorola_Moto_XT1955-5_OCEAN_PPO29.114-63_CID50 -- this is the build I used when I flashed in from hard brick. I did try a couple other builds but this is the only one that went full way through, and booted up.

crazyc5127 said:
So I have a G7 Power from Metro. Bootloader is unlocked, TWRP is not loaded yet, device DOES NOT have an IMEI right now.
I am attaching some screenshots of the main details of my phone. I am at a loss as to what to do next. Someone please help me. I am pretty sure that I need to find a way to put an IMEI on the phone before I can do anything with it, right???
Motorola_Moto_XT1955-5_OCEAN_PPO29.114-63_CID50 -- this is the build I used when I flashed in from hard brick. I did try a couple other builds but this is the only one that went full way through, and booted up.
Click to expand...
Click to collapse
You destroyed the baseband
Sent from my LG-LS997 using Tapatalk

cgigate said:
You destroyed the baseband
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
any way to repair it?

crazyc5127 said:
any way to repair it?
Click to expand...
Click to collapse
If you don't have backup, try to flash thr blankflash
Sent from my LG-LS997 using Tapatalk

cgigate said:
If you don't have backup, try to flash thr blankflash
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
thats what i used to be able to see the phone and get it back into fastboot after the hard brick.

crazyc5127 said:
thats what i used to be able to see the phone and get it back into fastboot after the hard brick.
Click to expand...
Click to collapse
Try to flash back the original version firmware (before it got brick) to see if it brings back baseband. If not , you may need to pull off from the same variant phone
Sent from my LG-LS997 using Tapatalk

cgigate said:
Try to flash back the original version firmware (before it got brick) to see if it brings back baseband. If not , you may need to pull off from the same variant phone
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
i ran a getvar all cmd and i can see the IMEI there, but the baseband is not found. And I didn't fully prepare for this task, as i didnt do a back-up before i tried flashing TWRP, which resulted in the hard brick.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(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: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s

How did you get a Verizon bootloader installed ?
Sent from my moto g(7) power using Tapatalk

MrCamby said:
How did you get a Verizon bootloader installed ?
Click to expand...
Click to collapse
Fastboot your factory image for your model device. Bootloader is part of it... Without a bootloader I believe the phone is a brick. I believe these have more than one bootloader. That may not be correct but seems like I read that somewhere. But not all AB partition Android devices are the same. My Pixel XL was AB and I never bricked it like I did in the beginning with my G7 Power.

Try to flash stock without wiping userdata

How to unlock Moto G stylus bootloader? Moto says not qualified

I just bought a new Moto G Stylus straight from Motorola website. I am familiar in general with the unlock process, as I have an unlocked/rooted Moto G6.
Anyway, I went to the Moto website using both Chrome and Firefox, and when I paste my unlock code it says that my phone is not qualified. I am unable to request an unlock code because of this. I don't understand why that would be the case, since this is straight from Motorola, and others have unlocked the phone here.
I've tried to format the unlock code myself, as well as by using the "formatter tool" on their website.
This is the unlock code I got from my phone:
Code:
(bootloader) 3A95801400567210#5A46363532334E
(bootloader) 4C4647006D6F746F2067200000#A861
(bootloader) C41232F748E8C9B0BAA949482C5A52C
(bootloader) 978A4#CBB8389400000000000000000
(bootloader) 0000000
Here is my formatted version:
Code:
3A95801400567210#5A46363532334E4C4647006D6F746F2067200000#A861C41232F748E8C9B0BAA949482C5A52C978A4#CBB83894000000000000000000000000
My phone is a sofiap retail XT2043-4.

All your info looks good to me, same formatting & length as the data that I used to unlock my Moto G Stylus. I have the same XT2043-4 SKU, also purchased from the Motorola Website. I was able to unlock my device on 5/6/2020. My best guess is that the Moto Unlock Tool is broken, or your phone is from a newer batch than mine and Motorola hasn't "authorized" your phone to be unlocked yet. I would complain to Motorola.

dafunk60 said:
All your info looks good to me, same formatting & length as the data that I used to unlock my Moto G Stylus. I have the same XT2043-4 SKU, also purchased from the Motorola Website. I was able to unlock my device on 5/6/2020. My best guess is that the Moto Unlock Tool is broken, or your phone is from a newer batch than mine and Motorola hasn't "authorized" your phone to be unlocked yet. I would complain to Motorola.
Click to expand...
Click to collapse
Thanks for that. Any suggestions on how best to complain? I found a support thread on Lenovo forums, and I posted there for help. If I get any help from there I'll make sure to add it to this thread. Here is the support thread on Lenovo site:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
It's a super long thread that goes on for hundreds of pages, but the thread is still up to date and being used currently.
**** UPDATE ****
I contacted Motorola support via chat, and they said they were unable to assist me with unlocking the bootloader on their end. They directed me to the exact same thread that I posted above.

kholdstayr said:
Thanks for that. Any suggestions on how best to complain? I found a support thread on Lenovo forums, and I posted there for help. If I get any help from there I'll make sure to add it to this thread. Here is the support thread on Lenovo site:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
It's a super long thread that goes on for hundreds of pages, but the thread is still up to date and being used currently.
**** UPDATE ****
I contacted Motorola support via chat, and they said they were unable to assist me with unlocking the bootloader on their end. They directed me to the exact same thread that I posted above.
Click to expand...
Click to collapse
Unfortunately I don't have any good contacts / recommendations on how to complain to Motorola. I think Motorola has a 30 day return policy. Personally, I would return the phone if I couldn't unlock the bootloader as that was one of the main selling points for me. You might give Moto support chat another try. When they say they can't help unlocking the bootloader, you can ask if they can help you with a return instead. Sometimes the threat of a return allows the support rep to escalate the issue. Best of luck!

dafunk60 said:
Unfortunately I don't have any good contacts / recommendations on how to complain to Motorola. I think Motorola has a 30 day return policy. Personally, I would return the phone if I couldn't unlock the bootloader as that was one of the main selling points for me. You might give Moto support chat another try. When they say they can't help unlocking the bootloader, you can ask if they can help you with a return instead. Sometimes the threat of a return allows the support rep to escalate the issue. Best of luck!
Click to expand...
Click to collapse
This is probably a dumb question, but for unlocking, do you need to have a SIM card installed?
When I contacted chat support they asked for the phone number, but I told them it doesn't have one because I haven't put the SIM in yet. I was planning on doing that after unlocking and setting the phone up the way I want.

kholdstayr said:
This is probably a dumb question, but for unlocking, do you need to have a SIM card installed?
When I contacted chat support they asked for the phone number, but I told them it doesn't have one because I haven't put the SIM in yet. I was planning on doing that after unlocking and setting the phone up the way I want.
Click to expand...
Click to collapse
No SIM was required for me. I unlocked the bootloader & patched the boot.img with Magisk before I ever inserted a SIM.

kholdstayr said:
I just bought a new Moto G Stylus straight from Motorola website. I am familiar in general with the unlock process, as I have an unlocked/rooted Moto G6.
Anyway, I went to the Moto website using both Chrome and Firefox, and when I paste my unlock code it says that my phone is not qualified. I am unable to request an unlock code because of this. I don't understand why that would be the case, since this is straight from Motorola, and others have unlocked the phone here.
I've tried to format the unlock code myself, as well as by using the "formatter tool" on their website.
This is the unlock code I got from my phone:
Code:
(bootloader) 3A95801400567210#5A46363532334E
(bootloader) 4C4647006D6F746F2067200000#A861
(bootloader) C41232F748E8C9B0BAA949482C5A52C
(bootloader) 978A4#CBB8389400000000000000000
(bootloader) 0000000
Here is my formatted version:
Code:
3A95801400567210#5A46363532334E4C4647006D6F746F2067200000#A861C41232F748E8C9B0BAA949482C5A52C978A4#CBB83894000000000000000000000000
My phone is a sofiap retail XT2043-4.
Click to expand...
Click to collapse
**** EDIT UPDATE ******
I was finally able to get the Motorola site to work, but I don't know why it works today when it didn't work yesterday.
Yesterday when I was trying to do the unlock, I saved the unlock data from my phone into a text file, and I've been using the same text file copy+paste every time I've tried to request the unlock code from Motorola.
There is one difference from yesterday vs today. Today when I tried it, I logged into the phone with my Google account, and then logged into the Motorola site using the same Google account. I don't know why that would make a difference, but that is it. Also, I used Chrome with no adblockers turned on. After requesting the unlock code, I received it in my email about 2 minutes later. The unlock code worked fine with no issues.

Does anyone here know if I can unlock my Moto G Stylus that I just got from MetroPCS? I want to unlock using the unlock app preinstalled on the phone, and also wondering if I can unlock the bootloader and install the stock rom to get rid of all the Metro stuff. I am new to all this, so any advice is appreciated. Thanks.

I'm going through the same issue my bootloader can't be unlock I put the code they send me and that code don't work the code is, AAAAAAAAAAAAAAAAAAAA
AFTER I ADB COMMAND WITH THIS CODE STILL DOESN'T WORK AND HONESTY I THINK IS THE WEBSITE NOT THE PHONE.
Sent from my moto g stylus using Tapatalk

god_of_wisdom said:
I'm going through the same issue my bootloader can't be unlock I put the code they send me and that code don't work the code is, AAAAAAAAAAAAAAAAAAAA
AFTER I ADB COMMAND WITH THIS CODE STILL DOESN'T WORK AND HONESTY I THINK IS THE WEBSITE NOT THE PHONE.
Click to expand...
Click to collapse
Is the code literally all A's? Then yes, that code is wrong then and it seems like a weird glitch with Motorola's email system that sent the code

Big_DDD said:
Does anyone here know if I can unlock my Moto G Stylus that I just got from MetroPCS? I want to unlock using the unlock app preinstalled on the phone, and also wondering if I can unlock the bootloader and install the stock rom to get rid of all the Metro stuff. I am new to all this, so any advice is appreciated. Thanks.
Click to expand...
Click to collapse
If you got it from MetroPCS you probably can't unlock it. You would want to buy the phone independently, not from a carrier, such as the Motorola site itself.
Do you know how to use fastboot? Run the command "fastboot getvar all" . In the long list of information you'll see a CID number. That number can help identify if the phone can be unlocked. My CID is 32.

kholdstayr said:
Is the code literally all A's? Then yes, that code is wrong then and it seems like a weird glitch with Motorola's email system that sent the code
Click to expand...
Click to collapse
What should I do
Sent from my moto g stylus using Tapatalk

god_of_wisdom said:
What should I do
Click to expand...
Click to collapse
Maybe try to request it again, or contact Motorola support.

I did they keep making excuses up.
Sent from my moto g stylus using Tapatalk

i get remote unlock error please help full getvar
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(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_10.11.03.22R SOFIAP_NA_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 Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s
---------- Post added at 05:53 PM ---------- Previous post was at 05:53 PM ----------
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(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_10.11.03.22R SOFIAP_NA_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 Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s

calijuana707 said:
(bootloader) cid: 0x0015
It seems like your phone could be unlockable. Your CID is 15 which is in the list of unlockable cids in this forum post:
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
Click to expand...
Click to collapse

Unlocked mine last night. Went smooth.