yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Alvin64DD:
Just to update, it is true that I had to wait for the "OEM Unlock" option to be enabled. It took about three days and after that, it was finally togglable. I have now unlocked the bootloader on this Moto G Power (2021) purchased and shipped with the Google Fi software channel, despite Motorola support telling me I couldn't do it due to it being a Google Fi model. I just wasn't sure if that was true or not due to it being a Google Fi phone.
[Upgrading, Modifying and Unlocking] Gen461:
Hi,

I'm using edge s pro with edge 20 pro firmware.

When I flashed RRA31.Q3-19-86, I successfully OEM locked with it, but after I flashed RRAS31.Q3-19-86-6, I can only do flashing_locked.

Does OEM locking availability depend on firmware? Or am I missing something?

Also I'm thing of revert flashing RRA31.Q3-19-86. Is it risky for future OTA?

Thanks in advance!
[Upgrading, Modifying and Unlocking] Gen461:
Sorry, I mean I'm flashing RETEU firmware.

And revert back firmware was prevented by vbmeta downgrade warning and unsuccessful (boot loop).
[Upgrading, Modifying and Unlocking] sd_shadow:
While you can flash other software channels, that does not change the persist partition.

Locking a Moto device on the original firmware is iffy.

Locking the bootloader on a different firmware is just asking for trouble.

I have no suggestions.
[Upgrading, Modifying and Unlocking] MrDeskSide:
Hello i would like some help unlocking my bootloader it is in fact a 0x0032 cid but i cant get the code from motorola. Any thoughts?
[Upgrading, Modifying and Unlocking] gguerra:
Old thread here but I'll post anyway. Moto G60s, I got it over a year ago. It's carrier unlocked, bought it on Ebay.

I'll make it quick. I got the unlock code from Motorola, issued this command from fastboot.

Got this as a result.

NEVER GOT this. Not sure if if this applies to all models.

I repeat, did NOT get the above confirmation screen.

OEM Toggle in developer options is still greyed out after 6 days. It's been on Wifi the whole time.

Is there a way to check if it's truly unlocked?

I already tried FASTBOOT GETVAR UNLOCKED. It came back with an error as unrecognized.
[Upgrading, Modifying and Unlocking] WoKoschekk:
try fastboot getvar all
[Upgrading, Modifying and Unlocking] gguerra:
Thanks. That worked gave me a long list of variables but as can be seen below, it still shows as locked.

So, OEM Unlocking still greyed. Should the above setting still show locked even though I issued command to unlock? Is it waiting for the change from Motorola I wonder?
[Upgrading, Modifying and Unlocking] WoKoschekk:
is it a carrier branded phone? otherwise - AFAIK - you have to wait 7 or 10 days before the OEM-unlock toggle will be available. but there are several threads about that issue here at XDA.
[Upgrading, Modifying and Unlocking] gguerra:
It's carrier unlocked. It has been 6 days so far. I've searched the threads. Some say to factory reset, some say it happened in 3 days, some more days, it's all over the place. I will wait, that is all I can do. Thanks.
[Upgrading, Modifying and Unlocking] bodstone:
i just can't proceed with fastboot on a motorola g8 power (blackjack), i get the same error everytime :[

# fastboot devices
0068630145 fastboot

# fastboot oem get_unlock_data
FAILED (remote: 'unknown command')
fastboot: error: Command failed

for my 'fastboot getvar all' output: https://paste.debian.net/1262606/
[Upgrading, Modifying and Unlocking] WoKoschekk:
Are you using the latest platform-tools?

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

what about

fastboot oem help

?
[Upgrading, Modifying and Unlocking] WoKoschekk:
Windows or Linux system?
[Upgrading, Modifying and Unlocking] bodstone:
Linux, but i tried on windows too and it fails (doesnt return any output), yes on the latest platform tools

# fastboot oem help
FAILED (remote: 'unknown command')
fastboot: error: Command failed

# fastboot --version
fastboot version 33.0.3-8952118
Installed as /opt/android-sdk/platform-tools/fastboot
[Upgrading, Modifying and Unlocking] gguerra:
I had a similar issue and it ended up being the driver. I think I put it back on the Motorola ADB interface and got it to work. My error message was different though, something like "Unable to open Fastboot HAL"

You may want to check the driver that it shows in device manager for Android Device
[Upgrading, Modifying and Unlocking] Kerrylee1738$$$:
I received my unlock code in a email but whenever I entered it. It said it failed to validate code. Any advice on how to fix issue besides emailing Motorola which I did already. Thanks
[Upgrading, Modifying and Unlocking] PatH21:
plz help me Sr.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: MBM-2.1-lisbon_retail-f472846951-221106

