Database Info

Did I just unlock the bootloader on the S7 Snapdragon?

I don't know if it's for real. And I don't know if I did it today or a few days ago. Nonetheless, according to developer options, I unlocked the bootloader on my Snapdragon S7. So I need some assistance to determine if this is the case. I have no idea how to tell if I did unlock it and I've no idea where to go or what to do from here.

Yes. You can install twrp now from Snapdragon development section

I ended up breaking the screen so i need to get it replaced. Here are the steps I took before i broke it:
1. Make sure OEM unlock is toggled on
1. Oreo, eng rooted, I Changed in build.prop, build type to userdebug.
2. Added 3 lines in build prop:
Code:
ro.oem_unlock_supported=1
sys.oem_unlock_allowed=1
ro.boot.flash.locked=0
3. Factory reset through recovery.
If that works i have a theory as to why. With an engineering kernel, it probably already allowed it, we just didn't know. These are legitimate build prop codes and are referenced the android source code. This has potential to work on other devices where you have the ability, without root, the manipulate the sys values and add some through adb shell using 'setprop'. I was able to add sys.oem_unlock_allow to a friends Alcatel.

That toggle has always been available to SD users, it's just never actually done anything. It's a switch not connected to anything.

Beanvee7 said:
That toggle has always been available to SD users, it's just never actually done anything. It's a switch not connected to anything.
Click to expand...
Click to collapse
Yes i know it's always been there. But The toggle never said the bootloader was already unlocked.

I'd be very surprised if you were the first person ever to unlock a SD device, and that of all methods it was accidental.
I find it more believable you accidentally toggled this in the past and forgot.
You could always try the files from the Chinese variant, but prepare for bootloops.

Beanvee7 said:
I'd be very surprised if you were the first person ever to unlock a SD device, and that of all methods it was accidental.
I find it more believable you accidentally toggled this in the past and forgot.
You could always try the files from the Chinese variant, but prepare for bootloops.
Click to expand...
Click to collapse
I wouldn't be that surprised. I always suspected it was stuck in limbo waiting for something to give it the ok to unlock, especially geven it being persistent. If the toggle was truly inoperable, it wouldn't do anything and a box wouldn't pop up. Given the engineering kernel, this unlocking seems very possible. From Android:
"The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock. ro.oem_unlock_supported should be set to "0" if flashing unlock is not supported on the device or "1" if flashing unlock is supported.
If the device supports flashing unlock (i.e. ro.oem_unlock_supported = 1), then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked (or the /firmware/android/flash.locked DT property) to "1" if locked or "0" if unlocked."
Click to expand...
Click to collapse
https://source.android.com/devices/bootloader/unlock-trusty

so, have you tried to flash twrp via odin yet? which device do you have?
Im on oreo too and mine says "Allow the phone to be OEM unlocked" my device is a 935V

Maxissc said:
so, have you tried to flash twrp via odin yet? which device do you have?
Im on oreo too and mine says "Allow the phone to be OEM unlocked" my device is a 935V
Click to expand...
Click to collapse
Not until i can get the screen fixed unfortunately. Just my luck. G930T to a G930U.

DragonFire1024 said:
I ended up breaking the screen so i need to get it replaced. Here are the steps I took before i broke it:
1. Make sure OEM unlock is toggled on
1. Oreo, eng rooted, I Changed in build.prop, build type to userdebug.
2. Added 3 lines in build prop:
Code:
ro.oem_unlock_supported=1
sys.oem_unlock_allowed=1
ro.boot.flash.locked=0
3. Factory reset through recovery.
If that works i have a theory as to why. With an engineering kernel, it probably already allowed it, we just didn't know. These are legitimate build prop codes and are referenced the android source code. This has potential to work on other devices where you have the ability, without root, the manipulate the sys values and add some through adb shell using 'setprop'. I was able to add sys.oem_unlock_allow to a friends Alcatel.
Click to expand...
Click to collapse
Im about to try your procedure. i'll update my results
edit: After applying the build.prop lines and rebooting (didn't do factory reset) my OEM unlock switch now says "Bootloader is already unlocked"
Im wondering if that is because the bootloader got really unlocked, or if it's because of any of the added lines and it's just text
edit2: tried to flash twrp via odin 3.13 3B and it fails

Maxissc said:
I ended up breaking the screen so i need to get it replaced. Here are the steps I took before i broke it:
1. Make sure OEM unlock is toggled on
1. Oreo, eng rooted, I Changed in build.prop, build type to userdebug.
2. Added 3 lines in build prop:
Im about to try your procedure. i'll update my results
edit: After applying the build.prop lines and rebooting (didn't do factory reset) my OEM unlock switch now says "Bootloader is already unlocked"
Im wondering if that is because the bootloader got really unlocked, or if it's because of any of the added lines and it's just text
edit2: tried to flash twrp via odin 3.13 3B and it fails
Click to expand...
Click to collapse
Damn. Perhaps its the version of TWRP. I guess we'll have to wonder until something else comes along.

case closed.

Maybe someone needs to build twrp for our fevice for it to work

maXDAmn said:
case closed.
Click to expand...
Click to collapse
Not really. I didn't expect nor did I think the experimental TWRP to work.

DragonFire1024 said:
Not really. I didn't expect nor did I think the experimental TWRP to work.
Click to expand...
Click to collapse
Just to confirm I tried this and got the same results I could not flash twrp with odin(none of the versions worked) So I installed the twrp img with the official twrp app and it failed to boot into twrp.

i would really like to try this, but i dont really understand the instructions^^
could someone put the instructions down once again?

tko said:
i would really like to try this, but i dont really understand the instructions^^
could someone put the instructions down once again?
Click to expand...
Click to collapse
Make sure OEM unlock enabled in settings.
Add to build.prop:
ro.oem_unlock_supported=1
sys.oem_unlock_allowed=1
Factory reset
You also could try adding this to build.prop:
ro.boot.verifiedbootstate=0
Like any mods, be prepared for the potential to brick. Im not responsible for anything that breaks.

Good news fellas! TWRP files for snapdragon devices is avaiable here TWRP files for Snapdragon so if anyone knows how to compile this we good.

Well, I'm erring on the side of "There's no way it was THIS simple all along" and assuming it means nothing, but still...it's interesting, I'll give it that.
FWIW, I can't seem to replicate the "Bootloader Is Already Unlocked" message for some reason. I've got SM-G935R4 (US Cellular S7 Edge, though these are sold unlocked straight out of the box so the carrier is more like a technicality...) and I'm still running Nougat. What I get is a greyed-out box, switched to "On" and not adjustable, with the normal "Allow the device to be OEM unlocked" text still present (but also greyed out). I also didn't factory reset, just a few reboots.
I added all four lines suggested here (the original three, plus "ro.boot.verifiedbootstate=0") and found that A). the ro.boot.verifiedbootstate one doesn't have any discernible effects from a purely visual standpoint, and B). If I remove/comment-out the "ro.boot.flash.lock" line, the ability to switch OEM Unlock On/Off returns and the setting isn't greyed out.
Does any of that matter or mean anything? Hell if I know, I'm just chiming in.

lugnut2099 said:
Well, I'm erring on the side of "There's no way it was THIS simple all along" and assuming it means nothing, but still...it's interesting, I'll give it that.
FWIW, I can't seem to replicate the "Bootloader Is Already Unlocked" message for some reason. I've got SM-G935R4 (US Cellular S7 Edge, though these are sold unlocked straight out of the box so the carrier is more like a technicality...) and I'm still running Nougat. What I get is a greyed-out box, switched to "On" and not adjustable, with the normal "Allow the device to be OEM unlocked" text still present (but also greyed out). I also didn't factory reset, just a few reboots.
I added all four lines suggested here (the original three, plus "ro.boot.verifiedbootstate=0") and found that A). the ro.boot.verifiedbootstate one doesn't have any discernible effects from a purely visual standpoint, and B). If I remove/comment-out the "ro.boot.flash.lock" line, the ability to switch OEM Unlock On/Off returns and the setting isn't greyed out.
Does any of that matter or mean anything? Hell if I know, I'm just chiming in.
Click to expand...
Click to collapse
No idea. This does tell us a bit though. OEM toggle isn't disabled. Has anyone who tried this do a factory reset?

Unable to unlock bootloader on non-carrier Pixel 2

With the Pixel 3 out, I decided to purchase a Pixel 2. I found one on ebay described as recently new but lightly used, bought from Google, and decided to take the risk. Received it today. The hardware appears to be in great condition, although I don't know if it's an original or RMA. I cannot unlock the bootloader with fastboot.
The phone came with the October 2018 build PPR2.181005.003. Whenever I factory reset the phone, I can enable Developer Options and on the first boot, "OEM unlocking" is an available option, and is set to enabled. When I reboot to the bootloader, 'fastboot flashing unlock' always returns 'Flashing Unlock is not allowed'. I have also tried unlock_critical. I've tried a few combinations of Factory Reset, providing internet access with WiFi, or adding my Google account, or both. I've tried disabling the OEM unlocking option right after the first start up and re-enabling it. So far, every permutation I've tried fails. I've also tried is 're locking' the bootloader, which fails because it's already locked, and changing the boot slot (it's on b), which also fails because it is currently locked.
The result of 'adb shell getprop sys.oem_unlock_allowed' is 0.
The result of 'adb shell getprop ro.boot.cid' is 00000000.
The result of 'fastboot flashing get_unlock_ability' is '1', so unlock *should* work...
The phone always starts with an option for Project Fi.
Is there anything I can do? I am not the original owner of the phone but as far as I know, all Pixel 2s are still under two-year warranty. Also, I am a Verizon customer with a Verizon sim card I will eventually put into this phone, with a grandfathered Unlimited Data plan. The main reason I wanted to unlock the bootloader was to gain access to modify build.prop so I could enable WiFi tether - which may not be necessary if a straight-from-Google phone with a Verizon sim can tether anyway.

Can A515W be root?

Hi any bro out there know that A515W version can be root, please? I just had a Canadian A515W version. Thank you.

I have been looking as well, I have the koodo version of sm-a515w, i have read that people with a515w rooting their phones easily yet i cant even get the unlock boot loader option to appear, and YES i tried the turn off internet, change the time back yadda yadda, nothing has worked, i am not new to rooting phones, i have rooted every android phone i have ever had, but this one.... I suspect that maybe i could flash a firmware with odin that has a bootloader that has the unlock botloader option, but i havent found one that works. I have had my phone for a few months now, i thought someone with a lot more knowledge would have done something about this by now, but i guess there just arent enough canadian devs that have this phone for anyone to care to put time into this phone.

Yes bro, I hear you. We are in the same boat. I thought because android 10 is hard to root. And I made a mistake thinking that A51 is exynos. So it is easy to root too. Sad !!

I got the phone for the same reason, history of bootloader unlock on Exynos (I have the dual sim S9+). I even flashed the U1 software on the W variant thinking it would allow the option. I have the U1 software on all my W series Samsungs since the U1 gets updates regularly and full updates (several camera updates are not on the W series updates).
I tried the internet trick and as the other user said (but I have never gotten that to work on any Exynos), no go. I am 11 hours away from 168 straight hours with no reboot so maybe it will appear (we shall see).
Interesting turn of events (using ADB) just occurred:
adb shell getprop sys.oem_unlock_allowed (this was 0 initially)
adb shell getprop ro.oem_unlock_supported (Get OEM unlock status, 0 off/1 on) (this shows as 1)
Then I ran the following:
adb shell setprop sys.oem_unlock_allowed 1
Now, it shows:
adb shell getprop sys.oem_unlock_allowed (shows as 1)
adb shell getprop ro.oem_unlock_supported (Get OEM unlock status, 0 off/1 on) (still shows as 1)
I have not rebooted to see if the OEM unlock will then show up (I am going to wait the 11 hours or so then reboot to see what happens).
Note: the "adb shell setprop sys.oem_unlock_allowed 1" command failed on S20 Ultra 5G (CA Snapdragon with US U1 software via ODIN).
I will update if OEM unlock showed up on this Exynos 9611 (CA W series with US U1 series software via ODIN) (either because of the 168 hours and/or the adb shell setprop sys.oem_unlock_allowed 1)
I am trying to keep the software update for U1 that just came from installing before 11 hours is up (it is the January 2021 security update)
Update: after 168h12m and the procedure above, it still does not show the OEM unlock (when I rebooted, the value went back 0 but I could change to 1 again). January security update, One UI 2.5.

