Good morning,
I want to install a custom rom but I'm not able because I haven't the "OEM Unlock" option in the developer area, I try everything that I found in Google like change the date at the calendar for example but doesn't work.
Someone have some other options to display the option? I have to wait 8 days to see the option automatically?
I already rooted the device
Thank you!
Pretty sure these old Samsung devices just had unlocked bootloaders by default
Related
I'd like to root my phone, but it seems, there is not a complete guide for my device. I could figure out I need to have the OEM unlock option enabled, but the menu item is missing from my dev. option menu. Searched the entire net for info, but it seems, there is no option. It is an ON7 2016 bootloader G6100ZHU2CRI8 with msm8953 chipset. I've tried date change, Miracle box 2.58 - non of the FRP reset options worked in it. Can we even unlock bootloader on Snapdgragon? Looking forward to your answers. Thank you.
Hi, Everyone
I'm new to this community. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options tied to improving privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If there is any other information I can provide to get some help with this problem, please add it to your reply. Excited to hear from the community.
Did you figure it out yet (I hope so)?
I came across your question on googling the missing OEM-Unlock on my device^^
For me basically steps 6-13 from here brought up the missing option in developer options.
After unlocking I had to do this again, to be able to flash the custom recovery
The toggle to enable OEM unlocking under developer options is completely missing, and nothing seems to make a difference.
The widely-shared workaround involving changing the date didn't work.
Waiting seven whole days didn't work.
Is 168 hours uptime with no reboots necessary?
Is a Google account necessary?
Is a Samsung account necessary?
Could someone please just explain the exact set of conditions necessary to enable this option?
try connecting to wifi
SiliconValleyPondScum said:
The toggle to enable OEM unlocking under developer options is completely missing, and nothing seems to make a difference.
The widely-shared workaround involving changing the date didn't work.
Waiting seven whole days didn't work.
Is 168 hours uptime with no reboots necessary?
Is a Google account necessary?
Is a Samsung account necessary?
Could someone please just explain the exact set of conditions necessary to enable this option?
Click to expand...
Click to collapse
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Is this an LTE variant?
-SpaceCowboy- said:
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Click to expand...
Click to collapse
I also have Samsung Galaxy Xcover Pro (SM-G715FN) with Android 11. On my phone the `OEM Unlocking` option appeared after using phone for 7 days and I successfully rooted the phone. I had Google account, Samsung account and automatic software updates enabled, but I don't know if it was neccesary.
d5sword said:
I also have Samsung Galaxy Xcover Pro (SM-G715FN) with Android 11. On my phone the `OEM Unlocking` option appeared after using phone for 7 days and I successfully rooted the phone. I had Google account, Samsung account and automatic software updates enabled, but I don't know if it was neccesary.
Click to expand...
Click to collapse
thank you, i trie and coment you
The following worked for me:
1. Factory reset
2. During tablet setup:
a. connect to wifi
b. Sign in to Google and Samsung accounts
3. turn on developer mode
4. the OEM Unlock option appears!
I did not have to reset the tablet date/time.
Can I get someone with a Tab S6 to confirm the above?
---
Edit:
Here's the relevant software info:
One UI Version: 3.1
Android Version: 11
Kernel Version: 4.14.190-21627332-abT860XXS3CUG1
Build Number: RP1A.200720.012.T860XXS3CUG1
-SpaceCowboy- said:
I would like to find the answer, I am with this problem in a galaxy xcover pro that I need to root to use development apps, no method worked for me and even worse it was automatically updated to Android 11, I have even less hope that it will work
Click to expand...
Click to collapse
TLDR: Just enable Wifi.
I bring you the answer today
I'm with a XCover Pro running Android 12 already (G715FNXXUADVG4). Before connecting the device to the internet, I absolutely wanted to prevent any further updates, as I'm going to use some variant of the xposed framework and higher Android versions make things more complicated.
So I disabled automatic Updates in the developer options (and everywhere else I could find anything update-related).
I even removed almost every app, including update apps, using this debloat script: https://github.com/khlam/debloat-samsung-android .
I have no Samsung account nor Google account.
The option to unlock the bootloader was still missing.
I changed the date from 2022 to 2023 (for some reason it was a couple of months off). I restartet the phone.
Still no option to unlock OEM.
The device told me there were updates available now (for whatever reason). There is not even a sim card inserted, yet.
Then I enabled wifi. Couldn't tell if any updates happened, didn't notice anything going on.
And then the magic happened ...
"Unlock OEM" appeared INSTANTLY in the developers menu, just after the device connected to wifi / internet.
That's it.
A friend of mine asked me to install a newer Android in his Samsung Galaxy Tab 4.0 3G (SM-T531, codename matisse3g), which is pretty old and still has a Kitkat install. So, as I have some experience with Android hacking, I got the tablet, gave it a factory reset and unlocked the Developer Options tab in the Settings app. All tutorials that I found, say that I should turn on the OEM Unlock option to unlock the bootloader, but there isn't this option in Developer Options tab.
I tried several workarounds, like setting a earlier date and time, turning off the Auto Update option (tip: there isn't this option too)... But I was unsuccessful. There is not an OEM unlock option, neither a Auto Update option in Developer Options tab, in the Settings app.
Any ideas would be welcome. BTW, I'm a Linux user, so I don't have any Windows here (besides into a Virtual Machine) to use Odin.
Cheers,
Ricardo.
Hi, these old Samsung devices don't have unlock bootloader option. Just install a custom recovery (TWRP or lineage - for this last one, to flash it through odin, you need to pack the renamed recovery.img file into an uncompressed .tar one with a random name)
Hi everyone, i’m having an extremely weird issue with my Samsung J5 Prime (SM-G570Y/on5xelte). First of all; sorry for bad english, this post will be a bit long.
So i want to unlock OEM, to install custom recovery and custom ROM (and being able to login with google account from gms (Google Play Service app)).
i activate developer options.
Then go to Settings > Developer Options, but OEM Unlock is missing (i did'nt have the screenshot of the settings), i already try every method to reappear it but nothing worked.
Trying my luck, im rebooting my phone to download mode, on there i didn’t see any text that says OEM Unlock, i tried to flash OrangeFox Recovery using ODIN. And suprisingly it worked, i even double-checked it by actually booting to recovery. i did'nt expect it to work though...
Then i install RadicalQuack Custom ROM, and do some root-level customization.
But as soon as i try to login Google account from Google Play Service (this didnt affect web login or any other login) on Stock/Custom ROM, and reboot the phone... my phone was FRP locked, i was shocked because my configuration isn’t even backed up.
I have to flash stock rom in download mode, get to setup, login google, remove the account, then i can get rid of FRP lock.
And at this point is where everything is confusing.
If i use stock rom without any changes, the "OEM Unlock" option is'nt appearing at all.
But if i use custom ROM (in this case i use RadicalQuack), the "OEM Unlock" option Appears (until i remove "ro.frp.pst" in build.prop)
So i can do anything but CANNOT login using Google Account from Google Play Services or get FRP locked and All data destroyed.
Now my question is, is it safe to enable "Unlock OEM"? Because i dont know if OEM Unlock is currently enabled or not, i dont know how to check if the bootloader is actually locked, i dont want to get locked forever on samsung stock and bloated shtt again.
PS:
Somehow... i can login Google account without getting FRP locked by:
Unlocking OEM (on the custom ROM ofcourse, since it won't be visible on stock ROM anyway...)
and removing "ro.frp.pst" (especially "ro.frp.pst=/dev/block/persistent") on /system/build.prop, /system/vendor/build.prop, /vendor/build.prop
what did you do?
Hiii, what did you do? I need to unlock oem un my j5 prime
Same Problem Happens to me But Now How you use custom rom without getting frp lock please Tell I Have Also J5 prime And Same Happens to me also I need to flash stock rom from which my custom rom get erased