Related
Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?
Quada said:
Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?
Click to expand...
Click to collapse
I have been poking around on google for a long time checking for Verizon bootloader unlock activity and I noticed that as well. This got me thinking, and while I haven't done a lot of digging to see if my idea if feasible here's what I got. I was thinking to leverage Spectre "https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)" somehow to leak a signature that can then be passed in an api call to unlock the bootloader. If i recall, I think I remember seeing a function in android source somewhere that took a prm specifying unlock/lock and then a signature created by the vendor to allow the unlock. if you could figure out the appropriate offsets in memory, maybe it would be possible? As said, I have not done much research on this but just figured I'd share and see what others thought.
Pixel 2 Verizon unlock bootloader instructions are here below
Unlocking the Bootloader WILL WIPE YOUR DEVICE!! so backup important files.
Install ADB/Fastboot Drivers
Enable Developer Options
Enable USB Debugging in Developer Options
Plug Pixel 2 into PC
Open a Command Prompt window;
In Command Prompt, type adb start-server
and hit ENTER
If you see * daemon started successfully *
continue to next step
In Command Prompt, type adb devices
and hit ENTER
If you see "List of devices attached" as well as "Your Devices Serial Number device or unauthorized"
continue to next step
On Pixel 2 - Allow PC for USB Debugging
In Command Prompt, type adb reboot bootloader
Once your Pixel 2 has rebooted into the bootloader
In Command Prompt, type fastboot flashing lock_critical
and hit ENTER Then follow the instructions on your Pixel 2 to finish Unlocking Bootloader.
Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pix...el-2s-t3726294
***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016, you will no longer be able to run the command. And downgrade is not available at this time.
As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method. Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) The command is not available on 8.0.
There is also another alternative way which has worked for me this week on Pixel 32GGB Verizon. Its called depixel8. more info can be found @ http://theroot.ninja/depixel8.html
Usage:
Step 1) Install fastboot and adb on your PC, ensure both are working with your Pixel.
Step 2) Run "adb push dePixel8 /data/local/tmp", "adb shell chmod 755 /data/local/tmp/dePixel8" and finally run the program "adb shell /data/local/tmp/dePixel8"
(put the depixel files in the same folder as your ADB/FASTBOOT drivers are where you do your command prompt commands)
Step 3) Wait for the phone to reboot to the bootloader. If it is not rebooting you can try to run various apps until it does, or you may have to reboot and start over.
Step 4) Issue the command "fastboot oem unlock", this will open up the unlock prompt and warning on the screen. You can now unlock. If you get an error, about unlocking not being allowed, start all over again.
MpandAUS said:
Pixel 2 Verizon unlock bootloader instructions are here below
Click to expand...
Click to collapse
dePixel8 is patched in Android 7.1.1 and newer.
lock bootlooader without power button
How can i relock my bootloader without use of my power button its broken
Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
Are you rooted?
Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe
KittyRgnarok said:
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe
Click to expand...
Click to collapse
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.
Keetoowah said:
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.
Click to expand...
Click to collapse
How much was the replacement button and installation by the way, I'm rather curious
getting back on track, it looks like someone claims to be able to OEM unlock after getting the April OTA? Can anyone support or contradict this claim? https://www.reddit.com/r/GooglePixel/comments/89rnoa/google_pixel_verizon_oem_unlock/
I have a samsung on7, SM-G600FY
I installed TWRP on it and rooted it. It worked perfectly fine, with no issues whatsoever.
However, i later disabled the OEM unlock option in developer options and a week(ish) later i switched off my phone. On trying to turn it on, i get a screen with an exclamation with the following on the top of the screen:
[WHITE] CUSTOM BINARY BLOCKED BY FRP.
[RED] SECURE FAIL : KERNEL
I think this is due to oem being locked, which is not allowing the OS to load, maybe?
Is there any way to enable it via CMD on the computer? Thanks
JimbakBoomA said:
I have a samsung on7, SM-G600FY
I installed TWRP on it and rooted it. It worked perfectly fine, with no issues whatsoever.
However, i later disabled the OEM unlock option in developer options and a week(ish) later i switched off my phone. On trying to turn it on, i get a screen with an exclamation with the following on the top of the screen:
[WHITE] CUSTOM BINARY BLOCKED BY FRP.
[RED] SECURE FAIL : KERNEL
I think this is due to oem being locked, which is not allowing the OS to load, maybe?
Is there any way to enable it via CMD on the computer? Thanks
Click to expand...
Click to collapse
i looked it further and due to the oem lock, it seems to be more hardware related than software? How can i flash/program the processor..?
Im 99% sure you need to download the firmware from sammobile and flash it with odin i don't think there are any other options other than that,
Maybe someone else could "chip in" to clarify it ?
Once you get your phone up and running again it's worth mentioning that when rooting you have to have "allow the device to be OEM unlocked" to the switched on position or you will just trip the FRP again
Hi7m3up said:
Im 99% sure you need to download the firmware from sammobile and flash it with odin i don't think there are any other options other than that,
Maybe someone else could "chip in" to clarify it ?
Once you get your phone up and running again it's worth mentioning that when rooting you have to have "allow the device to be OEM unlocked" to the switched on position or you will just trip the FRP again
Click to expand...
Click to collapse
well, i tried using odin to try and reflash the twrp again, but it failed and i got a tiny message on the phone screen that frp blocked it.
I don't believe that i will be able to flash the custom rom either, if my phone isn't allowing it...?
By the way, is it possible for you to share the link? I would like to give that a try too. Thanks!
JimbakBoomA said:
well, i tried using odin to try and reflash the twrp again, but it failed and i got a tiny message on the phone screen that frp blocked it.
I don't believe that i will be able to flash the custom rom either, if my phone isn't allowing it...?
By the way, is it possible for you to share the link? I would like to give that a try too. Thanks!
Click to expand...
Click to collapse
Go to https://www.sammobile.com download the correct firmware for your phone (important that it is the right firmware for your model) If your phone is unlocked to any network then it doesnt matter which country he firmware is from if your phone is locked to a specific carrier then you will need to make sure that the firmware you download is for your country and your carrier . You will need to register with sammobile but it's free download your firmware and flash using the most up to date odin you can get ,,you can find plenty of tutorials on how to do this using your search engine ..Dont worry if you dont manage the first go you can always try again. if you do all that right then your phone will boot normally after that . Be patient it can take 10-15 mins sometimes to flash then the first boot of your phone can take a while too..
Make sure usb debugging is on and most importantly that this time keep enable oem unlock at the switched on position (allow the device to be oem unlocked) or you will only trip the FRP and have to flash firrmware again
Your firmware package is around 2 gig so it will take a while to download and flash
make sure usb debugging is on also
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true
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?
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