Database Users

bootloader unlock data unavailable

I have India version unlockable moto g4 plus. While I was tried to unlock bootloader I got bootloader unlock data after fastboot oem get_unlock_data command. Anyone help me to get solution?

Did you enable "USB Debugging" and toggle "Allow OEM Unlock" in "Developer Options" before doing your fastboot commands?

yes i checked all these options. thanks

The command from Motorola site to get the code should work on any phone, even the subsidized ones.
Moto won't release the key for Amazon subsidized ones, but you always read the code.

did you ever fix this? i have the same problem

mahesvr said:
yes i checked all these options. thanks
Click to expand...
Click to collapse
Do you know you need to copy that long command on notepad and remove all spaces and other words.
You only need to keep that long number and alphabet list without spaces and than paste it in Moto site:good:

Have you solved this problem? I have the same problem.

j_cesarbm said:
Have you solved this problem? I have the same problem.
Click to expand...
Click to collapse
If you're getting unlock data unavailable after using the fastboot oem get_unlock_data command, then you might have better luck submitting a post over at the Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Please read the initial post of that thread, and submit the information that is requested (the output of fastboot oem get_unlock_data and fastboot getvar all). Hopefully someone from Motorola should contact you and help you resolve the issue.

echo92 said:
If you're getting unlock data unavailable after using the fastboot oem get_unlock_data command, then you might have better luck submitting a post over at the Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Please read the initial post of that thread, and submit the information that is requested (the output of fastboot oem get_unlock_data and fastboot getvar all). Hopefully someone from Motorola should contact you and help you resolve the issue.
Click to expand...
Click to collapse
I am trying to unlock Bootloader from my device, however I get the following message. I am desperate !! Thank you
fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.125s]
finished. total time: 0.125s
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(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: 0038392474
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 549BA60500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355644084608195
(bootloader) meid:
(bootloader) date: 09-14-2017
(bootloader) sku: XT1710-07
(bootloader) carrier_sku:
(bootloader) battid: SNN5983B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 9 6:36:38 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:8.0.0/OPSS27.
(bootloader) ro.build.fingerprint[1]: 76-12-25-15/13:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.341.13.albus.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband[0]: M8953P_41.50.07.63.02R ALBUS_BRAZILDSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6c0cc6c (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]: Thu Feb 7 06:11:12 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=e4ac270-dirty
(bootloader) devcfg.git: git=e4ac270-dirty
(bootloader) keymaster.git: git=e4ac270-dirty
(bootloader) cmnlib.git: git=e4ac270-dirty
(bootloader) cmnlib64.git: git=e4ac270-dirty
(bootloader) prov.git: git=e4ac270-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.053s

j_cesarbm said:
I am trying to unlock Bootloader from my device, however I get the following message. I am desperate !! Thank you
fastboot oem get_unlock_data
<snip>
finished. total time: 0.053s
Click to expand...
Click to collapse
Thanks - again, the only place that can really help you is Motorola (and I've seen that you've posted over there). Once Alphadog sees your message, your case should be escalated up. Hopefully you'll be able to get your Z2 play unlocked, though it may take some time. Also, looking through your log, seems that there's no entry for ro.carrier, which might be causing the issues. However, we'll have to wait for Motorola to assist. Good luck.

Bootloader unlock data unavailable
I am unable to unlock bootloader of my device Moto e5 plus -(XT2924-3)Hannah
Please help me
C:\adb>fastboot devices
ZF6222V57X fastboot
C:\adb>fastboot oem help
(bootloader) config...
(bootloader) hw...
(bootloader) partition...
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) bp-tools-on
(bootloader) bp-tools-off
(bootloader) qcom-on
(bootloader) qcom-off
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) cid_prov_req
(bootloader) read_sv
(bootloader) off-mode-charge
OKAY [ 0.019s]
Finished. Total time: 0.027s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BF.55
(bootloader) product: hannah
(bootloader) board: hannah
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 4
(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: MSM8937
(bootloader) serialno: ZF6222V57X
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: A01DA8DF00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355528093905579
(bootloader) meid:
(bootloader) date: 07-11-2018
(bootloader) sku: XT1924-3
(bootloader) carrier_sku: XT1924-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 28 10:22:49 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ahannah/ahannah:8.0.0/OPP
(bootloader) ro.build.fingerprint[1]: S27.91-179-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.221.4.ahannah.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: M8937_26.30.05.75R HANNAH_APDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g9ad2fe5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Mar 28 02:54:24 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VBF.55-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=9692555-dirty
(bootloader) devcfg.git: git=9692555-dirty
(bootloader) keymaster.git: git=9692555
(bootloader) cmnlib.git: git=9692555
(bootloader) cmnlib64.git: git=9692555
(bootloader) prov.git: git=9692555-dirty
(bootloader) aboot.git: git=MBM-NG-VBF.55-0-g4e3d3ac
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: unknown
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.191s
C:\adb>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.020s]
Finished. Total time: 0.030s

Bootloader Unlock data unavailable Moto G5s Plus
echo92 said:
Thanks - again, the only place that can really help you is Motorola (and I've seen that you've posted over there). Once Alphadog sees your message, your case should be escalated up. Hopefully you'll be able to get your Z2 play unlocked, though it may take some time. Also, looking through your log, seems that there's no entry for ro.carrier, which might be causing the issues. However, we'll have to wait for Motorola to assist. Good luck.
Click to expand...
Click to collapse
My phone is motog5s plus. It also shows the same output despite my phone's cid is 0x0000 means bootloader can be unlocked.
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
Please help me out. Went to the Motorola Service Centre, they said to replace the motherboard. Now that would cost high price which is not feasible.
I need to unloack bootloader because the phone's IMEI code is lost. Unable to put any calls. If there is another way to get IMEI code then it's good.

Ac3_DeXt=R said:
My phone is motog5s plus. It also shows the same output despite my phone's cid is 0x0000 means bootloader can be unlocked.
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
Please help me out. Went to the Motorola Service Centre, they said to replace the motherboard. Now that would cost high price which is not feasible.
I need to unloack bootloader because the phone's IMEI code is lost. Unable to put any calls. If there is another way to get IMEI code then it's good.
Click to expand...
Click to collapse
Not a lot we can do sadly, if the motherboard needs replacing, then maybe you could see if an independent shop could do it for you?
I'm not sure how your IMEI got lost, did you buy the device used or did something happen to the device?

echo92 said:
Not a lot we can do sadly, if the motherboard needs replacing, then maybe you could see if an independent shop could do it for you?
I'm not sure how your IMEI got lost, did you buy the device used or did something happen to the device?
Click to expand...
Click to collapse
IMEI is lost after an update OTA. I believe it can be fixed if I downgrade from Oreo to Naughat with custom rom. But the phone is not showing oem unlock data at all. The phone is bootloader unlockable.

