'Only official released binaries are allowed to be flashed' - After OEM Unlock 1 Wk.

[xDreDz]

Ah ok. Not really fixed completely though... if you flash twrp, etc. and there's no oem toggle afterwards you can still end up in jail on reboot.Samsung instituted the timer of course, but what goes on behind the scenes isn't quite as clear. Check out the OEM Unlock and root threads for steps/process and more info.

Im on Renovate Ice btw. And theres a guide about that next problem youre saying

 

[GODSPD]

Im on Renovate Ice btw. And theres a guide about that next problem youre saying

i got into jail after i switched from Renovate to Dr.Ketan rom... after my first reeboot it was jail time... i still have a few days till my oem lock returns so id gladly read on on some proven guides to install a new rom without any issues...

 

[xDreDz]

i got into jail after i switched from Renovate to Dr.Ketan rom... after my first reeboot it was jail time... i still have a few days till my oem lock returns so id gladly read on on some proven guides to install a new rom without any issues...

Well, I didnt have that issue and its on my first try. I just followed the TWRP steps then next,the RIce rom. I didnt have any issues.

Used this for TWRP
https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036

 

[cdnsnOw]

Trying to compile as many users who have faced the same issue and to get some data to find a work around.

SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.

Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.

This is my experience and now have the official binaries issue.

I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.

I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.

So the plot thickens.

Will this work on the Canadian unlocked note 8

 

[sefrcoko]

Will this work on the Canadian unlocked note 8

Will what work?

 

[carlosmedia]

Guys I think it has to do with RMM STATE=PRENORMAL in Download mode
Edit: At least for me, I flashed a carrier UK Firware and it popped out of nowhere when in DL mode

 

[cdnsnOw]

Will what work?

Flashing a different country firmware on my note 8 without turning it I to a paper weight

 

[sefrcoko]

Flashing a different country firmware on my note 8 without turning it I to a paper weight

Ok, that post was regarding firmware for N950F, which is Exynos. Canadian Note 8 is Snapdragon, so you can't flash that particular one.

 

[OptimuSlime]

Sounds like V3 Bootloader in N8 locks up crossflashing and downgrading. Expect same V3 soon for S8 and S8+ and avoid!

Dev Options has Auto Update Toggle!

 

[shadowsami4]

Hi everybody ! I'm sorry that we are all in there to discuss about this problem ! Cuz of a phone that used to run on OPEN SOURCE OS !
This is my case ! i've got some questions too if someone can answer.

I was on the aurora rom v4 with september patch. Yesterday i've tried to update with (full wipe) to alexega on bra2 base
First boot okay no problem with root etc ... Decided to reboot to flash viper4android.
AND there it is... " Only official s*** are allowed to be flashed "
So decided to flash stock rom (september one)
And now i can't flash any custom binaries even if my bootloader, modem etc.... are from the AQJ1 build of september.
No oem unlock button in dev options

So there are my questions !
1: Why i can't flash custom binaries even if my fastboot shows me " OEM LOCK OFF" "FAP LOCK OFF"
2: Will i need to keep my phone power on during 168h without any reboot ? to get back that oem button ?
3: Why i've got this problem ? That only concern december and january patches ?

Thanks for reading and maybe your answers ! That's a shame for sammy .... maybe we gonna get closer and closer of apple with this kind of politics

 

[sefrcoko]

Hi everybody ! I'm sorry that we are all in there to discuss about this problem ! Cuz of a phone that used to run on OPEN SOURCE OS !
This is my case ! i've got some questions too if someone can answer.

I was on the aurora rom v4 with september patch. Yesterday i've tried to update with (full wipe) to alexega on bra2 base
First boot okay no problem with root etc ... Decided to reboot to flash viper4android.
AND there it is... " Only official s*** are allowed to be flashed "
So decided to flash stock rom (september one)
And now i can't flash any custom binaries even if my bootloader, modem etc.... are from the AQJ1 build of september.
No oem unlock button in dev options

So there are my questions !
1: Why i can't flash custom binaries even if my fastboot shows me " OEM LOCK OFF" "FAP LOCK OFF"
2: Will i need to keep my phone power on during 168h without any reboot ? to get back that oem button ?
3: Why i've got this problem ? That only concern december and january patches ?

Thanks for reading and maybe your answers ! That's a shame for sammy .... maybe we gonna get closer and closer of apple with this kind of politics

