Database Info

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8

Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!

Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.

Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?

Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.

annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?

hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?

Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:

Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.

How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol

Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)

Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?

GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...

annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse

I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing

Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?

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?

How to install Oreo ROM?

Hi! I'm really humbly sorry, I'm new to this stuff, so I have to ask you...
I have a Galaxy S8+ Duos (SM-GD955FD). I bricked it once or twice trying to root it. So I had to flash a sammobile.com ROM...
Now this is done, I have a successfully rooted phone with with the Baseband version G955FXU1AQH3 and the irritating "security notice" (since I was not able to install Magisk, and the NotifyClean app doesn't work either).
I would like to flash the latest Oreo and root it. I also heard good things about the Oreo ROM by alexega.
So: I'm on AQH3 rooted. What can I do?
Thank you for your patience.

If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.

josegon30 said:
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
Click to expand...
Click to collapse
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...

andifla852 said:
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
Click to expand...
Click to collapse
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.

Just rooted the new Oreo ROM with TWRP. Works just fine, thank you.
So, what are the advantages of the Oreo ROM by alexega compared to XXU1CRAP?

josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.

juange said:
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
Click to expand...
Click to collapse
Just follow the steps from the link in my previous repply. As it's an original software, it won't trip knox or void your warantee.

hi, does anybody knows how to install the oreo firmware using odin but without changing the csc I already have?

josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?

costafabiof said:
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
Click to expand...
Click to collapse
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.

josegon30 said:
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
Click to expand...
Click to collapse
Did not work.
I can not find out where I went wrong.

developer11 said:
Android.com.pl **** you
Little cocksucker
Click to expand...
Click to collapse
Translation?

costafabiof said:
Did not work.
I can not find out where I went wrong.
Click to expand...
Click to collapse
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.

josegon30 said:
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
Click to expand...
Click to collapse
That did not work out. But thank you for your attention.

Question about RMM State (Only official released binaries are allowed to be flashed)

Hello comunity! I'm not getting this thing clear so i wanted to ask some questions.
I followed the steps from this guide: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-install-twrp-root-galaxy-t3752492
I decided to install Magisk then when i booted into System i could see that the device was succesfully rooted, but here comes the problem...
I rebooted the device and then after that, the boot screen appears with the message "Only official released binaries are allowed to be flashed"
I flashed an official Nougat ROM with Odin and then i could boot to system again (I was really worried about having the device as a brick haha), now i waited for the 7 days to have the OEM unlock setting, but i also updated again to Oreo with the official OTA's.
Now my main question is: What i have to do in order to root the device and be able to reboot whenever i want without having this trouble?, I saw that there was a RMM State Bypass that i need to flash after doing all the rooting process but after doing that, will i be able to reboot and not get the message "Only official released binaries are allowed to be flashed" anymore? I saw that you need to edit de build.prop file also, but i dont know when.
Thanks in advance!

Stock in boot
I got the same problem today, with the ROM G950FXXS3CRG1 ZTO, I tried so many times but I can't do root in TWRP mode. I need help too.

same problem in A320F

petrucioSneto72 said:
I got the same problem today, with the ROM G950FXXS3CRG1 ZTO, I tried so many times but I can't do root in TWRP mode. I need help too.
Click to expand...
Click to collapse
Same exact problem on my S9.

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 should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun

this verity.zip is necessary? or can I flash another rom right after install twrp?
edit: by "update.zip" you mean the PIE Beta?

LucasBernardesLopes said:
this verity.zip is necessary? or can I flash another rom right after install twrp?
edit: by "update.zip" you mean the PIE Beta?
Click to expand...
Click to collapse
It decrypt the Userdata.
Yes i mean the Pie Beta.

It works perfect, I was worried because I could not find a solution, very good guide thank you very much

Laiyox said:
Hello Guys
-------------------------------------------------
1. Download CRL3 via Samfirm SamFirm Download from mega.nz
2. Install CRL3 via Odin Odin v3.13.1 direct download
3. Boot Stock CRL3 after install with Odin
Click to expand...
Click to collapse
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?

tomaasz said:
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
Click to expand...
Click to collapse
I don't really know. The Beta was published while CRL3. So i think it is needed, but you can try. If it dont work you just can reflash CRL3 via Odin

tomaasz said:
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
Click to expand...
Click to collapse
Following this thread you should be on CRL3.
https://forum.xda-developers.com/galaxy-s8/how-to/s8-exynos-pie-oneui-beta-official-t3890376

do we have to flash twrp after every pie beta update?

How to root s8plus 9.0 one ui
I need help root android 9.0 one ui s8plus ??

i followed everything 9.0 Pie beta also done but after format wipe OEM is gone.
actually i want to root my G955F but its showing error becous RMM status is Prenormal so i cant root my S8 plus
please guide me how to root after beta pie 9.0?
Thx.

talhagsm said:
i followed everything 9.0 Pie beta also done but after format wipe OEM is gone.
actually i want to root my G955F but its showing error becous RMM status is Prenormal so i cant root my S8 plus
please guide me how to root after beta pie 9.0?
Thx.
Click to expand...
Click to collapse
I have just written a new thread with a new method to bypass it:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-skipping-kg-prenormal-oneui-t3911862

How to install the crlb via odin

When I do this on Pie, the OEM Unlock toggle in Dev Options shows up. When I toggle it, it shows the following in download mode:
RMM STATE: Prenormal
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF
And I am unable to flash TWRP or any custom binaries.
So I downgraded to Oreo, and followed the exact same steps as outlined and now I cannot get the OEM toggle to show up! And of course it says Prenormal in download... but not KG State.
RMM STATE: Prenormal
FRP LOCK: OFF
OEM LOCK: ON
WTF am I doing wrong??

kgr said:
When I do this on Pie, the OEM Unlock toggle in Dev Options shows up. When I toggle it, it shows the following in download mode:
RMM STATE: Prenormal
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF
And I am unable to flash TWRP or any custom binaries.
So I downgraded to Oreo, and followed the exact same steps as outlined and now I cannot get the OEM toggle to show up! And of course it says Prenormal in download... but not KG State.
RMM STATE: Prenormal
FRP LOCK: OFF
OEM LOCK: ON
WTF am I doing wrong??
Click to expand...
Click to collapse
Did you did everything step by step?
If you miss any step it won't work

Laiyox said:
Did you did everything step by step?
If you miss any step it won't work
Click to expand...
Click to collapse
Yep absolutely followed the directions exactly. In the end I just wanted the 7 days

kgr said:
Yep absolutely followed the directions exactly. In the end I just wanted the 7 days
Click to expand...
Click to collapse
Also used latest Base?
I didn't update the thread to official Pie

can I still flash without root?
I have a J337VPP galaxy J3 running on android oreo 8.0.0 and the hardware version is J337v.04. it is non-rooted. Would I be able to do your steps without root? it has to be able to be done without root since the only way to root is by unlocking the bootloader using the OEM unlock (which I can't do because of this stupid RMM prenormal Samsung decided to create). Thanks! been trying to root different phone of mine for years to take complete control over annoying system apps! (atleast I already have Package Disabler Pro) Thanks again. Hope I can have help. I've heard of going to download mode and seting the date before RMM prenormal. I think I am good with tech but new to this RMM stuff.
---------- Post added at 12:18 AM ---------- Previous post was at 12:01 AM ----------
Turns out RMM state prenormal isn't in download mode/odin. Weird... maybe J3 doesn't support oem unlock

just tried this on SM-G950F (Galaxy S8), RMM state is still prenormal and I can't flash TWRP. I did have the oem unlock option available before doing this though, and had turned it on, but I'm on android 9 which might make a difference

hiden oem option
Laiyox said:
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 should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun
Click to expand...
Click to collapse
when i do deactivate oem option ask for factory reset when i do then thereh is no oem option ?

Hi guys, i have a problem with my S8 (SM-G950F), I want to flash twrp and a custom rom but I can't flash twrp because i have last update (1 september 2019), someone can help me? When I flash the twrp from odin I have FAIL ever, how can i fix kg state prenormal? I used adb and fastboot, i used odin, odin patched-b, princecomsy odin but I can't flash it. I used linux ubuntu 19 with Heimdall flash but it's the same. Thanks in advance.