Hi guys, how y'all doing?
I've been trying to unlock the bootloader of my phone a couple of months now and every single attempt is a failure. I've done all the steps right but, in the Motorola website I receive a message that my phone don't apply for unlocking the bootloader.
Anyone knows anything about this, if it can be bypassed somehow or if has anyway to contact Motorola to get any information about this issue.
Thanks in advance.
1Apokalypsis said:
Hi guys, how y'all doing?
I've been trying to unlock the bootloader of my phone a couple of months now and every single attempt is a failure. I've done all the steps right but, in the Motorola website I receive a message that my phone don't apply for unlocking the bootloader.
Anyone knows anything about this, if it can be bypassed somehow or if has anyway to contact Motorola to get any information about this issue.
Thanks in advance.
Click to expand...
Click to collapse
Well, I can think of a few reasons why you can't unlock your bootloader.
1. The most obvious one: you haven't enabled OEM unlocking under developer settings.
2. You're not using a retail device. Only retail devices can unlock BL AFAIK. Non-retail devices are those sold by carriers (AT&T, Verizon, whatever else).
3. Your bootloader is not unlockable, even if its retail.
The 1st problem is easy to solve and I won't discuss it.
The other two are stored as variables on your bootloader and can be checked with the "fastboot getvar [x]" command, where [x] is the variable name.
The variables of interest here are:
1. "ro.build.version.full" - this tells if device is retail or not. It should return something like "retail.en.US" or "retail.xx.XX", depends on region.
2. "cid" - I have no idea cid stands for, but I think it's related to bootloader type.
3. Be aware that I don't know if the 1st variable has the same name on all motorola devices. In case of doubt, use "fastboot getvar all" to list all variables, then you can check manually.
Nowadays, it's not common for Motorola devices to have locked cids. In Lollipop/Marshmallow days, some devices had that issue where it was retail but impossible to unlock due to cid. The un-unlockable cids should be the same for all devices but you'll have to research, I don't remember which is which anymore.
SUMMARY:
1. check the developer setting "Allow OEM unlocking". It's a switch. If it's off, turn it on and you'll be able to unlock the BL
2. If that doesn't work, check if your phone is a retail model. If not, you're out of luck.
3. If it is retail and you can't unlock it, you are either providing the wrong unlock code to fastboot, or you have an unlockable cid, in which case you're also out of luck.
[edit]
Forgot to mention this, if your device has a mediatek CPU/SoC, forget about it, they're impossible to unlock too.
[edit 2]
I found the cid list: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
freeZbies said:
Well, I can think of a few reasons why you can't unlock your bootloader.
1. The most obvious one: you haven't enabled OEM unlocking under developer settings.
2. You're not using a retail device. Only retail devices can unlock BL AFAIK. Non-retail devices are those sold by carriers (AT&T, Verizon, whatever else).
3. Your bootloader is not unlockable, even if its retail.
The 1st problem is easy to solve and I won't discuss it.
The other two are stored as variables on your bootloader and can be checked with the "fastboot getvar [x]" command, where [x] is the variable name.
The variables of interest here are:
1. "ro.build.version.full" - this tells if device is retail or not. It should return something like "retail.en.US" or "retail.xx.XX", depends on region.
2. "cid" - I have no idea cid stands for, but I think it's related to bootloader type.
3. Be aware that I don't know if the 1st variable has the same name on all motorola devices. In case of doubt, use "fastboot getvar all" to list all variables, then you can check manually.
Nowadays, it's not common for Motorola devices to have locked cids. In Lollipop/Marshmallow days, some devices had that issue where it was retail but impossible to unlock due to cid. The un-unlockable cids should be the same for all devices but you'll have to research, I don't remember which is which anymore.
SUMMARY:
1. check the developer setting "Allow OEM unlocking". It's a switch. If it's off, turn it on and you'll be able to unlock the BL
2. If that doesn't work, check if your phone is a retail model. If not, you're out of luck.
3. If it is retail and you can't unlock it, you are either providing the wrong unlock code to fastboot, or you have an unlockable cid, in which case you're also out of luck.
[edit]
Forgot to mention this, if your device has a mediatek CPU/SoC, forget about it, they're impossible to unlock too.
[edit 2]
I found the cid list: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/m-p/3222809
Click to expand...
Click to collapse
Thanks for all the info.
1. I liked that you mentioned the "OEM Unlocking" switch, but I'm not a total dummy, it's turned on lol.
2. I don't believe that my model is one of those sold by carriers, at least afaik.
3. I will try to get the variables and look it up, but I'm feeling that I'm out of luck already.
It's the Qualcomm version of the One Fusion+
1Apokalypsis said:
Thanks for all the info.
1. I liked that you mentioned the "OEM Unlocking" switch, but I'm not a total dummy, it's turned on lol.
2. I don't believe that my model is one of those sold by carriers, at least afaik.
3. I will try to get the variables and look it up, but I'm feeling that I'm out of luck already.
It's the Qualcomm version of the One Fusion+
Click to expand...
Click to collapse
If it's the qualcomm version and it doesn't unlock it must be bc it must be either bc it is not retail or cid. If you're using a retail phone and cid is unlockable then keep trying/check unlock code/try asking for it again, whatever, it should work.
Related
I bought ANE-LX1 (P20 Lite) on June 2018 and immediately unlocked the OEM from the developer options (automatic factory reset was done then), but i never rooted or installed custom rom, recovery...etc.
All updates was normally arriving and i was updating my phone regularly (current build is: ANE-LX1 8.0.0.170(C185)).
I decided to root my device using fastboot, but when the device is in recovery mode i can see:
Code:
Phone Locked -- (in green font color)
FRP Unlock -- (in red font color)
When i try to flash using fastboot i got:
Code:
FAILED (remote: Command not allowed)
While searching online i found that Huawei decided to lock bootloader for all users (so we buy their hardware which contains an opensource software and then they lock it... PERFECT!), and it seems that the only way now is to get the unlock code by contacting third-party codes providers, pay money and they guarantee to provide the correct unlock code (pay and pray) + I will have to expose my device information.
My questions are:
-How can i see in the developer options that my OEM is already unlocked, while the recovery is not convinced?
-Do i really have to unlock it again with the code "after purchasing it ofcourse -- which i will never do" (e.g. using fastboot)?
-Is there any solution from xda experts for my case rather than buying codes and exposing my device information or stay with a Locked bootloader?
(attached evidence images for a clearer view)
drive.google.com/open?id=1e9CepsHp2O541ZKGS0E6uqS2hBwp8ry1
drive.google.com/open?id=119eCoO4Z0TvydupLIsEv-r5lsGHOD4o0
drive.google.com/open?id=1IBA1nYnw_PU25VLPTzqSLswTpGMQxuXP
Thanks in advance for your kind support.
and Thanks Huawei for putting us as a development community in this situation, where we have to pay for the black markets to unlock our own phones in an unofficial way.
Yes please, shoot some answers!
alimerdan said:
I will have to expose my device information.
Click to expand...
Click to collapse
What do you expose?
bouncingsoul said:
Yes please, shoot some answers!
What do you expose?
Click to expand...
Click to collapse
IMEI, product S/N (if i correctly understood the process, i have to provide my device info so they can extract the bootloader unlock key)
According to the information that's available, the code used to unlock the bootloader is unlocked in a very complicated way and it's basically unique for everyone. Now, I don't know how much this is true and how and why these people got their hands on the "method" of creating the code, but no one has been able to find a way that's guaranteed to work or even work at all, except for, of course, these sites that make you pay for it. I hope I'm not mistaken and forgive me if I am, but I don't think there is any way to obtain the bootloader code manually or without exposing your information to random strangers on the internet.
Need to unlock bootloader with dc unlocker to get unique unlock code. Look guide bootloader unlocking
EDIT: Problem solved. I just had to wait a few days to get the switch available. It seems it's a "security feature"...
Hello, guys.
I recently bought a Moto One, already with the bootloader unlocking in mind. I live in Brazil, and here phones are required to be unlockable. But here's the thing: this one has the "OEM unlock" option grayed out. I already did a Factory Reset multiple times, following different ways to do it, and nothing worked.
It says I need to connect to internet (which I obviously already did) or contact my mobile operator. But it's a retail device, so they have nothing to do with it.
Does someone have the same problem or am I the only lucky one?
lucasdeeiroz said:
Hello, guys.
I recently bought a Moto One, already with the bootloader unlocking in mind. I live in Brazil, and here phones are required to be unlockable. But here's the thing: this one has the "OEM unlock" option grayed out. I already did a Factory Reset multiple times, following different ways to do it, and nothing worked.
It says I need to connect to internet (which I obviously already did) or contact my mobile operator. But it's a retail device, so they have nothing to do with it.
Does someone have the same problem or am I the only lucky one?
Click to expand...
Click to collapse
I've seen another Brazilian guy over in our telegram group having the same problem. I don't know more about it tho.
Boot to fastboot and do:
Code:
fastboot getvar cid
Here you'll see which cid's can be unlocked or not. https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
If your cid returns a value that is supposed to be unlockable then you should report the bug in that motorola community.
https://forums.lenovo.com/t5/motorola-one-motorola-one-power/bd-p/Motorola_One
tys0n said:
I've seen another Brazilian guy over in our telegram group having the same problem. I don't know more about it tho.
Boot to fastboot and do:
Code:
fastboot getvar cid
Here you'll see which cid's can be unlocked or not. https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
If your cid returns a value that is supposed to be unlockable then you should report the bug in that motorola community.
https://forums.lenovo.com/t5/motorola-one-motorola-one-power/bd-p/Motorola_One
Click to expand...
Click to collapse
Thank you for your answer. My cid is eligible for unlocking. I even got the Unique Key to unlock it already. I suppose I'll have to report the bug to Motorola.
I've read somewhere that this is supposed to be a new security thing (not sure if it's from manufacturer or from the OS): in order to activate the Unlock switch, user is supposed to wait a minimum time period: something close to 7 days of uptime.
It's funny, though, Motorola's site doesn't mention this restrain at all.
m2habert said:
I've read somewhere that this is supposed to be a new security thing (not sure if it's from manufacturer or from the OS): in order to activate the Unlock switch, user is supposed to wait a minimum time period: something close to 7 days of uptime.
It's funny, though, Motorola's site doesn't mention this restrain at all.
Click to expand...
Click to collapse
That is interesting... and it's true. After 4 days the switch is finally available. Thanks for the info!
Thread closed by OP request!
I bought a Moto G Play 2021 unlocked from best buy yesterday. I can't enable "OEM unlocking" in Developer Settings. It is grayed out.
I factory reset a few times.
The phone CID is listed as a phone that can be unlocked on the Motorola site. I got the unlocking key from the Motorola site through a process that sends an email out with the key. Then I run <fastboot oem unlock "key">, but I get
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
I don't think any fastboot command will work as long as the "OEM unlocking" is grayed out and disabled in settings.
Called Motorola. They offer no help.
I'm new to custom ROMs and having a hard time. Any advice is appreciated. Thanks
dary1361 said:
I bought a Moto G Play 2021 unlocked from best buy yesterday. I can't enable "OEM unlocking" in Developer Settings. It is grayed out. I factory reset a few times.
The phone CID is listed as a phone that can be unlocked on the Motorola site. I get the unlocking key from the Motorola site through a process that sends an email out with the key. Then I run <fastboot oem unlock "key">, but I get
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
I don't think any fastboot command will work as long as the "OEM unlocking" is grayed out and disabled in settings. Called Motorola. They offer no help. I'm new to custom ROMs and having a hard time. Any advice is appreciated. Thanks
Click to expand...
Click to collapse
I almost bought thru best buy and found out that Verizon/sprint was the service provider. So, I went and bought unlocked at amazon. Hopefully, not what happened to you... There was something about greyed out oem unlocking on this phone somewhere here in XDA. Do a search.
dary1361 said:
I just bought a Moto G Play 2021 unlocked from best buy yesterday. I can't enable "OEM unlocking" in Developer Settings. It is grayed out. I factory reset a few times.
The phone CID is listed as a phone that can be unlocked on the Motorola site. I get the unlock code from the Motorola site through a process that sends an email out with the key. Then I run <fastboot oem unlock "key">, but I get
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
I don't think any fastboot command will work as long as the "OEM unlocking" is grayed out and disabled in settings. Called Motorola. They offer no help. I'm new to custom ROMs and having a hard time. Any advice is appreciated. Thanks
Click to expand...
Click to collapse
Not that unusual.
Sometimes there's a time delay, and required connection to WiFi or LTE.
Also sometimes a factory reset will ungray the OEM unlock toggle.
I suggest a factory reset, then connect to wifi if it's still grayed out, it may take a few days to change.
Also you can check the CID code list in my Bootloader unlock thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Lostbytes_xda said:
I almost bought thru best buy and found out that Verizon/sprint was the service provider. So, I went and bought unlocked at amazon. Hopefully, not what happened to you... There was something about greyed out oem unlocking on this phone somewhere here in XDA. Do a search.
Click to expand...
Click to collapse
Tried XDA and elsewhere. They have solutions I have already tried above. Thanks
sd_shadow said:
Not that unusual.
Sometimes there's a time delay, and required connection to WiFi or LTE.
Also sometimes a factory reset will ungray the OEM unlock toggle.
I suggest a factory reset, then connect to wifi if it's still grayed out, it may take a few days to change.
Also you can check the CID code list in my Bootloader unlock thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Tried factory reset. Tried with and without Wifi after factory reset. I don't have a sim for it yet. So can't get LTE.
Can't find a "CID code" list in your post. Do you mean a list with CID's that lets you know if your phone can be unlocked? I found my CID is allowed for unlocking on Motorola's site.
Do you know why a delay might work? You think there is a timer or something for unlocking?
Thanks
dary1361 said:
Tried factory reset. Tried with and without Wifi after factory reset. I don't have a sim for it yet. So can't get LTE.
Can't find a "CID code" list in your post. Do you mean a list with CID's that lets you know if your phone can be unlocked? I found my CID is allowed for unlocking on Motorola's site.
Do you know why a delay might work? You think there is a timer or something for unlocking?
Thanks
Click to expand...
Click to collapse
There's a link in my Bootloader unlock thread, to the official cid list, you likely have seen already.
I don't know if wifi/lte is needed just going by what has been reported in the forums for last few years.
You can wait or return the device, there isn't any other options that I know of.
sd_shadow said:
There's a link in my Bootloader unlock thread, to the official cid list, you likely have seen already.
I don't know if wifi/lte is needed just going by what has been reported in the forums for last few years.
You can wait or return the device, there isn't any other options that I know of.
Click to expand...
Click to collapse
How many days should I wait before returning the phone? Is there any way to know before buying which ones are bootloader unlocked?
dary1361 said:
How many days should I wait before returning the phone? Is there any way to know before buying which ones are bootloader unlocked?
Click to expand...
Click to collapse
I've seen anywhere from mins to a couple of days reported, No pattern that I can see.
Factory reset, and connecting to the internet seem to help.
You could try Flash rescue with LMSA, but I haven't seen replies that helps.
If the CID is good, and you can get the unlock code from moto site, I don't know what else could be the issue.
sd_shadow said:
I've seen anywhere from mins to a couple of days reported, No pattern that I can see.
Factory reset, and connecting to the internet seem to help.
You could try Flash rescue with LMSA, but I haven't seen replies that helps.
If the CID is good, and you can get the unlock code from moto site, I don't know what else could be the issue.
Click to expand...
Click to collapse
So after three days, I did another factory reset. Nothing changed. I then used the KingRoot app. I clicked on Root, it didn't give me a confirmation. But when I went to the Developer Settings I could enable "OEM unlocking"!!! I then used <fastboot oem unlock "key"> on the bootloader and the device is unlocked now. Can't find twrp or any ROMs for this device though
I can confirm a three day time gate on the Moto G Play 2021 I got through T-Mobile Monday. The OEM Unlock has been greyed out since I first booted. Today, Thursday, after the 72 hour window, the toggle became accessable.
dary1361 said:
I bought a Moto G Play 2021 unlocked from best buy yesterday. I can't enable "OEM unlocking" in Developer Settings. It is grayed out.
I factory reset a few times.
The phone CID is listed as a phone that can be unlocked on the Motorola site. I got the unlocking key from the Motorola site through a process that sends an email out with the key. Then I run <fastboot oem unlock "key">, but I get
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
I don't think any fastboot command will work as long as the "OEM unlocking" is grayed out and disabled in settings.
Called Motorola. They offer no help.
I'm new to custom ROMs and having a hard time. Any advice is appreciated. Thanks
Click to expand...
Click to collapse
Is it a Verizon phone asking because since Verizon doesn't allow bootloader to be unlocked it could be reason why
sd_shadow said:
I've seen anywhere from mins to a couple of days reported, No pattern that I can see.
...
If the CID is good, and you can get the unlock code from moto site, I don't know what else could be the issue.
Click to expand...
Click to collapse
Weirdly (or absurdly), yesterday I found a Lenovo forum post that says it might take up to a week to get OEM Unlock. I posted on it (here) to see if anybody else has had the same experience that I'm still in the middle of -- THREE days, on WiFi, still no unlock.
Strange(r) thing is the "advice" from Moto/Lenovo in the link relates to a 3-year-old phone. I bought a Moto G6 (carrier-unlocked & BL-unlockable -6) in mint condition, updated to latest Pie (April 2020 security patch).
But maybe the G6/plus/play is just extra-odd? I've owned and rooted or unlocked 6-8 Moto phones (see my sig, not a complete list) and I've never in the past waited more than a few minutes to get OEM Unlock enabled. And all it took with my lady's Moto G Stylus '21 was making a WiFi connection, as has been super-typical for me.
I guess I'm just babbling out of frustration. Seems this mystery only gets weirder.
Edit to add, your last comment addresses one niddly little question I put forth in my post linked above . . . my CID (0x032) says the phone is unlockable, and I already got the unlock code from Moto. Is there ANY other detail, in getvar or anywhere, that might reveal that a phone is NOT unlockable?
Moondroid said:
Weirdly (or absurdly), yesterday I found a Lenovo forum post that says it might take up to a week to get OEM Unlock. I posted on it (here) to see if anybody else has had the same experience that I'm still in the middle of -- THREE days, on WiFi, still no unlock.
Strange(r) thing is the "advice" from Moto/Lenovo in the link relates to a 3-year-old phone. I bought a Moto G6 (carrier-unlocked & BL-unlockable -6) in mint condition, updated to latest Pie (April 2020 security patch).
But maybe the G6/plus/play is just extra-odd? I've owned and rooted or unlocked 6-8 Moto phones (see my sig, not a complete list) and I've never in the past waited more than a few minutes to get OEM Unlock enabled. And all it took with my lady's Moto G Stylus '21 was making a WiFi connection, as has been super-typical for me.
I guess I'm just babbling out of frustration. Seems this mystery only gets weirder.
Edit to add, your last comment addresses one niddly little question I put forth in my post linked above . . . my CID (0x032) says the phone is unlockable, and I already got the unlock link from Moto. Is there ANY other detail, in getvar or anywhere, that might reveal that a phone is NOT unlockable?
Click to expand...
Click to collapse
The CID is the only thing to look at, that I know of.
Usually, OEM unlock is available within 3 days, but some have reported a couple of weeks.
Factory Reset seems to help if it's been over 3 days, but you will need to reconnect to the internet.
sd_shadow said:
The CID is the only thing to look at, that I know of.
Usually, OEM unlock is available within 3 days, but some have reported a couple of weeks.
Factory Reset seems to help if it's been over 3 days, but you will need to reconnect to the internet.
Click to expand...
Click to collapse
Thanks man. I haven't tried FDR yet, afraid of starting the countdown all over again. But if I don't get unlock in the next day or two I'll give it a shot.
Edit-- I was wondering as much as anything if maybe this phone could be an unlockable Amazon variant that had been blasted with stock firmware to hide the fact. But I don't even know how that could be done.
Moondroid said:
Thanks man. I haven't tried FDR yet, afraid of starting the countdown all over again. But if I don't get unlock in the next day or two I'll give it a shot.
Edit-- I was wondering as much as anything if maybe this phone could be an unlockable Amazon variant that had been blasted with stock firmware to hide the fact. But I don't even know how that could be done.
Click to expand...
Click to collapse
If it was an Amazon version the CID would be different.
The getvar all will have the software channel and other info
Code:
fastboot getvar all
sd_shadow said:
If it was an Amazon version the CID would be different.
The getvar all will have the software channel and other info
Code:
fastboot getvar all
Click to expand...
Click to collapse
Ah ok. Yeah I ran getvar all yesterday, found the CID and confirmed I'm on RetUS channel. Much obliged sd_shadow, as always, you're a super-reliable source of help and info here on XDA.
Moondroid said:
Ah ok. Yeah I ran getvar all yesterday, found the CID and confirmed I'm on RetUS channel. Much obliged sd_shadow, as always, you're a super-reliable source of help and info here on XDA.
Click to expand...
Click to collapse
You're on RetUS so you should be good, if unlocking was blocked it would be the Amazon channel
Do you have gaumna?
Amazon isn't even listed on lolinet.
That doesn't mean there isn't an Amazon channel, but it's not likely.
https://mirrors.lolinet.com/firmware/moto/guamna/official/
sd_shadow said:
Do you have gaumna?
Click to expand...
Click to collapse
Nope, never even heard of it that I recall. What is it?
Moondroid said:
Nope, never even heard of it that I recall. What is it?
Click to expand...
Click to collapse
Code:
fastboot getvar product
sd_shadow said:
Code:
fastboot getvar product
Click to expand...
Click to collapse
Ooooh dang. I mangled this convo. Clarification, the Moto G Stylus (not Play) is my lady's phone. The phone I'm currently struggling with is a G6 (unlocked version XT1925-6). That one is Ali. Her Stylus is codename Minsk. I unlocked and rooted her Stylus (via Magisk patch) months ago, no problems there. Serious apologies for channeling down the wrong road in this thread.
hi It says im unlocked in the unlock app. and I also have the token.bin from oneplus. I can't do anything in adb to unlock becuase i can't seem to unlock the bootloader it's greyed out in the developers options. How do you get the grey out?
i dont follow. you already got the token but cant enable OEM unlock? in order to get the token you need to have had OEM unlock enabled. to enable OEM unlock follow the debloat thread script. it will enable OEM unlock.
droidbot1337 said:
i dont follow. you already got the token but cant enable OEM unlock? in order to get the token you need to have had OEM unlock enabled. to enable OEM unlock follow the debloat thread script. it will enable OEM unlock.
Click to expand...
Click to collapse
I have the token from my last logic board that broke. Since I had to install a new logic board from e bay my IMEI has also changed since that is what it's attached to.
Also I tried contacting the carrier and they said I need the original owners information in order to continue. I stated it's my phone from your company but i just replaced the part. Of course they told me the same thing. That I need the original owners information... Since the IMEI is no longer the same. The IMEI really is just a fingerprint for carriers to track. Doesn't really hold much more significance.
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
TLDR; I am wondering if all U.S. phones with Snapdragon cannot be normally rooted by just enabling OEM unlock/unlocking bootloader and must be rooted in an expert/costly method. Or if accounts from people saying they enabled OEM unlock on their Moto G Powers I read were not just fictional or with non-U.S. phones.
Click to expand...
Click to collapse
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
jwoegerbauer said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked...
Click to expand...
Click to collapse
See the CID and OEM unlock posts
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
If you get the bootloader unlocked
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
Click to expand...
Click to collapse
Absolute nonsense.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, this there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
Click to expand...
Click to collapse
You must wait, I believe it was several days of the device being online (wifi at least) to get it to permit unlocking the bootloader. I know with mine (US Xfinity Wireless), out of the box, it was gray, but 2 or 3 days later it was able to be toggled and I unlocked and got Magisk installed easily, using the patch stock boot.img method, and flashing it via fastboot beyond that. So you can do it, just can't do it before you activate the thing properly I think is the main block there you're describing. So perhaps those outside the US (with US models they can't toggle) can connect to a VPN'd wifi network and have it look like it's in the US, maybe.
There's a lot that can be done on these with just tinkering to get it there is all. But make sure you have your stock firmware is all, so you can quickly get it back into bootloader and just a flash away to fix anything really.
jwoegerbauer said:
Absolute nonsense.
Click to expand...
Click to collapse
Okay. Legit question here... How does one go about injecting SU binary to the system on the moto g 2021 series with secured boot?
Why should SU binary get housed in /system/... ? It's irrelevant where it's located, the main thing is that it's available and executable. Even Magisk doesn't store it in /system/.. but in /data/..
Because folder /data/local/tmp by default is mounted as RW my recommendation is to store it there. Using this storage place isn't conflicting with SELinux and/or AVB.
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When you have to run a shell command what requires elevated rights, then you run
Code:
adb devices
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-HERE>'"
Deleted member 1890170 said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
it needs to be unlock