Database Info

Can Oreo android 8 firmware be rooted on s8 exynos? G955FXXU1CRAP

HI Guys, I have installed the G955FXXU1CRAP at my s8+ but when I try to flash twrp with odin it get status fail and the phone says that installation of custom binaries are not allow (OEM LOCK and RMM STATE: PRENORMAL).
Did you tryed to install Twrp and root G955FXXU1CRAP? How you solve this bootloader lock?.
thanks in advance.
Alex.

In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.

This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -

Well, thank you so much for that information guys. I did not know it.

Geekser said:
This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -
Click to expand...
Click to collapse
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.

cyborgium said:
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.
Click to expand...
Click to collapse
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22

Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..

Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol

cyborgium said:
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..
Click to expand...
Click to collapse
Go into download mode (Power, Bixby and Vol Down) when you are in download mode, you can see what the RMM State is - it will either say NORMAL or PRE-NORMAL.
If yours says NORMAL - then you go can go ahead and flash TWRP via ODIN. If you are having flash issues at this point, ask in the TWRP Thread and you should be able to get some help.
However, if you are PRE-NORMAL in download mode, then you are locked and won't be able to flash anything until you pass the 7 day period.I think the 7 days begins on the date you flashed your current firmware.
YOu can be in PRE-NORMAL and still see OEM UNLOCK. BUT if you are pre-normal and you see OEM UNLOCK you cannot flash until your RMM State changes to NORMAL.
I hope that helps.

xxxrichievxxx said:
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol
Click to expand...
Click to collapse
Yes, the RMM Fix must be flashed after you flash TWRP or after you flash a custom rom, everytime. UNLESS the rom has the RMM Fix baked into the rom - some do - some may not. Won't hurt to fllash it just in case, everytime.

Thanks again for the rapid response but, I'm identifying an issue with the storage on this firmware g955fxxu1crap. My phone exynos g955f has 64 gb of internal storage, but after this upgrade it shows only 16 gb of internal storage.
Did get this same error , how you solve it?
thanks in advance.
Ale3385

josegon30 said:
In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.
Click to expand...
Click to collapse
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.

Psyscope said:
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.
Click to expand...
Click to collapse
After 7 days I could perfectly flash TWRP and root, no big deal. If you go into download mode and see RMM STATE: PRENORMAL then you can't flash. I guess all new phones with 8.0 since January are pre-normal, but I'm not sure.

Ive seen in the other thread that you could flash the entire nougat stock rom (nov 2017 perhaps) which will allow you to bypass the rmm and then flash TWRP and custom ROM? Could anyone confirm this workaround?

[GUIDE] How To Install TWRP & Root Galaxy S8 After Oreo Update

A simple guide for users which will help them to install TWRP on their S8 after Oreo Update.
This guide is only for Exynos models.
Requirement -
1. PC/Laptop
2. Original Samsung USB Type-C Cable
3. Prince Comsy Odin (Because some users reported on this thread that normal Odin doesn't work)
Instructions -
1. Backup your important data from internal storage before proceeding towards the installation.
2. Now go to Settings - About Phone - Software Information - Tap On Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON.
4. Power off device and boot into download mode.
5. Connect your device to the PC/Laptop.
6. Now Open Prince Comsy Odin and click on the AP option.
7. Choose the TWRP .tar file and press the START button.
8. Now after Odin says PASS, press the VOLUME UP, BIXBY KEY, and POWER BUTTON at the same time until device boots into TWRP recovery.
9. Now allow the modifications and go to WIPE option.
10. Choose FORMAT DATA - Type yes - ENTER.
11. Just Reboot Once Into Recovery Once.
12. Flash no-verity-opt-encrypt.zip.
12. Now Choose INSTALL option and install Magisk or SuperSU.
13. Done!
You can also refer to this video for installation of TWRP - https://www.youtube.com/watch?v=2SqgHFcHLMw
Downloads -
Latest TWRP For Exynos S8 - TWRP 3.2.1-0-DREAMLTE
Prince Comsy Odin - https://drive.google.com/open?id=1enVG5a_ocyjhRlta8AX_0b7LLoHWciVU
No dm-verity - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
SuperSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Credits -
@jesec for TWRP
@topjohnwu for Magisk
@Chainfire for SuperSU
Prince Comsy Odin

The main problem is that most users dont have oem unlock after oreo update (e.g me)

EugenStanis said:
The main problem is that most users dont have oem unlock after oreo update (e.g me)
Click to expand...
Click to collapse
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox

Ruturaj Kadam said:
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Click to expand...
Click to collapse
Flashed official XEO for Poland and still OEM unlock isnt there :/

Does the Oreo update affect the the locked bootloader on the Snapdragon version? I thought it was impossible to install TWRP on the Snapdragon versions of the S8?

I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard

EugenStanis said:
Flashed official XEO for Poland and still OEM unlock isnt there :/
Click to expand...
Click to collapse
Try use AQK7 ( 4 file firmware + re-partition PIT)
In my case I 100% success returned form CRAP to AQK7.
OEM unlock is in dev settings, no RMM and FRP.
Powodzenia ^_^

I'm guessing this is not for the US snapdragon variant.

There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.

Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.

Will822 said:
I'm guessing this is not for the US snapdragon variant.
Click to expand...
Click to collapse
I'm sorry! It was one of my friends who told me the method is same. I'm sorry again. OP edited

iamnotexisting said:
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Click to expand...
Click to collapse
I'm sorry for that! Edited the OP! Got misguided due to one of my friends

Silenus21 said:
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Click to expand...
Click to collapse
Haha yes! Exynos devices are best in performance and battery too.

This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?

168 hours Open my device oem lock on of after twrp flash data storage 0 dm verity flash wipe data

thiagomed said:
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
Click to expand...
Click to collapse
TWRP trips Knox if I'm not mistaken.

i did this guide and everything is went good but when i restarted the phone it went to a softbrick and i had to do a restore...
the error was something on the original binary

to have the OEM option, will I have to go back to crap?

I have just tried this method and booted into TWRP but the screen was totally unresponsive, rebooted and still the same. I had to go back to Oreo.
How do I get around this problem?

dr.vetony said:
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
Click to expand...
Click to collapse
Wipe / format data - " yes"

[Solved]"only official released binaries are allowed to be flashed" (CRi9)

Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
1. Changed the date of the date of the phone and went to "update firmware" and then reset to get OEM unlocked
2. Went to download mode and flashed succesfully TWRP.
3. In TWRP I formated data (yes) and rebooted into recovery
4. Flashed the following files: a) Magisk, b) No verify 6.0, c) RMM state bypass Mesa, d)samsung anti-root removal 4.1
5. Rebooted into system
Click to expand...
Click to collapse
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?

josegon30 said:
Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?
Click to expand...
Click to collapse
More than likely RMM state zip didn't work are you using the version 2 zip and did you allow modifications in twrp before flashing zip files.

@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.

josegon30 said:
@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.
Click to expand...
Click to collapse
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....

Johnny™ said:
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....
Click to expand...
Click to collapse
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).

thanks im really struggling, im on the 11th try, every time is just gives me only official bineries.... , ive tried several methods, all root nicely but wont reboot.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
i cant find the v2 its coming up as 4k where v1 is 100k?

josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!

Johnny™ said:
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!
Click to expand...
Click to collapse
:good: I´m glad it worked.

josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...

nasko7 said:
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...
Click to expand...
Click to collapse
Depending on .android version, you will need to have the following coditions to be able to flash non signed samsung firmware eg: twrp,root, custom roms etc.
In system - OEM unlocked
Download mode -
RMM status - normal ( or disappeared )
KG status - checking
Otherwise you will get errors

S7 edge SM-G935F remove root/ back to stock

Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks

Vinni777 said:
Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks
Click to expand...
Click to collapse
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader

kpwnApps said:
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader
Click to expand...
Click to collapse
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.

Vinni777 said:
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.
Click to expand...
Click to collapse
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void

kpwnApps said:
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void
Click to expand...
Click to collapse
Thanks mate. I managed yesterday to flash on latest software and everything works perfectly apart Sam Pay and Sam Health Offcourse android pay and etc works fine.

only official released binaries are allowed to be flashed(recovery) RQT_CLOSE !!

I bought s8 plus (G955f) couple days ago and i wanted to change rom and flash twrp but i cant, while trying flash twrp on odin its failing, i have android 9 and oem unlock option, i tried to flash older rom (i dont have a screenshot) thats official but it show this error sw rev check fail bootloader binary 4 device 11 and stuck on bootloader.img.

kitsane said:
I bought s8 plus (G955f) couple days ago and i wanted to change rom and flash twrp but i cant, while trying flash twrp on odin its failing, i have android 9 and oem unlock option, i tried to flash older rom (i dont have a screenshot) thats official but it show this error sw rev check fail bootloader binary 4 device 11 and stuck on bootloader.img.
Click to expand...
Click to collapse
A couple of things i can see but will need more information
The SW Rev check error is your trying to flash older firmware than what is on your phone. Use latest firmware.
If you have OEM unlocked but KG/RMM state in prenorrnal state then you can't flash.
From your screen shot of odin, you phone is not connected. Near the top left there a box with ID:Com should show up as being connected.
Also use the latest twrp from twrp website.

spawnlives said:
A couple of things i can see but will need more information
The SW Rev check error is your trying to flash older firmware than what is on your phone. Use latest firmware.
If you have OEM unlocked but KG/RMM state in prenorrnal state then you can't flash.
From your screen shot of odin, you phone is not connected. Near the top left there a box with ID:Com should show up as being connected.
Also use the latest twrp from twrp website.
Click to expand...
Click to collapse
SW rev shows only when im flashing android 8 (older firmware)
I dont know how to check KG/RMM state
Yes i know i just removed it after and make screenshot much much later, it always shows when phone is in dl mode
Yes Im using latest twrp from twrp site.

spawnlives said:
A couple of things i can see but will need more information
The SW Rev check error is your trying to flash older firmware than what is on your phone. Use latest firmware.
If you have OEM unlocked but KG/RMM state in prenorrnal state then you can't flash.
From your screen shot of odin, you phone is not connected. Near the top left there a box with ID:Com should show up as being connected.
Also use the latest twrp from twrp website.
Click to expand...
Click to collapse
I checked in download mode KG/RMM state RMM is prenormal and KG is checking

kitsane said:
SW rev shows only when im flashing android 8 (older firmware)
I dont know how to check KG/RMM state
Yes i know i just removed it after and make screenshot much much later, it always shows when phone is in dl mode
Yes Im using latest twrp from twrp site.
Click to expand...
Click to collapse
Due to bootloader version numbers you can not downgrade your device only upgrade. Bootloader is the 5th number/letter from the right of the firmware name you are downloading.
KG/RMM state can be checked in download mode.
prenorrnal - can't flash ( you can only flash stock samsung firmware )
checking/not there - you can flash
Edit:
If RMM is prenormal you can't flash. you can try the date method to see if help this changes the state.
There are many guides on this method some are slightly different
eg:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
or wait the so called waiting 7 days ( 168 hrs ) seems to fix this as well ( with internet connection ).

spawnlives said:
Due to bootloader version numbers you can not downgrade your device only upgrade. Bootloader is the 5th number/letter from the right of the firmware name you are downloading.
KG/RMM state can be checked in download mode.
prenorrnal - can't flash ( you can only flash stock samsung firmware )
checking/not there - you can flash
Edit:
If RMM is prenormal you can't flash. you can try the date method to see if help this changes the state.
There are many guides on this method some are slightly different
eg:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
or wait the so called waiting 7 days ( 168 hrs ) seems to fix this as well ( with internet connection ).
Click to expand...
Click to collapse
Thanks its probably it, i will check it tommorow, thank you for help.