Database Info

Anyone know of a working root?

Just got a Nokia 3.1 to use a testing tool and other fun stuff, and therefore would like to root it. Does anyone of you know of a working root of the 3.1?

So this phone is a no go for root and custom roms I guess.

kaslopis said:
So this phone is a no go for root and custom roms I guess.
Click to expand...
Click to collapse
Why do you think so? Bootloader can be unlocked via Developer settings, and I think there is no special magic preventing this device from rooting.
I would try rooting it by flashing some SuperSU zips or something like that, but I didn't try it yet

Has anyone checked this out? I haven't purchased a Nokia 3.1 but am considering it. I went so far as to create a Nokia account and there is a bootloader unlock apk, as well as an unlock.key that can be downloaded, and there are clear instructions on the Nokia page itself.. Since I don't have the phone, I did not attempt to proceed. However, if the 3.1 qualifies (I don't see why it wouldn't) then getting root should be as easy as following Magisk instructions.
There is even a page for the open source releases.
If I were to get the 3.1, my main objective would likely be to just obtain root. Looks like it should be doable.
Edit - well over 100 views since I posted this but no one has tried to unlock and/or root. I thought that was the purpose of this thread.

Unfortunately that app always crashes

VidarPT said:
Unfortunately that app always crashes
Click to expand...
Click to collapse
That is unfortunate! Perhaps, does activating Developer Options allow to select OEM Unlocking and USB Debuging, then running the Unlocking App? To run step 5 of 5 (see NOKIA INSTRUCTIONS below) you would need to have USB Debugging enabled anyway. Nowhere in the instructions is that mentioned.
FYI - Activate Developer Options: Go to Settings>About Phone and tap Build Number 7 times. Back out to access Developer Options.
Also, I do not have this phone but am interested in it. I cannot confirm if any of the advice I am giving will work, but it is what I would try.
NOKIA INSTRUCTIONS
Introduction
Firstly, we need to validate that the phone you would like to unlock is operated by you. There are a few steps to this, so we ask that you carefully follow all instructions. Let’s get started.
To participate, simply complete the following steps:
1. Please download the Nokia Bootloader Unlocker app. You can download the apk from this link and install the apk on your device. If you don’t understand how to install an apk on your device, please do not unlock the bootloader on your device. Doing so will void your phone's warranty and may cause irreparable damage.
2. Launch the Nokia Bootloader Unlocker app and fill your email information and click “Submit”.
3. The app will display a code. Please enter this in the form below along with your email address. Then press "Request to Unlock"
Your bootloader can now be unlocked. Follow the instructions below:
Step 1/5
Check the email you entered during registration. You should receive an email with a message as follows:
Hi, Thanks for requesting the unlocking bootloader. Please download your unlock key from the following link. xxxxxxxxxxxxxxxxxxxxxxxxxx
Download the unlock key and save it as “unlock.key”.
Step 2/5
Power off your device. Once powered off, press and hold the Volume Down button.
Step 3/5
While keeping the Volume Down button pressed, connect the device to the computer via USB cable. The device will boot into “Download mode”. If you have difficulty, try powering up normally, power off the device again and start back from Step 1.
Step 4/5
Download the following fastboot binary for your OS here.
Step 5/5
Open a command prompt:
Windows: Start > cmd
Mac: Applications > Utilities > Terminal.app
Linux: Terminal
Navigate to the directory where the previously downloaded unlock.key file is saved. Then enter the following commands:
fastboot flash unlock unlock.key
fastboot oem unlock
If successful, you should see the below message:
Unlock success!
Then reboot the device by entering the following command:
fastboot reboot
You are done!

It doesn't work either way. I tried with both those options enabled and disabled but the program always crashes. It's interesting to note that the app itself fails to install through chrome or "Files" app. Gives an error saying "Can't open app". I only managed to install it through ES File Explorer. Could it be because of I bought the phone on a Vodafone store? I can't find the original stock rom to flash, sadly.

VidarPT said:
It doesn't work either way. I tried with both those options enabled and disabled but the program always crashes. It's interesting to note that the app itself fails to install through chrome or "Files" app. Gives an error saying "Can't open app". I only managed to install it through ES File Explorer. Could it be because of I bought the phone on a Vodafone store? I can't find the original stock rom to flash, sadly.
Click to expand...
Click to collapse
I have been researching this and have found that, as of this writing, only the Nokia 8 qualifies for bootloader unlocking. See here. The only thing holding me back from jumping on this Nokia 3.1 is the inability to unlock the bootloader (and maybe the lack of fingerprint sensor.) Hopefully it gets "approved soon".

Currently the oem unlock using the Nokia bootloader unlock only works for Nokia 8

is there a way to root the 3.1 yet successfully? im a noob at this stuff and don't want to screw my phone.

snarfydog said:
is there a way to root the 3.1 yet successfully? im a noob at this stuff and don't want to screw my phone.
Click to expand...
Click to collapse
No, not until Nokia decides to allow users to unlock bootloader.

What about the 3.1 plus. I've already unlocked OEM. I just started looking, thought I'd start here first.

XSHADOW3 said:
What about the 3.1 plus. I've already unlocked OEM. I just started looking, thought I'd start here first.
Click to expand...
Click to collapse
It doesn't matter if you have enabled "OEM unlocking" option in Developer settings, currently Nokia doesn't allow unlocking of bootloader and thus rooting device, unless you are Nokia 8 user. You can try this, but it will crash almost for sure.

As far as I can tell, my bootloader is unlocked. I am a noob of course, but I have been researching this topic for a couple of months now. I could be mistaken in thinking "upload" mode is it, but I can't seem to figure out the difference. Otherwise, I don't know what to do next.

Nightseer said:
As far as I can tell, my bootloader is unlocked. I am a noob of course, but I have been researching this topic for a couple of months now. I could be mistaken in thinking "upload" mode is it, but I can't seem to figure out the difference. Otherwise, I don't know what to do next.
Click to expand...
Click to collapse
Can you please tell what did you do exactly?

MilesSeventh said:
Can you please tell what did you do exactly?
Click to expand...
Click to collapse
To get to "Upload" mode? Assuming it's the same for the 3.1 Plus-maybe I should have specified that-holding power button and volume up during startup will open "Upload" mode.
You can also use adb with the command "reboot bootloader." For that reason, I think it's the bootloader, but I could be wrong.
Sorry if I was a bit misleading and it is totally different on the Nokia 3.1, I was just some kinda hopeful to actually see people talk about it.

Let's get her done
Nightseer said:
To get to "Upload" mode? Assuming it's the same for the 3.1 Plus-maybe I should have specified that-holding power button and volume up during startup will open "Upload" mode.
You can also use adb with the command "reboot bootloader." For that reason, I think it's the bootloader, but I could be wrong.
Sorry if I was a bit misleading and it is totally different on the Nokia 3.1, I was just some kinda hopeful to actually see people talk about it.
Click to expand...
Click to collapse
I'm not bringing any sizable programming skills to the table unless somebody wants to teach me real fast.
Hopefully, I bring tidings of great joy. So I got two these Nokia's and they're both locked. to the carrier, Cricket. I suspect they are at least unlawfully locked. . My understanding is you can't lock to used phone especially if it's been sold as a prepaid phone. I believe this falls under the reseller flex policy. I bought it off of eBay from a guy that sells nothing but phones and he's been extremely cagey about what he'll admit to, so I called the carrier. I literally waited an hour and a half on the phone because I am falling asleep and I was on a computer speaker phone so it kept on the time of the call. I only held that long because I had fallen asleep. Anyway since I'm not in a cricket or AT&T customer then don't plan to eitherbe they could care less about me it actually told me they didn't have any information on the phone after I gave them the IMEI number.
My guess is the fcc's not going to do much because it's a trump Administration. So I spent about 45 minutes on the phone with Nokia and well at least they're interesting I think Microsoft paid between 7 and 12 billion to acquire them I recently sold them off for like a box of jujyfruits. Anyway they're committed to customer service so I figure my predicament might give me an in there.
So those unlock codes that it was a link earlier in the post for that's just to unlock the bootloader, right? You know this is a pretty decent phone for a low-end guy I got the newer 3.1 C it's got Cricket's bootloader in bloatware on it,
takes up a ton of space.
I mean it probably won't happen but if Nokia ever goes public again - I think the acquiring companies. Their eye on the prize and they're going to kick some ass. So I'm all in on this let's get this done. If you want I can see what I can do about asking Nokia 4 whatever it's going to take just to keep me a satisfied customer since they know Cricket/ATT isn't following the Obama regs.

Oof... It would be beautiful if Nokia customer support could guide us onto rooting this phone.