(bootloader) product: lisbon

(bootloader) board: lisbon

(bootloader) secure: yes

(bootloader) hwrev: PVT

(bootloader) radio: 1

(bootloader) storage-type: UFS

(bootloader) ufs: 128GB SKHYNIX H9HQ15AECMBDAR FV=A002 WB=2048

(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5=06 M6=06 M7=00 M8=11

(bootloader) cpu: MT6785

(bootloader) serialno: ZY22DXT2ZX

(bootloader) cid: 0x0032

(bootloader) channelid: 0x27

(bootloader) uid: 88E43885D3E1BBA3000000000000

(bootloader) securestate: oem_locked

(bootloader) factory-modes: disabled

(bootloader) iswarrantyvoid: no

(bootloader) max-download-size: 268435456

(bootloader) reason: Reboot mode set to fastboot

(bootloader) imei: 354911551429350

(bootloader) imei2: 354911551429368

(bootloader) meid:

(bootloader) date: 12-18-2021

(bootloader) sku: XT2133-1

(bootloader) carrier_sku: XT2133-1

(bootloader) battid: SB18C77773

(bootloader) iccid:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Sat Dec 24 5:32:22 UTC 2022"

(bootloader) ro.build.fingerprint[0]: motorola/lisbon_retail/lisbon:12/S

(bootloader) ro.build.fingerprint[1]: 3RLS32.114-25-3/1ae1da:user/releas

(bootloader) ro.build.fingerprint[2]: e-keys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.mtk: alps-mp-s0.mp1.tc2sp-V2.168

(bootloader) version-baseband: MT6785_TC2.PR1.SP.V1.2.P8.01.39R

(bootloader) kernel.version[0]: Linux version 4.14.186+ (nobody@android-

(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390

(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android

(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project

(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7

(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH

(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79

(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Sun Nov 6 23:38:33 CST

(bootloader) kernel.version[8]: 2022

(bootloader) frp-state: no protection (0)

(bootloader) ro.carrier: openla

(bootloader) current-slot: b

(bootloader) running-boot-lun: 2

(bootloader) running-slot: _b

(bootloader) slot-successful:_a: no

(bootloader) slot-successful:_b: no

(bootloader) slot-bootable:_a: No

(bootloader) slot-bootable:_b: Yes

(bootloader) slot-retry-count:_a: 0

(bootloader) slot-retry-count:_b: 2

(bootloader) slot-suffixes: _a,_b

(bootloader) slot-count: 2

(bootloader) pcb-part-no: SB28D03067

(bootloader) is-userspace: no

(bootloader) is-logical:

all: listed above

finished. total time: 0.236s

What can I do? I want to unlock the OEM but nothing works (sorry for the English I'm in the translator)
[Upgrading, Modifying and Unlocking] gguerra:
What was your question? Not clear on that.
[Upgrading, Modifying and Unlocking] gguerra:
A month after I unlocked bootloader through fastboot the OEM Unlocking option is still greyed out in developer settings.

It's carrier unlocked, I had it with T-Mobile.

Any other way to toggle it besides wait? Maybe a contact over at Motorola?
[Upgrading, Modifying and Unlocking] sd_shadow:
What does this say?

fastboot getvar securestate

So you are unable to root?

Tried reflashing firmware?
[Upgrading, Modifying and Unlocking] gguerra:
Since bootloader is locked, I cannot do anything, root, flash older stock rom, nothing. The greyed out option never changed in developer settings.

Don't have the phone with me, I will check on the getvar securestate tomorrow.
[Upgrading, Modifying and Unlocking] sd_shadow:
You still should be able to flash same stock firmware with locked bootloader, at least with LMSA.

Flashing older firmware is a bad idea even with the bootloader unlocked.

https://xdaforums.com/t/rescue-and-smart-assistant-lmsa-motorola-lenovo-only.3951714/
[Upgrading, Modifying and Unlocking] gguerra:
Let me quickly summarize. Phone is a brick after A12 update. I want to root it, go back to A11. That is the whole point of this. I've been through EVERYTHING in trying to fix it. I even went out and bought another phone. I want to go back to A11 and need to prevent future Android updates unless there's another way to stop it, I need to root. Nothing to lose here. At this point, it's just a Wifi phone or 6" tablet or whatever you want to call it. As a phone it doesn't work.
[Upgrading, Modifying and Unlocking] Renate:
I don't trust "magic tools" that do everything automatically.

I'm more "old skool" with EDL mode.

Still, a few Motorola units that were "unlocked" still give me access problems and "range-restricted" in EDL.

I'm seeing:

C:\>fastbogus getvar securestate
securestate: flashing_unlocked

C:\>fastbogus getvar cid
cid: 0x0032

C:\>fastbogus getvar secure
secure: yes

You may be asking, "fastbogus"?

Motorola uses non-standard USB VID/PID for fastboot.

You can either install some driver .inf with that or just use Zadig for generic WinUSB.

Then you have to patch fastboot to use the Interface GUID from WinUSB.
[Upgrading, Modifying and Unlocking] PatH21:
Quiero desbloquear el cargador de arranque pero la opción oem en desarrollo no está habilitada (atenuada)

Mod translation: I want to unlock the bootloader but the oem option in development is not enabled (grayed out)
[Upgrading, Modifying and Unlocking] Badger50:
Greetings. A friendly reminder regarding XDA Rule #4:

Spoiler content hidden.

Your cooperation is greatly appreciated. Thank you.

-Regards: Badger50
[Upgrading, Modifying and Unlocking] gguerra:
There is nothing to do but wait. Some reports say up to two weeks. Assuming it is actually unlocked that is. For me it never happened and I went through all of the steps required.
[Upgrading, Modifying and Unlocking] sd_shadow:
Ok, so you got the unlock code from Motorola's unlock site.

Then was unable to use it because allow OEM unlocking cannot be toggled.

Is that correct?
[Upgrading, Modifying and Unlocking] yesca213:
Lemme know if I can help, I have been toying around with mine trying to get past unlockable status and managed to flash in edl a few times with firehose to get back to first instance of (bootloader?) On device. But I did manage to brick it and bring it back to edl and boot stock atat quite a few times using test points. Still haven't found what I need tho.
[Upgrading, Modifying and Unlocking] Renate:
What are you showing for fastboot getvar secure?

How did you make your device not "secure" (vs. flashing_unlocked)?

Have you ever run into the error "range-restricted"?
[Upgrading, Modifying and Unlocking] yesca213:
Fastboot getvar secure returned secure: yes
[Upgrading, Modifying and Unlocking] Renate:
Hmm, well, that's interesting.

Are you saying that you can read all the partitions over EDL?

The Firehose loader that I'm using on my Moto G Power (2021) has a table of which blocks I'm allowed to read.

Take a read here, please: https://github.com/bkerler/edl/issues/355

Could you give me a link to your Firehose loader?
[Upgrading, Modifying and Unlocking] yesca213:
I didn't try reading partitions just writing

I didn't try to read any partitions... Prob should have tried. I gotta get on my PC at home to find out which loader I used, but may be a day or 2. Working now....
[Upgrading, Modifying and Unlocking] gguerra:
That is correct, please see post #46 and #48 (and others) in this thread, a couple of pages back. That should explain a few things. Went through all the steps, the greyed out oem unlock will not enable.
[Upgrading, Modifying and Unlocking] gguerra:
Thanks, at this point don't know what else I could try. The phone works as a wifi device, not a phone. When I use a sim card, it will periodically drop signal. This started happening right after the A12 update. I had no problem with A11, would like to try going back to that.
[Upgrading, Modifying and Unlocking] sd_shadow:
Did you try just flashing the radio firmware?
[Upgrading, Modifying and Unlocking] yesca213:
I got a lot of things from here "https://mirrors.lolinet.com/software/windows/Motorola/Drivers/", including qboot.exe and star.exe. you have to look in a few different blankflash folders under different devices as not all of them contain those 2 files. Then proceeded to obtain proper device blankflash file, add the 2 files mentioned above to the same folder. you have to use these files to unpack the bootloader.img to create your own singleimage.bin. Once thast is done, you will run blank-flash.bat it will say waiting for device. with phone off, short out test points while plugging in usb, firehose will run and do its thing. Now, if there was a way to get unsigned or resigned files to flash in here, maybe theres a way it will accept any firmware instead of just the factory images. But I have not made it that far yet.

sorry for the confusion on my part in the first edition of this post. i think it is correct now....

also read

https://www.reddit.com/r/MotoG/comments/k73n66
[Upgrading, Modifying and Unlocking] gguerra:
Sure, why not. How to proceed?
[Upgrading, Modifying and Unlocking] sd_shadow:
Flashing Radio Only

Flashing the Radio Firmware
[Upgrading, Modifying and Unlocking] Ozhkavosh:
is there any alternative way to unlock motorola bootloader? I have a RAZR i and I see that the trick of putting the code in the url no longer works, the official page says that my device does not apply for unlocking and the CID code is a ''c'' and they are not numbers, and they are not It is a version of Verizon or anything like that. Can someone help me unlock this?

Device ID:

3A25150965572733#544133323430414E514500000000000000000000#14F54689559E089C028C166248E4F9D3AC10C4D6#C356AB6E3B0879842E7DE05B92B30000
[Upgrading, Modifying and Unlocking] gguerra:
Thanks but I don't see my model listed.

It's a Moto G60s XT2133-2. Yeah, I know, it's a weird one but I really liked it. Way better than what I had to buy in a pinch, the Moto G Power 2022. That one really lags but anyway, could not find that one listed for the radio firmware, mostly older models it seems.
[Upgrading, Modifying and Unlocking] Renate:
Lol! I just intentionally bought a Moto G Power 2021 last Black Friday a month ago.

That has a Qualcomm processor.

In 2022 they swapped in a Mediatek processor and by all reports, it's crap.
[Upgrading, Modifying and Unlocking] gguerra:
Little did I know they got worse, not better. Didn't even read into it, I just needed a phone and did not want to spend a lot.
[Upgrading, Modifying and Unlocking] Renate:
Sorry. I paid $130 for the 2021 w/64M. The 2022 had 128M but was closer to $200?

I got burned with the same concept before.

I had a Moto E5 which was a pretty decent for the time.

I replaced it with a Moto E6 which was junk.
[Upgrading, Modifying and Unlocking] gguerra:
The 128 was what I wanted, paid $169 on Black Friday. If I can get my older one to work I will switch back. Not betting on it.

I was temped to go with the Pixel 6a but the smaller battery turned me off, it was 299. Should of done it anyway.
[Upgrading, Modifying and Unlocking] sd_shadow:
Did you even look?

https://mirrors.lolinet.com/firmware/motorola/lisbon/official/RETEU/
[Upgrading, Modifying and Unlocking] gguerra:
I did look but I looked in the wrong place. Never flashed just part of the firmware as in this example. I now realize you just flash the radio part of it?

I have already used LMSA to re-flash at the beginning when I first had this problem. Would that not flash radio firmware along with the rest of the firmware?

I'm a noob obviously, thanks for the help. I'm willing to try it if it may help. Is it worth it?

Edit: So, I download the latest firmware from December for that model. Opened it up, I don't see a 'radio.img" in the folder. Here is a listing of the contents.
[Upgrading, Modifying and Unlocking] yesca213:
The md1img.img is prob the modem file.
[Upgrading, Modifying and Unlocking] gguerra:
So modem is the same as radio I assume? Would it hurt anything to try that file?
[Upgrading, Modifying and Unlocking] yesca213:
That file should contain radio baseband and modem.
[Upgrading, Modifying and Unlocking] gguerra:
Thanks Guys. Finally got around to try and flash the radio firmware. I was going to use the md1img.img but can't seem to find which partition.

"fastboot flash radio" and "fastboot flash modem" both come back with 'unknown partition'

Looked for fastboot commands that would list the partitions. Could not find any when I do "fastboot help"

Any ideas?
[Upgrading, Modifying and Unlocking] Renate:
fastboot getvar all
[Upgrading, Modifying and Unlocking] gguerra:
I had run that command before for something else, didn't think a partition was a variable but here it is. Thanks

D:\Moto G60s\platform-tools>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: MBM-2.1-lisbon_retail-f472846951-221106

(bootloader) product: lisbon

(bootloader) board: lisbon

(bootloader) secure: yes

(bootloader) hwrev: PVT

(bootloader) radio: 2

(bootloader) storage-type: UFS

(bootloader) ufs: 128GB SKHYNIX H9HQ15ACPMBDAR FV=A002 WB=2048

(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=06 M7=00 M8=11

(bootloader) cpu: MT6785

(bootloader) serialno: ZY22CX4J26

(bootloader) cid: 0x0032

(bootloader) channelid: 0x00

(bootloader) uid: 6580BA226BF71630000000000000

(bootloader) securestate: oem_locked

(bootloader) factory-modes: disabled

(bootloader) iswarrantyvoid: no

(bootloader) max-download-size: 268435456

(bootloader) reason: Volume down key pressed

(bootloader) imei: 356212330745457

(bootloader) imei2: 356212330745465

(bootloader) meid:

(bootloader) date: 08-06-2021

(bootloader) sku: XT2133-2

(bootloader) carrier_sku: XT2133-1

(bootloader) battid: SB18C77773

(bootloader) iccid:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Fri Jan 13 20:48: 3 UTC 2023"

(bootloader) ro.build.fingerprint[0]: motorola/lisbon_retaile/lisbon:12/

(bootloader) ro.build.fingerprint[1]: S3RLS32.114-25-3/1ae1da:user/relea

(bootloader) ro.build.fingerprint[2]: se-keys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.mtk: alps-mp-s0.mp1.tc2sp-V2.168

(bootloader) version-baseband: MT6785_TC2.PR1.SP.V1.2.P35.01.64R

(bootloader) kernel.version[0]: Linux version 4.14.186+ (nobody@android-

(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390

(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android

(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project

(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7

(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH

(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79

(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Sun Nov 6 23:38:33 CST

(bootloader) kernel.version[8]: 2022

(bootloader) frp-state: no protection (0)

(bootloader) ro.carrier: reteu

(bootloader) current-slot: b

(bootloader) running-boot-lun: 2

(bootloader) running-slot: _b

(bootloader) slot-successful:_a: yes

(bootloader) slot-successful:_b: yes

(bootloader) slot-bootable:_a: Yes

(bootloader) slot-bootable:_b: Yes

(bootloader) slot-retry-count:_a: 1

(bootloader) slot-retry-count:_b: 1

(bootloader) slot-suffixes: _a,_b

(bootloader) slot-count: 2

(bootloader) pcb-part-no: SB28D03068

(bootloader) is-userspace: no

(bootloader) is-logical:

all: listed above

Finished. Total time: 0.088s
[Upgrading, Modifying and Unlocking] Renate:
Oh, that was worth a try. Many fastboots print out a lot of junk for each partition.

Well, you really don't want to flash something if you're not even sure what partition it is.

If you have a working system or recovery you can ls -l /dev/block/by-name

If you have a working EDL (even if restricted) you can display the GPT.
[Upgrading, Modifying and Unlocking] yesca213:
Try this partition name I found it in the flashfile.xml for that device
[Upgrading, Modifying and Unlocking] sd_shadow:
All the flash commands are in the .XML files.

Flashing

Commands
[Upgrading, Modifying and Unlocking] gguerra:
Makes sense that partition name would be the same as the file name.

I will try it, thanks.
[Upgrading, Modifying and Unlocking] gguerra:
OK. I tried flashing radio firmware. It went through OK.

I took the sim out of my working phone and placed it in the problem phone, as I have done many times already.

Same results. Without making a call, you can see the icon for LTE drops to 0 bars, then 4g, then LTE. When I place a call, it will change to G which I assume is 2G. Doesn't make sense since T-Mobile dropped that a while back. The call will sometimes go through and after about a minute it drops and says "Cellular Network Not Available for Voice Calls". Sometimes the call will not go through and you get the same message.

I will not bother to go through all of the troubleshooting steps I have taken. I even took in to T-Mobile and they replaced the SIM with a brand new one. I've tried other people's SIM in my phone, same thing. It drops the calls if it even goes through to begin with.

It's either a physical problem with my phone such as the sim slot, or a firmware issue. Problem started right after the A12 update. Thanks
[Upgrading, Modifying and Unlocking] gguerra:
I have an update to this issue. Somebody replied to my post on Reddit and let me know about it. Apparently, after a couple of system updates, Motorola fixed the bug and I am now able to toggle the OEM unlock in Developer Settings. This should allow me to downgrade back to A11.

Before I do that though, I have a question. It will do me no good to downgrade to A11 if it will automatically want to upgrade back to A12.

Will there be any way to prevent updates to Android in the future? Do I have to be rooted to do that?
[Upgrading, Modifying and Unlocking] WoKoschekk:
the app which needs to be deactivated/deleted is called: com.motorola.ccc.ota

path: /system_ext/priv-app/3c_ota

delete/deactivate the app (non-root):

a) delete the folder by using TWRP > File manager

— or —

b) deactivate the app by using ADB:

adb shell pm uninstall --user 0 com.motorola.ccc.ota
[Upgrading, Modifying and Unlocking] gguerra:
I am still contemplating. Thanks for the info.
[Upgrading, Modifying and Unlocking] WoKoschekk:
This is the only way to prevent updates getting installed automatically by your system.
[Upgrading, Modifying and Unlocking] gguerra:
I realize that but just to give you a real quick rundown on this. My phone was on A11, worked great, it updated to A12 which broke the phone. I won't get into details but I couldn't unlock the bootloader to downgrade. I finally did 3 months later but in the meantime I had to buy another phone. Not sure if I want to go back to A11 since it will be eventually be outdated. If I did it would just be a project and I am using the phone as a wifi device now. Hence why I am still contemplating what to do. Thanks.