I am having a Motorola Moto G7 Amazon Subsidized Phone. I am unable to unlock the bootloader as not getting the unlock key and getting the same message as mentioned above:
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
I too went to the Motorola Service Centre, they said to replace the motherboard. Replacing motherboard meaning spending an equal amount of money as spent on this one.
fastboot getvar all output is below:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-cf76a327f28-200930
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 6
(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: SDM632
(bootloader) serialno: ZF622xxxxx
(bootloader) cid: 0x0000
(bootloader) channelid: 0xc0
(bootloader) uid: A7C468A700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354xxxxxxxxxxxx
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-16-2019
(bootloader) sku: XT1962-6
(bootloader) carrier_sku: XT1962-6
(bootloader) battid: SB18C34005
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 29 14: 0:35 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/river/river:10/QPUS30.52-
(bootloader) ro.build.fingerprint[1]: 16-2-7-4/e7923d:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_41.00.01.163R RIVER_APEMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Sep 30 11:2
(bootloader) kernel.version[3]: 9:39 CDT 2020
(bootloader) sbl1.git: MBM-2.1-river_retail-315bc626c6-200930
(bootloader) rpm.git: MBM-2.1-river_retail-20f2cf34-200930
(bootloader) tz.git: MBM-2.1-river_retail-03d85fce32-200930
(bootloader) devcfg.git: MBM-2.1-river_retail-03d85fce32-200930
(bootloader) keymaster.git: MBM-2.1-river_retail-03d85fce32-200930
(bootloader) cmnlib.git: MBM-2.1-river_retail-03d85fce32-200930
(bootloader) cmnlib64.git: MBM-2.1-river_retail-03d85fce32-200930
(bootloader) prov.git: MBM-2.1-river_retail-03d85fce32-200930
(bootloader) aboot.git: MBM-2.1-river_retail-cf76a327f28-200930
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retin
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C35906
all: listed above
finished. total time: 0.193s
>> fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.023s]
finished. total time: 0.025s
>> fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.047s]
finished. total time: 0.047s
>> fastboot devices
ZF622xxxxxx fastboot
>> adb devices
List of devices attached
(shows nothing)
I have tried below command to get the unlock key from Motorola Website:
>> fastboot oem cid_prov_req
...
(bootloader) 0001dddddddddddddddd000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 000006ea3b1821784e881ce694286221
(bootloader) ecfe000100f0000100000062a7c468a7
(bootloader) 00000000000000000000000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 0000dddddddddddddddd000631313131
(bootloader) 31313131313131313131313131313131
(bootloader) 0000ffffffffffffffffffffffffffff
(bootloader) ffffffffffff
OKAY [ 0.048s]
finished. total time: 0.048s
But get the message as PUID is not found in the above string.
I have then tried getting UID from the getvar all command which is;
(bootloader) uid: A7C468A700000000000000000000
and tried different ways in combining the UID with the above string but failed to get the [unlock key]
I am not sure whether this way is correct or not since I have purchased the device from Amazon and I have read somewhere that amazon subsidized phones will not get the unlock key.

fortnightbattle said:
>> fastboot devices
ZF622xxxxxx fastboot
>> adb devices
List of devices attached
(shows nothing)
I have tried below command to get the unlock key from Motorola Website:
>> fastboot oem cid_prov_req
...
(bootloader) 0001dddddddddddddddd000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 000006ea3b1821784e881ce694286221
(bootloader) ecfe000100f0000100000062a7c468a7
(bootloader) 00000000000000000000000000000000
(bootloader) 00000000000000000000000000000000
(bootloader) 0000dddddddddddddddd000631313131
(bootloader) 31313131313131313131313131313131
(bootloader) 0000ffffffffffffffffffffffffffff
(bootloader) ffffffffffff
OKAY [ 0.048s]
finished. total time: 0.048s
Click to expand...
Click to collapse
did you try to get unlock data with this command:
fastboot oem get_unlock_data

Yes correct, I have tried the same command and below is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.053s]
finished. total time: 0.054s
zitronenmelissa said:
did you try to get unlock data with this command:
fastboot oem get_unlock_data
Click to expand...
Click to collapse

Yes correct, I have tried the same command and below is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.053s]
finished. total time: 0.054s
zitronenmelissa said:
did you try to get unlock data with this command:
fastboot oem get_unlock_data
Click to expand...
Click to collapse

fortnightbattle said:
Yes correct, I have tried the same command and below is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.053s]
finished. total time: 0.054s
Click to expand...
Click to collapse
your cid is 0x0000, so it should be unlockable source: https://forums.lenovo.com/t5/MOTO-G...ader-Unlock-Help-Please-post-here/m-p/3024663
did you activate oem unlocking in developer settings (turn wifi on, activate dev settings, activate oem unlocking) ?

zitronenmelissa said:
your cid is 0x0000, so it should be unlockable source: https://forums.lenovo.com/t5/MOTO-G...ader-Unlock-Help-Please-post-here/m-p/3024663
did you activate oem unlocking in developer settings (turn wifi on, activate dev settings, activate oem unlocking) ?
Click to expand...
Click to collapse
Since the Phone is in a bad state , I can only access bootloader where I have typed - "fastboot oem get_unlock_data", to unlock the bootloader but it is not working for me. The Software works proper but by the time system boots up (generally tries 4 times to come up with a vibrate effect) and then sends a message on the screen the verification has failed. ID it gives as blank. Then again phone has to be rebooted to go to the bootloader mode. I read somewhere since (bootloader) cid: 0x0000 so it is an unlockable phone (ATT Device).

CAN'T UNLOCK BOOTLOADER - OEM Data Unavailable

I've tried all the methods but can't get to unlock bootloader.
I have an XT1643. Device is eligible.
I get this when I try to get the string-
mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.100s]
finished. total time: 0.103s
I had my motherboard replaced once under warranty. And I'm on the latest June security update. Couldn't find any forum or post that got this resolved or could provide a way to have this resolved
My cid is 0x0000, so it's unlockable, according to Moto Forums!

Your best bet might be to submit your fastboot getvar info and the get_unlock_data (even though it failed) to this Lenovo thread: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
Please read the first post to determine how the data should be presented, and looks like they are taking at least 2 business days to generate your code (so you may get a response by Wednesday or Thursday).

abhijeetdahiya said:
I've tried all the methods but can't get to unlock bootloader.
I have an XT1643. Device is eligible.
I get this when I try to get the string-
mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.100s]
finished. total time: 0.103s
I had my motherboard replaced once under warranty. And I'm on the latest June security update. Couldn't find any forum or post that got this resolved or could provide a way to have this resolved
My cid is 0x0000, so it's unlockable, according to Moto Forums!
Click to expand...
Click to collapse
mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.100s]
finished. total time: 0.103s
Same problem
Xt1643 not unlocking bootloader
Build number npj-25.75-2
Help plz..

mj.mhatre said:
mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.100s]
finished. total time: 0.103s
Same problem
Xt1643 not unlocking bootloader
Build number npj-25.75-2
Help plz..
Click to expand...
Click to collapse
Did you submit your data to the above Lenovo forum link that I posted a while back? They can help generate an usable unlock code.

echo92 said:
Did you submit your data to the above Lenovo forum link that I posted a while back? They can help generate an usable unlock code.
Click to expand...
Click to collapse
Hi echo92,
I am facing the same issue with xt1643 (Moto g4 +). I have emailed the my getvar info. anything else needs to be done here ?
Please reply. Thanks.

hardythaker said:
Hi echo92,
I am facing the same issue with xt1643 (Moto g4 +). I have emailed the my getvar info. anything else needs to be done here ?
Please reply. Thanks.
Click to expand...
Click to collapse
I saw your report on the website - I see no mention of the result of the fastboot oem get_unlock_data command, which they want as well. Even if the command didn't give you the data, I would edit your post to include the results of that fastboot command (have a look at the post above and below yours in that thread).
Once you edit that - be patient. As Alpha_dog on that thread mentions, once your request is forwarded, it may take at least 2 business days to get a response. If the request is forwarded on Sunday/Monday, for example, you have to wait until Wednesday for a reply. However, with your odd (bootloader) ro.carrier: unknown and (bootloader) cid: 0x0000 they may take longer and you may be asked to give your device to service if they can't get a code for you.

echo92 said:
I saw your report on the website - I see no mention of the result of the fastboot oem get_unlock_data command, which they want as well. Even if the command didn't give you the data, I would edit your post to include the results of that fastboot command (have a look at the post above and below yours in that thread).
Once you edit that - be patient. As Alpha_dog on that thread mentions, once your request is forwarded, it may take at least 2 business days to get a response. If the request is forwarded on Sunday/Monday, for example, you have to wait until Wednesday for a reply. However, with your odd (bootloader) ro.carrier: unknown and (bootloader) cid: 0x0000 they may take longer and you may be asked to give your device to service if they can't get a code for you.
Click to expand...
Click to collapse
Okay tomorrow I will edit that post and let you know here. Thanks.

echo92 said:
I saw your report on the website - I see no mention of the result of the fastboot oem get_unlock_data command, which they want as well. Even if the command didn't give you the data, I would edit your post to include the results of that fastboot command (have a look at the post above and below yours in that thread).
Once you edit that - be patient. As Alpha_dog on that thread mentions, once your request is forwarded, it may take at least 2 business days to get a response. If the request is forwarded on Sunday/Monday, for example, you have to wait until Wednesday for a reply. However, with your odd (bootloader) ro.carrier: unknown and (bootloader) cid: 0x0000 they may take longer and you may be asked to give your device to service if they can't get a code for you.
Click to expand...
Click to collapse
Hi @echo92,
I have updated my post with the required data. Thanks. :good:

From the Motorola bootloader unlocking website says my device is not elegable.(I past my bootloader coad to get my unlocking coad

C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX64MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322DZ5XP
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 3368E91D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351834090464352
(bootloader) meid:
(bootloader) date: 11-27-2017
(bootloader) sku: XT1805
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 17 1:26:53 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_retid_n/sanders_n
(bootloader) ro.build.fingerprint[1]: :8.1.0/OPS28.65-36-14/63857:user/r
(bootloader) ro.build.fingerprint[2]: elease-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders_re
(bootloader) ro.build.version.full[1]: tid.retid.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_52.61.07.98R SANDERS_EMEADSDS_CUST
(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.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=c3b9056-dirty
(bootloader) devcfg.git: git=c3b9056-dirty
(bootloader) keymaster.git: git=c3b9056-dirty
(bootloader) cmnlib.git: git=c3b9056-dirty
(bootloader) cmnlib64.git: git=c3b9056-dirty
(bootloader) prov.git: git=c3b9056-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (343)
(bootloader) ro.carrier: unknown
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.222s
please help me.

Moto G4 plus stuck in bootloader mode (Hard Brick)

Hi All.
I have unlock boot-loader and flash stock ROM after that i got an update (nougat 7.1) and I allowed.
after allowing my mobile stuck in bootloader and i am not able flash new images getting:
FAILED (remote failure)
finished. total time: 0.144s,
i tried all possible way.
for hard brick i followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but no success. please help me out.

If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.

echo92 said:
If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.
Click to expand...
Click to collapse
Below is the output of fastboot getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: d72acc4e
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: EC1CEC0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.104s
and i flash nougat 7 then i got update, I allowed update and phone got stuck in bootloader.

What firmware are you trying to flash now? Looks like your main issue is that you do not have a GPT partition table on your device, so your device does not know what files to flash.
I would recommend downloading the Oreo firmware from here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip delete the old stock ROM files from your ADB folder and replace with the Oreo firmware files. Then try to flash the Oreo GPT file

Stuck on bootloader with NO OS and OEM_LOCKED -- (MOTOG4PLUS)
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!

viking_vikram said:
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!
Click to expand...
Click to collapse
What happened to your device before this?
Which GPT.bin are you trying to load up? Try the April 2018 GPT and bootloader https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI or the December 2018 GPT and bootloader: https://drive.google.com/open?id=1TlFPYf4y3MEARFUuHSNB5Ty0GD-SQua-
However, if your device continues to report GPT partition initialisation errors, it's possible your flash storage is damaged and may require a motherboard replacement.

Where can I get a motherboard replacement ?
will it finally solve my problem ?

viking_vikram said:
Where can I get a motherboard replacement ?
will it finally solve my problem ?
Click to expand...
Click to collapse
Probaly a service centre would be the best place to request a motherboard replacement. It may solve your issue, however, as your G4 Plus is out of warranty, a motherboard replacement is not cheap - I've seen quotes for 8000-1000 rupees. Thus, you may wish to look into buying a new device altogether.

Moto G6 Plus OEM LOCKED ¿BRICKED?

Hi im new on this forum...lets jump the the problems. (sorry i got the verbs wrong, im not english native speaker)
1st problem: cannot enter in recovery (if i select the option the phone turn off and the led starts blinking)
2st problem: cannot flash stock rom/firmware because the phone wont turn on. (already tried to flash with oem locked but give me errors linked to the oem)
3st problem: the phone didnt charge but the leds blinking, already disconnected the battery, plugged the phone then reconnect the battery, this only give me the "lightining" icon but doesnt charge. if i press the power button shows me the "lightining" likes if is charging
I dont know what to do anymore, with the oem locked i cant flash anything, its giving me headaches...thanks for reading, hope i find the solution
Update: (this is the error i got, already know its from oem, plus when finished the phone just goes off, and didnt charge, only led blink)
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.738s

cowb0y said:
Hi im new on this forum...lets jump the the problems. (sorry i got the verbs wrong, im not english native speaker)
1st problem: cannot enter in recovery (if i select the option the phone turn off and the led starts blinking)
2st problem: cannot flash stock rom/firmware because the phone wont turn on. (already tried to flash with oem locked but give me errors linked to the oem)
3st problem: the phone didnt charge but the leds blinking, already disconnected the battery, plugged the phone then reconnect the battery, this only give me the "lightining" icon but doesnt charge. if i press the power button shows me the "lightining" likes if is charging
I dont know what to do anymore, with the oem locked i cant flash anything, its giving me headaches...thanks for reading, hope i find the solution
Update: (this is the error i got, already know its from oem, plus when finished the phone just goes off, and didnt charge, only led blink)
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.738s
Click to expand...
Click to collapse
So not a solution?

cowb0y said:
So not a solution?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands

Update
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Click to expand...
Click to collapse
Update yesterday i found reading here how to get the correct version of the rom stock, and already flashed it.
the phone wont charge (only appears the lightning icon but never increase or show "%") wont turn on, and didnt enter in recovery mode. i thinks its problem of the battery beacuse i buy new one and doesnt fit at all in the phone (it lacks 1cm) (also the battery is 3010mAh, and g6plus is 3200mAh i think)
Anyways here what you asked for Again sorry for my bad english.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: B6D17C90
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 12-05-2018
(bootloader) sku: XT1926-6
(bootloader) carrier_sku: XT1926-6
(bootloader) battid: SB18C208
(bootloader) battery-voltage: 2793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-16/5555b:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.361.26.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf134223-0256
(bootloader) kernel.version[1]: 0-g4e158e0 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Thu Jan 2 01:06:09 CST
(bootloader) kernel.version[4]: 2020
(bootloader) git:abl: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) git:xbl: MBM-3.0-evert_retail-b872199-200102
(bootloader) gitmic: MBM-3.0-evert_retail-b872199-200102
(bootloader) git:rpm: MBM-3.0-evert_retail-718b013-200102
(bootloader) git:tz: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:hyp: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:devcfg: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:keymaster: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) gitrov: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:storsec: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
(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: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.184s

Help needed moto G5 plus - stuck in fastboot menu? cant flash?

I have spent the last 12 hours trying to fix this. I am tech savvy but have never flashed a cellphone before, hence I dunno if I am doing something wrong. And apologies if my terms aren't correct. please correct me when I am wrong.
Phone is a moto G5 plus XT1681 (according to imei), one day it powered to fastboot (see image 1) and what ever I try to press, I get an error. (see image 2)
I followed and tried many guides. but especially this one
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
when I try to run the first line of the script I get the following error.
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
If I keep advancing in the code I get the same error than this guy
Bricked MOTO G5(XT1676) stucked at fastboot menu
hELLO.. I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from...
forum.xda-developers.com
the phone is detectable with command "fastboot devices"
Despite running this, the phone still stays "oem_locked" like in the images
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem unlock
(bootloader) feature disabled
OKAY [ 0.017s]
Finished. Total time: 0.018s
I tried also installing TWRP and I get this error (because maybe that bypasses a locked bootloader?)
"(bootloader) Preflash validation failed
FAILED (remote failure)¨
And here is the log for what I learned that you always ask for
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ca31f0ad
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 423FF92E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(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: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.175s
QUESTIONS
Am I just confusing rom because of firmware or country?
is all of this because my bootloader seems locked?
do I just need to get to recovery mode first?
I just want the phone to work, don't care for the data inside.
Other people that seem to be stuck with the same problem
https://forum.xda-developers.com/t/...-question-noob-friendly.3963645/post-85232253
THANKS IN ADVANCE AND SORRY FOR THE LONG POST I WANTED TO GIVE ALL MY INFORMATION AND RESEARCH

Same problem here.