[INFO] [Exynos] Note 8 - Exynos - N950F/FD - OEM Unlock Option available?

Mar 14, 2015
39
15
0
Dublin
I got a Note 8 Unlocked from O2 UK, but I actually live in Ireland so I was trying to get the XEU ROM/Version on it.. after trying several times my SW was still XEU/XEU/O2U. I din't know back then that many people have failed trying to get the third option changed. So I've decided then look for this "OEM Unlock" after seen someone mentioning it.. then flashed XEU and was still showing up XEU/XEU/O2U. I decided then would leave it that way and use it as it was.. but then I finish setup my phone and tried to setup Android Pay and it didn't work as FRP/OEM are both OFF and comes up with a message that Android isn't secure or something like that .. then tried to flash again, and again, and again and to get the damn "OEM Unlock" again (so I could disable it), cause right now isn't even showing up on my Developer Option anymore!

..so I am the team that think the isn't a pattern/standard on it, is has to be some crazy settings that Samsung might have confused during building up this Multi/Same CSC for everyone!!
So now I have "FRP/OEM (both OFF)" which should't void my warranty as I haven't tried rooting it or anything like that, but I can't simple use Android Pay, and I am afraid that this "OEM Unlock" will never show up again on my Developer Option so I can toggle it back OFF, and leave it the way it was before.

Even tried some adb comands, but hence Samsung uses Odin rather than adb, it makes life even harder!
 

ALEXRUSS55

Senior Member
Sep 24, 2009
101
5
0
Finally got my OEM unlock option yesterday after 6 days... Tried flashing Ketans rom and all went well flashed fine booted great and installed all my apps with titanium backup. But then I rebooted and got only official binaries can be installed on red letters and got soft bricked.... Flashed a stock rom to recover my device, and now OEM toggle is gone, even though oem lock is OFF in recovery menu. Tried to flash TWRP again in this state and red letter show up in recovery saying I can only flash official binaries, so it's a fail in ODIN.... I guess I have to wait 7 days again and have a shot at it. If not then I will return it to Amazon.

I bought 1000 dollar device but am not going to flash whatever, and whenever I want? Then it's not truly unlocked...
 

CACV

Member
Nov 21, 2013
23
2
0
Asuncion
ALEXRUSS55 we already advertise this in so many post, if you don't see the oem unlock toggle when you flash ketan's rom, you have to wait 7 days to show up again

Regards
 

FX-32

Member
Oct 9, 2016
6
1
0
I bought one from never-msrp on tuesday, arrived today and NO Oem Unlock. Taiwan version. What is the other version besides Taiwan does never-msrp has?
 

krabman