1-Because you are in jail now.
2-No, just wait 7 days. Reboots don't matter when in jail.
3-You may have rebooted without checking to see if OEM Unlock was toggled...If so then it would mean jail because you had already flashed something custom. Normally you would have to toggle it again or wait 7 days for it to appear before rebooting.

 

[shadowsami4]

1-Because you are in jail now.
2-No, just wait 7 days. Reboots don't matter when in jail.
3-You may have rebooted without checking to see if OEM Unlock was toggled...If so then it would mean jail because you had already flashed something custom. Normally you would have to toggle it again or wait 7 days for it to appear before rebooting.

Many thanks ! that's approximatly what i've thought.
So last one, because i'm a compulsive flash o maniac. What will i have to do ? in order to flash as i want when i want, without waiting 7 days each time ?
Flash a custom kernel will be the solution ? And if i do the last update of january in official way, i'll be able to root and flash custom stuff anyways ?

Sammy did something very horrible with that thing, on my last notes phones i was able to tick one time the oem unlock and it stood for ever

 

[carlosmedia]

Hi everybody ! I'm sorry that we are all in there to discuss about this problem ! Cuz of a phone that used to run on OPEN SOURCE OS !
This is my case ! i've got some questions too if someone can answer.

I was on the aurora rom v4 with september patch. Yesterday i've tried to update with (full wipe) to alexega on bra2 base
First boot okay no problem with root etc ... Decided to reboot to flash viper4android.
AND there it is... " Only official s*** are allowed to be flashed "
So decided to flash stock rom (september one)
And now i can't flash any custom binaries even if my bootloader, modem etc.... are from the AQJ1 build of september.
No oem unlock button in dev options

So there are my questions !
1: Why i can't flash custom binaries even if my fastboot shows me " OEM LOCK OFF" "FAP LOCK OFF"
2: Will i need to keep my phone power on during 168h without any reboot ? to get back that oem button ?
3: Why i've got this problem ? That only concern december and january patches ?

Thanks for reading and maybe your answers ! That's a shame for sammy .... maybe we gonna get closer and closer of apple with this kind of politics

Have you checked if your fastboot screen showed "RMM state: prenormal"? thats probably the cause
Anyway, all the people I saw reporting the missing OEM unlock buttom at dev options said that they had it back at the 7th day of uptime, so yes thats the only option you can try for now.
As for why, no one seems to know what that RMM thing is really for or why Samsung just silently put it there.

 

[ahmedfaisalsiddiqi]

Someone seems to have found a solution and its working for ppl with note8. Haven't confirmed it myself.

Hello everybody. I got interested about this problem since my friends @Yahia Angelo and @corsicanu got the "Only official released binaries are allowed to be flashed" problem, so I decided to search deeply about this. Find out that this problem isn't related to FRP/OEM Unlock (even if enabled same problem comes), but to a new prop that you can see in Download Mode (RMM State: Prenormal). By searching in system, seems this prop is related to a new "thief" protection Samsung added in latest firmwares. Let's make an example: you get the device, setup Google Account, all good... then someone steals the device and wipes it... ok. After wipe he boots, but he can't pass the setup without internet, and when he connects to internet it asks for your Google account, since your account is saved in FRP partition, so he can't setup. This RMM State is more than that simple FRP, as it doesn't allow him to flash custom binaries to remove FRP. So now let's cut to the chase: who still doesn't have this RMM lock can avoid to get the device locked by following these two simple steps:

1. In build.prop, make sure "ro.security.vaultkeeper.feature" property is set to 0, like this:


2. Remove Rlc app. To do this go in "/system/priv-app" folder with a root file manager or with twrp file manager and remove "Rlc" folder.

For those who unfortunately has RMM State set to "Prenormal", as this user reports, seems that by keeping your phone running without shut it off/reboot, at a certain device running time value RMM State prop will set again to "Normal", so you can flash custom binaries again, if it works to you make sure to follow the above steps to not get locked again, I'll keep you guys updated about this when there will be news.

EDIT:
In attachments now you can find a zip that does the job for you. So when RMM State is set back to "Normal", flash a custom recovery and then flash the zip below to avoid lock again

 

[sefrcoko]

Many thanks ! that's approximatly what i've thought.
So last one, because i'm a compulsive flash o maniac. What will i have to do ? in order to flash as i want when i want, without waiting 7 days each time ?
Flash a custom kernel will be the solution ? And if i do the last update of january in official way, i'll be able to root and flash custom stuff anyways ?

Sammy did something very horrible with that thing, on my last notes phones i was able to tick one time the oem unlock and it stood for ever

Overall, just toggle OEM (or wait 7 days for it to appear, then toggle it). After that you can flash what you need (twrp, root, etc.) as per instructions in those threads. Once you boot for first time after that, make sure OEM Unlock is toggled before reboot again to avoid jail. If OEM toggle isn't there, you must wait 7 days for it to appear before you can toggle and reboot again.

There's also a new suggestion in the oem unlock thread that involves removing rlc and changing build.prop to ensure OEM toggle no longer disappears once unlocked, but I haven't tried it yet myself.

Long story short, once OEM is unlocked you should be fine but yes you must be more careful than with previous Sammy devices like Note 4. A lot can depend on the specific rom, kernel, and/or root method because each have a lot of factors and no one fully understands what's going on behind the scenes. Some have no issues, while others reported dissappearing oem toggle after flash, etc. Be sure to read up on the threads related to what you are flashing

 

[shadowsami4]

Thanks all ! in approximatly 1 h my phone will be free again ! i'll try to do my best for keeping him out of jail forever now ! it seems that we have a solution now

Flashing twrp and RMM patch without rebooting and full wipe and format data before. And then i think i'm gonna try a custom kernel and find a rom with no oem toggle problem ! Do you know one ?

 

[ppelao3k]

if I have this message in download mode --- 'Only official released binaries are allowed to be flashed' after having installed official CRB7 --- can I flash official AQL5 ROM to go back to version 7 and thus be able to install TWRP ??

Please advise before doing so, as I understand in the state that is today, I must wait a week to install something in download mode ... is it correct?

If I make a mistake without asking, I could be without a phone for a week and I would have to commit suicide ... hahaha

Thank you.

 

[Geekser]

Overall, just toggle OEM (or wait 7 days for it to appear, then toggle it). After that you can flash what you need (twrp, root, etc.) as per instructions in those threads. Once you boot for first time after that, make sure OEM Unlock is toggled before reboot again to avoid jail. If OEM toggle isn't there, you must wait 7 days for it to appear before you can toggle and reboot again.

There's also a new suggestion in the oem unlock thread that involves removing rlc and changing build.prop to ensure OEM toggle no longer disappears once unlocked, but I haven't tried it yet myself.

Long story short, once OEM is unlocked you should be fine but yes you must be more careful than with previous Sammy devices like Note 4. A lot can depend on the specific rom, kernel, and/or root method because each have a lot of factors and no one fully understands what's going on behind the scenes. Some have no issues, while others reported dissappearing oem toggle after flash, etc. Be sure to read up on the threads related to what you are flashing

Your comments are correct, after flashing TWRP (after waiting 7 days for OEM unlock to come back) it is important to flash the RMM State fix before you reboot your phone. Otherwise, there is a good chance that the phone could get locked again. There is a link a few posts back to the RMM State fix - or you can go to the original thread found here: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22

I have done this and most if not all of the new roms out there have the RMM state fix included in them. If you try flashing a rom that doesn't have the fix - and you haven't flashed the fix yourself, you run the risk of being put back into the "Pre-Normal" state again and being locked out for another 7 days.

 

[galaxynote2]

After getting out of jail and enabling OEM Unlock, flashed TWRP and I've ended up with the official binaries error again, this time without being able to put the device in download mode. I finally got into download mode to flash my stock rom again, and guess what? OEM Unlock gone again. 7 wasted days. I'm starting to hate this phone. For real, I didn't had problems with ANY of my Samsung phones, yet this one is the worst I've ever bought.

 

[sefrcoko]

After getting out of jail and enabling OEM Unlock, flashed TWRP and I've ended up with the official binaries error again, this time without being able to put the device in download mode. I finally got into download mode to flash my stock rom again, and guess what? OEM Unlock gone again. 7 wasted days. I'm starting to hate this phone. For real, I didn't had problems with ANY of my Samsung phones, yet this one is the worst I've ever bought.

Sorry to hear that. What happened between flashing twrp and the point where you had the binaries error message?