I got the device today, but OEM Unlock is missing from Developer Settings. I tried the date and time hack, but it didn't work. I put it 15 days back. Then a month back. Then I put it to the earliest possible date, January of 2004. When I reboot the device, OEM Unlock still does not show up.
How do I get past this? I can't even proceed to anything without activating OEM Unlock.
T220, OEM Unlock won't show up even after date trick.
Ok I got OEM Unlock to show up. Follow these instructions EXACTLY.
Factory Reset Device (Sorry but this will happen when you unlock anyway, and has to be done first.)
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later).
I did nothing else, didn't even enable dark theme.
Enable developer options and disable automatic system updates from there.
Connect to a WiFi network.
DISCONNECT from internet after a few seconds. You'll see it trying to update things in the pull down menu, disconnect from internet, you don't want it to update anything. It just needs to be connected long enough to update the day and time to the correct day and time, and register your device. If it didn't work, it didn't register your device yet.
For me, it did get to the point where there was a notification that said, "Finish setting up your Tab A7 Lite." DO NOT finish setting anything up, but do make sure internet is disconnected. Ignore notification, but you should see that.
Disable automatic software update. Settings > Software Update > turn off.
Go to General > Date and Time settings and select for the time to be set manually (don't touch time zone). Set the date to be EXACTLY 10 days BEHIND from your current date.
Go to Developer Options, and OEM Unlock should be there!
If it still doesn't work, you may have to go to extreme measures, but I didn't have to. But first just make sure you did the above steps EXACTLY.
Go here for extreme measures if you did EXACTLY like above and still didn't work (my instructions above were a bit different) https://forum.xda-developers.com/t/a7-2017-w-binary-9-rmm-state-unlock.4057831/post-82049513
xbt- said:
Ok I got OEM Unlock to show up. Follow these instructions EXACTLY.
Click to expand...
Click to collapse
Does this technique work for any T220 in any region? I'm thinking about getting the T220, but I read in another post by @tom.android that Samsung doesn't allow OEM Unlock in North America.
Update - Can confirm that this works! Thanks xbt-!
Related
Hi.
Before my question I'll write about my experience because I am sure it will help many many people.
As many of you, I always ROOT my smartphones.
Nowadays, the new phones, they come with this new technology to avoid root and other things called " OEM Lock " under the Developer's Options.
Following every step provided in the root guide for you phone, the new step to enable OEM Unlock under Developer Options
is a must!
The only thing that they don't say is that you MUST leave OEM Unlock ALWAYS ENABLED during and AFTER the root, and not only during the root
process.
Not knowing that, what did I do? Right After rooting my Samsung Note 5 I disabled the OEM Unlock. When I restarted the smartphone, it got into something called FAP Protection Black Screen where you are not able to leave not even if you try to root the phone again with the img file!
If you get in the FAP Protection Screen, like I did, despair will take over, I promise! And Google will not help you!
Is there a solution?
I found one, but not in any Google Page.
You need to download the firware img file for your phone, exactly same model,
in my case it was SM-N920G (Samsung Note 5), and for your specific country. Luckily for my phone it was not so hard to find, just hard to download (1,7GB with average 15 kB/s speed!). You will find different versions, some related to a Phone Company Operator that your country has, other related to no operator at all (sure I chose that).
After you get the firware file, just use Odin with that file to flash the phone, just like how you did to root the phone, but now, instead of using the root img file with Odin Software, you'll use the firmware file. That will not only solve the problem and give you access to your phone again, but in my case the Operator Flag disappeared and the data and apps installed miraculously were intact! I was pretty sure I was supposed to lose everything, but that didn't happen!
I'm sure what I wrote above will help many desperate people out there!
Now, my main question here:
You can never disable OEM Unlock in your life, with a rooted phone, period! So, it's really dangerous to leave the developer options enabled, allowing anyone that uses the phone to change it, even if by accident. In my case, as another example, besides rooting my phone, I rooted my father's phone too (because it was previously mine). I'd like to avoid by any means that by any chance me, or my father, disable to the OEM Unlock.
So, my question:
If I disable the Developer Option in order to "hide" it, will the changes that I did inside it remain working perfectly? I'm afraid that if I disable the developer options, somehow, it might take every option inside it back to the "default", just like it was before I enabled the developer Options, meaning in this case, OEM Unlock would get DISABLED again!
Is it safe to disable the Developer Options when OEM Unlock is Enable and MUST Remain like that?
Thank you.
Lost a night of sleep for the same problem with a Samsung S8.
This should be added to *every* mod guide.
In my case was worse too...if you root the phone and wipe data, when you open first time developer option you'll find "OEM Unlock" disabled (but I assume it's enabled at bootloader level). So when I check / uncheck it I doom my phone to lock on next restart...
how to get to boot menu on htc u12 plus, smallest width setting got adjusted wrong in developer options and power got cycled, all I can see on lock screen are 1,2 and 3 cant unlock, any ideas?
Hi. I am using Samsung A5 2017 (Android 8.0) and have reset it and set up as new device. I then do the date trick hoping to show the OEM unlock option but it doesn't work. I am not sure I am do it correctly.
- Change date to previous month, turn off auto update in Developer option.
- Manual check for update so that it shows the checked date as the date I set, Restart device
- Check the OEM unlock
Someone says after reboot, i should turn on auto update. I follow this advice and check for update with automatic update setting. My phone then show available update. But still I can't see OEM option.
What can I do now if I don't want to wait for 7 days?
Does anyone have solution?
I've been in this kind of situation before
I tried to factory reset via recovery, boot the phone as normal but don't log in to the Samsung account. Then I wait for about 1 week (I'm not sure this thing is important because I only try it once) and viola the OEM unlock appear
good luck
ntd252 said:
Does anyone have solution?
Click to expand...
Click to collapse
So far the confirmed solution is this, as someone wrote in another post which I forgot and found it by trial and accidentally also. Just flashed the Australian version of the stock SM-A520F ROM (country code is XSA) via Odin. Yesterday morning I tried to flash this stock ROM after waiting for more than 2 weeks in desperation... :silly:, and voilà, suddenly the OEM unlock option shown up directly in the Developer Option setting without have to waiting for days... But I reset all settings to the factory settings since I want to flash a new custom ROM after that, I don't know if you can do it without the need of factory settings reset, you can try then... :good:
From the time I wait for OEM to be unlocked, I can tell there's no way without waiting. Be sure you guys have factory reset, log in google account (no need samsung account), check for update (to have device registered), then wait. Af thẻ 168 hrs waiting, you should close settings and re-open settings again, go checking for OEM toggle.
ntd252 said:
Hi. I am using Samsung A5 2017 (Android 8.0) and have reset it and set up as new device. I then do the date trick hoping to show the OEM unlock option but it doesn't work. I am not sure I am do it correctly.
- Change date to previous month, turn off auto update in Developer option.
- Manual check for update so that it shows the checked date as the date I set, Restart device
- Check the OEM unlock
Someone says after reboot, i should turn on auto update. I follow this advice and check for update with automatic update setting. My phone then show available update. But still I can't see OEM option.
What can I do now if I don't want to wait for 7 days?
Click to expand...
Click to collapse
Solution is on youtube.
ntd252 said:
Hi. I am using Samsung A5 2017 (Android 8.0) and have reset it and set up as new device. I then do the date trick hoping to show the OEM unlock option but it doesn't work. I am not sure I am do it correctly.
- Change date to previous month, turn off auto update in Developer option.
- Manual check for update so that it shows the checked date as the date I set, Restart device
- Check the OEM unlock
Someone says after reboot, i should turn on auto update. I follow this advice and check for update with automatic update setting. My phone then show available update. But still I can't see OEM option.
What can I do now if I don't want to wait for 7 days?
Click to expand...
Click to collapse
If you still haven't gotten the OEM toggle, try these steps. These have worked for me plenty of times:
https://forum.xda-developers.com/showpost.php?p=82049513&postcount=6
did you find a solution?
---------- Post added at 07:49 PM ---------- Previous post was at 07:49 PM ----------
nevertechdose said:
If you still haven't gotten the OEM toggle, try these steps. These have worked for me plenty of times:
https://forum.xda-developers.com/showpost.php?p=82049513&postcount=6
Click to expand...
Click to collapse
tried that solution, didn't work
The same thing happens to me with my a520f adroid 8. wait 3 times 7 days and nothing I did factory reset wait again 7 days and nothing now flashed and I'm waiting. The trick of the date never worked for me; (
I hope someone knows the solution..
Hello,
I have unlocked the bootloader of my A10 and it says so when booting up. However, the OEM unlocking option in developer settings has dissapeared completely, not even appearing greyed out.
The problem is that I cannot flash TWRP because the phone says it supports only official binaries. What should I do.
SM-A105FN unlocked
My CSC:
PDA A105FNXXU4BTI2
CSC A105FNOXM4BTI2
Hi, try reading this:
https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
crisnar said:
Hi, try reading this:
https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Click to expand...
Click to collapse
I did use that tutorial as well, and after relocking my bootloader to start over again, the OEM Unlocking options isn't even there anymore
dradudi_rom said:
I did use that tutorial as well, and after relocking my bootloader to start over again, the OEM Unlocking options isn't even there anymore
Click to expand...
Click to collapse
In the post it says to proceed like this:
afaneh92 said:
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Click to expand...
Click to collapse
Is what you did?
Otherwise you can try like this:
1. Disable Automatic date and time and set the date back 10 days
2. Restart the phone
3. Set the automatic date, if you are connected to a network, or manually reset it to the correct date
4. Restart the phone
Or you can wait a week and the OEM Unlocking options reappears
crisnar said:
In the post it says to proceed like this:
Is what you did?
Otherwise you can try like this:
1. Disable Automatic date and time and set the date back 10 days
2. Restart the phone
3. Set the automatic date, if you are connected to a network, or manually reset it to the correct date
4. Restart the phone
Or you can wait a week and the OEM Unlocking options reappears
Click to expand...
Click to collapse
Man, I already did everything you said, I told you
Its ok
dradudi_rom said:
Hello,
I have unlocked the bootloader of my A10 and it says so when booting up. However, the OEM unlocking option in developer settings has dissapeared completely, not even appearing greyed out.
The problem is that I cannot flash TWRP because the phone says it supports only official binaries. What should I do.
SM-A105FN unlocked
My CSC:
PDA A105FNXXU4BTI2
CSC A105FNOXM4BTI2
Click to expand...
Click to collapse
You have no problem bro, OEM might be hidden but it's stiched on. Even if you factory reset it it will remain the same. If you insist in finding it, Download a software update or press check for updates then quickly toggle your OEM
Hello recently I tried to root my phone, wanting to fix ghost touch, I did something wrong and the phone stopped working, "Only official binary blah blah blah ..." popped up during startup, I decided to reinstall the official stock, the phone started working normally, even ghost touch repaired, I looked at the Root Checker application if I have root, it turned out not, which is all right, but when I want to add the card to google pay or open McDonald's applications, I get a message that the phone is rooted or was somehow rooted modified, what can I do in such a situation, please help me, I tried to install other stocks from other operators and restore the phone to factory settings: _ (
I saw one solution, probably in this forum where someone wrote to enable OEM Unlock and USB Debugging then disable and enable again, something like this, but I don't see OEM Unlock in the developer option, I know that with a failed root attempt, I somehow unlocked this option, but I don't remember how and I prefer someone to help me as best as he can, because I don't want to break anything anymore, I just want Google Pay to start working for me
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware
But I use official firmware from some Samsung firmware site, i think my bootloader is locked, anyway do you have any solves to make work google pay?
I tried to unlock OEM but this solution with data & time doesn't work for me.
Hey, when I go to Google Play Shop there is an information that my device isn't certified, I tried to register my ID Device and still doesn't work can It be a problem, because of that Google Pay doesn't work?
syonox said:
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware.
Click to expand...
Click to collapse
If i wait 7 days OEM option should unlock automatically?
Is it good idea to root this device correctly and use magisk to make google pay work good or for example root this device and then unroot to make work google pay?
Eco24 said:
If i wait 7 days OEM option should unlock automatically?
Click to expand...
Click to collapse
before you do this if odin says you are in custom mode backup all your data before doing this. no it wont automatically, first you have to go to odin mode and hold up for a bit until the screen shuts and shows the question (do you wanna lock your bootloader) you select yes once done if you are on custom it will bring up only odin mode before anything thats where u flash firmware, now that should get rid of the root, and then if u wanna disable oem connect to wifi disconnect date and time unselect automatically and go 7 days ahead and the option will appear.
How to check if i have custom mode and what i have to hold up?? please explain better because i don't know what i have to do
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.