its so simple to unlock oem on nokia 3.1 plus. no third app needed. after developer option on -> go to developer option setting -> there is toggle button to on/off developer option , just use that toggle to off it and on it -> press yes for on dev options -> and select oem unlock. that all

It is pretty straightforward once you have unlocked bootloader (not by Nokia). If you want, you can simply dump boot_a or boot_b with SPflash tool, patch in Magisk app, and reflash.
Otherwise you can use my TWRP (NO TOUCH, and has disabled dm-verity). Please note it's only working on build v3.180, updates not supported - as it was only needed for my project.
https://forum.xda-developers.com/no...m-kali-nethunter-nokia-3-1-android-9-t4157681

Google repair shop re-locked my bootloader... wtf now?

OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.

If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.

Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?

Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.

Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N

n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.

Smartisan Nut Pro 2 problems unlocking boot loader

Tutorial here say to unlock oem in devleoper options to unlock the boot loader.
Smartisan Nut Pro 2 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Smartisan with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
I have clicked on everything under developer options but there is nothing label oem unlocking to unlock the bootloader. Someone has experience with this phone? I can press the power and the down volumer to get boot options but when i select rebbot to bootloader it just reboots! I feel so dumb. How can this be this nutso? Who has a good idea? I have chased down many links on web searches only to run into dead ends with links that are 404 files which were taken down and even the framaroot or whatever it's called here is of no utility for this phone. please help. i just want to install android 10.

This Chinese phablet is running Android 7.1.
If in Android's settings -> Developer options the option OEM Unlock isn't offered, then don't waste your time with trying to unlock this phablet's bootloader.

Yah that's what i was afraid of. I bought the phone after seeing there were custom roms available for it but after i looked into deeper since buying the phone, i see now that the links are dead to the files to be used for the programs to unlock it and people's accounts were closed by mega for gross violation of terms of service and such. Darn shame that. For a 4 year old phone it still has great specs and would have run a more stock android 10 very well. I mean i do have google play store installed i searched the chineese store for the GMS app with that on the icon so i have facebook and whatnot that i would use. Just that so many things are in mandarin there so i cant read them to know any apps from that place i might want to use. I'm a stupid american, functionally illiterate in english for pitty's sake, i cant be expected to read mandarin. PLus some apps, like walmart don't play nice on this phone. Overall for 85$ that i paid for it, it's not horrible. Android 7 clone is alright. Had i known i couldnt put a custom rom on it i would have spent my money someplace else. I'm pretty sure the person who sold it to me knew all this and was looking to dump it on any sucker they could find. It's still a better phone than the other one i am currently using. I guess it's too much to hope they will put out a new stock rom update for it anytime at all?

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?

[Help] Bricked phone stuck in bootloop

I have an old Asus Zenfone 4 that randomly got stuck in a boot loop while it was recharging, and now I don't know how to fix it, or even if it is possible to fix. The only thing that still works is fastboot mode (recovery mode doesn't work either, so SD cards are out of question).
I have tried a number of things to factory reset the phone and see if it changes anything, but it seems impossible to unlock its partitions for flashing: commands such as fastboot flashing unlock, fastboot oem asus-go or anything similar just throw errors saying that the command doesn't exist, or if it does, that I don't have permission to run them. For this same reason, I couldn't use things such as TWRP as I can't flash any of the partitions on my phone. Additionally, I have tried to enable adb through fastboot oem, but even though the command is successful, whenever I get the system info, it says that adb debugging is still off.
Does anyone know a way to either unlock this device or factory reset it without unlocking?

Another old-ish device killed by the silent OTA update of the OEM!
The deadly mistake of connecting an old-ish device to OEM servers for fresh install.

Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.

OldNoobOne said:
Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.
Click to expand...
Click to collapse
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.

rafk12 said:
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.
Click to expand...
Click to collapse
I threw away two old chaina phones just because I made the mistake of reflashing the original OS and tried to update from OEM servers..BOOM! Dead Phone!
The moment OEM servers detect an old device connected to their servers for an update, they kill the device so that new devices can be sold in the market, why would this happen to a device which was working perfectly under a Custom ROM before? I dont update the device from OEM channelsbecause OEM might try to kill the device after warranty period, instead I update through the Custom ROM channel.

Maybe some chip got fried while charging the device, among the asian brands shamshung & WonPlus have durable components but other asian brands maximum 4 years before the components like display etc. or even the chipset components begin to fail. Or it could be the OEM update thing too