Related
http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
This article is pretty much straight forward but i wasnt sure on it cause ive never had a phone with oem unlock in developer settings. From what it says oem unlock is required to be turned on anytime you do any kind of modification or flashing a stock tar.... so it has to be on basicially permentantly correct just to be on the safe side if your doing modifications or have modifications already on your phone?
haro25 said:
http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
This article is pretty much straight forward but i wasnt sure on it cause ive never had a phone with oem unlock in developer settings. From what it says oem unlock is required to be turned on anytime you do any kind of modification or flashing a stock tar.... so it has to be on basicially permentantly correct just to be on the safe side if your doing modifications or have modifications already on your phone?
Click to expand...
Click to collapse
Everytime I've used OEM unlock was for a device that supports fastboot to unlock the bootloader. Now, Samsung doesn't do fastboot but it seems that you must click OEM unlock to flash (thru Odin) a custom recovery such as twrp.
-sent from this device using this app.
This what someone said online cant be 100 % sure if its accurate..
Quoted text.....
Sadly it backed fires the users who accidentally got themselves boot-looped and forgot to unlock oem.
Like me... Oem locked, and all are stocks no cwm/twrp... All i can do is bring this to the service center. :/
Mistake for me, error for google.
I don't fully understand the process of unlocking a bootloader on a phone, but what makes a Samsung phone so difficult to unlock? For instance could we unlock this phone using the same method as went use on other phone with a Snapdragon 835 processor?
State.of.mind said:
I don't fully understand the process of unlocking a bootloader on a phone, but what makes a Samsung phone so difficult to unlock? For instance could we unlock this phone using the same method as went use on other phone with a Snapdragon 835 processor?
Click to expand...
Click to collapse
It's not difficult to unlock, it's impossible to unlock. The team of guys who achieved root access on an SD835 S8 used a root exploit to get root on the phone, the bootloader is still locked and they won't be able to flash anything that isn't signed by Samsung.
As for your second question, ABSOLUTELY NOT.
Each OEM has a different way of unlocking their devices bootloaders.
Sony and HTC email you an unlock code after you submit your IMEI for bootloader unlocking, only with that code you can unlock your device.
Samsung phones (on applicable devices like Exynos ones), simply have a switch in developer options for OEM Unlock, just like Google's Pixel and Nexus devices, once that option is enabled, consider the bootloader 'unlocked', and you should be able to flash whatever you want, regardless of whether it's signed by Samsung or developed by some guy in his moms basement.
TL;DR:
No.
murtaza02 said:
It's not difficult to unlock, it's impossible to unlock. The team of guys who achieved root access on an SD835 S8 used a root exploit to get root on the phone, the bootloader is still locked and they won't be able to flash anything that isn't signed by Samsung.
As for your second question, ABSOLUTELY NOT.
Each OEM has a different way of unlocking their devices bootloaders.
Sony and HTC email you an unlock code after you submit your IMEI for bootloader unlocking, only with that code you can unlock your device.
Samsung phones (on applicable devices like Exynos ones), simply have a switch in developer options for OEM Unlock, just like Google's Pixel and Nexus devices, once that option is enabled, consider the bootloader 'unlocked', and you should be able to flash whatever you want, regardless of whether it's signed by Samsung or developed by some guy in his moms basement.
TL;DR:
No.
Click to expand...
Click to collapse
If you're using a phone with an unlocked boot loader could you in theory switch between operating systems? For instance could I flash a rom to run Lollipop on one slot and on another slot run Nougat?
State.of.mind said:
If you're using a phone with an unlocked boot loader could you in theory switch between operating systems? For instance could I flash a rom to run Lollipop on one slot and on another slot run Nougat?
Click to expand...
Click to collapse
Most phones don't have 'slots'. It's not a common thing yet.
The Google Pixel and Moto Z2 are the only ones that come to mind that have A/B partitions for seamless OS updates and in theory (on a Pixel), one should be able to flash Nougat on Slot A and Android O on Slot B, however I wouldn't recommend it at all, I always like having the same sh*t on both slots.
Also, Lollipop and Nougat are too far apart and there is no device in existence that has its OEM ROM based on LP and N. So no you wouldn't be able to.
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
Hello.
I need someone that has a A125U variante that would like to test crossflashing bettween fimware to bypass U model PBL-unlock-restrictions.
More info, dm me.
EDIT: Changed to GENERAL thread because it turned in to a discussion now.
i have a A125U i can test this out if you want me to
Yes I would be willing to but you would have to walk me through the steps I know nothing of what I'm doing trying to learn
Scotterd said:
Yes I would be willing to but you would have to walk me through the steps I know nothing of what I'm doing trying to learn
Click to expand...
Click to collapse
Download patched odin and flash A125F fimware even if you are on A125U model.
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Samsung Galaxy A12 Firmware Download SM-A125F Free Download
Samsung Galaxy A12 Firmware Download SM-A125F Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Clean flashing new fimware useing Odin
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # Your warranty is now void # # You have been warned. # # I will laught at you if you point the finger at me...
forum.xda-developers.com
I'm not responsible for any damage don to your device
You can use the patched odin to flash any A12 FW with a matching binary, but it won't affect your ability to unlock the bootloader. The most likely option is to use the EDL method by pulling the back encasing from your phone and using a paperclip or pair of tweezers to short the EDL pin while plugging into your PC. EDL is kind of a secondary bootloader that will allow you to run a variety of functions. Since the A12 is a MediaTek processor, I've tried using the MTKClient exploit through EDL mode to force unlock the bootloader, but so far I haven't seemed to get it working.
R0GUEEE said:
You can use the patched odin to flash any A12 FW with a matching binary, but it won't affect your ability to unlock the bootloader. The most likely option is to use the EDL method by pulling the back encasing from your phone and using a paperclip or pair of tweezers to short the EDL pin while plugging into your PC. EDL is kind of a secondary bootloader that will allow you to run a variety of functions. Since the A12 is a MediaTek processor, I've tried using the MTKClient exploit through EDL mode to force unlock the bootloader, but so far I haven't seemed to get it working.
Click to expand...
Click to collapse
It is possible and a method will be found. It could be that the SBL requires a key for PBL to be unlocked, have you tried useing any exploits on this phone?
LAST_krypton said:
It is possible and a method will be found. It could be that the SBL requires a key for PBL to be unlocked, have you tried useing any exploits on this phone?
Click to expand...
Click to collapse
As far as everything I've tested so far...
Attempted to downgrade A11 to A10 (can't do it because of incompatible FW binaries)
Flashed several different model FWs & various other CSCs... the model I'm using is SM-A125U (AT&T). Currently the FW running on it is for SM-A125U1 (the carrier unlocked model) but of course still no "OEM Unlock" option in dev settings.
After I tried a few dozen builds I looked into EDL/BROM flashing, since EDL works as a ground zero primary boot interface and seems to work as a recovery/fastboot hybrud allowing both flashing & a CMD interface vs a separated Samsung "Download Mode" and Fastboot mode.
I haven't really spent much time scouring the web for different exploits (that aren't paid services) but I did come across "MTKClient" (https://github.com/bkerler/mtkclient), which I was able to successfully run. I tried using the "unlock bootloader" command, at which point it was a "success" and resulted in the device obviously being wiped, but after the following boot there still was no "OEM Unlock" option in the dev menu. Afterwards I tried flashing a custom boot.img built with Magisk, but even using EDL mode to flash, the device wouldn't boot and just gave the basic "this isn't an approved FW" error, so I had to flash the original boot back.
R0GUEEE said:
As far as everything I've tested so far...
Attempted to downgrade A11 to A10 (can't do it because of incompatible FW binaries)
Flashed several different model FWs & various other CSCs... the model I'm using is SM-A125U (AT&T). Currently the FW running on it is for SM-A125U1 (the carrier unlocked model) but of course still no "OEM Unlock" option in dev settings.
After I tried a few dozen builds I looked into EDL/BROM flashing, since EDL works as a ground zero primary boot interface and seems to work as a recovery/fastboot hybrud allowing both flashing & a CMD interface vs a separated Samsung "Download Mode" and Fastboot mode.
I haven't really spent much time scouring the web for different exploits (that aren't paid services) but I did come across "MTKClient" (https://github.com/bkerler/mtkclient), which I was able to successfully run. I tried using the "unlock bootloader" command, at which point it was a "success" and resulted in the device obviously being wiped, but after the following boot there still was no "OEM Unlock" option in the dev menu. Afterwards I tried flashing a custom boot.img built with Magisk, but even using EDL mode to flash, the device wouldn't boot and just gave the basic "this isn't an approved FW" error, so I had to flash the original boot back.
Click to expand...
Click to collapse
You can't downgrade from Android 11 to 10, because Android 10 has a lower SW_REV value. OEM unlocking shouldn't matter if you can force the PBL to be unlocked by a exploit. You can play with date and time settings in the OS and OEM unlocking may come back, as explained here:
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
You can try editing fimware files if you can't find a exploit for downgradeing SW_REV, or you can try from booting in to PRELOADER and with SP_FLASH_TOOL flash Android 10 scattar fimware. This phone is very new so it may be more difficult for finding exploits, you can play with crossflashing fimware and PRELOADER mode. Another thing is that EDL mode is only for snapdragon chipsets.
And try disabeling thoes security locks:
MTK "secure" boot -use mtksecbypass to disable
"Secure" downloads - try MTKClient
LAST_krypton said:
You can't downgrade from Android 11 to 10, because Android 10 has a lower SW_REV value. OEM unlocking shouldn't matter if you can force the PBL to be unlocked by a exploit. You can play with date and time settings in the OS and OEM unlocking may come back, as explained here:
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
You can try editing fimware files if you can't find a exploit for downgradeing SW_REV, or you can try from booting in to PRELOADER and with SP_FLASH_TOOL flash Android 10 scattar fimware. This phone is very new so it may be more difficult for finding exploits, you can play with crossflashing fimware and PRELOADER mode. Another thing is that EDL mode is only for snapdragon chipsets.
Click to expand...
Click to collapse
I just tried flashing twrp lol, obviously didn't work. So with the a125, it runs on a mediatek processor (MT6765) which has the EDL mode if you short the internal pin. I've tested a couple different exploits which "unlock" it, but after flashing anything custom it always boots with "you can't have custom...". So right now I'm just going around in circles
Edit: Right now I'm playing around with Miracle Box to see what all I can accomplish. I'll update if anything new comes along.
R0GUEEE said:
I just tried flashing twrp lol, obviously didn't work. So with the a125, it runs on a mediatek processor (MT6765) which has the EDL mode if you short the internal pin. I've tested a couple different exploits which "unlock" it, but after flashing anything custom it always boots with "you can't have custom...". So right now I'm just going around in circles
Edit: Right now I'm playing around with Miracle Box to see what all I can accomplish. I'll update if anything new comes along.
Click to expand...
Click to collapse
Ok, good luck with Miracle Box, hope you got the one that isn't backdoored...
EDL mode should be only for Snapdragon, mediatek has it's own PRELOADER mode, as I know of it. Some phones have META-MODE. Could be miscommunication bettwen us.
@R0GUEEE
Here I will share these links and documents that could help.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
How to unlock Unisoc (SPD) bootloader using Identifier Token
This tutorial will explain how to unlock a Unisoc / Spreadtrum (SPD) Android device's bootloader using its Identifier Token. This guide is ideal for those who had tried the generic fastboot bootloader
forum.hovatek.com
Where is the "download mode" code stored?
At least Samsung Galaxy series devices support download mode(also known as Odin mode or flash mode) which usually can be accessed by pressing down specific buttons while powering on the phone. Is t...
android.stackexchange.com
How I can downgrade from U3 to U1 "oreo to nougat"
I want to downgrade my phone from Oreo to Nougat My phone is Samsung J730F. But the problem is that Samsung locked the boot-louder. Can I go back by flashing the phone combination ROM then flash my
android.stackexchange.com
http://newandroidbook.com/21-Security.pdf?aboot
Reverse Engineering Android's Aboot
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
How to use an MTK Secure Boot Download Agent (DA) file
This tutorial will explain how to use that DA file you just downloaded for your Mediatek (MTK) device with Secure Boot. You'll need the DA file to backup, flash, bypass Factory Reset Protection (FRP)
forum.hovatek.com
LAST_krypton said:
@R0GUEEE
Here I will share these links and documents that could help.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
How to unlock Unisoc (SPD) bootloader using Identifier Token
This tutorial will explain how to unlock a Unisoc / Spreadtrum (SPD) Android device's bootloader using its Identifier Token. This guide is ideal for those who had tried the generic fastboot bootloader
forum.hovatek.com
Where is the "download mode" code stored?
At least Samsung Galaxy series devices support download mode(also known as Odin mode or flash mode) which usually can be accessed by pressing down specific buttons while powering on the phone. Is t...
android.stackexchange.com
How I can downgrade from U3 to U1 "oreo to nougat"
I want to downgrade my phone from Oreo to Nougat My phone is Samsung J730F. But the problem is that Samsung locked the boot-louder. Can I go back by flashing the phone combination ROM then flash my
android.stackexchange.com
http://newandroidbook.com/21-Security.pdf?aboot
Reverse Engineering Android's Aboot
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
How to use an MTK Secure Boot Download Agent (DA) file
This tutorial will explain how to use that DA file you just downloaded for your Mediatek (MTK) device with Secure Boot. You'll need the DA file to backup, flash, bypass Factory Reset Protection (FRP)
forum.hovatek.com
Click to expand...
Click to collapse
Yeah, I've pretty much gone around and around in circles with this. The thing that makes it curious though is after running adb shell getprop and looking through the build, I noticed most of the properties relating to oem unlocking were actually set to allow, the one outlier was sys.oem_unlock_allowed. Which kinda pushes me back towards the KG/RMM. Athough, I'm not sure if that's because I have the unlocked U1 FW flashed (it's actually an a125u), or if its the same on both. Either way, running an MTK exploit to unlock the bootloader (which I've done) doesn't actually contribute anything to whether or not OEM Unlocking is visible in dev settings, which is the primary prereq for unlocking the bootloader.
I did consider trying to update the sys.oem within build.prop in /system, but obviously without a root it's impossible, which lead me to possibly unpacking the stock FW super.img and trying to pre-edit the build within so I could re-pack and flash using the MTK Bypass exploit, but those necessary oem properties aren't even listed on either of the build files I did manage to find.
So as of now I've got one more test I'm going to try before I give up. All things considered, the most likely issue is the KG/RMM state, so I'm going to test a few different methods to try and circumnavigate those and possibly unlock the missing OEM Unlock option.
I can at least say that it's likely not an issue of manufacturer locked loaders, considering that's primarily a snapdragon issue, whereas the A12 runs on MediaTek, so fingers crossed.
R0GUEEE said:
Yeah, I've pretty much gone around and around in circles with this. The thing that makes it curious though is after running adb shell getprop and looking through the build, I noticed most of the properties relating to oem unlocking were actually set to allow, the one outlier was sys.oem_unlock_allowed. Which kinda pushes me back towards the KG/RMM. Athough, I'm not sure if that's because I have the unlocked U1 FW flashed (it's actually an a125u), or if its the same on both. Either way, running an MTK exploit to unlock the bootloader (which I've done) doesn't actually contribute anything to whether or not OEM Unlocking is visible in dev settings, which is the primary prereq for unlocking the bootloader.
I did consider trying to update the sys.oem within build.prop in /system, but obviously without a root it's impossible, which lead me to possibly unpacking the stock FW super.img and trying to pre-edit the build within so I could re-pack and flash using the MTK Bypass exploit, but those necessary oem properties aren't even listed on either of the build files I did manage to find.
So as of now I've got one more test I'm going to try before I give up. All things considered, the most likely issue is the KG/RMM state, so I'm going to test a few different methods to try and circumnavigate those and possibly unlock the missing OEM Unlock option.
I can at least say that it's likely not an issue of manufacturer locked loaders, considering that's primarily a snapdragon issue, whereas the A12 runs on MediaTek, so fingers crossed.
Click to expand...
Click to collapse
If you were able to see the settings are enabled through ADB that is the same as it showing in settings. KG/RMM state could also be the factor of why it isn't beeing shown as of what you have said. Samsung has came a long way with these dumb knox securities which just makes everything worse, you might be able to find a clue for this within their KNOX documents ( I sent a link in a post above). Maybe you can find a profesional, a person that has worked for samsung and can maybe help you with this. It just gets too complicated at one point. If you have telegram or something were we can talk further about this it would be nice because some exploits and stuff if you mention can violate xda rules... So I don't know what else to tell you, I never really was in a situation where I was required to do these type of stuff, only if I had to because of some problems I had. Maybe you can find answers for all of this on some really old forums where people use to do everything to brake apart samsungs and mediateks security locks but still dout it.
For now, hope you learned something and dm me if you want to chat on telegram or etc about this. Don't think something is impossible because you can't find a answer for it, everything is possible.
LAST_krypton said:
If you were able to see the settings are enabled through ADB that is the same as it showing in settings. KG/RMM state could also be the factor of why it isn't beeing shown as of what you have said. Samsung has came a long way with these dumb knox securities which just makes everything worse, you might be able to find a clue for this within their KNOX documents ( I sent a link in a post above). Maybe you can find a profesional, a person that has worked for samsung and can maybe help you with this. It just gets too complicated at one point. If you have telegram or something were we can talk further about this it would be nice because some exploits and stuff if you mention can violate xda rules... So I don't know what else to tell you, I never really was in a situation where I was required to do these type of stuff, only if I had to because of some problems I had. Maybe you can find answers for all of this on some really old forums where people use to do everything to brake apart samsungs and mediateks security locks but still dout it.
For now, hope you learned something and dm me if you want to chat on telegram or etc about this. Don't think something is impossible because you can't find a answer for it, everything is possible.
Click to expand...
Click to collapse
Well after trial and error, I finally got it. I had to hunt down an Android 10 firmware with a matching binary to allow a downgrade, and after a couple of tries, using the auto-date/time method, OEM unlocking finally decided to show itself in dev settings. Specifically, I used this FW, flashed with Odin https://samfw.com/firmware/SM-A125U/USC/A125USQS2AUF3
R0GUEEE said:
Well after trial and error, I finally got it. I had to hunt down an Android 10 firmware with a matching binary to allow a downgrade, and after a couple of tries, using the auto-date/time method, OEM unlocking finally decided to show itself in dev settings. Specifically, I used this FW, flashed with Odin https://samfw.com/firmware/SM-A125U/USC/A125USQS2AUF3
Click to expand...
Click to collapse
Well, you couldev done that allready out of the start. But even do you got OEM_UNLOCKING shown doesn't really mean anything on U model, unless you have exploits and methods for unlocking PBL. Which as said wasn't very sucessful at all for you. I recomend to you that you check our DMs. mtkclient has some bugs which are on the way to be fixed.
I've been working with mtkclient for months, before it even unlocked bootloaders, I was the first to unlock the stylo 6 bootloader and I had a bit of a hand in working out some of the bugs with the tool, I'm doing a full backup of the A125U model right now with mtkclient and after it's done I plan to try the unlock without having oem unlock option in dev options, but first I'll check to see what binary version I'm on, not sure if it's on android 10 or 11 right now. But I will sheet the backup
I finally finished my tutorial for the stylo 6 bootloader unlock and root so now I'm working with the A125U. I'm on 2nd binary and i think i got the bootloader unlocked, but if I flash the patched boot.img it won't boot. I'm gonna try a few ideas i have, so far no luck but I'm not gonna give up, I may crossflash, but I'm trying to find the easiest way to do this.
LAST_krypton said:
@R0GUEEE
Here I will share these links and documents that could help.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
How to unlock Unisoc (SPD) bootloader using Identifier Token
This tutorial will explain how to unlock a Unisoc / Spreadtrum (SPD) Android device's bootloader using its Identifier Token. This guide is ideal for those who had tried the generic fastboot bootloader
forum.hovatek.com
Where is the "download mode" code stored?
At least Samsung Galaxy series devices support download mode(also known as Odin mode or flash mode) which usually can be accessed by pressing down specific buttons while powering on the phone. Is t...
android.stackexchange.com
How I can downgrade from U3 to U1 "oreo to nougat"
I want to downgrade my phone from Oreo to Nougat My phone is Samsung J730F. But the problem is that Samsung locked the boot-louder. Can I go back by flashing the phone combination ROM then flash my
android.stackexchange.com
http://newandroidbook.com/21-Security.pdf?aboot
Reverse Engineering Android's Aboot
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
How to use an MTK Secure Boot Download Agent (DA) file
This tutorial will explain how to use that DA file you just downloaded for your Mediatek (MTK) device with Secure Boot. You'll need the DA file to backup, flash, bypass Factory Reset Protection (FRP)
forum.hovatek.com
Click to expand...
Click to collapse
GitHub - MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
I'm glad to see Hovatek being suggested, i worked with them on my stylo 6 project, they even gave me a shout out if you look in the mtkclient instruction for the K51.
Here's the scatter file for the A125U model
MT6765_A12_scatter.txt
drive.google.com
LAST_krypton said:
Well, you couldev done that allready out of the start. But even do you got OEM_UNLOCKING shown doesn't really mean anything on U model, unless you have exploits and methods for unlocking PBL. Which as said wasn't very sucessful at all for you. I recomend to you that you check our DMs. mtkclient has some bugs which are on the way to be fixed.
Click to expand...
Click to collapse
R0GUEEE said:
Well after trial and error, I finally got it. I had to hunt down an Android 10 firmware with a matching binary to allow a downgrade, and after a couple of tries, using the auto-date/time method, OEM unlocking finally decided to show itself in dev settings. Specifically, I used this FW, flashed with Odin https://samfw.com/firmware/SM-A125U/USC/A125USQS2AUF3
Click to expand...
Click to collapse
I own a a125u with FW A125USQU2BUI3. Would I be able to use this method to make oem unlock appear and then root? If so could you please assist me and help with the steps? I've been attempting to root this thing for a week and my girl friend is starting to hate me because I'm obsessed and paymore attention to this than her lol
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?