Senior Member
Sep 22, 2008
2,982
926
183
Gents, make sure you follow the working instructions that have been posted several times already. While ridiculous in their many steps some of which must be unneeded (but we don't know which) that process works. No one who has followed it to the letter and installed ketan's rom has failed. For the time being do not install a CSC. Make sure your sims are out during the install.
 
  • Like
Reactions: kenpaci

ALEXRUSS55

Senior Member
Sep 24, 2009
101
5
0
Gents, make sure you follow the working instructions that have been posted several times already. While ridiculous in their many steps some of which must be unneeded (but we don't know which) that process works. No one who has followed it to the letter and installed ketan's rom has failed. For the time being do not install a CSC. Make sure your sims are out during the install.
I followed them to the T, everything worked great, I thought to myself wow finally something easy, since struggling with Galaxy s4 att and galaxy s6 international.. The problem was when I decided to reboot after I had been using it for a few hours, then I got the red letters.
 

krabman

Senior Member
Sep 22, 2008
2,982
926
183
You're sure you followed the step by step instructions exactly? I have done it three times and I just got a message from one of the guys who did it telling me he is on day four and working fine. Haven't heard from the others that did the exact procedure but none of them have reported back as having a problem. Can you please post you exact procedure? I actually flashed the last rom I did just to do it because another had the phone running for days rooted but then switched roms and ran into binaries. It turned out he didn't format on the second go around. At any rate if you did follow the blow by blow then you're first and thats not good. I had been thinking we had a working procedure.
 

zhengsmall

Member
Feb 24, 2009
32
2
28
Singapore
I followed them to the T, everything worked great, I thought to myself wow finally something easy, since struggling with Galaxy s4 att and galaxy s6 international.. The problem was when I decided to reboot after I had been using it for a few hours, then I got the red letters.
The point is that if oem unlock toggle went missing after you flash ketan's rom, you have to wait another 7 days without reboot for it to show up again, or you may (very likely) end up in bootloop.
 

ALEXRUSS55

Senior Member
Sep 24, 2009
101
5
0
The point is that if oem unlock toggle went missing after you flash ketan's rom, you have to wait another 7 days without reboot for it to show up again, or you may (very likely) end up in bootloop.
Will try again after the second 7 day wait, still don't understand why i did not get the permission options to either skip or install. Very excited to once i got this to boot, but will wait before reboot like you said if these options do not appear on the second time around. Thanks
 

ZeroDefined

Senior Member
Jul 2, 2011
118
34
58
Toronto
Nah, I did it like 10 times. When this started out we were trying various schemes to get the toggle to show and that meant flashing a lot of firmware as well as trying resets, a couple different apks and flashes one of our kind developers gave us, BLs, CSCs, etc. Tasted a lot of pain. Actually when I look back on it I might of popped the binaries more than ten times. I'm pretty sure it isn't a factor because I've been rooted, rom'ed from the time I gave up, waited what ended up being 5 days, and installed my first rom. Done it twice more since then, once with the update to the first rom and then I moved over to light rom. Still chugging along just fine.

I'm not sure why folks don't just follow the format that works? I would.
Ok cool. At least we can eliminate this theory
 

Deezy88

Senior Member
Nov 22, 2010
773
48
48
Thank you!
I haven't tried any simcard yet because i wanted to root before using it... It has an update ready to install, should I insert simcard, update and see what happens or what should I try to make OEM-Unlock to show up?
its doesnt matter that what i did and nothing happend,i still had to wait 7 days
 

lv128

Member
Jun 2, 2010
40
3
0
I just got my N950F/DS 5 days ago. The CSC says BRI and it's on AHQ9. Google account and Samsung account both logged in. A Software update was downloaded (most recent, don't remember what version) and it's been a full 5 or 5 1/2 days of leaving it powered on and intermittently charging it.
Read through a good portion of this thread and it's branches already.
As others have experienced, the OEM unlock isn't there and I've poked around download and recovery.
I started looking through the recovery logs and noticed something, maybe someone else more up on the build.prop or logs, but in the stock recovery, looking at the last_log, I found ro.oem_unlock_supported=1
and then in all the previous logs (it's around 40 - 50% in the scroll) it says ro.oem_unlock_supported=0
I'm not sure if this means anything or it's just log spam. It didn't seem to make any difference as to making the toggle appear.

If I've rebooted within this 7 day period, does that mean I'm starting over on the countdown? Do it actually need to let is come to 7 days on the Up Time counter?
I think someone at samsung likes The Ring movies too much.
 

rocketmail.com

Senior Member
Feb 2, 2010
311
106
63
Accra
I just got my N950F/DS 5 days ago. The CSC says BRI and it's on AHQ9. Google account and Samsung account both logged in. A Software update was downloaded (most recent, don't remember what version) and it's been a full 5 or 5 1/2 days of leaving it powered on and intermittently charging it.
Read through a good portion of this thread and it's branches already.
As others have experienced, the OEM unlock isn't there and I've poked around download and recovery.
I started looking through the recovery logs and noticed something, maybe someone else more up on the build.prop or logs, but in the stock recovery, looking at the last_log, I found ro.oem_unlock_supported=1
and then in all the previous logs (it's around 40 - 50% in the scroll) it says ro.oem_unlock_supported=0
I'm not sure if this means anything or it's just log spam. It didn't seem to make any difference as to making the toggle appear.

If I've rebooted within this 7 day period, does that mean I'm starting over on the countdown? Do it actually need to let is come to 7 days on the Up Time counter?
I think someone at samsung likes The Ring movies too much.
You can reboot several times, just don't factory reset.
 

Deezy88

Senior Member
Nov 22, 2010
773
48
48
can explain to me why F model does not come with oem unlock ,my supplier has tons of F model but none have oem unlock on them and it should its a F model

please can somebody answer this
 

shouren04

Senior Member
Feb 17, 2013
1,092
400
0
can explain to me why F model does not come with oem unlock ,my supplier has tons of F model but none have oem unlock on them and it should its a F model

please can somebody answer this
It's not the model, some Fs have the issue also. No one knows exactly why yet but it seems to be related to the region where the phone originated.
 

azq8ooz

Senior Member
Feb 19, 2015
67
7
0
i talk with samsung and the reason is to activate the phone in to activate it in same country


Sent from my iPhone using Tapatalk
 
Last edited: