I opened up the developer options on my Moto G Stylus and went under OEM Unlocking and selected the allow the bootloader to be unlocked option. That was either last week or a few weeks ago because I wanted to root it and put a custom rom on it. I didn't rooted it yet because I'm not sure what roms are good, I only had cyanogin mod roms on my other phones and I'm not sure which rom is the safest and best to use so I still use the stock rom. I turned on Pandora to play music before I went to sleep. When I woke up my phone was in some kind of recovery mode and said something like the operating system failed to boot. Two options were available, 1- to try booting again, and 2-factory reset the phone which would erase all data. I selected 1, and my phone booted up. Could this be because the bootloader is unlocked? Does having the bootloader unlocked leave it suspectable to being hacked? Could my phone have been hacked?
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
k3dar7 said:
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
Click to expand...
Click to collapse
Would selecting the bootloader option to be unlocked in the developer options make my phone more vulnerable to be hacked?
A few hours later my phone did the same thing and went into recovery mode saying that my phone could not load the OS and might be infected or something. I had the same options to either try to load the OS again or factory data reset the phone. How could this happen?
I factory data reset my phone this time. I just hope I don't have some kind of malware.
Mine was hacked like this. Changed stuff so it won't boot back to original. Got into system files and remote control my phone. Is there a way to get back to original without computer? It's useless now
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
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
smartasiankid said:
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
In theory, because you are already unlocked.
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
notmyrealhandle said:
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
Click to expand...
Click to collapse
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
smartasiankid said:
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
Click to expand...
Click to collapse
I'm not sure then.
If I was in your situation and I didn't mind wiping my data, I'd probably try booting into the bootloader and trying `fastboot flashing unlock` just to see what happens. If this command works, it will wipe your data so be sure about your backups. If it does unlock, you could try rebooting, check the OEM lock (I expect it will still be greyed out with an unlocked bootloader), and then relock and check again. Regardless if you can unlock inspite of the OEM toggle you shouldn't have much to worry about (at least until the next update).
If this doesn't work then I'd just wait a week or so. Alternatively, you could try the moto site, request your unlock key (again) and then wait a few days. It would be silly if this works, but maybe moto just needs to send a reminder to your device to enable the OEM unlocking toggle.
If none of this works, then I'd try posting to the moto official forums.
HTH
Never mind guys!! Just wait three maybe four days and it will automatically be toggle able again!! Thanks to all of those who tried to help me out!
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
smartasiankid said:
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
Click to expand...
Click to collapse
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
MrCamby said:
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
Click to expand...
Click to collapse
it is greyed out for me. i am on at&t network. it has been greyed out ever since android 11. not sure why that is happening.
So i received a american pixel 4 xl with a locked bootloader. imei starting with 35
i was able to unlock the bootloader here is the steps i took, note im in Australia.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
the firmware on the device was american,
i flashed my countrys firmware (australian) optus/telstra/vodaphone etc
use adb side load *firmware.zip*
factory reset , booted device on with australian sim,
and boom oem was available ,
(last step is to adb reboot bootloader,
and ./fastboot flashing unlock and you will see a message on pixel.
intially with the Original firmware on the device it would not unlock.. i tried factory reset
/ fastboot flashing unlock etc and it would not work...
anyhoo i have not seen anything on here suggested flashing another firmware origin so i thought this might help those with locked at&t / verison carriers, intially it was GREYED OUT AND SAID contact carrier or connect to the internet.
Hope this helps someone ! as all the forums ive swiped thru have said this is not do-able, lol turns out it is.
xorrgnlusrx said:
So i received a american pixel 4 xl with a locked bootloader. imei starting with 35
i was able to unlock the bootloader here is the steps i took, note im in Australia.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
the firmware on the device was american,
i flashed my countrys firmware (australian) optus/telstra/vodaphone etc
use adb side load *firmware.zip*
factory reset , booted device on with australian sim,
and boom oem was available ,
(last step is to adb reboot bootloader,
and ./fastboot flashing unlock and you will see a message on pixel.
intially with the Original firmware on the device it would not unlock.. i tried factory reset
/ fastboot flashing unlock etc and it would not work...
anyhoo i have not seen anything on here suggested flashing another firmware origin so i thought this might help those with locked at&t / verison carriers, intially it was GREYED OUT AND SAID contact carrier or connect to the internet.
Hope this helps someone ! as all the forums ive swiped thru have said this is not do-able, lol turns out it is.
Click to expand...
Click to collapse
The firmware does not determine whether the bootloader is unlockable.
When the device connects to the Internet, it checks its IMEI against a whitelist on Google's servers. If it has been authorized for bootloader unlock, OEM Unlocking will become available.
If it doesn't, it's likely that you have a locked variant.
V0latyle said:
The firmware does not determine whether the bootloader is unlockable.
When the device connects to the Internet, it checks its IMEI against a whitelist on Google's servers. If it has been authorized for bootloader unlock, OEM Unlocking will become available.
If it doesn't, it's likely that you have a locked variant.
Click to expand...
Click to collapse
What if it is already unlocked and I want to relock it? I flashed stock firmware, the bootloader is still unlocked but now I can't lock it again because the option is greyed out.
emko7 said:
What if it is already unlocked and I want to relock it? I flashed stock firmware, the bootloader is still unlocked but now I can't lock it again because the option is greyed out.
Click to expand...
Click to collapse
The OEM Unlocking toggle does not lock or unlock the bootloader itself. It simply allows you to unlock the bootloader when enabled.
If you want to relock your bootloader, you do this via ADB while in bootloader mode: fastboot flashing lock
V0latyle said:
The OEM Unlocking toggle does not lock or unlock the bootloader itself. It simply allows you to unlock the bootloader when enabled.
If you want to relock your bootloader, you do this via ADB while in bootloader mode: fastboot flashing lock
Click to expand...
Click to collapse
For some reason I couldn't get into fastboot mode, "adb reboot bootloader" would just restart my device. If I booted into recovery, the "reboot into bootloader" option would just start up the phone. But I eventually found out I can lock the bootloader in download mode
Hey I am trying to root my sm-a037w, fully updated.
I remember having OEM unlocked it using the developer option which is now gone completely.
I'm using Magisk to patch the AP file
Then use ODIN to flash it and it stops at vbmeta with a error.
I'm new to this and have googled alot but now I'm really stuck.
So it fails, corrupt phone, I reflash oem AP and it restarts.
I have adb and fastboot ready to go,
Thank you.
Johnhek said:
Hey I am trying to root my sm-a037w, fully updated.
I remember having OEM unlocked it using the developer option which is now gone completely.
Click to expand...
Click to collapse
This is your problem, right here. If you closely read the Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If you can't see OEM Unlocking in Developer Options, and you see KG STATUS: PRENORMAL on the download mode screen, Vaultkeeper is still active and will reject custom images.
V0latyle said:
This is your problem, right here. If you closely read the Magisk installation instructions:
If you can't see OEM Unlocking in Developer Options, and you see KG STATUS: PRENORMAL on the download mode screen, Vaultkeeper is still active and will reject custom images.
Click to expand...
Click to collapse
Yea I've been trying for the last 48 hours and I can't figure it out how to get it back.
I did have developer mode active and had seen and allowed oem unlocking, not sure when I disappeared, I think it was the latest update.
Don't know how to proceed.
Tried setting the date back , disabling system update and software update, still no OEM Unlocking.
I have read those instructions many times, I have no prior experience rooting or modding android :/
Should I reflash original firmware?
Where do I go from here?
Johnhek said:
Yea I've been trying for the last 48 hours and I can't figure it out how to get it back.
I did have developer mode active and had seen and allowed oem unlocking, not sure when I disappeared, I think it was the latest update.
Don't know how to proceed.
Tried setting the date back , disabling system update and software update, still no OEM Unlocking.
I have read those instructions many times, I have no prior experience rooting or modding android :/
Should I reflash original firmware?
Where do I go from here?
Click to expand...
Click to collapse
Did you ever see the OEM Unlocking toggle after you unlocked the bootloader?
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Reflashing the firmware might be a good idea. Keep in mind that Samsung is notorious for trying to disallow custom binaries on newer bootloaders. This is all speculation though, I'd need to see the error you got to have a better idea what the issue is.
flashing firmware is bad idea, this won't reset vaultkeeper. check RMM/KG state from download mode screen first. btw it's called odin mode (not fastboot mode)
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
aIecxs said:
flashing firmware is bad idea, this won't reset vaultkeeper. check RMM/KG state from download mode screen first. btw it's called odin mode (not fastboot mode)
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
Click to expand...
Click to collapse
Knox Guard has to be disabled by connecting to the Internet and checking for updates, and you have to be on stock firmware to do it.
Flashing the OEM firmware won't hurt anything, and is the only way to unlock KG.
Vaultkeeper is disabled by flashing the multidisabler in TWRP.
V0latyle said:
Did you ever see the OEM Unlocking toggle after you unlocked the bootloader?
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Reflashing the firmware might be a good idea. Keep in mind that Samsung is notorious for trying to disallow custom binaries on newer bootloaders. This is all speculation though, I'd need to see the error you got to have a better idea what the issue is.
Click to expand...
Click to collapse
Hey thank you once again for your help.
To be clear this is how I recall the events .
1. I did enable OEM unlocking in developer options.
2. I updated the phone through the user interface.
3. OEM unlocking option dissapeared entirely after updating to android 12.
4. Downloaded XAC region firmware using SamFirm
5. Copied AP to my phone storage
6. Patched AP with Magisk, then transferred patched file to my PC.
7. Flashed BL, patched AP, CP and CSC(not home) using ODIN 3.14
ODIN said AUTH fail at Vbmeta on my PC and on the phone iirc.
8.Reflashed using stock AP to make the phone usable again.
At downloader screen I never saw hold volume up to unlock bootloader, only press up to continue. (after booting holding volume up+down+power)
Are KG and Vaultkeeper the same thing?
I guess my bootloader is locked and now OEM Unlocking option is gone.
This is the phone currently on latest firmware.
ODIN MODE reads:
FRP LOCK:ON
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE (0)
sec ctrl status (1)
SECURE DOWNLOAD: ENABLE
Baseband version A037WVLS 3 BVJ1 (bootloader version 3?)
Thanks for all the info, sorry for the messy post and not including all the info required.
I will provide you with the info you request, I do not know how to verify my KG status, it reads checking in ODIN MODE.
I am also not sure of how to identify the region firmware I need, the software version in my about phone says:
SAOMC_SM-A037W_OYV_BMC_12_0004
BMC/BMC/XAC/BMC
I have downloaded both XAC and BMC, both have worked for me.
Ohhh, it's a Mediatek device
Johnhek said:
At downloader screen I never saw hold volume up to unlock bootloader, only press up to continue. (after booting holding volume up+down+power)
Click to expand...
Click to collapse
The proper way to enter device unlock mode is thus:
Unplug any USB cables, power device off completely
Connect a USB cable to your PC, don't connect it to your phone yet
Hold both Volume buttons, do not press Power, and plug in the USB cable.
The screen should turn on with 3 options: Volume Up for download mode, long press Volume Up for device unlock mode, Volume Down for restart. Release both Volume buttons, then hold Volume Up.
Device should prompt you to confirm you want to unlock. If it prompts you to confirm you want to re-lock, stop! The bootloader is already unlocked.
Johnhek said:
Are KG and Vaultkeeper the same thing?
Click to expand...
Click to collapse
More or less...Vaultkeeper is the process that determines the Knox Guard status, which in turn is what actually allows custom binaries
Johnhek said:
I guess my bootloader is locked and now OEM Unlocking option is gone.
Click to expand...
Click to collapse
We'll see...
Johnhek said:
KG STATUS: CHECKING
Click to expand...
Click to collapse
This means that KG (Knox Guard)/Vaultkeeper hasn't yet verified your device is supposed to be unlocked.
Johnhek said:
MTK SECURE BOOT: ENABLE (0)
sec ctrl status (1)
SECURE DOWNLOAD: ENABLE
Click to expand...
Click to collapse
Is there nothing on there that says OEM LOCK?
Johnhek said:
Thanks for all the info, sorry for the messy post and not including all the info required.
I will provide you with the info you request, I do not know how to verify my KG status, it reads checking in ODIN MODE.
Click to expand...
Click to collapse
That's exactly how - it tells you in download/Odin mode.
Since it says CHECKING, there are two things we need to do:
Ensure the bootloader is indeed unlocked, using the steps I gave above
Once bootloader is confirmed to be unlocked, you need to boot into Android, connect to the Internet (use a WiFi network), go into Settings > System > System update and check for software updates. This also checks Vaultkeeper/KG.
After checking for software update, enable developer options (if not already enabled) and verify OEM Unlocking is present; it should be grayed out with the message "Bootloader is already unlocked".
The proper way to enter device unlock mode is thus:
Unplug any USB cables, power device off completely
Connect a USB cable to your PC, don't connect it to your phone yet
Hold both Volume buttons, do not press Power, and plug in the USB cable.
The screen should turn on with 3 options: Volume Up for download mode, long press Volume Up for device unlock mode, Volume Down for restart. Release both Volume buttons, then hold Volume Up.
Device should prompt you to confirm you want to unlock. If it prompts you to confirm you want to re-lock, stop! The bootloader is already unlocked.
Click to expand...
Click to collapse
I just tried this and there is no mention of unlock bootloader, same as before (volume up to continue) I click to continue and it reads;
PRODUCT NAME: SM-A037WCURRENT BINARY: SAMSUNG OFFICIALFRP LOCK: ONKG STATUS: CHECKING (I never created a samsung account on this phone if that means anything)MTK SECURE BOOT: ENABLE (0)sec ctrl statu (1)WARRANTY VOID: 0x0 (0x0)RP SWREV: B3 NS3 Kb3, Kr3, Vb3, Vbs3 S3SECURE DOWNLOAD: ENABLEMaybe I have to wait 7 days as I have read somewhere before I get the OEM Unlock option back?Thank you for your help
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
aIecxs said:
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
Click to expand...
Click to collapse
I am using the device normally and bought the phone new, using the google account i created for it , so i dont understand how this is possible.
Idk maybe FRP LOCK: ON disappears once you removed all bonded samsung and google accounts (maybe not caused by Google Factory Reset Protection but Samsung Reactivation Lock)?
V0latyle said:
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Click to expand...
Click to collapse
No he didn't unfortunately. For bootloader unlocking and passing vaultkeeper one have to repeat that step twice, before and after unlocking/factory reset in odin/download mode.
https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699
aIecxs said:
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
Click to expand...
Click to collapse
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
@Johnhek you have already connected your device to WiFi, yes? If not, you need to do so, then go to Settings > System > Software update to trigger a check. Once done, go back to Developer Options to see if OEM Unlocking is visible.
If the bootloader wasn't unlockable, the OEM Unlocking toggle would never be present. The toggle controls the state of sys.get_unlock_ability which tells the bootloader it can be unlocked. There are a couple of props that control whether OEM Unlocking is available, ro.oem_unlock_supported which is supposed to be baked into the ROM at build time, and ro.oem_unlock_allowed which determines whether the toggle is available.
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy.
V0latyle said:
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
Click to expand...
Click to collapse
I don't know for SM-A037W but I know about people selling their Samsung phones on Android 10 for buying same model on Android 9 for reason.
Johnhek said:
I did have developer mode active and had seen and allowed oem unlocking, not sure when it disappeared, I think it was the latest update.
Click to expand...
Click to collapse
There is no official information but there are rumors that from certain security patch Samsung removed OEM unlocking forcefully (USA/Canada devices).
It's also my experience with SM-T555 region DBT still not unlockable as of today.
I think it's common sense when it comes to rooting/unlocking that older android versions are easier to root.
V0latyle said:
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
Click to expand...
Click to collapse
For other brands it's not possible to flash anything when FRP Lock is on. Furthermore that state means device is actually FRP locked. Didn't know about Samsung FRP LOCK ON is only information about device is ready for FRP locking, sorry about that...
nevertheless FRP lock is contradictory to OEM unlock, both together is afaik not possible (except for Xiaomi).
btw flashing stock firmware won't unlock RMM/KG prenormal
we will know more about in 7 days...
V0latyle said:
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
@Johnhek you have already connected your device to WiFi, yes? If not, you need to do so, then go to Settings > System > Software update to trigger a check. Once done, go back to Developer Options to see if OEM Unlocking is visible.
If the bootloader wasn't unlockable, the OEM Unlocking toggle would never be present. The toggle controls the state of sys.get_unlock_ability which tells the bootloader it can be unlocked. There are a couple of props that control whether OEM Unlocking is available, ro.oem_unlock_supported which is supposed to be baked into the ROM at build time, and ro.oem_unlock_allowed which determines whether the toggle is available.
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy.
Click to expand...
Click to collapse
@V0latyle hey I have tried those suggestions still no luck. Thank you and happy holidays, I will try waiting 7 days ND let everyone know
aIecxs said:
I don't know for SM-A037W but I know about people selling their Samsung phones on Android 10 for buying same model on Android 9 for reason.
There is no official information but there are rumors that from certain security patch Samsung removed OEM unlocking forcefully (USA/Canada devices).
It's also my experience with SM-T555 region DBT still not unlockable as of today.
I think it's common sense when it comes to rooting/unlocking that older android versions are easier to root.
For other brands it's not possible to flash anything when FRP Lock is on. Furthermore that state means device is actually FRP locked. Didn't know about Samsung FRP LOCK ON is only information about device is ready for FRP locking, sorry about that...
nevertheless FRP lock is contradictory to OEM unlock, both together is afaik not possible (except for Xiaomi).
btw flashing stock firmware won't unlock RMM/KG prenormal
we will know more about in 7 days...
Click to expand...
Click to collapse
@Alecxs Yea I probably should have left it android 11.
V0latyle said:
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy
Click to expand...
Click to collapse
I will read the link tonight , much appreciated
Johnhek said:
@V0latyle hey I have tried those suggestions still no luck. Thank you and happy holidays, I will try waiting 7 days ND let everyone know
Click to expand...
Click to collapse
You can also try disconnecting from the Internet (take out your SIM as well) and set the date back by at least a week. Or you can set it forward.
Johnhek said:
@Alecxs Yea I probably should have left it android 11.
Click to expand...
Click to collapse
It shouldn't matter, honestly, although I generally prefer to do one thing at a time - unlock the bootloader, THEN update.
I have a feeling that the MediaTek aspect of things may be the issue here, although I have no way of knowing.
Johnhek said:
I will read the link tonight , much appreciated
Click to expand...
Click to collapse
Hopefully it will be of some help to you. It's not beginner friendly - you have to install Python and compile it, but if you can get MTKclient working, you can see if it's what you need.
V0latyle said:
I have a feeling that the MediaTek aspect of things may be the issue here, although I have no way of knowing.
Hopefully it will be of some help to you. It's not beginner friendly - you have to install Python and compile it, but if you can get MTKclient working, you can see if it's what you need.
Click to expand...
Click to collapse
Reading it now, I think I can handle it, the instructions seem clear.
As for the date trick.
I tried it while connected to wifi, I dont even have a sim card in this phone lol.
Tried setting to last month, havent tried forward in time though, will try disconnected as well.
The mediatek thing seems promising, I think the sec ctrl status (1) in the download screen is MTK related...
I will let you know.
I have read in one of the linked threads that SIM card plays a role here. I recommend to enable mobile data for 7 days, although there is less hope.
from what I have learned from elliwigy one can't cheat samsung bootloader not even with mtkclient. there is however paid service for devices with DID token on download screen (afaik Qualcomm only). but try mtkclient first it's a good exercise and maybe you're lucky and it works.
aIecxs said:
I have read in one of the linked threads that SIM card plays a role here. I recommend to enable mobile data for 7 days, although there is less hope.
from what I have learned from elliwigy one can't cheat samsung bootloader not even with mtkclient. there is however paid service for devices with DID token on download screen (afaik Qualcomm only). but try mtkclient first it's a good exercise and maybe you're lucky and it works.
Click to expand...
Click to collapse
I tried mtkcient but I kept getting unauthorized handshake when trying to connect phone :/
Followed instructions as per link but I encounter one error in the process:
Get latest UsbDk 64-Bit
Install normal MTK Serial Port driver (or use default Windows COM Port one, make sure no exclamation is seen)
Get usbdk installer (.msi) from here and install it
Test on device connect using "UsbDkController -n" if you see a device with 0x0E8D 0x0003
Works fine under Windows 10 and 11
I'm on windows 11 and when I put the command "UsbDkController -n" in terminal it doesn't recognize it.
I installed the usbdk drivers from git hub, a .msi fil, from the guide.
Another problem is I don't know how to set windows default COM Port one.