Related
Hi everyone. I just won a Google Pixel. The contest was on a tech site and prize was provided by verizon. The phone package doesn't show verizon on it at all. Is there a way to tell if it is verzion locked? Also what does it mean if it is? Will I not get the updates when they go out? I am currently with T-Mobile and my phone before is a Nexus 6P. I haven't rooted or flashed a phone in years. Doesn't mean I'm not willing. Just thought I'd post and see if I could get some advice on what to do next with my Google Pixel. Any help is greatly appreciated. Thanks!
When you get the phone, reboot it to bootloader mode and use fastboot from your pc (obviously connect phone to computer first) and run the command: fastboot oem unlock
If it unlocks then you're money. If not, it's prolly Verizon and if that's the case try to figure out what software is on the phone (pray that it's an old phone somehow) before they fixed the bootloader workaround.
uodii said:
When you get the phone, reboot it to bootloader mode and use fastboot from your pc (obviously connect phone to computer first) and run the command: fastboot oem unlock
If it unlocks then you're money. If not, it's prolly Verizon and if that's the case try to figure out what software is on the phone (pray that it's an old phone somehow) before they fixed the bootloader workaround.
Click to expand...
Click to collapse
It won't unlock that way no matter what version if he doesn't hit the slider first.
OP:
You will get updates from google if it does not have a Verizon sim in it. If it does they come from Verizon. The Verizon version of the software has some tweeks for their network, nothing more.
To find out if it is unlockable hit the developer options and find 'oem unlock' if you can slide it to allow oem unlock it is a Google version. That will not unlock it, that will allow you to then do what the poster above said...and that will unlock it.
You must have an internet connection to use the slider. That can be just with wifi if you want. It phones home to see if it is allowed to unlock. And that is the only difference between a VZ version and a Google version. It is in the data base to be unlockable or not.
TonikJDK said:
It won't unlock that way no matter what version if he doesn't hit the slider first.
OP:
You will get updates from google if it does not have a Verizon sim in it. If it does they come from Verizon. The Verizon version of the software has some tweeks for their network, nothing more.
To find out if it is unlockable hit the developer options and find 'oem unlock' if you can slide it to allow oem unlock it is a Google version. That will not unlock it, that will allow you to then do what the poster above said...and that will unlock it.
You must have an internet connection to use the slider. That can be just with wifi if you want. It phones home to see if it is allowed to unlock. And that is the only difference between a VZ version and a Google version. It is in the data base to be unlockable or not.
Click to expand...
Click to collapse
I forgot about that in the developer settings. It's been a while since I did that. Good catch.
Thanks. Unfortunately the oem unlocking option isn't available. So I should be able to just pop my T-mobile Sim in and have no issues?
GeekyWilliam said:
Thanks. Unfortunately the oem unlocking option isn't available. So I should be able to just pop my T-mobile Sim in and have no issues?
Click to expand...
Click to collapse
Yep, you will be all set. And updates will come from google.
About phone...what version of N is it on? Dont let it update until you answer that. If it is lower than 7.1.1 you can unlock it still.
http://theroot.ninja/depixel8.html
It is 7.1. Thanks again!
GeekyWilliam said:
It is 7.1. Thanks again!
Click to expand...
Click to collapse
Hit it now. You don't have to full unlock but depixel8 it and get the slider done before it updates.
Ok. I'll do it now. Once I depixel8 then I can get the updates?
GeekyWilliam said:
Ok. I'll do it now. Once I depixel8 then I can get the updates?
Click to expand...
Click to collapse
Yea, you can finish the unlock later after it updates. But be aware the next step in unlocking will wipe your phone. So you may want to get it over with.
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
cyborgium said:
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
Click to expand...
Click to collapse
You should be fine. If you go into download mode and see RMM State Prenormal then you've been locked out from flashing anything.
xxxrichievxxx said:
You should be fine. If you go into download mode and see RMM State Prenormal then you've been locked out from flashing anything.
Click to expand...
Click to collapse
Yeah I didn't see anything like that in download mode so I just went F it and I managed to flash TWRP and magisk. Just to be sure though, I did flash the RMM state fix.
I still don't quite get why my OEM was unlocked when all the other people's got theirs locked. Any ideas?
cyborgium said:
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
Click to expand...
Click to collapse
what Oreo firmware did you put
After 212 Hours..... and nothing happened, OEM unlock don't appear in developer option :crying:
WalterSilverio said:
After 212 Hours..... and nothing happened, OEM unlock don't appear in developer option :crying:
Click to expand...
Click to collapse
It doesn't appear you are in developer options but, rather, About Phone, Status.
I know I'm not in the developer option, the screenshot is so you can see that it's already 7 days (168 hours) and even in the developer option it does not show me the oem unlock option
I show you
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
- Hit settings
- about phone
- software information
- build number 5 times
- profit
I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.
RedHatter271 said:
I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.
Click to expand...
Click to collapse
Have you tried through fastboot? (fastboot oem unlock)
Oh, got you. Sorry!
As far as I'm aware samsung devices don't support fastboot. I did attempt to connect it in case I was wrong but was not able to get fastboot to recognize the device.
RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.
darkidz555 said:
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.
Click to expand...
Click to collapse
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
Did your Developer Options come already unlocked after setting it up?
twistedumbrella said:
Did your Developer Options come already unlocked after setting it up?
Click to expand...
Click to collapse
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9
luigi90210 said:
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9
Click to expand...
Click to collapse
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.
twistedumbrella said:
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.
Click to expand...
Click to collapse
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking
luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking
Click to expand...
Click to collapse
They support it.
RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
If you can boot into download mode there is an instruction just press vol up button and it will prompt do you want to unlock bootloader mine is like that. Im not sure yours since mine is korea version.
luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader .
Click to expand...
Click to collapse
They support bootloader unlock. samsung dont support using fastboot unlock or command at all
if you're in North America, Canada etc Qualcomm chips there do not support bootloader unlocking, at least the Samsung one's don't, not sure about other OEMs.
darkidz555 said:
They support bootloader unlock. samsung dont support using fastboot unlock or command at all
Click to expand...
Click to collapse
They used to, so there was always a possibility it returned.
I recently read this article on XDA about unlocking the boot loader on the Fold 3 which results in Samsung disabling the camera (WTH?), Is this a thing on the Flip3 too?
My device is rooted. I have always been able to find the OEM unlock option under developer options without any constraints.
My camera is NOT affected. I can still use it without any issues.
I have an European device (SM-F711B).
Hope this helps some of you to track down whether this is a location or carrier based problem.
Hey Redhatter,
Out of topic question, but are you getting Tmobile 5G just fine?
RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse
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 Bootloaderbookmark_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 bootloaderTo 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 bootloaderTo 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 propertiesThe 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?
Greetings,
I'm really frustrated trying different methods online to show the hidden "OEM unlock" in developers menu, but without avail. Anyone can help to root this mobile?
VERSION:
AP: A136WVLU1AUK9
CP: A136WVLU1AUK9
CSC: A136WOYV1AUK9
MODEL: SM-A136W
Android Version: 11
Regards,
Hope this helps
droidkill3r said:
Hope this helps
Click to expand...
Click to collapse
Thank you for sharing, I’ll give it a try
To root a phone's Android unlocking its bootloader is NOT required.
You simply have to add SU binary to Android's filesystem and make this binary executable.
I want to oem unlock bootloader for trwp and roms but I can't find oem unlock in dev settings and tried the video above and a couple of other things I found
You need the Samsung flash tool and the version of android for the phone and su +twep+magisk is optional good luck
Ps. Allways back up everything!
lashark06 said:
You need the Samsung flash tool and the version of android for the phone and su +twep+magisk is optional good luck
Ps. Allways back up everything!
Click to expand...
Click to collapse
And I'm fixing the Samsung flash tool is PC only correct? My **** got stolen like a few weeks ago so I'm trying to figure out how to do this **** without a computer and it's a pain in the ass pretty much impossible.
I am having this issue and can't find a resolution for it anywhere.
Boost Galaxy a13 5g android 12:
No OEM unlock switch available...
The trick changing the date doesn't work at all...
I am not trying to flash custom ROM, just to tweak the system kernal settings.
I seen someone mentioned to root w/o the OEM unlocking switch available, all that is needed is to flash the SU binary with Odin.. I haven't tried this yet but I am almost positive Odin for windows doesn't even read the Samsung devices without the bootloader being unlocked.
Anyone care to chime in here? i'd be very appreciative!
Mainly WTF is the OEM unlock switch not available on my device. I actually have 2 of the same devices and both are without the switch.
Also would flashing SU work and do the trick?
Any other useful information you could send my way would be really helpful too.
Maybe who's find how to unlock bootloader on this device after July update?
When u chage time back to 3 years OEM Unlock is comeback
nagante0 said:
When u chage time back to 3 years OEM Unlock is comeback
Click to expand...
Click to collapse
Tell how to do this
I just got the galaxy a13 and have tried to unlock the bootloader without success. Has anyone figured this out or am I looking in the correct forum?
nagante0 said:
When u chage time back to 3 years OEM Unlock is comeback
Click to expand...
Click to collapse
Tried this multiple tines without success. Can you explain ?
hello guys. i have an mkopa samsung galaxy a13, -current binary Samsung official -KG state Active (01) -OEM lock On(L) -Eng mode Factory bin allowed (DASEUL) -Eng mode Atcmd allowed(DASEUL).............is it possible to flash its software....?????????? bootloader also locked
xXx yYy said:
To root a phone's Android unlocking its bootloader is NOT required.
You simply have to add SU binary to Android's filesystem and make this binary executable.
Click to expand...
Click to collapse
how do i achieve this
DerekLindvall said:
I am having this issue and can't find a resolution for it anywhere.
Boost Galaxy a13 5g android 12:
No OEM unlock switch available...
The trick changing the date doesn't work at all...
I am not trying to flash custom ROM, just to tweak the system kernal settings.
I seen someone mentioned to root w/o the OEM unlocking switch available, all that is needed is to flash the SU binary with Odin.. I haven't tried this yet but I am almost positive Odin for windows doesn't even read the Samsung devices without the bootloader being unlocked.
Anyone care to chime in here? i'd be very appreciative!
Mainly WTF is the OEM unlock switch not available on my device. I actually have 2 of the same devices and both are without the switch.
Also would flashing SU work and do the trick?
Any other useful information you could send my way would be really helpful Odin is sams factory setup utility
Click to expand...
Click to collapse
Odin is sam's factory utility for setup and repair. It will flash any sams device with it's OEM firmwear AFASIK
DerekLindvall said:
I am having this issue and can't find a resolution for it anywhere.
Boost Galaxy a13 5g android 12:
No OEM unlock switch available...
The trick changing the date doesn't work at all...
I am not trying to flash custom ROM, just to tweak the system kernal settings.
I seen someone mentioned to root w/o the OEM unlocking switch available, all that is needed is to flash the SU binary with Odin.. I haven't tried this yet but I am almost positive Odin for windows doesn't even read the Samsung devices without the bootloader being unlocked.
Anyone care to chime in here? i'd be very appreciative!
Mainly WTF is the OEM unlock switch not available on my device. I actually have 2 of the same devices and both are without the switch.
Also would flashing SU work and do the trick?
Any other useful information you could send my way would be really helpful too.
Click to expand...
Click to collapse
United States versions of samsung phones never have the oem unlock option. even if it is unlocked.
TheWorldYT said:
United States versions of samsung phones never have the oem unlock option. even if it is unlocked.
Click to expand...
Click to collapse
only models outside the united states have the oem unlock option.
TheWorldYT said:
only models outside the united states have the oem unlock option.
Click to expand...
Click to collapse
Is there any way to root the A136U 5g without unlocking the bootloader. I'm currently running on Android 13.. I want to delete or debloat the ATT & Samsung app installed at that takes up 8G of storage