Hello,
I would like to unlock the bootlader or my Pixel 6 (ultimate goal is to flash GrapheneOS).
Unfortunately, this does not work:
- I entered into developper mode, allowing USB debugging and OEM unlocking
- I downloaded android platform-tools and ensured all paths are working, incl. drivers for my Pixel 6
- I boot into Fastboot Mode of the Pixel 6 by holding POWER and VOL_DOWN during boot
- I connect the Pixel 6 with my desktop via the original USB-C cable
- I ensure that the desktop recognizes the Pixel 6:
fastboot devices -l
- Then I run "fastboot flashing unlock" - but the terminal gets stuck here.
Additionally, the Pixel 6 is also somehow stuck, I cannot do anything with it and have to hard reset it (POWER+VOL_UP)
Any idea how to unlock the boot loader?
memberger
Maybe try using GrapheneOS Web Installer instead of unlocking/flashing manually
What is wrong using and posting in this guide?
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Which model of the Pixel 6 do you have? Verizon, T-Mobile, AT&T or from Google Store?
Check under "Regulatory Labels" your model number first.
Cheers
memberger said:
Hello,
I would like to unlock the bootlader or my Pixel 6 (ultimate goal is to flash GrapheneOS).
Unfortunately, this does not work:
- I entered into developper mode, allowing USB debugging and OEM unlocking
- I downloaded android platform-tools and ensured all paths are working, incl. drivers for my Pixel 6
- I boot into Fastboot Mode of the Pixel 6 by holding POWER and VOL_DOWN during boot
- I connect the Pixel 6 with my desktop via the original USB-C cable
- I ensure that the desktop recognizes the Pixel 6:
fastboot devices -l
- Then I run "fastboot flashing unlock" - but the terminal gets stuck here.
Additionally, the Pixel 6 is also somehow stuck, I cannot do anything with it and have to hard reset it (POWER+VOL_UP)
Any idea how to unlock the boot loader?
memberger
Click to expand...
Click to collapse
Try using an A to C cable using USB 2.0 port.
memberger said:
Hello,
I would like to unlock the bootlader or my Pixel 6 (ultimate goal is to flash GrapheneOS).
Unfortunately, this does not work:
- I entered into developper mode, allowing USB debugging and OEM unlocking
- I downloaded android platform-tools and ensured all paths are working, incl. drivers for my Pixel 6
- I boot into Fastboot Mode of the Pixel 6 by holding POWER and VOL_DOWN during boot
- I connect the Pixel 6 with my desktop via the original USB-C cable
- I ensure that the desktop recognizes the Pixel 6:
fastboot devices -l
- Then I run "fastboot flashing unlock" - but the terminal gets stuck here.
Additionally, the Pixel 6 is also somehow stuck, I cannot do anything with it and have to hard reset it (POWER+VOL_UP)
Any idea how to unlock the boot loader?
memberger
Click to expand...
Click to collapse
As pointed out already, you want to check to be certain you have a device that CAN be unlocked. This is the most important thing we need to know before we can properly help, otherwise the answers you get are like shooting in the dark. The model number, which we need, can be found in the settings.
Verizon and AT&T devices cannot be unlocked. T-Mobile I think will once you have had service with them for a few months.
vandyman said:
What is wrong using and posting in this guide?
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
Hello,
this is interesting - the guide you are posting is different from the one I used: The line "adb devices" shows no Pixel 6 devices, while "fastboot devices" does show the device. Maybe this is the important piece.
Unfortunately, all solutions given in the tutorial are already fulfilled, this will not help.
Question: Should "adb devices" report the Pixel 6 in fastboot more? Or with the Pixel 6 in normal mode? Any idea where the error is?
memberger said:
Hello,
this is interesting - the guide you are posting is different from the one I used: The line "adb devices" shows no Pixel 6 devices, while "fastboot devices" does show the device. Maybe this is the important piece.
Unfortunately, all solutions given in the tutorial are already fulfilled, this will not help.
Question: Should "adb devices" report the Pixel 6 in fastboot more? Or with the Pixel 6 in normal mode? Any idea where the error is?
Click to expand...
Click to collapse
ADB devices is used when booted into the system. Fastboot devices is used when booted into fastboot mode.
Did you try using an A to C cable with USB 2.0 port?
Strephon Alkhalikoi said:
Verizon and AT&T devices cannot be unlocked. T-Mobile I think will once you have had service with them for a few months.
Click to expand...
Click to collapse
AT&T Pixels can be bootloader unlocked, that is if you paid off and SIM unlocked the phone.
AT&T locking bootloaders completely is mainly for non-Pixel devices like Samsung and Motorola.
@neelchauhan I stand corrected, as I should have remembered this from when I used my Pixel 2 XL. That said, I would still go nowhere near a device touched by a carrier.
Hi everyone. Before doing the proper research, I bought a Pixel 6 from Swappa assuming it could be OEM Unlocked for a custom ROM install.
Here is what I know from the description:
Model: GB7N6
Carrier Compatibility: AT&T, T-Mobile, Unlocked, Verizon, TextNow, US Cellular, Consumer Cellular, Cricket, Google Fi, Metro PCS, Net10, Reach Mobile, Red Pocket, Simple Mobile, Spectrum, Straight Talk, Ting, Total Wireless, TracFone, US Mobile, Visible, Xfinity
I spent a fair amount of time searching the net, but can't find anywhere if that model, GB7N6, is indeed OEM Unlocked.
Any information is geatly appreciated.
No device is OEM unlocked. The switch is only to allow you to unlock the bootloader. If you can't flip the switch you can't unlock it so either return it or sell it. Simple as that.
GemStater said:
Hi everyone. Before doing the proper research, I bought a Pixel 6 from Swappa assuming it could be OEM Unlocked for a custom ROM install.
Here is what I know from the description:
Model: GB7N6
Carrier Compatibility: AT&T, T-Mobile, Unlocked, Verizon, TextNow, US Cellular, Consumer Cellular, Cricket, Google Fi, Metro PCS, Net10, Reach Mobile, Red Pocket, Simple Mobile, Spectrum, Straight Talk, Ting, Total Wireless, TracFone, US Mobile, Visible, Xfinity
I spent a fair amount of time searching the net, but can't find anywhere if that model, GB7N6, is indeed OEM Unlocked.
Any information is geatly appreciated.
Click to expand...
Click to collapse
Same model as mine, yes the botloader can be unlocked and not carrier locked.
Cheers
Tom
tom1807 said:
Same model as mine, yes the botloader can be unlocked and not carrier locked.
Cheers
Tom
Click to expand...
Click to collapse
Thanks Tom. It was easier with my Pixel 4. I just looked for a "Google Edition" which had it's own specific model number. All I see for the Pixel 6 are three model numbers and no real solid info on what is what other than one is for Japan.
If I do some cross referencing in Swappa, I find the following:
Model# GB7N6 = TMobile/Unlocked
Model# G9S9B = AT&T/Verizon
My ROM info says if it's a Verizon phone, sell it.
memberger said:
- I entered into developper mode, allowing USB debugging and OEM unlocking
Click to expand...
Click to collapse
A lot of posts here about being able to allow OEM unlocking, but you said you were able to do that.
Did you authorize your computer for adb?
With the phone running normally, do an "adb reboot bootloader". If the computer hasn't been authorized, it will fail, but you should get a popup on your phone asking you to authorize adb access. Accept it, then try again. It should reboot to bootloader, at which point you can try the "fastboot flashing unlock".
mike.s said:
A lot of posts here about being able to allow OEM unlocking, but you said you were able to do that.
Did you authorize your computer for adb?
With the phone running normally, do an "adb reboot bootloader". If the computer hasn't been authorized, it will fail, but you should get a popup on your phone asking you to authorize adb access. Accept it, then try again. It should reboot to bootloader, at which point you can try the "fastboot flashing unlock".
Click to expand...
Click to collapse
The video below appears to be very comprehensive on topic...
Update: Got the Pixel 6 from Swappa today. Mint condition in original box, great deal!
Developer options, OEM unlocking, and USB debugging are all available.
Here is some info on the phone:
Model (IC): 10395A-GB7N6
SKU: GAO2900-US
neelchauhan said:
AT&T Pixels can be bootloader unlocked, that is if you paid off and SIM unlocked the phone.
AT&T locking bootloaders completely is mainly for non-Pixel devices like Samsung and Motorola.
Click to expand...
Click to collapse
Moto phones could be bootloader unlocked but had a similar process to unlocking on T-Mo. The website still active, with the threat that your warranty is terminated. Will they still give the unlock token?
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
Related
Hi! My name is Bautista.
This is my first post well explained, I already asked this question before but I did not express myself well (I hope to do it correctly in this attempt)
My problem happens with my Samsung Galaxy A01 SM-A015M, Running on OneUI 2.0/Android 10 with 2gb of ram, a Snapdragon 439, the stock rom/firmware and 32GB of storage, from Argentina.
Things I tried so far, and didn't work for me:
Unlocking the bootloader by following the Gearallnews and Cyanogenmods guides to the letter.
When trying to unlock the bootloader with the guides on the aforementioned pages, when starting the device a sign should appear saying that the bootloader is unlocked, which did not appear.
The device started correctly in the process to configure the device the first time it is turned on, connect the wifi as the guides said. Followed by that I went to the developer options and the option "Oem unlock" was still activated and in blue (which should not happen, it should appear grayed) I heard that some Samsung devices with snapdragon processors had a bootloader that cannot be unlocked
Unlocking the bootloader using ADB AND Fastboot. (ADB detects my device fine, but fastboot doesn't detect it at all)
Using Fastboot from Windows 7, Windows 10, and Kali Linux.
Installing TWRP.
Use rooting apps. (the ones that appear on the XDA rooting page)
What I am going to with this thread, is:
Can my device's bootloader be unlocked? And if so, how?
If the bootloader cannot be unlocked, how can I root or install TWRP?
Please, if you don't understand something or need more information, let me know by replying to this thread or sending me a private message.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
it's the same as Gearallnews and Cyanogenmods guides, i already did that, it dont work
Like the original poster I also have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) Panama. I have gone through all the aforementioned procedure and the bootloader does not unlock. There is no bootloader unlock warning on reboot and the OEM Unlock in developer option does not grey out. Does the Snapdragon processor not allow bootloader unlock or is anyone aware of a solution. Thanks for any assistance.
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
jwoegerbauer said:
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
mullerh said:
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
Click to expand...
Click to collapse
Hi! Did you manage to find a way to unlock the bootloader?
I have not been able to unlock the bootloader on this SM-A015M/DS (Latin American) model with Snapdragon processor. I have done a lot of searching but found little info except articles stating Samsung had gone through some extra effort to secure their latest phones. That also means I can not root it. I was hoping to get some feedback from other who may have had a better experience,
have you tried using the twrp app to install twrp?
i had an old galaxy grand prime which was impossible to unlock, but the app worked without issues
the only thing i had to pay attention is to turn it off right before ir reboots after installing and then loading into recovery
letting the mobile startup without doing this overrieded the command to install twrp
Thanks for your response. It is my understanding (I could be wrong) that before TWRP can be installed the Bootloader needs to be unlocked. The older Samsung usually allowed the Bootloader to be unlocked even if there was difficulty in rooting them. It appears that some of the newer Samsung's with the Snapdragon processors have added an additional security feature called SecureBoot which blocks the Bootloader from being unlocked.
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
For what it's worth, when I flashed the firmware onto the phone in the first place, I had to enable the developer option manually- I did this by booting into download mode and then a long press on the volume up button when prompted by the menu. I don't see why this wouldn't work for other devices. There are youtube videos that explain in greater detail if you haven't tried this yet.
Newiser7 said:
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
Click to expand...
Click to collapse
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
jwoegerbauer said:
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
Click to expand...
Click to collapse
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
mullerh said:
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
Click to expand...
Click to collapse
You are right: I was mistaken.
Thank you for clarifying that the bootloader is still locked. But how can I unlock it? Odin will let me flash the files, but I keep getting AUTH errors when I try to flash magisk patched files to root the phone. I'm assuming this is because the bootloader preventing the files from transferring. Is there a way to unlock it using ADB without fastboot, or a way using Odin? It seems crazy that unlocking the bootloader is enabled but I am still unable to actually unlock it.
I have also tried the CROM Service app (couldn't get it to install on my phone, error 3003 with ADB install), as well as the bootloader unlock method where I boot into download mode, hold the volume up key, and unlock the bootloader that way. I have done the latter at least 5 times and the bootloader is still locked. Ridiculous.
This prop apparently only confirms that the phone supports being unlocked, not that it is actually unlocked.
adb shell "getprop ro.oem_unlock_supported"
Check a few others, also see the official docs.
sys.oem_unlock_allowed
androidboot.flash.locked (the docs say this, but I think Samsung uses something different)
ro.boot.flash.locked
ro.boot.other.locked
Maybe also check these:
ro.boot.verifiedbootstate
ro.boot.veritymode
The docs indicate that the verifiedbootstate should be orange if the bootloader is unlocked. I don't know much about it, though.
You can always use grep to search for any interesting values, like "lock" or "boot" or "flash":
adb shell getprop | grep lock
adb shell getprop | grep boot
adb shell getprop | grep flash
Maybe report any interesting values you have with and without OEM Unlock checked. Maybe someone smarter than us will find it useful.
I would really like to see an A01 root happen, it's such an affordable and accessible device for all sorts of things. Great as a backup device or for a project. You think someone would've released some goods for it by now. It's been out all year.
And for the 16GB model, it's absolutely terrible because Samsung eats up so much space, then has the nerve to remove the Adoptable Storage feature. So even if you get a fast SD card, you can't install apps on it. Other than that, it's a perfectly serviceable phone. I would think with root we could get Adoptable Storage working.
To summarize what has been previously stated the Samsung Galaxy A01, version SM-A015M/DS is the Latin American version of this cellphone. This cellphone has a Snapdragon processor. This version is very similar to the versions (also Snapdragon processors) used by some US Carriers. Many current versions of Samsung cellphones have an additional security feature called "SecureBoot" which blocks bootloader unlocking. Some say this features was added at the request of US Carriers
The Asian version of the A01 has a Exynos processor. It is my understanding that with these it is very easy to unlock the bootloader and root the phone using the usual conventional methods. The Asian variant unfortunately does not cover some of the wireless bands used in the US/Canada/Latin America.
I have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) for Panama.
My research indicates that there is not yet an available bootloader unlocking and easy root method for this (A01) phone. For some other current Samsung models there does appear to be a method of flashing certain custom ROMs without a bootloader unlock but they appear to come with problems which include loss of some cellphone functions and a reduction in the charged battery life. So it seems hardly worth it.
It also appears that it is current well known that all current Samsung phones with Snapdragon processors have not allowed bootloader unlocking and rooting due to the enhanced security feature.
At this time we can only complain and/or not buy any additional Samsung phones
Perhaps with time skillful developers will come up with a method to solve this problem with this inexpensive A01.
Please provide any new or updated info if you have it.
Any solution for rooting Galaxy A01 ?
I use A015f region SER (Russia) In Russia, too, the device is locked (bootloader) of course, give any solution
One thing I know is that a fellow SM-M015f, which is almost identical, which is with the same Snapdragon 439, except for the battery capacity and screen size and gigabytes of internal memory, successfully unlocks and gets Magisk root.
this phone actually has a fastboot mode, from recover mode select reboot to bootloader, it will boot to fastboot mode,but ive still been unsucessful in getting fastboot mode to work, devices manager reports device error,
I can start the unlock proccess.
But after it is done and the data is wipped,
It keeps locked.
Sad
Hi All.
Yesterday I bought this thing and as with everything, I immediately attempted to begin rooting the damn thing.
Update: 6th of November 2021
I re-enabled Developer Options and OEM Unlocking became selectable. Don't know how.
NOTE #1: The Motorola Edge 20 Lite also is the Motorola Edge 20 Fusion
NOTE #2: This Motorola Edge 20 Fusion was bought in Australia with it Carrier Unlocked from JB HiFi (Tech shop)
So far I have been unsuccessful and as the 3rd of November 2021 am currently stuck at:
"Your device does not qualify for bootloader unlocking."
After 30 minutes of online chat with Motorola's support I ended up getting this response:
"Try to check if your device was listed here : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215."
This info was already known to me
"You can reach-out some help at this site : Here's the link: https://forums.motorola.com/search?find=unlock+bootloader"
Yay. Great fun
The below steps are what I have tried so far
ROOT Attempt Steps
Enable Developer Options
Enable USB Debugging
Power off device
Power Button + Down Volume until startup
Volume Keys until "Recovery Mode"
Start
At "No Command" Hold Power and press the Up Volume
"Mount /System"
Enter FastBoot - This will restart once or twice
(On Windows) Open up cmd go to adb and fastboot installation folder
(On Windows) run "fastboot oem get_unlock_data" which should then "Wait for device"
Volume key to "Reboot to bootloader"
Eventually during the reboot it should provide you the oem unlock data
Follow the instructions here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
???
OEM Unlocking becomes selectable # NOTE: This became selectable on the 6th of November.
Profit
I am stuck at number 14 as for me it says "Your device does not qualify for bootloader unlocking" and chatting with support tells me to go speak to a Developer on Lenovo's forum, but I would rather be dealing with XDA Developers honestly.
I am putting this all here for future men to attempt to figure out. Hopefully with time we will get a solution.
P.S. Two other options that I have seen elsewhere as well:
Factory Reset your device after getting your Sim Card installed and it Online
The it stay online for a Week and then "OEM Unlocking"
1st didn't work and I doubt 2nd will fix it.
Cheers.
> Root Possibilities? - What has been tried and tested...
It is possible.
Here is hints.
I already have rooted my Edge 20 Fusion with the standard ROM version RRK31.Q3-19-54
See https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
You have to install the USB driver for Motorola smartphone before using adb.exe and fastboot.exe execution.
And execute adb.exe devices or fastboot.exe devices and check the connection between Edge 20 fusion and PC.
If the command says "Wait for device", it is failure the connection.
In good connection case, then we can see a DEVICE NAME.
The USB driver is here, https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
Maybe you get a little bit confuse because you can not find boot.img under "C:\ProgramData\LMSA\Download\RomFiles\".
In my case, I found boot.img file under "C:\ProgramData\RSA\Download\RomFiles\".
These paths are a little bit diffirent.
Patch boot.img by the Magisk on your Edge 20 fusion.
You have to unlock the bootloader before flashing patched boot.img file into your Edge 20 fusion.
Edge 20 fusion have boot_a and boot_b partitions.
Enjoy!
how did you unlock the bootloader? officially through the moto website or unofficially using a tool like mtkclient?
luridphantom said:
how did you unlock the bootloader? officially through the moto website or unofficially using a tool like mtkclient?
Click to expand...
Click to collapse
Hi
Let's go https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
And click "Unlock the Bootloader".
Regards
TakaSZK said:
Hi
Let's go https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
And click "Unlock the Bootloader".
Regards
Click to expand...
Click to collapse
Came here lurking from DuckDuckGo. Sounds promising.
Only query I have is: would it be currently possible to unbrick the phone in case something goes wrong?
Unlock code and 72 hours wait for OEM unlock option to change from grey.. Worked great for me.
I googled RRKS31.Q3-19-97-3 and found a link to firmware on androidfilehost
Only extracted the boot.img to patch in magisk.
Flashed to boot_a and boot_b in fastboot. Job done
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Direct links to firmware
TakaSZK said:
Hi
Let's go https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
And click "Unlock the Bootloader".
Regards
Click to expand...
Click to collapse
I had re-installed latest ROM by the Rescue and Smart Assistant from a booting loop accident.
1 week ago, I had made my Edge 20 Fusion booting loop accident.
At that time, I had accidentally corrupted the file /system/build.prop file.
I was so paniced.
Fortunately my Edge 20 Fusion booted with the fastboot mode.
Then, I had rescued(re-installed) my Edge 20 Fusion by the Rescue and Smart Assistant.
the Rescue and Smart Assistant makes to install latest ROM.
I noticed that the quality of the camera has improved on ROM RRKS31.Q3_19_98.
I am so happy now ;-)
Maybe we can recover a Edge 20 Fusion with manually flashing ROM.
Please be careful, I have no experience or conviction for a manual recovering.
And you should get and memo two IMEI numbers(slot 1 and slot 2) before rooting your device.
Because the Rescue and Smart Assistant checks IMEI number for the identify a device when we try to rescue.
I didn't have IMEI, but I was able to rescue it.
How to boot with the fastboot mode.
Volume down button + Power button.
Enjoy rooted environment.
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
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working
Currently, RSA does not support XT2311-3 for unknown reason. However, I found a ROM for Tracfone, but the boot works with unlocked version.
Download: https://www.androidfilehost.com/?fid=10620683726822053015
MD5 60f8e629cbe7e969923c07538d6c3c7c
Bootloader unlock required. However, VPN disappeared after bootloader unlocked. You have to set up user account if you need VPN
Note: your phone is wiped during bootloader unlock process. Since RSA does not work with this phone at this time, you may not be able to rescue if something goes wrong.
Note: Titanium Backup does not work with Android 13. You need Swift Backup (pay $2.5 a year to use your choice of cloud service)
You should do it before initial setup. Wi-Fi connection and/or data connection needed for Magisk. Transfer the boot.img downloaded to your phone and patch it with Magisk, and transfer the patched boot back to host computer.
Now reboot the phone to bootloader or fastbootd
Code:
adb reboot fastboot
Flash patched boot
Code:
fastboot flash boot
Press space once, drag-and-drop the patched_boot onto command window, and press enter.
Post process:
Install the following as modules and you should install Fox's Magisk Module Manager
ADB fastboot
shamiko (you can setup Deny List but you don't have to enable because shamiko takes care of it)
Universal SafetyNet Fix 2.4.0
Systemless host within Magisk
liboemcrypo disabler is not required as it plays Netflix fine after these modules added, and it appears L1 on mine (good)
You can complete setup after root is done. Make sure you add Play Store and Play Services into Deny List as well as any app can detect root
How do you unlock the bootloader on this phone? When I copy & paste my device ID into the Motorola bootloader unlock page and click on "Can my device be unlocked" button, I get a message saying, "Your device does not qualify for bootloader unlocking".
dmw_4814 said:
How do you unlock the bootloader on this phone? When I copy & paste my device ID into the Motorola bootloader unlock page and click on "Can my device be unlocked" button, I get a message saying, "Your device does not qualify for bootloader unlocking".
Click to expand...
Click to collapse
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
basixs_2 said:
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
Click to expand...
Click to collapse
I got mine from Best Buy
Now there's a workaround for missing VPN
Get App Ops from Play Store and add sui (zygisk) module on Magisk
Check the list on App Ops and allow VPN on app needed
Moreover, Netflix works after USNF @Displax mod added, added Play Store and Play Services in Deny List, and Shamiko module added.
Mine shows L1 and Netflix (and cable TV app) work
basixs_2 said:
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
Click to expand...
Click to collapse
I bought mine at Best Buy, but that shouldn't make any difference. It's the unlocked version for use on any carrier, so it should be bootloader unlockable.
I enabled Developer Options, but I noticed that "OEM Unlocking" is grayed out. When trying to Google this and find out why, I came upon a Lenovo forum where people were asking the exact same thing, and Lenovo's response was that the phone needs an Internet or Wi-Fi connection for 7 days before the "OEM Unlocking" option will become available(?!).
Now, I'm wondering if that's what's going on here, and why I'm getting the message that my phone isn't eligible for bootloader unlocking. I guess I'll see in a few days, LOL!
dmw_4814 said:
I bought mine at Best Buy, but that shouldn't make any difference. It's the unlocked version for use on any carrier, so it should be bootloader unlockable.
I enabled Developer Options, but I noticed that "OEM Unlocking" is grayed out. When trying to Google this and find out why, I came upon a Lenovo forum where people were asking the exact same thing, and Lenovo's response was that the phone needs an Internet or Wi-Fi connection for 7 days before the "OEM Unlocking" option will become available(?!).
Now, I'm wondering if that's what's going on here, and why I'm getting the message that my phone isn't eligible for bootloader unlocking. I guess I'll see in a few days, LOL!
Click to expand...
Click to collapse
I know this is weird.
Mine takes 7 days and it's on internet/SIM active
Back then my situation was more difficult because even RSA was not ready for the phone (it says not supported). I needed boot.img for rooting
I think I'm on day 2 of waiting... It's only on WiFi as I need the SIM for my old phone. Kind of frustrating that it's not a more immediate result/change.
Yesterday was 7 days from when I bought my Moto G Power 5G, and I checked it this morning - lo and behold, OEM Unlocking is available!
I don't understand the reasoning/desire behind Lenovo's wanting to impose this 7 day waiting period, but it is what it is. Time to {hopefully!} go unlock my bootloader.
dmw_4814 said:
Yesterday was 7 days from when I bought my Moto G Power 5G, and I checked it this morning - lo and behold, OEM Unlocking is available!
I don't understand the reasoning/desire behind Lenovo's wanting to impose this 7 day waiting period, but it is what it is. Time to {hopefully!} go unlock my bootloader.
Click to expand...
Click to collapse
Good Luck!!!
I'm still waiting (on day 5) but this is great to hear
basixs_2 said:
Good Luck!!!
I'm still waiting (on day 5) but this is great to hear
Click to expand...
Click to collapse
What a pain in the a$$!! I had to keep trying over and over before it would work. It worked the first or second time (gave me the option to get an unlock code), but I forgot to put it in bootloader mode, so I got an error. Then, I had to try multiple times before it would give me another chance to get the unlock code (kept telling me my device wasn't eligible for unlock). Finally got it unlocked, and then rooted!