Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

Motorola Community

Moto G Phonesmoto g stylus (2021)
All Forum Topics
Options

5 Posts

04-07-2021

United States of America

5 Signins

25 Page Views

  • Posts: 5
  • Registered: ‎04-07-2021
  • Location: United States of America
  • Views: 25
  • Message 1 of 19

UNLOCKING bootloader AFTER receiving code

2021-04-07, 22:18 PM

bought device from motorola.com

contacted motorola support, they could not help.

finally found boodloader unlock web page from motorola

 

THIS IS TO SHOW THE IMMENSE WASTE OF TIME, but this is not yet done

 

So, motorola webpage confirms the device is unlockable, agreed on the terms, confirmed my decision.

Received unlock code by email.

 

And a guide if necessary. The guide does not work. WASTE OF TIME continues.

 

turned on piece of junk

opened elevated command prompt

adb devices (recognized)

adb reboot bootloader

- device enters bootloader -

fastboot devices (recognized)

fastboot oem unlock UNIQUE_KEY (entered code received by email)

 

ERROR

(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)

 

checked the settings and OEM unlocking is GRAYED OUT

 

updated firmware by connecting to the internet,

the OEM unlocking is still GRAYED OUT

 

customer support have no clue

they do not honor student discounts either

 

Now, why is it that motorola cannot keep their s**te together?

this piece of beautiful junk goes back

Reply
Options

6 Posts

04-08-2021

United States of America

2 Signins

45 Page Views

  • Posts: 6
  • Registered: ‎04-08-2021
  • Location: United States of America
  • Views: 45
  • Message 2 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 7:46 AM

Thank you for bringing this HUGE DEFECT to light, I have the same identical problem as you, completely misleading of motorala to advertise unlocking, when it is non functional. I've spent 7 hours trouble shooting this same exact error to no avail.  lenovo please fix this, I wont be buying again and will steer friends away if this is not worked out. I feel conned.

Reply
Options

6 Posts

04-08-2021

United States of America

2 Signins

45 Page Views

  • Posts: 6
  • Registered: ‎04-08-2021
  • Location: United States of America
  • Views: 45
  • Message 3 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 7:55 AM

someone please help, I really want to like motorola. but this has been dissapointing. @MotorolaExpert 

 

 

Reply
Options

13400 Posts

03-05-2018

United States of America

1272 Signins

172690 Page Views

  • Posts: 13400
  • Registered: ‎03-05-2018
  • Location: United States of America
  • Views: 172690
  • Message 4 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 14:25 PM

Hi Motorola $uck$

 

Can you please share your bootloader details and the getvar details? Thanks.

 

Best regards,
Rich
Motorola-Lenovo Support



Did someone help you today? Click the thumbs up button to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

We value your opinion. Read More

Reply
Options

5 Posts

04-07-2021

United States of America

5 Signins

25 Page Views

  • Posts: 5
  • Registered: ‎04-07-2021
  • Location: United States of America
  • Views: 25
  • Message 5 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 15:56 PM

I have been less wiser and spent 10+ hours to try and find a workaround. There is no workaround. There is no mention of any wait until the OEM unlocking being grayed out in motorola's unlock email. I am sure they know about this issue and they enforce it to harvest even more personal data on the buyers. We'll use this as evidence for a potential class action. This has to stop.

Reply
Options

1 Posts

04-08-2021

United States of America

1 Signins

0 Page Views

  • Posts: 1
  • Registered: ‎04-08-2021
  • Location: United States of America
  • Views: 0
  • Message 6 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 16:16 PM

Needed to create another account because motorola/lenovo censorship did not allow me to post additional messages with the error

More than the limit for new users to post 

 

Can you believe it? there's the evidence.

 

regardless,

@ agent rich, here is the requested info. Please do not beat around the bush and provide a solution if there is any.

 

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-minsk_retail-e6dffe91c4-210104
(bootloader) product: minsk
(bootloader) board: minsk
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V8001DM-B622 FV=1500
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM6150 1.1
(bootloader) serialno: xxxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: xxxxxxxx
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-25-2020
(bootloader) sku: XT2115-1
(bootloader) carrier_sku: XT2115-1
(bootloader) battid: xxxxxxxxxx
(bootloader) battery-voltage: 4242
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/minsk_retail/minsk:10/QPC
(bootloader) ro.build.fingerprint[1]: S30.Q4-31-26-1-2/ed1bf83:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.8.9.r1-10400-SM6xx.0
(bootloader) version-baseband: M6150_25.276.01.30.01R MINSK_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ (nobody@and
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Mon Jan 4 12:2
(bootloader) kernel.version[3]: 5:34 CST 2021
(bootloader) git:xbl: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:xbl_config: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:aop: MBM-3.0-minsk_retail-xxxxxxxxx-210104
(bootloader) git:tz: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:hyp: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:devcfg: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:cmnlib: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:keymaster: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:storsec: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:prov: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) git:abl: MBM-3.0-minsk_retail-xxxxxxxxxxx-210104
(bootloader) git:uefisecapp: MBM-3.0-minsk_retail-xxxxxxxxxx-210104
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86598
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
all: listed above

 

 

 

Reply
Options

6 Posts

04-08-2021

United States of America

2 Signins

45 Page Views

  • Posts: 6
  • Registered: ‎04-08-2021
  • Location: United States of America
  • Views: 45
  • Message 7 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 16:55 PM
I'm not as upset about it, it's a new phone with some bugs, but definatly feeling frustrating. could you remind me the fastboot command to get my system status?
Reply
Options

5 Posts

04-07-2021

United States of America

5 Signins

25 Page Views

  • Posts: 5
  • Registered: ‎04-07-2021
  • Location: United States of America
  • Views: 25
  • Message 8 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 17:04 PM

I hope this is what you were looking for

 

in bootloader, elevated command prompt on PC

 

fastboot getvar all

Reply
Options

6 Posts

04-08-2021

United States of America

2 Signins

45 Page Views

  • Posts: 6
  • Registered: ‎04-08-2021
  • Location: United States of America
  • Views: 45
  • Message 9 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 17:22 PM

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-minsk_retail-e6dffe91c4-210104
(bootloader) product: minsk
(bootloader) board: minsk
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V8001DM-B622 FV=1500
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM6150 1.1
(bootloader) serialno: removed - privacy - Rich
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 67E7D149
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: removed - privacy - Rich
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-06-2021
(bootloader) sku: XT2115-1
(bootloader) carrier_sku: XT2115-1
(bootloader) battid: SB18C57819
(bootloader) battery-voltage: 4280
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/minsk_retail/minsk:10/QPC
(bootloader) ro.build.fingerprint[1]: S30.Q4-31-26-1-2/ed1bf83:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.8.9.r1-10400-SM6xx.0
(bootloader) version-baseband: M6150_25.276.01.30.01R MINSK_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ (nobody@and
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Mon Jan 4 12:2
(bootloader) kernel.version[3]: 5:34 CST 2021
(bootloader) git:xbl: MBM-3.0-minsk_retail-f65e61d98-210104
(bootloader) git:xbl_config: MBM-3.0-minsk_retail-f65e61d98-210104
(bootloader) git:aop: MBM-3.0-minsk_retail-c5beedb-210104
(bootloader) git:tz: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:hyp: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:devcfg: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:cmnlib: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:keymaster: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:storsec: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:prov: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) git:abl: MBM-3.0-minsk_retail-e6dffe91c4-210104
(bootloader) git:uefisecapp: MBM-3.0-minsk_retail-5bd9738ed-210104
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 5
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86598
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.155s

C:\droid\Minimal ADB and Fastboot>

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reply
Options

13400 Posts

03-05-2018

United States of America

1272 Signins

172690 Page Views

  • Posts: 13400
  • Registered: ‎03-05-2018
  • Location: United States of America
  • Views: 172690
  • Message 10 of 19

Re:UNLOCKING bootloader AFTER receiving code

2021-04-08, 20:56 PM

Hi akbridger

 

Thanks for sharing. We can get you a code. Can you also share with me the OEM data? I will forward this details to the team. 

 

Hi Motorola $uck$

 

Sorry to hear that. Let me check this with the team as well. Can you share the IMEI of the phone? You can send me a private message for that details, just click my profile. Thanks.

 

Best regards,
Rich
Motorola-Lenovo Support



Did someone help you today? Click the thumbs up button to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

We value your opinion. Read More

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms