Database Develop

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

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.

Andysmith71 said:
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.
Click to expand...
Click to collapse
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week(oem unlock was there), flashed SuperSU 2.82. When I was configuring an app to modify host(to disable ads), the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed' [emoji33]

Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.

thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.

zhengsmall said:
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week, flashed SuperSU 2.82. When I was configuring an app, the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed'
Click to expand...
Click to collapse
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.

Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
It's good we're getting to a point where we can collect data and try different approaches. It was a much darker time when we were all sitting around wondering if/when the OEM Unlock toggle would show up!
Yes, I did a wipe/format prior to flashing Magisk. One thing I haven't been doing is clearing the cache/dalvik following successful flash... is that important? I recall doing that back when I rooted my S7 Edge, but I've not seen or heard about anyone doing it since.

You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...

krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Thanks mate, been reading up there and seen the posts. Looks like Renovate has had most success so far with that method. Looks promising, fingers crossed. I've got another few more days in jail before I get the OEM unlock back.

I don't think anyone has reported a failure yet doing it that way. Still a ways to go on the testing though, It appears folks aren't all that anxious to screw up a good thing once they get up and running. The good news is if ordinary dumbassez like us can get in the smart guys should get something figured out sooner rather than later. Anyhow, good luck, if it's any consolation mine showed up in 5 days...

Andysmith71 said:
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Click to expand...
Click to collapse
Thanks for the suggestion mentioned, but what do you mean by redo the process? Or just switch off and then on the oem unlock toggle when it reappears in 7 days after the first flash(twrp and supersu) followed by a reboot(as only via reboot can I judge if it works)?
In addition, in my case the phone restarted itself when I tried to modify host to disable the annoying ads, not during configuring SuperSU.

Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device

AndiF85 said:
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
Click to expand...
Click to collapse
Hey mate, try the below mentioned method and see if it works.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse

I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk

krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Well I got out of Jail yesterday after getting back the OEM unlock for the 2nd time. This time I decided to 'play it safe' until the smart people figure out what the issues are. This method worked perfectly for me and I've now been flashing Viper, flashing extra fonts, doing backups in TWRP and generally using the phone as normal again. The current Renovate release (r95) has most of the issues fixed and is a good daily driver, also the facial recognition is all fixed and Magisk is working with no issues, I've been able to use my banking apps for over the counter purchases again, tested and all working. Here is the method that worked for me -
How to flash Renovate and not stuff up. Remove SIM card before starting (I got this from Krabman's posts so I was not going to tempt fate at this stage by leaving in my SIM card, this is just a playing safe method for now).
1. Install TWRP (I trust you all are okay with everything up to this part)
2. In TWRP, swipe right and go into menu.
3. Wipe / Format Data / Yes
4. Reboot into RECOVERY
5. Flash DM-Verity
6. Wipe / Factory reset (by swiping)
7. Flash Renovate - I chose to root with Magisk cause it works for my banking apps.
8. After flashing Renovate, allow it to boot into System.
9. Do your basic setup and then reboot.
10. Now insert SIM and continue to setup your phone, Ti and all that good stuff. Phone is now rooted and working, TWRP is all working and safe to use as normal. This is the part that I did Ti restore and flashed Viper4Android etc etc.
11. Happy days for now, until we work out exactly what the issues are.......
The only thing I did not do was to try and flash the XSA firmware (Australia Unbranded) with the S8 CSC firmware installer. Apparently another user used it and it worked for them on the Note 8, however I did not want to chance it for now. The only drawback is on Volte and WiFi calling is missing but that's not a deal breaker. I might research a bit more before I try to flash the CSCSelection_S7_S8 zip.

AndiF85 said:
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
I was in the same boat as you - if Renovate floats your boat then check out my last post, I've installed Renovate and all working nicely again... Waiting for one week then in jail for another week sucked hard!

Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk

AndiF85 said:
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Just tested that out for you, unfortunately that is the only one that does not work (Well we know Samsung Pay won't work due to KNOX being tripped). It goes through all the setup okay, then on final authentication it says "Samsung Pass is temporarily unavailable, please try again later". So that's a bit of a bummer.. I've tested Android Pay, all good, and I also use NAB pay and works with no issues as well as long as you set it up correctly with Magisk (there is a bit of a method to follow but I found a way to make it work - in case your with NAB at all).
I might make a suggestion to mwilky to see if that could possibly be fixed in the ROM as I agree it's a great feature.
Edit - That question was already asked by another user, mwilky says that it does not work the moment TWRP is flashed and not likely able to be changed. Bummer.

Soft brick
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!

bwallis said:
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
Click to expand...
Click to collapse
Use Samsung Smart Switch for that. it will tell you the region code for your phone. It could restore for you, or you could use http://fw.updato.com/, or SamFirm, to download appropriate ROM

Alright finally I'm out of jail.
About to download everything then going to attempt tonight.
Andsmith71 how have you found the rom over the past week?
Any issues?
still holding Root?
Does Bixby Voice still work?
Sent from my SM-N950F using Tapatalk

Galaxy S8 verizon - G950USQU4CRE9

Hi developers.
Please do not hate me, but I have been looking for the answer and didn't see it anywhere. I just got Galaxy S8 verizon - G950USQU4CRE9 (it was a free gift from Verizon for their mistake) and I wanted to root it, but it seems that OEM unlock is missing in the developer menu, I have tried many things, not luck, so I thought I would ask you guys. IS there any chance to root it, or downgrade it to 7 and then root it?
Thank you very much for your answers and solutions

romanko258 said:
Hi developers.
Please do not hate me, but I have been looking for the answer and didn't see it anywhere. I just got Galaxy S8 verizon - G950USQU4CRE9 (it was a free gift from Verizon for their mistake) and I wanted to root it, but it seems that OEM unlock is missing in the developer menu, I have tried many things, not luck, so I thought I would ask you guys. IS there any chance to root it, or downgrade it to 7 and then root it?
Thank you very much for your answers and solutions
Click to expand...
Click to collapse
For future reference, when you are looking for how to root a specific device, the best thing to try is to do a Google search for:
"How to root (your specific model number)"
In your case it would be:
"How to root S8 SM G950U"
If you had done a search using your model number, you would have easily found this:
https://www.skyneel.com/root-samsung-galaxy-s8-sm-g950u
Remember, when you have a question about a certain device or if you want to know how to do something on a certain model number, it is always best to use the device's specific model number in your search terms along with the thing you're looking for or along with what you want to do to the device.
Sent from my LGL84VL using Tapatalk

Thank you
Thank you for your answer. Believe me I have tried it all, that is why I have chooses this form. In the link provided there is mention OEM unlock option, now this is what I do not have on my phone.
That is why I have posted the question. I read that snapdragon version is difficult to root, so I hoped to find the answer here, where there are lot of smart developers.
I am afraid to use the method described in the link because I have not unlocked the bootloader and I am not sure if that would work without it and if it will not brick the phone.
So, is the version irrelevant when looking for the root option? It is good enough to look just for G950US instead of G950USQU4CRE9? I know I have many questions, but I am just starting the path you already walked on.

romanko258 said:
Thank you for your answer. Believe me I have tried it all, that is why I have chooses this form. In the link provided there is mention OEM unlock option, now this is what I do not have on my phone.
That is why I have posted the question. I read that snapdragon version is difficult to root, so I hoped to find the answer here, where there are lot of smart developers.
I am afraid to use the method described in the link because I have not unlocked the bootloader and I am not sure if that would work without it and if it will not brick the phone.
So, is the version irrelevant when looking for the root option? It is good enough to look just for G950US instead of G950USQU4CRE9? I know I have many questions, but I am just starting the path you already walked on.
Click to expand...
Click to collapse
Usually, the model number in device settings or the model number behind battery should be enough, what you posted looks like the baseband or build number, there shouldn't be a need for the baseband or the build number unless there is more than one android version available for the device that are different from each other. In this case, the baseband or build number might make a difference if the method to root is different for each baseband/build number.
For example, some Samsung devices that use CF-autoroot have more than one android version/baseband/build number available, for some of these devices, the version of CF-autoroot is different, you can't use the CF-autoroot that is built to work with "this" version/baseband/build number on "that" version/baseband/build number.
If you're in doubt, check which version/baseband/build number that the CF-autoroot for your model number is built to work with, if it's different than the version/baseband/build number that is currently installed on your device, you can't use it.
Now, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then check settings to see if you have the OEM unlock option.
Sent from my LGL84VL using Tapatalk

Thank you
Thank you for the explanation, it is clearer to me after your explanation
As per :Noa, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then chrck settings to see if you have the OEM unlock option.
I have tried that and no luck.
SO it means that until I will have the option on my phone, I can NOT do anything regarding rooting the phone, correct? Maybe I should explain what I am looking for with the root option. I am not a developer at any means, I just like to have a control over the device, so that Being said and I want be able to remove any bloatware that I do not need.
Droidriven said:
Usually, the model number in device settings or the model number behind battery should be enough, what you posted looks like the baseband or build number, there shouldn't be a need for the baseband or the build number unless there is more than one android version available for the device that are different from each other. In this case, the baseband or build number might make a difference if the method to root is different for each baseband/build number.
For example, some Samsung devices that use CF-autoroot have more than one android version/baseband/build number available, for some of these devices, the version of CF-autoroot is different, you can't use the CF-autoroot that is built to work with "this" version/baseband/build number on "that" version/baseband/build number.
If you're in doubt, check which version/baseband/build number that the CF-autoroot for your model number is built to work with, if it's different than the version/baseband/build number that is currently installed on your device, you can't use it.
Noa, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then chrck settings to see if you have the OEM unlock option.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse

romanko258 said:
Thank you for the explanation, it is clearer to me after your explanation
As per :Noa, as for the OEM unlock option. Try disconnecting from mobile data and Wifi then remove your SIM card, then disable the telephone app on your device, then reboot the device, then chrck settings to see if you have the OEM unlock option.
I have tried that and no luck.
SO it means that until I will have the option on my phone, I can NOT do anything regarding rooting the phone, correct? Maybe I should explain what I am looking for with the root option. I am not a developer at any means, I just like to have a control over the device, so that Being said and I want be able to remove any bloatware that I do not need.
Click to expand...
Click to collapse
If you can't unlock the bootloader then your only chance is if one of the universal android apps for rooting android devices or one of the universal PC programs for rooting android devices just happens to work on your model.
Do some searches for:
"PC tools to root any android device"
Or
"Universal rooting apps for android"
There are many different android apps and PC programs for rooting android devices, try any and all android apps or PC programs designed for rooting that you can possibly find, maybe you'll get lucky.
Sent from my LGL84VL using Tapatalk

thanks again
thanks agin for your reply, I really appreciate it, I just tried I think all of them I have found, still no luck
Droidriven said:
If you can't unlock the bootloader then your only chance is if one of the universal android apps for rooting android devices or one of the universal PC programs for rooting android devices just happens to work on your model.
Do some searches for:
"PC tools to root any android device"
Or
"Universal rooting apps for android"
There are many different android apps and PC programs for rooting android devices, try any and all android apps or PC programs designed for rooting that you can possibly find, maybe you'll get lucky.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse

I guess I need to wait for OEM unlock option to appear on my phone, without it I can not do anything, Root genius was pretty close to 87% and then I got message that the phone is too solid to root
romanko258 said:
thanks agin for your reply, I really appreciate it, I just tried I think all of them I have found, still no luck
Click to expand...
Click to collapse

Mod Edit
romanko258 said:
I guess I need to wait for OEM unlock option to appear on my phone, without it I can not do anything, Root genius was pretty close to 87% and then I got message that the phone is too solid to root
Click to expand...
Click to collapse
there is no oem unlock on our devices we have bootloader locked phones Dude is not very smart and rolling off stock piles of crap
he needs to learn to search himself before making posts obviously
he is using a lg not even a samsung to post from
Depending on your firmware on your device now makes or breaks root
S8 bootloaders 1 and 2 only can be rooted 3 or higher no chance as of now and no downgrade possible
If the firmware you have listed in the title is correct you are on version 4 which is not rootable by anymeans need to get a different device

Thank you, I was suspicious about it as well, because I have researched it myself before I turned for the answer in here. The good neews is that my phone is not bricked and it works, and hopefully there will be root options sometime soon.
TheMadScientist said:
Mod Edit
there is no oem unlock on our devices we have bootloader locked phones Dude is not very smart and rolling off stock piles of crap
he needs to learn to search himself before making posts obviously
he is using a lg not even a samsung to post from
Depending on your firmware on your device now makes or breaks root
S8 bootloaders 1 and 2 only can be rooted 3 or higher no chance as of now and no downgrade possible
If the firmware you have listed in the title is correct you are on version 4 which is not rootable by anymeans need to get a different device
Click to expand...
Click to collapse

romanko258 said:
Thank you, I was suspicious about it as well, because I have researched it myself before I turned for the answer in here. The good neews is that my phone is not bricked and it works, and hopefully there will be root options sometime soon.
Click to expand...
Click to collapse
Sammy patched the only root method we had at the time
Im just glad you got the info before messing up the device Some people want to help but they dont know what is going on

TheMadScientist said:
Mod Edit
there is no oem unlock on our devices we have bootloader locked phones Dude is not very smart and rolling off stock piles of crap
he needs to learn to search himself before making posts obviously
he is using a lg not even a samsung to post from
Depending on your firmware on your device now makes or breaks root
S8 bootloaders 1 and 2 only can be rooted 3 or higher no chance as of now and no downgrade possible
If the firmware you have listed in the title is correct you are on version 4 which is not rootable by anymeans need to get a different device
Click to expand...
Click to collapse
Actually, I'm very familiar with CF autoroot.
I hate to break it to you but there are more than a few devices that can flash CF autoroot even though they have a LOCKED bootloader. Chainfire found a way around it on some devices, but those devices could only root via CF autoroot, they couldn't get TWRP at the same time. Granted, whether "this" or "that" device could use CF autoroot on locked bootloader is device specific, but that is where the user reads the CF Autoroot thread to see if their device meets that version of CF autoroots requirements, if it's one that can be used on locked bootloader, it will say so, if not, it will say that also.
Mod Edit
Also, if you look a few posts up, I actually posted the only possibilities to root if the bootloader could not be unlocked.
I understand where you're coming from though.
Sent from my LGL84VL using Tapatalk

Root for Note 8 Exynos on Pie? Help appreciated. SOLVED

When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.

jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.

Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers

stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.

jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.

jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/

jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.

Note 8, no 'OEM unlocking' in dev ops; methods for making it available don't work

I don't know if I was supposed toflash STOCK ROM for Germany-DBT or Germany-T-Mobile. So I flashed the first. Forgot to check if there is 'OEM unlocking option', and flashed magisk-patchet boot.img. At first, root worked, however nex morning on booting, on samsung logo was written 'only official released binaries are allowed'.
So, I flashed again the same rom, now there is no 'OEM unlocking' opt in dev ops. Tutorials on unlocking it don't work.
Can you suggest something ?
I'm thinking to go Germany(T-Mobile) stock rom, don't know if I should. Don't know if it will make hard-brick if rom is not for this Note 8.
Should I try it ?
However, mate, I'll be grateful if you know what should I do and suggest something, cuz I'm starting to feel like fighting Diablo without a weapon.
Thanks
EDIT: Found a way to get OEM UNLOCKING (with automatic updates try).

What's you're model number

Dr.Lost said:
What's you're model number
Click to expand...
Click to collapse
Well I fixed it, I just went auto-update; after it started downloading , I stopped it & OEM unlocking appeared.

Downgrade from 13 to 12?

Is it possible to downgrade from 13 to 12? I think the upgrade messed up my camera. Or maybe a way to reflash the camera firmware?

If the bootloader wasn't updated you can roll it back.

How can I find out if it was updated? I have a US unlocked phone. Its updated from 11 to 12 and now to 13.

See this thread, different models but the same information applies.

blackhawk said:
See this thread, different models but the same information applies.
Click to expand...
Click to collapse
This is the build I'm on now:

RedCrane3 said:
This is the build I'm on now:
Click to expand...
Click to collapse
Hello good morning
Of course, it can be downgraded, as long as the binary number is the same... example in the image.

The bootloader version is 9 so for you to roll back that build number's 5th digit from the end needs to be the same or higher.
With stock Snapdragon's locked bootloader it's easy to get locked into an OTA upgrade you don't want if it updates the bootloader too. I have two N10+'s, one running on 9, the other 10 (can't be rolled back to 9). That's what they were loaded when bought new. They will likely remain on those versions for their service lives as they are running well. I prefer Pie though.
I could be running Android 11 or 12 but I blew them off mostly because of the scoped storage bs.
The first thing I disable is OTA updates, once bitten twice shy. Had a S4+ that got screwed up by a OTA update that couldn't be rolled back... it sucks.

Thank you guys for helping me with all of this information. I guess I have a decision to make.
I can try to rollback to Android 12 in the hopes that will fix my camera issue, or I can sit tight and hope that a future update will resolve it.
Either way, I'm beginning to regret allowing OTA updates.
I really love the hardware of this phone, especially the screen, but its not important to me to have the latest Android (security updates are important though).
I originnaly submitted the problem to Samsung through their members app and the tech who looked at it said he *thought* it was a hardware issue, but come on, what are the chances that the one camera stops working right after the update to 13 and OneUI 5? I take very good care of my phone and never drop it (certainly didn't recently, after the update), there's not a scratch on it.
I suppose its possible, but it would be an incredible coincidence...
The tech suggested I visit a service center (which for me would be a Best Buy, yikes) or call their support 800 number, but what are they going to be able to do that the tech couldn't?
I just don't know if I can trust their initial assessment - no one knows everything, and plenty of people give up on a problem and pass it off the first trouble they run into. Maybe the tech just wasn't interested in digging deeper? A quote from their answer:
"Chi request is getting timed out. Read wide camera sensor seems to be not responding to requests [...]"
I guess my question is: can a downgrade to 12 even fix the issue?
Should I wait for another update?
Or should i just heave Samsung over the side and try to install a custom ROM?
Thanks again for all your help.

You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.

blackhawk said:
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
Click to expand...
Click to collapse
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.

RedCrane3 said:
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
Click to expand...
Click to collapse
That refers to the carrier not bootloader I think. Not sure about your specific model's bootloader.