Related
Of course S7 on Tmobile gets unlocked the day it updates to 7.0 but I want to drop a cleaner rom on it, I hate the T-Mobile/Samsung crap that just eats space and battery.
I have enabled developer mode, turned on USB Debugging and enabled the OEM Unlock.
I have tried Odin 3.12.3 and 3.10.6 ( which comes with Chain fire ).
Before and after trying a factory reset, I am completely unable to replace the recovery with TWRP or chainfire or even just drop a new rom on it. When I try to use Odin, I get an error message " Complete(Write) operation failed" or " Complete(AUTH) operation failed". I've tried running Odin as Admin, I've rebooted my computer and the phone multiple times and tried 4 different USB cables ( thick and thin ) which all pass data at a good speed.
Any thoughts? This is getting annoying.
Nomadadon said:
Of course S7 on Tmobile gets unlocked the day it updates to 7.0 but I want to drop a cleaner rom on it, I hate the T-Mobile/Samsung crap that just eats space and battery.
I have enabled developer mode, turned on USB Debugging and enabled the OEM Unlock.
I have tried Odin 3.12.3 and 3.10.6 ( which comes with Chain fire ).
Before and after trying a factory reset, I am completely unable to replace the recovery with TWRP or chainfire or even just drop a new rom on it. When I try to use Odin, I get an error message " Complete(Write) operation failed" or " Complete(AUTH) operation failed". I've tried running Odin as Admin, I've rebooted my computer and the phone multiple times and tried 4 different USB cables ( thick and thin ) which all pass data at a good speed.
Any thoughts? This is getting annoying.
Click to expand...
Click to collapse
Hi mate
yes a few..
First you are in the wrong forum check here
https://forum.xda-developers.com/tmobile-galaxy-s7
Second you can root a snapdragon S7 BUT even so your bootloader is still locked , therefore you cant flash TWRP or any custom rom....
Sorry mate
Hi, I´m not in the business of unlocking phones, just looking how to SIM unlock my personal phone. Would you please explain what does it mean the bootloader is locked? With that issue in mind, that prevents me to SIM Unlock the phone?
MAX 404 said:
Hi mate
yes a few..
First you are in the wrong forum check here
https://forum.xda-developers.com/tmobile-galaxy-s7
Second you can root a snapdragon S7 BUT even so your bootloader is still locked , therefore you cant flash TWRP or any custom rom....
Sorry mate
Click to expand...
Click to collapse
fbolzoni said:
Hi, I´m not in the business of unlocking phones, just looking how to SIM unlock my personal phone. Would you please explain what does it mean the bootloader is locked? With that issue in mind, that prevents me to SIM Unlock the phone?
Click to expand...
Click to collapse
Carrier lock is what would prevent you from using your SIM in the phone if it's not the right carrier. You'll either need to call the carrier of the phone (Verizon, AT&T etc) to unlock it or use an online unlocker like http://updato.com/unlock but I don't know how reliable these are.
Bootloader lock is what OP is experiencing, which prevents you modifying the boot image, so you can't put TWRP or custom ROM's on a bootloader that's locked.
This means that at the time there is no way to unlock bootloader and flash any custom roms, in order to unlock SIM on G9030T?
Beanvee7 said:
Carrier lock is what would prevent you from using your SIM in the phone if it's not the right carrier. You'll either need to call the carrier of the phone (Verizon, AT&T etc) to unlock it or use an online unlocker like ----- but I don't know how reliable these are.
Bootloader lock is what OP is experiencing, which prevents you modifying the boot image, so you can't put TWRP or custom ROM's on a bootloader that's locked.
Click to expand...
Click to collapse
fbolzoni said:
This means that at the time there is no way to unlock bootloader and flash any custom roms, in order to unlock SIM on G9030T?
Click to expand...
Click to collapse
Correct, at this stage there is know no way to unlock the bootloader and flash any custom roms.
You'll need to follow normal carrier unlock procedure
I have looked around for a long time but I can't find a solution to my problem.
When I try to root or install a custom ROM to my phone I get bootloop because of the FRP lock.
I have read that the only way to get around this is to log out of your Google account and never sign in but then I will lose a lot of features.
Is there really no way to root a Samsung Galaxy S7 with Google services enabled?
And is there any way of getting rid of the FRP lock without logging out off your Google account?
Any help is much appreciated!
Have you enabled OEM unlock in developer options?
*Detection* said:
Have you enabled OEM unlock in developer options?
Click to expand...
Click to collapse
Yes, I have, TWRP recovery also works fine.
Couldn't you just sign out, install, then sign back in? What would you lose by signing out that wouldn't come back when you sign in again?
Beanvee7 said:
Couldn't you just sign out, install, then sign back in? What would you lose by signing out that wouldn't come back when you sign in again?
Click to expand...
Click to collapse
I have already tried that, it works fine until I login to Google again. Then, if I restart the phone it goes into bootloop because FRP lock has been re-enabled.
byCorza said:
I have already tried that, it works fine until I login to Google again. Then, if I restart the phone it goes into bootloop because FRP lock has been re-enabled.
Click to expand...
Click to collapse
Never ever heard of this happening before, it obviously doesn't usually happen otherwise XDA would be full of people with the same problem... FRP lock should only appear if you try to reset the device from recovery without signing out first
*Detection* said:
Never ever heard of this happening before, it obviously doesn't usually happen otherwise XDA would be full of people with the same problem... FRP lock should only appear if you try to reset the device from recovery without signing out first
Click to expand...
Click to collapse
FRP lock appears when the bootloader changes. But I will try one more time with deactivating Google Services and signing out now just to be sure and report back. :good:
*Detection* said:
Never ever heard of this happening before, it obviously doesn't usually happen otherwise XDA would be full of people with the same problem... FRP lock should only appear if you try to reset the device from recovery without signing out first
Click to expand...
Click to collapse
Okey, I signed out of Google and Samsung, went into download mode and followed the exact guide here https://forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
Now I am stuck in bootloop again and it says in the top right corner: "Kernel is not seandroid enforcing" .
When I go into download mode again it still says: "FRP LOCK: OFF"
And as usual the only way I have been able to fix this is by flashing back to stock ROM.
Full Download mode info:
PRODYCT NAME: SM-G930F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
WARRANTY VOID: 1 (0X0203)
byCorza said:
Okey, I signed out of Google and Samsung, went into download mode and followed the exact guide here https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Now I am stuck in bootloop again and it says in the top right corner: "Kernel is not seandroid enforcing" .
When I go into download mode again it still says: "FRP LOCK: OFF"
And as usual the only way I have been able to fix this is by flashing back to stock ROM.
Full Download mode info:
PRODYCT NAME: SM-G930F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
WARRANTY VOID: 1 (0X0203)
Click to expand...
Click to collapse
That's for the Verizon S7, snapdragon, yours is the International Exynos S7
You're flashing the wrong files, use G930F files
SOLVED
I tried to flash different files for root without any help, so I decided to flash the Superman ROM which comes with root. I could actually boot now but OEM-unlock disappeared from the developer options.
I then had to enable OEM unlock somehow so i did:
Code:
> adb reboot bootloader
> sudo fastboot oem unlock
Now everything works perfect.
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Blackion said:
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Click to expand...
Click to collapse
If there's an option for OEM Unlock in developer settings enable that to disable FRP
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
reflash the stock fw using odin
Not sure
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Blackion said:
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Click to expand...
Click to collapse
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
corvasce03 said:
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
Click to expand...
Click to collapse
I used smartswitch when I encountered frp lock
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
1eStar said:
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Click to expand...
Click to collapse
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
kiwigi said:
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
Click to expand...
Click to collapse
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
corvasce03 said:
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
Click to expand...
Click to collapse
@corvasce03
Thanks.
I think I got back allright except this here and I used exactly the same stock(file) as a year ago
Someone Help My Soul!!!
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Cirphrank said:
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Click to expand...
Click to collapse
It stops someone stealing your phone, wiping it, installing new firmware and using it as if it was new. If you know the gmail and password you put on the phone to access the play store then you just need to re-enter it after the phone restarts. FRP will only kick in if you have flashed new firmware to the phone.
I have a new firmware flashed on the phone.
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Cirphrank said:
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Click to expand...
Click to collapse
I'm not sure what you mean. If you have a Google account on the phone that you know the email and password to, then just reboot the phone. FRP lock will only activate if you flash new firmware to the phone without removing the Google account first.
Your device should only have 1 Google account registered on the device which let's you access Play store etc. If there is more than one, you need to delete the ones you don't know the email and password to.
Okay...
Oh, okay, now I am getting the rationale.
Albeit, when I flashed in the new custom firmware, it started give me the undo changes by restarting your phone notification, like it did the first time ever that I got the lock. I didn't click it, activated an app that discarded the notification rather.
Now it makes me doubt if I had really removed my mail before flashing the phone.
hey
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
stasikkk777 said:
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
Click to expand...
Click to collapse
Yeah you've messed it up by not signing out of account before unistalling xposed. When you say 3 different rom's do you mean stock or custom?
Even in this state you should be able to flash a stock rom to the device with Odin and it will ask you to type the google email and password after boot.
Always turn off FRP lock before modifying the phone, it's a really annoying feature.
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.
i've read a blog post somewhere which talks of the possibility to lock a sumsung download mode, how can this be done or undone?
thelite said:
i've read a blog post somewhere which talks of the possibility to lock a sumsung download mode, how can this be done or undone?
Click to expand...
Click to collapse
Can you provide more details?
The bootloader lock prevents flashing and booting of unsigned images. With a locked bootloader, download mode does not accept custom software; all software packages must be OEM signed.
An unlocked bootloader (with Knox Guard disabled) will allow flashing custom firmware, such as TWRP recovery.
So, in that sort of sense, I suppose the bootloader lock does control what download mode will accept via Odin.
V0latyle said:
Can you provide more details?
The bootloader lock prevents flashing and booting of unsigned images. With a locked bootloader, download mode does not accept custom software; all software packages must be OEM signed.
An unlocked bootloader (with Knox Guard disabled) will allow flashing custom firmware, such as TWRP recovery.
So, in that sort of sense, I suppose the bootloader lock does control what download mode will accept via Odin.
Click to expand...
Click to collapse
im on the sumsung galaxy a032F, there is no oem unlock in developer options so i guess i cannot unlock the bootloader, and when i try to flash a custom firmware via odin i get an error mdm mode can't download odin. so after reading the blog post i was wondering, could the download mode be locked
thelite said:
im on the sumsung galaxy a032F, there is no oem unlock in developer options so i guess i cannot unlock the bootloader, and when i try to flash a custom firmware via odin i get an error mdm mode can't download odin. so after reading the blog post i was wondering, could the download mode be locked
Click to expand...
Click to collapse
im a newbie and i could be wrong about all this, but its been 2 days and googling has not hepled
thelite said:
im on the sumsung galaxy a032F, there is no oem unlock in developer options so i guess i cannot unlock the bootloader, and when i try to flash a custom firmware via odin i get an error mdm mode can't download odin. so after reading the blog post i was wondering, could the download mode be locked
Click to expand...
Click to collapse
Ah, ok. That makes a little more sense.
The bootloader has to be unlocked in order to flash custom firmware.
The process works like this:
Turn on OEM Unlocking in Developer Options (allows bootloader to be unlocked)
Boot device into unlock mode - starting with device off, hold both Volume buttons and plug in USB cable)
Follow device instructions to unlock (will wipe data)
Boot into system, allow system to connect to Internet to disable Knox Guard
Reboot into download mode, use Odin to flash TWRP
Use TWRP to flash custom ROM
So, if OEM Unlocking is not available, you can't do any of this, because that is the first step.
Unless you have factory restarted your device within the last week, no oem unlock means no custom firmware. You have the snapdragon variant, right?
V0latyle said:
Ah, ok. That makes a little more sense.
The bootloader has to be unlocked in order to flash custom firmware.
The process works like this:
Turn on OEM Unlocking in Developer Options (allows bootloader to be unlocked)
Boot device into unlock mode - starting with device off, hold both Volume buttons and plug in USB cable)
Follow device instructions to unlock (will wipe data)
Boot into system, allow system to connect to Internet to disable Knox Guard
Reboot into download mode, use Odin to flash TWRP
Use TWRP to flash custom ROM
So, if OEM Unlocking is not available, you can't do any of this, because that is the first step.
Click to expand...
Click to collapse
thanks for the answer, but i was wondering is there a way in which the oem unlock option can be hidden and unhidden or some way in which you can be prevented from unlocking the bootloader, because even the wipe data/factory reset is disabled, i came across this kind of devices and i was just curious is this entailed in android development or what material can you recommend if i want to know more about this
thelite said:
thanks for the answer, but i was wondering is there a way in which the oem unlock option can be hidden and unhidden or some way in which you can be prevented from unlocking the bootloader, because even the wipe data/factory reset is disabled, i came across this kind of devices and i was just curious is this entailed in android development or what material can you recommend if i want to know more about this
Click to expand...
Click to collapse
Bootloader lock doesn't prevent a factory reset. The screen you showed is recovery mode, not download mode. That's really strange, I've never seen factory reset hidden before
thelite said:
i get an error mdm mode can't download odin.
Click to expand...
Click to collapse
I think this is the clue. You have a organization managed device with an MDM lock (Mobile Device Management). MDM is used by enterprise IT departments to manage devices and can prevent bootloader unlocking as well as factory reset.
Let me guess, you bought this device used?
V0latyle said:
Bootloader lock doesn't prevent a factory reset. The screen you showed is recovery mode, not download mode. That's really strange, I've never seen factory reset hidden before
I think this is the clue. You have a organization managed device with an MDM lock (Mobile Device Management). MDM is used by enterprise IT departments to manage devices and can prevent bootloader unlocking as well as factory reset.
Let me guess, you bought this device used?
Click to expand...
Click to collapse
yes, i got this device from somebody for experiment, just to see if i can go past all this, and yes the screen i showed is a recovery mode screen, i was showing the hidden factory reset option. any help how i can go about this
thelite said:
yes, i got this device from somebody for experiment, just to see if i can go past all this, and yes the screen i showed is a recovery mode screen, i was showing the hidden factory reset option. any help how i can go about this
Click to expand...
Click to collapse
I think your only option is to find out which company the phone belonged to before. If they removed it from their fleet, they can probably remove the MDM lock. This is actually pretty common - enterprise managed devices will be "retired" from fleet service and sold without being properly decommissioned - they're wiped, but the IT department doesn't remove the MDM lock.
They might or might not unlock it for you, but it doesn't hurt to ask.
V0latyle said:
I think your only option is to find out which company the phone belonged to before. If they removed it from their fleet, they can probably remove the MDM lock. This is actually pretty common - enterprise managed devices will be "retired" from fleet service and sold without being properly decommissioned - they're wiped, but the IT department doesn't remove the MDM lock.
They might or might not unlock it for you, but it doesn't hurt to ask.
Click to expand...
Click to collapse
so technically i can't find a way around it myself, i just have to request the company
There is no way I know to bypass it.
There are lots of videos online if you Google “ bypass mdm lock android “
thelite said:
so technically i can't find a way around it myself, i just have to request the company
Click to expand...
Click to collapse
MDM locks typically can't be removed by the end user. That's the whole point - to prevent employees from using devices inappropriately and removing them from enterprise management via factory reset
Kolay gelsin hocalarım telefon kendi kendine Samsung yazısında kaldı revovery kullanamıyor bende Odin ile stok rom attı kilit açmadan
Şuan telefon indir sadece tek giriyor başka hiçbir şey açılmıyor OEM kilit ve frp kapalı
Take it easy, my teachers, the phone is stuck in the Samsung text itself, cannot use revovery, I have a stock rom with Odin, without unlocking it Now the phone is downloading only one entry nothing else does not open OEM lock and frp is off