Bootloader is both locked and unlocked

Just to preface, I'm not a total noob when it comes to android, but I'm definitely not savvy or knowledgeable in any way either.
I purchased a Motorola p50 a while ago from a seller on Aliexpress, and when booting the phone I get a message saying that the bootloader is unlocked. Going into the developer settings shows the OEM unlock option is in the off position, greyed out and with a message saying that the bootloader is already unlocked. However, booting into fastboot and running 'fastboot oem lock' gives me an error message telling me to enable unlocking in the developer options... which I can't do, because it's greyed out. Running 'fastboot oem unlock' tells me that the bootloader is already unlocked. From what I can tell the phone is running the stock android 10 motorola ROM, and I would like to lock the bootloader so that I can use google pay, as the phone supports NFC.
According to settings, the model is "motorola one vision", the hardware version is PVT, the SKU is XT1970-5 and the software channel is 'retcn'
Any help on how I can lock the bootloader, or even just get google pay working would be greatly appreciated.

There exists many threads on xda about this issue and it all boils down to this: your Bootloader thinks you're running modified software, hence locking it will hard brick your device (at least there is a possibility). According to the above linked thread, here's what you can do to troubleshoot this (in order of what could work):
Factory reset your device from Settings. (Relocking will erase your data anyways, Backup is advised)
Flash The Stock Firmware and attempt the lock process again.
Flash Magisk and enable Magisk Hide (this one is dangerous, since a modified boot.img while relocking can hard brick your device as well, do it at your own risk!!!)
Pass Safetynet check by flashing latest Magisk canary, enabling Magisk Hide and flashing this Universal Safetynet fix.
Step 4 is what I would do if I were you, however, advising people on the internet to root in order to solve this problem is not very wise, hence it being the last step.

Alright, I might give the last one a go since I don't know what the stock firmware for the phone is supposed to be. Thanks a lot for your help

Update: after attempting to install magisk with little success, I eventually found a single russian article that solved the issues I was having with magisk. I installed that plugin you linked, and success! Google pay now works without issue. Your help is greatly appreciated

Question OEM Unlock missing on SM-A326U

Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys

7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.

Seriously... So there's no way to unlock for free, or by waiting...?

Not a bootloader unlock. Its not just Tmo that are locking these down tighter.
You can unlock it for free if you can figure out whatever they do ;-)

Nah idc about a network unlock since I don't have service for this phone, I just wanna know if its possible to unlock the bootloader... I've tried everything

Who is talking about a network unlock?

TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
You said not a "bootloader unlock" so I was assuming you're talking about network unlock... Sorry, but should I just give up, there's seemingly NO WAYY to unlock the bootloader of a T-Sh*t phone.

Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.

TimmyP said:
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
Click to expand...
Click to collapse
That's kinda sad, I think I'm gonna just give up, but thanks for the information... Hopefully something happens in the future that allows it to be unlocked soon... Thanks man

I doubt they'll bring it back. OEM unlock that is. My phone is over 7 days old and I did the factory reset by holding the volume down and power buttons and then the volume up and power button and did the full factory reset. OEM unlock is still gone. Yes I got the developer options turned on. I rooted a couple of Nexus 6p's which of course are obsolete now since they were 3G and there is no backward capability. At least I got them used, replaced the batteries myself and can use them as WiFi phones with Talkatone through my WiFi. Read some blurbs about Kingo root working but I'd like to see that someone has pulled it off with the A32. Am under a 2 year obligation but I bought a second one to experiment on. I did that before I found out there was no OEM unlock. Well, if I break one, I'll have a backup. Except the phone is tied to the SIMM and I'd have to bring the backup in to have it reprogrammed.

TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...

iabhua said:
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
Click to expand...
Click to collapse
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know

TimmyP said:
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Click to expand...
Click to collapse
Do you have any device with an unlock bootloader or unlock? I am trying to get a ram dimp for days nobody have an device.

andioshelp said:
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
Click to expand...
Click to collapse
I have two SM-A236U’s but unfortunately one has binary 6 FW and the other binary 7.

1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
There was a similar procedure to unlock bootloader on a samsung mtk (A125U) same carrier as yours (T-Mobile TMB and the same applies to MetroPCS TMB) basicaly, you had to flash BL files from the A125W (canadian version) then unlocking bootloader using testpoint (bootrom mode) then using any paid or free app (in my case i use a paid one because i run a repair shop). even if you unlock bootloader using paid tools, it gets locked again when it turns on. (i tested it without flashing BL files)
sadly, i dont have a A326U lying arround to test said procedure.

1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock

DjoFight said:
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
Click to expand...
Click to collapse
In case people need the procedures for those processes, I wrote this up recently to help others do it easier than it was for me to figure out.
How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode

Has any one made any progress regarding the missing oem unlock? I know what parameters to add to our kernel v1 to v3 during building to enable oem unlock and add access to fastbootd. Because of project treble our options have changed.
Sources:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
Sign in
DOCUMENTATION
Docs
More
Getting Started
Security
Core Topics
Compatibility
Android Devices
Reference
GO TO CODE ➚
Overview
Architecture
Overview
Hardware Abstraction Layer (HAL)
Kernel
HIDL (General)
HIDL (C++)
HIDL (Java)
Configuration
Device Tree Overlays
Vendor NDK
Vendor Interface Object
AIDL
Bootloader
Overview
Boot Reason
Boot Image Header
Implementing Bootconfig
Recovery Images
DTB Images
Supporting OTA Updates
Locking and Unlocking the Bootloader
Version Information in AVB Properties
Fastboot in Userspace
Partitions
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Virtualization
Tests
Updates
AOSP
Docs
Core Topics
Was this helpful?
Locking/Unlocking the Bootloader​bookmark_border
On this page
Unlocking the bootloader
Locking the bootloader
Setting lock/unlock properties
Protecting critical sections
By default, most Android devices ship with a locked bootloader, meaning that users can't flash the bootloader or device partitions. If needed, you (and device users with Developer options enabled) can unlock the bootloader to flash new images.
Unlocking the bootloader​To unlock the bootloader and enable partitions to be reflashed, run the fastboot flashing unlock command on the device. After setting, the unlock mode persists across reboots.
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the get_unlock_ability to 1). After setting, this mode persists across reboots and factory data resets.
When the fastboot flashing unlock command is sent, the device should prompt users to warn them that they might encounter problems with unofficial images. After the user acknowledges the warning, the device should perform a factory data reset to prevent unauthorized data access. The bootloader should reset the device even if it can't reformat it properly. Only after a reset can the persistent flag be set so that the device can be reflashed.
All RAM not already overwritten should be reset during the fastboot flashing unlock process. This measure prevents attacks that read leftover RAM contents from the previous boot. Similarly, unlocked devices should clear RAM at every boot (unless this creates an unacceptable delay), but should leave the region used for the kernel's ramoops.
Locking the bootloader​To lock the bootloader and reset the device, run the fastboot flashing lock command on the device. Devices intended for retail should be shipped in the locked state (with get_unlock_ability returning 0) to ensure that attackers can't compromise the device by installing a new system or boot image.
Setting lock/unlock properties​The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device supports flashing unlock, set ro.oem_unlock_supported to 1.
If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0.
If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or to 0 if unlocked. This variable must be set in bootconfig instead of in the kernel command line in Android 12.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.

I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?

evnStevn said:
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
Click to expand...
Click to collapse
I'm wondering too. Could you please pm me what you were trying to post?