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!
Related
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 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.
I picked up a secondhand Pixel 4. The seller said that this phone was purchased directly from Google and the only services ever used with it were AT&T prepad and Google Fi, never under any contract. But when I do 'adb reboot bootloader' the device state says locked and the OEM unlock option is greyed out. I have read that some Pixels purchased from Google end up bootloader locked after using Verizon service. If that is the case, is there any hope of getting the bootloader unlocked? Or maybe it got locked by some other means that I'm not aware of. Is there any way to get a history of carriers used with the phone via the IMEI in order to get a better idea of what might be going on?
Also, when I run 'adb shell pm list features' I do notice these lines:
feature:com.verizon.hardware.telephony.ehrpd
feature:com.verizon.hardware.telephony.lte
Does this mean that this is a Verizon model phone? Seems strange that it would have Verizon packages for a Google model phone.
You must have a sim inserted and data turned on for OEM unlocking not to be greyed out. I took a clue I guess from others by inserting my AT&T sim (still greyed out), rebooted (still greyed out), turned on mobile data (still greyed out), and rebooted. Then there was the glorious OEM unlocking option available.
For other clueless people who might read this: I immediately connected my phone via usb to my laptop, shutdown the phone, and held the power and volume down buttons to get into fastboot mode. Then from a terminal on my laptop ran 'fastboot flashing unlock', and the phone gave me the option to unlock the bootloader. adb and fastboot were previously installed.
I have seen other people mention the OEM unlocking option becoming available on their carrier version Pixel phones after inserting a not yet activated sim from another carrier. The latest mention that I saw was here in post #3
https://forum.xda-developers.com/t/manual-unlock-bootloader-for-locked-at-t-device.4374613/
Happy days. Just in time for Lineage OS 19.1
Sell your phone, then buy again with oem unlcok on
fitzly said:
You must have a sim inserted and data turned on for OEM unlocking not to be greyed out. I took a clue I guess from others by inserting my AT&T sim (still greyed out), rebooted (still greyed out), turned on mobile data (still greyed out), and rebooted. Then there was the glorious OEM unlocking option available.
For other clueless people who might read this: I immediately connected my phone via usb to my laptop, shutdown the phone, and held the power and volume down buttons to get into fastboot mode. Then from a terminal on my laptop ran 'fastboot flashing unlock', and the phone gave me the option to unlock the bootloader. adb and fastboot were previously installed.
I have seen other people mention the OEM unlocking option becoming available on their carrier version Pixel phones after inserting a not yet activated sim from another carrier. The latest mention that I saw was here in post #3
https://forum.xda-developers.com/t/manual-unlock-bootloader-for-locked-at-t-device.4374613/
Happy days. Just in time for Lineage OS 19.1
Click to expand...
Click to collapse
Same with my pixel 4 xl, i purchased on second hand market. I check the phone imei offline without other carrier sim and it was an at&t set. However, the bootloader option was not grey out. I quickly, unlock the bootloader after that and installed lineage os 18. . No luck for those whom got greyed out.
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
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.