Develop Bugs

Failure to Install the Stock ROM

Hi! Installing stock ROM on One M8 has driven me crazy. My software version is 2.22.401.5. I couldn't find it in HTC Dev. So, I rummaged forum & find this thread. http://forum.xda-developers.com/showthread.php?t=2696282 But, When installing ROM through fastbook, I get Error 12 (Signature Verification Failed). It's mentioned in thread that it might be related to CID number mismatch. There is two ways; S-Off & SuperCID or change android-file.txt in the zip & add my CID. I don't want to S-Off. So, Only the second way is remained. How I can change the aforesaid file?
In addition to these ways, Do you know any other method? I really need to flash stock firmware.
Installing stock ROM on HTC phones isn't easy...
Thanks!

Failure to Install the Damn Stock ROM
I forgot to mention that my bootloader is relocked, TWRP Recovery is installed & the phone is rooted. I will be grateful if anyone help me.

That link is for radios not stock ROMs...

ILIVE4HEAD said:
That link is for radios not stock ROMs...
Click to expand...
Click to collapse
Sorry ... I edited the link

arian_0098 said:
Sorry ... I edited the link.
Click to expand...
Click to collapse
The link in the OP are FIRMWARES ! not stock roms ! And stop being so mad aggressive, it doesn't help you in any way.....stay calm and read well !

Mr Hofs said:
The link in the OP are FIRMWARES ! not stock roms ! And stop being so mad aggressive, it doesn't help you in any way.....stay calm and read well !
Click to expand...
Click to collapse
There is difference between Firmware & ROM? ! Would you explain me the differences shortly?
I found a Nandroid backup in your topic which matches with my CID Number! :laugh: But, I have a few questions. (I can't ask them in your topic. Because I haven't 10 posts or more. So, I can't reply to any topic in development section.)
1- If I use them, Root access will be lost?
2- They aren't manipulation?

I'm not in the dev section, it's the general
1: yes root is gone on a nand backup (that's why they are called stock nand backups) at least they should be because i didn't test them !
2: they are afaik not manipulated in any way. Haven't received any complaints yet
Edit :
Stock rom is the pure software. The firmware contains the hboot/bootloader (no rom)

arian_0098 said:
.... Buying a HTC Phone was one of the biggest wrongs in my life....
Click to expand...
Click to collapse
I want to help you and many other may want to help you but you're not helping yourself when you put the blame on your device when the biggest wrongs is you yourself. Please search and read as there are many guides on XDA
For a start:
1. You need to unlock the bootloader. So the question is : do you still have the unlock_code.bin that you got from HTCdev ?
a- Yes ... use it to unlock the bootloader
b- No ... apply for a new one
Next step - I will tell after you answer the first one

ckpv5 said:
I want to help you and many other may want to help you but you're not helping yourself when you put the blame on your device when the biggest wrongs is you yourself. Please search and read as there are many guides on XDA
For a start:
1. You need to unlock the bootloader. So the question is : do you still the unlock_code.bin that you got from HTCdev ?
a- Yes ... use it to unlock the bootloader
b- No ... apply for a new one
Next step - I will tell after you answer the first one
Click to expand...
Click to collapse
I had unlocked my bootloader through fastboot using Unlock_code.bin. I relocked it again. Now I want to use a nandroid backup & bootloader should unlocked. So, I wanted to unlock it again. But stock recovery should installed. I downloaded stock recovery v 2.22.401.5 which matches with software number & when installing it through fastboot, I get "Signature Verify Failed" error.

arian_0098 said:
I had unlocked my bootloader through fastboot using Unlock_code.bin. I relocked it again. Now I want to use a nandroid backup & bootloader should unlocked. So, I wanted to unlock it again. But stock recovery should installed. I downloaded 2.22.401.5 which matches with software number & when installing it through fastboot, I get "Signature Verify Failed" error.
Click to expand...
Click to collapse
You don't really read what people say ...
Here are the basic step
1. unlock bootloader
2. restore nandroid backup 2.22.401.5 with TWRP (when the backup is made with TWRP)
3. flash stock recovery 2.22.401.5 (but why you need this ?)
4. relock bootloader if you want to but NOT necessary and again why do you need this ?
See .. relock bootloader is the last process not the first one ... can you understand now ?
"Signature Verify Failed" error because the bootloader is relocked. You need to unlock it first then there will be no error.
That's why no.3 is before no.4

ckpv5 said:
You don't really read what people say ...
Here are the basic step
1. unlock bootloader
2. restore nandroid backup 2.22.401.5 with TWRP (when the backup is made with TWRP)
3. flash stock recovery 2.22.401.5 (but why you need this ?)
4. relock bootloader if you want to but NOT necessary and again why do you need this ?
See .. relock bootloader is the last process not the first one ... can you understand now ?
"Signature Verify Failed" error because the bootloader is relocked. You need to unlock it first then there will be no error.
That's why no.3 is before no.4
Click to expand...
Click to collapse
I don't know how easier I can explain. I can't unlock bootloader unless the recovery isn't stock.
I mean I unlocked bootloader, Then installed TWRP recovery & then relocked bootloader. (Recovery is still TWRP.) Because recovery isn't stock, I can't unlock it for the second time.
easier than this? !

arian_0098 said:
I don't know how easier I can explain. I can't unlock bootloader unless the recovery isn't stock.
Click to expand...
Click to collapse
Now ... you make it clear what your problem is. And I don't remember whether unlocking bootloader will not work when TWRP is installed.
Requirement : must have external sdcard.
1. Download the untouched firmware here : http://sourceforge.net/projects/htconem8/files/2.22.401.5_firmware.zip/download
2. Rename the 2.22.401.5_firmware.zip to 0P6BIMG.zip
3. put 0P6BIMG.zip on the external sdcard
4. Boot into hboot - the system will scan the file and ask you whether you want to update - select yes by pressing volume up
5. Now you have stock recovery installed.
6. do whatever you want to do like unlocking bootloader
If the above sound complicated, and you still have root (or install SuperSU as you still have TWRP),
1. install flashify (https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
2. put the stock recovery in your sdcard or external sdcard
3. run flashify to install stock recovery

ckpv5 said:
Now ... you make it clear what your problem is. And I don't remember whether unlocking bootloader will not work when TWRP is installed.
Requirement : must have external sdcard.
1. Download the untouched firmware here : http://sourceforge.net/projects/htconem8/files/2.22.401.5_firmware.zip/download
2. Rename the 2.22.401.5_firmware.zip to 0P6BIMG.zip
3. put 0P6BIMG.zip on the external sdcard
4. Boot into hboot - the system will scan the file and ask you whether you want to update - select yes by pressing volume up
5. Now you have stock recovery installed.
6. do whatever you want to do like unlocking bootloader
If the above sound complicated, and you still have root (or install SuperSU as you still have TWRP),
1. install flashify (https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
2. put the stock recovery in your sdcard or external sdcard
3. run flashify to install stock recovery
Click to expand...
Click to collapse
Thanks so much! I easily send the file to a sd card & after boot into HBoot, It easily installed!
I unlocked the bootloader too!
Now I don't know which nandroid backup is better to use.
1.54.401.5 from PopAhmad which matches exactly with my cid number & update it to 2.22.401.5 using ota (Maybe never updates through ota!) or directly download 2.22.401.5 from you? (I trust to you & your works more.)

arian_0098 said:
Now I don't know which nandroid backup is better to use.
Click to expand...
Click to collapse
Use 2.22.401.5 because you have the latest firmware installed
Or you can use 2.22.401.4 then do OTA to 2.22.401.5 (but not necessary)

Dear "ckpv5", My phone was completely destroyed. :crying: Everything was good until I installed PhilZ recovery. I entered recovery & selected backup & restore. Then, Selected backup to /sd card. It took about 3 minutes to complete. After that, I didn't do anything & went out for about 5 mins. The screen turned off. (It should turns off after 3 mins based on settings.) I was turning on the screen by pressing power button. But, This time nothing happend. I pressed volume buttons too. But ...
I found that if I touch the screen, It vibrates. I tapped the screen many times & nothing happend except vibrate. I holded volum down+power & the device started vibration continuesly & stopped after a few seconds. Once again, I holded volume up+power & the device turned off & rebooted 5 secs later. I was happy. But, found that it stuckes at boot screen.
Now, I can only hold volume up+power to turn off & then, hold volume down+power to boot into bootloader.
I think it's not repairable & want to sell it. (I bought it expensive in Iran.) I think correctly?
However, if it be repairable, I'm sure it's not like its first day.
So much thanks to you. Because you help me sympathetic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

arian_0098 said:
.....Now, I can only hold volume up+power to turn off & then, hold volume down+power to boot into bootloader....
Click to expand...
Click to collapse
I don't understand what you are trying to do .. first you have TWRP installed then you wanted the stock recovery to unlock bootloader then now you flashed Philz recovery
Anyway.... when you can go to bootloader ... it just a soft brick.
I don't know much about Philz recovery as I find it a bit complicated for me to use it.
I'm using TWRP ... if you can flash a TWRP recovery then I can guide you to bring back your device to life.
For a start, just follow my signature for the TWRP that I'm using.
If you don't have an external sdcard
1. flash TWRP recovery
2. download a ROM like MaximusHD for e.g - http://forum.xda-developers.com/showthread.php?t=2695706
3. boot to recovery - go to mount - make sure data is selected
4. Put the ROM.zip in the folder where you have your adb file then push the ROM.zip to your device with command
adb push ROM.zip /data/media/0/
5. install the ROM.zip
6. once everything is up and running ... then later you can decide whether to restore to stock ROM as the first day that you got the phone.
When you have an external sdcard
1. flash TWRP recovery
2. download a ROM like MaximusHD for e.g - http://forum.xda-developers.com/showthread.php?t=2695706
3. Put the ROM.zip on the external sdcard
4. in recovery, install the ROM.zip
5. once everything is up and running ... then later you can decide whether to restore to stock ROM as the first day that you got the phone.

arian_0098 said:
Dear "ckpv5", My phone was completely destroyed. :crying: Everything was good until I installed PhilZ recovery. I entered recovery & selected backup & restore. Then, Selected backup to /sd card. It took about 3 minutes to complete. After that, I didn't do anything & went out for about 5 mins. The screen turned off. (It should turns off after 3 mins based on settings.) I was turning on the screen by pressing power button. But, This time nothing happend. I pressed volume buttons too. But ...
I found that if I touch the screen, It vibrates. I tapped the screen many times & nothing happend except vibrate. I holded volum down+power & the device started vibration continuesly & stopped after a few seconds. Once again, I holded volume up+power & the device turned off & rebooted 5 secs later. I was happy. But, found that it stuckes at boot screen.
Now, I can only hold volume up+power to turn off & then, hold volume down+power to boot into bootloader.
I think it's not repairable & want to sell it. (I bought it expensive in Iran.) I think correctly?
However, if it be repairable, I'm sure it's not like its first day.
So much thanks to you. Because you help me sympathetic.
Click to expand...
Click to collapse
If it can boot into bootloader then it's not destroyed. Just reflash recovery and reflash/restore ROM, after that you can reflash the stock recovery if you prefer.
If you're going to sell it, you should be fair to the person you're going to try and rub that device on, the device that you messed up. Sell it for way less than it's actually worth, seeing as he should spend all the time fixing what you broke in the first place. When I say way less, I mean, less than $100 if the phone cost $700.
Else, if you want to sell it for a decent price then the least you can do is fix it first then sell the phone, seeing as you're not up to scratch with smartphones.
Just repeat the steps already explained to you many times up to now.
Flash custom recovery.
Restore Nandroid backup.
Flash stock recovery.
Might this be a lesson then...if anyone wants to flash custom stuff they HAVE to read up and learn about it first. Instead of just flashing any custom ROM for the sake of running around their friends pretending to be a hardcore "hacker" for having a "modified" phone. "Look at my M8, way better than stock sense, I gots Viper!!! Badass!" until the first fail...
What an expensive lesson to learn, could have saved a lot of money.

Thread closed briefly for a "tidy-up"...
Thread reopened.

LenAsh said:
Thread closed briefly for a "tidy-up"...
Thread reopened.
Click to expand...
Click to collapse
PLEASE don't close the thread in 1-2 next days.

arian_0098 said:
PLEASE don't close the thread in 1-2 next days.
Click to expand...
Click to collapse
I don't intend to close it - you need to get your phone sorted.
I sent you a PM - please read it - it explains why I had to temporarily close the thread.

RMM STATE:Prenormal

So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.

carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076

arys64 said:
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076
Click to expand...
Click to collapse
Yeah...a few users are testing the 168 hour theory. We will find out what happens in 6 days

carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.

billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped

carlosmedia said:
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped
Click to expand...
Click to collapse
Try to flash it with combination firmware, enable OEM Unlock, remove screen lock and Google account.
Finally disable the RMM app called RLC, and modify the build.prop as posted earlier. If your don't do all those, the RMM lock will re-activate as soon as you try to flash a custom recovery.
Unfortunately simply waiting for a week, will not auto-magically solve all you problems, you must disable it manually.
The reason you had to wait, is to able able to flash signed firmware again.

billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste

carlosmedia said:
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste
Click to expand...
Click to collapse
Unfortunately there's no way for us mere mortals to "untrip Knox". I'm pretty sure Samsung can do it internally but not us, so you just gonna have to live with it. It's not the end of the world, just a flag to tell Samsung that someone has messed with it.

[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

UPDATE 17.06.2019 - NEW RMM/KG bypass patch
UPDATE 23.02.2019 - Pie and more
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about this guide!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Flashing any custom binary will trigger knox and you may lose your warranty. Make sure you know what you do to your device.
Introduction
December 2017 update (for some even older) brought us a different lock, that creates panic among users as usual. As described here by my friend @BlackMesa123, this is not a lock to developement, rather an advanced lock for theft or scams. This has a bypass too, specially when you`re the owner of the device.
How it works
This lock is in bootloader, but the trigger to it is inside the system, it`s hard to reproduce, but usually happens when you plug another country sim than your firmware country, because changing the country might not seem as a traveling guy and more like a thief. If you are on stock rom all this time, you might not feel the change, as the device reboots and wipes data, but it will eventually boot. The nice thing comes if you already have custom binary installed (rooted kernel or twrp), as you can`t boot anymore because bootloader is preventing you to boot on custom binaries and alter the system.
Devices confirmed to have the lock:
Any other Samsung device manufactured after 2017
Samsung Galaxy S9 & S9+ - SM-G960F & SM-G965F
Samsung Galaxy Note 8 - SM-N950F
Samsung Galaxy S8 & S8+ - SM-G950F & SM-G955F
Samsung Galaxy A8 & A8+(2018) - SM-A530F & SM-A730F
Samsung Galaxy A Series (2017) - SM-A320F/FL, SM-A520F & SM-A720F
Samsung Galaxy Note FE - N935F
How to know if you are locked
There are 3 things at this chapter:
1. "Only official released binaries are allowed to be flashed" message shows up and now you know for sure you got locked outside your phone
2. Missing OEM unlock toggle in developer settings, if your device has FRP
3. "RMM state = Prenormal" in download mode
How to unlock
1. As i personally did, and other users reported, if you face any of the things above, flash latest full stock fw of your country with Odin, boot up, don`t reboot, don`t unplug the sim and don`t disconnect the network connection for 7 full days (168h). It seems that after 7 days of uptime, RMM state resets and you can flash TWRP again without issues. You can see uptime in settings/about device/status.
2. Some users reported this guide was working in first Oreo fw releases, can't guarantee it still works.
How to avoid getting locked again
Unfortunately bootloader can`t be reverted to older revisions, so we need to live with this. My friend @BlackMesa123 made some investigation and found out how to disable this lock. After waiting those 7 days, go to settings/developer option and enable OEM unlock. In order to never get locked again, flash TWRP for your device (install instructions below), boot into TWRP (do not boot into rom yet as you might get locked again), download and flash his fix from here (don`t forget to thank him too for his findings).
You can keep this zip near and flash it after flashing any custom rom, to be sure you don`t get locked again. The zip contains an universal script that disables the services responsable. Can be flashed on any device, if the device has the lock, won`t get locked again, if not, nothing will happend. I like to say "better safe than sorry".
How to safely install TWRP
Considering you are already unlocked (waited those 7 days), follow the next steps carefully:
Make sure you downloaded latest Odin, samsung usb drivers installed, latest RMM-State_Bypass fix (download links are in #2 post) and latest TWRP available for your device
Put RMM-State_Bypass.zip in external sdcard
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Reboot the phone into download mode and connect the usb cable
Open Odin, go into options and untick Auto-reboot and put the TWRP tar file in AP tab of odin, hit Start and wait
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip
Now you can reboot into rom and hopefully never get locked again.
If any of above steps fail, redo from step 1, more carefully this time.
How to safely root
Considering you already unlocked (waited those 7 days) and you have TWRP installed, follow the next steps carefully:
Download root zip and no-verity-opt-encrypt-6.0 (download links are in #2 post) and drop the zips into external sdcard
Boot into TWRP and swipe "Allow modifications"
Go into Wipe menu and select "Format data" - note that this will erase all your data including internal storage
Reboot recovery, swipe to "Allow modification" and flash RMM-State_Bypass.zip
Flash no-verity-opt-encrypt-6.0 zip downloaded at step #1 to disable data partition encryption
Flash root zip downloaded at step #1
Reboot the phone into system
After booting up in setting wizard make sure to uncheck diagnostic data
If any of above steps fail, redo from step 1, more carefully this time.
You can read more about it here here, here, here, here or here.
Credits
@BlackMesa123
@RicePlay33
@Yahia Angelo
@TaifAljaloo
@ananjaser1211

Useful links
Samsung Firmware download - Updato / Sammobile / Samsung-Firmware.org / Samsung-Updates.com
Samsung Usb Drivers
Odin 3.13.1
Latest SuperSU stable or test/beta
Latest Magisk stable or test/beta
NEW-RMM-State_Bypass
no-verity-opt-encrypt-6.0
FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes?
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: Why not formatting data at twrp install?
A: Phone will boot even if data is encrypted if you don't root. Also system partition is not encrypted meaning you can flash RMM-State_Bypass anyway.

Reserved for later use [emoji16]

corsicanu said:
Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything.
[*]After booting up in setting wizard make sure to uncheck diagnostic data
[/LIST]
Click to expand...
Click to collapse
The above item, diagnostic data, may have been the reason for blocking again the RMM STATE, since it was the only thing I did not do?

Perfect... Merci (bien suivre les indications et aucun problèmes...)
In Odin Mode:
FRP unlock
OEM unlock

[email protected] said:
Perfect... Merci (bien suivre les indications et aucun problèmes...)
In Odin Mode:
FRP unlock
OEM unlock
Click to expand...
Click to collapse
If you read again first post you'll see i already mentioned to make sure you have the OEM unlock toggle as On.
The toggle reflects the state of OEM unlock:
Toggle ON - phone unlocked, OEM off, FRP off.
Toggle OFF - phone locked, OEM on, FRP on.
Sent from my SM-A530F using Tapatalk

corsicanu said:
If you read again first post you'll see i already mentioned to make sure you have the OEM unlock toggle as On.
The toggle reflects the state of OEM unlock:
Toggle ON - phone unlocked, OEM off, FRP off.
Toggle OFF - phone locked, OEM on, FRP on.
Sent from my SM-A530F using Tapatalk
Click to expand...
Click to collapse
Question does twrp get flashed permanent ?
Sent from my LEX720 using xda premium

mchlbenner said:
Question does twrp get flashed permanent ?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
Yes.
Sent from my SM-A530F using Tapatalk

Update?
corsicanu said:
If you read again first post you'll see i already mentioned to make sure you have the OEM unlock toggle as On.
The toggle reflects the state of OEM unlock:
Toggle ON - phone unlocked, OEM off, FRP off.
Toggle OFF - phone locked, OEM on, FRP on.
Sent from my SM-A530F using Tapatalk
Click to expand...
Click to collapse
Hello can you tell me how install official firmware update? The best way?
- With Flashfire and keep root etc... (maybe too TWRP)
- Or Odin and reroot?
Thanks for your response...

[email protected] said:
Hello can you tell me how install official firmware update? The best way?
- With Flashfire and keep root etc... (maybe too TWRP)
- Or Odin and reroot?
Thanks for your response...
Click to expand...
Click to collapse
Personally i'd recommend flashing using odin. Flash the FW in odin, force it reboot in download mode, flash twrp, force the phone in twrp, flash again rmm bypass and you'll have updated fw with lock disabled.
Regards.
Sent from my SM-A530F using Tapatalk

corsicanu said:
Personally i'd recommend flashing using odin. Flash the FW in odin, force it reboot in download mode, flash twrp, force the phone in twrp, flash again rmm bypass and you'll have updated fw with lock disabled.
Regards.
Sent from my SM-A530F using Tapatalk
Click to expand...
Click to collapse
Install via Odin andOK but lose all... After the problemis impossible install TWRP (Little red line in (Odin) Download Mode who said "Only official released binaries are allowed to be flashed (RECOVERY)"), and my FRP and my OEM always OFF ...
Or waiting like describe here: https://forum.xda-developers.com/galaxy-note-8/help/official-released-binaries-allowed-to-t3681883

[email protected] said:
Install via Odin andOK but lose all... After the problemis impossible install TWRP (Little red line in (Odin) Download Mode who said "Only official released binaries are allowed to be flashed (RECOVERY)"), and my FRP and my OEM always OFF ...
Or waiting like describe here: https://forum.xda-developers.com/galaxy-note-8/help/official-released-binaries-allowed-to-t3681883
Click to expand...
Click to collapse
You have to developers in settings and click on about 7 times enable OEM unlock.
I hear what been happening idea!
Zips you need make sure you get them and flash all.
SuperSU.zip.
RMM-state-by pass mesa.zip
NO-verity-no-encrypt ashyx.zip
Don't put sim card in then boot up go to developers setting enable OEM unlock.
Make sure all your drivers are installed.
Setup Odin next put your phone in download mode next flash twrp.
Then hold volume up and down +power when screen turn black hold power+ volume+.
You will go into twrp flash all your zips then reformat data and reboot.
Make sure you swipe to allow modifications.
You should boot up fine but slow.
Sent from my LEX727 using xda premium

mchlbenner said:
You have to developers in settings and click on about 7 times enable OEM unlock.
I hear what been happening idea!
Zips you need make sure you get them and flash all.
SuperSU.zip.
RMM-state-by pass mesa.zip
NO-verity-no-encrypt ashyx.zip
Don't put sim card in then boot up go to developers setting enable OEM unlock.
Make sure all your drivers are installed.
Setup Odin next put your phone in download mode next flash twrp.
Then hold volume up and down +power when screen turn black hold power+ volume+.
You will go into twrp flash all your zips then reformat data and reboot.
Make sure you swipe to allow modifications.
You should boot up fine but slow.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thanks for your help...
I'll remove my sim card in then boot up go to developers setting, but i've not enable OEM unlock line.
My drivers are OK.
The first time for the root it was easy, now problem persist with OEM....(maybe due update with latest A730FXXU2ARC9).
I'm waiting a few days to see if OEM unlock reappears...

[email protected] said:
Thanks for your help...
I'll remove my sim card in then boot up go to developers setting, but i've not enable OEM unlock line.
My drivers are OK.
The first time for the root it was easy, now problem persist with OEM....(maybe due update with latest A730FXXU2ARC9).
I'm waiting a few days to see if OEM unlock reappears...
Click to expand...
Click to collapse
Are you locked out?
Sent from my LEX727 using xda premium

mchlbenner said:
Are you locked out?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Sorry for my bad English, i don't understand this???
It does remove lock code or Bootloader? (i'll remove all code who work with this phone...)
I'm not locked to any carrier...
I read this:
Firmware to last version and this update blocked the bootloader.
In Europe latest firmware's are locked so you can't flash TWRP via Odin.
But countries like India, Turkey etc.... there isn't any problem.
https://forum.xda-developers.com/samsung-a-series-2017/help/help-flash-twrp-t3715529

[email protected] said:
Sorry for my bad English, i don't understand this???
It does remove lock code or Bootloader? (i'll remove all code who work with this phone...)
I'm not locked to any carrier...
I read this:
Firmware to last version and this update blocked the bootloader.
In Europe latest firmware's are locked so you can't flash TWRP via Odin.
But countries like India, Turkey etc.... there isn't any problem.
https://forum.xda-developers.com/samsung-a-series-2017/help/help-flash-twrp-t3715529
Click to expand...
Click to collapse
Actually after 7-9 days the OEM Unlock reappears in developer settings...
And you can again via Odin reinstall TWRP and SuperSU...
But don't forget erase data (factory reset), otherwise you may have some problems...
:laugh:

[email protected] said:
Actually after 7-9 days the OEM Unlock reappears in developer settings...
And you can again via Odin reinstall TWRP and SuperSU...
But don't forget erase data (factory reset), otherwise you may have some problems...
:laugh:
Click to expand...
Click to collapse
Make sure you do all your installs with twrp before you reformat your device.
Keep in mind after reformat all you had on your sdcard is gone mtp doest work on twrp.
If you reboot without those zips you will be locked out for around 168 hours again.
Sent from my LEX727 using xda premium

mchlbenner said:
Make sure you do all your installs with twrp before you reformat your device.
Keep in mind after reformat all you had on your sdcard is gone mtp doest work on twrp.
If you reboot without those zips you will be locked out for around 168 hours again.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you that happened to me ... And wait again ...
Because the first time it worked, but i'll erase some applications like knox ... (with root uninstaller), and after reboot black screen and red message, and nothing... Require to install the firmware via Odin and wait 168h.:fingers-crossed:

[email protected] said:
Thank you that happened to me ... And wait again ...
Because the first time it worked, but i'll erase some applications like knox ... (with root uninstaller), and after reboot black screen and red message, and nothing... Require to install the firmware via Odin and wait 168h.:fingers-crossed:
Click to expand...
Click to collapse
this what did with and it worked I did this with no SIM card in you will have to reformat first.
make sure you have a micro sdcard for device.
install usb driver for device and download odin and set it up.
download twrp and root,mesascustom kernel v1.zip, no verify no encrypt.ashy yx. zip.
flash recovery with odin in ap after pass unplug hold power and volume up down at the same time.
when right when download leaves then push on power and volume up you will boot into twrp then make sure you have put in micro sdcard and swipe to allow modifications and then reformat device.
I chose to reboot to recovery.
go to micro sdcard and do your install.
then reboot phone after check your phone root and you check everything turn of your phone.
put in SIM card and turn on phone.
the no SIM will work that is what I did.
Sent from my SM-A730F using xda premium

Hello, Need precision my english is limited ...
mchlbenner said:
this what did with and it worked I did this with no SIM card in you will have to reformat first.
make sure you have a micro sdcard for device.
install usb driver for device and download odin and set it up.
download twrp and root,mesascustom kernel v1.zip, no verify no encrypt.ashy yx. zip.
flash recovery with odin in ap after pass unplug hold power and volume up down at the same time.
when right when download leaves then push on power and volume up you will boot into twrp then make sure you have put in micro sdcard and swipe to allow modifications and then reformat device.
I chose to reboot to recovery.
go to micro sdcard and do your install.
then reboot phone after check your phone root and you check everything turn of your phone.
put in SIM card and turn on phone.
the no SIM will work that is what I did.
------------------------------------------------------------------------------------------------
I have a problem to translate your message, if I understand I proceed like this:
I've Odin already installed and drivers...
I remove my sim card, and insert a Micro-SD card on my device,
1. I'll reformat my phone (return stock via settings).
2. i'll install TWRP recovery via Odin and i'll reboot directly to Recovery mode and swipe to allow
modifications and then reformat device.
3. I'll reboot in recovery mode and install "mesascustom kernel v1.zip" and "no verify no encrypt.ashy yx.zip"
from my SD-card.
4. Then i'll reboot phone after check your phone root and you check everything turn off your phone.
I'll put my SIM card and turn on phone.
The no SIM will work that is what I did.
What does mean the no SIM will work ? (no band active?) and Should i install "RMM-State_Bypass" too...? in step 3.
Thank you for correcting me if I made a mistake and it will be perfect...
Thank you in advance.
Gil
Click to expand...
Click to collapse

Samsung j610fn stuck in bootloop even after nand erase and pit flash, please help !

Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.

stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.

stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk

Try to flash latest rom

Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done

alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk

Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.

alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk

(Snapdragon) [ROM, TWRP, SUPERSU ROOT!] Samsung Galxy S8+ SM-G955U and SM-G955U1

This only works on the v7 and v8 bootloader(for now)
I am proud to present a new rom pre-installed with supersu!
Make sure to follow instructions. You will also be able to downgrade to 7.0 if you have 9.0
This tutorial is easy and will take a max time of 30 minutes to complete.
The samsung s8+ snapdragon has been hard to root to only have temp root, to bricking, but now, I have found and modified some files that you can use to permanently root your s8+ G955U and..You...can...install...TWRP!!!
TWRP will be installed as you go threw the process. Safetrap will be disabled and like all of the other rooting methods, your phone will only charge to 80%. YOUR WARRANTY WILL VOID DUE TO ROOTING AND INSTALLING A CUSTOM ROM. I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE(some idiot will accidentally brick there device. Like bruh, this method is easy. I don't see any way how you could accidentally brick your phone. If your reading this after bricking your phone...read the damn title next time. This method is only for the u.s versions of the s8+ aka Snapdragon.)
Let's get started!
You will first need to download this custom rom. It will disable safetrap and install twrp!
While the files are downloading, take that time to factory reset the phone and clear the cache.
Mod edit: Link removed.
This file package includes a modified version of odin.
There will be two firmware files. DO NOT FLASH BL AS IF YOU HAVE A BOOTLOADER 8 IT WILL NOT WORK. If you have bootloader 7 then it might work.
Next, put the phone into download mode. Hold Power + Volume Down + Bixby Button until the blue screen shows up. Press the volume button to continue after the blue screen shows up.
After that, open up odin and connect your phone with your cable to your computer using a USB 2.0 port. You can try USB 3.0 but might suffer a failure like a Auth error.
Once your phone is connected to your computer., odin should be showing (added!) and also will show a bar saying com. It doesn't matter what the number is.
After that, download the bootloader file for v8. You might be able to tell if your bootloader is 8 or seven(if you try flashing, it might say 8 > 7 or it just might say error. If you have v7 flash the file that came with the first download.
IF YOU FLASH SOMETHING AND IT FAILS, YOU HAVE TO RESTART THE PHONE INTO DOWNLOAD MODE AGAIN TO CLEAR THE ERRORS. IF NOT THE PHONE WILL NOT ALLOW YOU TO DOWNLOAD OTHER THINGS.
V8 BL download
Link removed.
If v8 fails then you might have to flash v7( located in folder from first download) if v7 fails flash v8(second download)
Flash the BL by clicking the BL button and navigating to the file location of the BL file.
In odin, go to the options table and unchecked f reset time and auto reboot. After that click flash! It will be quick when flashing the BL. After that once it says pass! Reboot the phone into download mode again. After that, click the reset button next to start and click on the AP button. Go to the folder where the AP file is located and load it into odin. It will freeze odin for a few seconds as it checks the MD5. Once your phone is in download mode and odin is responding again, click start and wait for the system to flash over! Depending on the speed of your pc it might go slow or fast.
Once it is done, it will said Failed! but that's ok. It has successfully completed installing and now you can reboot the phone normally. After it loads, safetrap should be disabled if a screen pops up saying continue or recovery. If none of that pops up that's fine, we still have some more files to flash.
Give the phone time to boot. The phone is not usable yet as android is still locked down. Wifi will not work but you will have temporary root access to the phone. You will see a app called flash fire. Open it but before you do, download the system file below!
Link removed.
Give it time to download. Extract the file from the 7z(have a file extractor that supports 7z). There should be a img file. Right click on it and press Send to the click on the phone. It will send it to the internal folder not downloads. Once it's on the phone, open flashfire then on the plus button. Then press the flash system(not Ota button) look for the img file and then press flash once you loaded in the .img Give it a few minutes to flash. After it's done flashing it will auto reboot. It might say that you flashed unauthorized files onto the phone and to contact your carrier. If not then skip this step. Go into odin. Select a BL file(remember if you think you have v8 flash the second download you downloaded. If you have the v7 bootloader, flash the BL that came with odin aka the first download. Uncheck f reset time and auto reboot. Flash the BL then wait. Once its done reboot the phone normally(hold Power button + down button) The error should be gone. The phone should reboot itself with a new boot logo animation. If that does happen, congrats you finished step one successfully . Now on to step two!
Shut down the phone and wipe the data and cache(factory reset)
Download the pre-installed supersu rom below:
Link removed.
Extract the files and only keep the AP file.
Go. Ack into odin and click on the AP button. Load in the AP file you just downloaded. Odin will freeze while checking the MD5. Once unfrozen, select the BL file you have. Remember, if you have v8 use the second download. If you have v7 use the first download or the one that came with odin. After that flash the two selected files and wait for the system to install.
Once the system is done it will say failed! Which is still good! Then reboot the phone and wait for it to load again. It will load into safe mode on first startup. Setup phone without Google until you want to login. Keep wifi off until your done setup. Once setup is done reboot phone by pressing power off. Once phone powers off, hold Power button until boot. Congrats if you made it this far! You have successfully rooted the samsung s8+ 955U snapdragon!
Will be making a video soon for people who had trouble installing.

@Flinnyd Please check your PM inbox. Thank you.
-Regards: Badger50 FSM

THANK YOU HAVE ...i made It as a NOOB !!! best user noob level guidance ever !!! I am trying to get to pixel simulation rom ...any pointers

jeetjeet said:
THANK YOU HAVE ...i made It as a NOOB !!! best user noob level guidance ever !!! I am trying to get to pixel simulation rom ...any pointers
Click to expand...
Click to collapse
So you were able to get your s8+ rooted?Look for any rom that might support your phone or cpu. As you learn, you might be able to edit rom files to work with your phone. The only problem is that phone companies are making it harder to make custom roms and also there's increasing security. I would say go for it!

Yes i fully rooted the SM 955u Snapdragon using the instructions above word by word and step by step ! Thanks a lot !

jeetjeet said:
Yes i fully rooted the SM 955u Snapdragon using the instructions above word by word and step by step ! Thanks a lot !
Click to expand...
Click to collapse
Yay!!!! Glad it helped

I am trying to flash other ROMS like Pixelexperience using the safestrap4.06v>Install>the zip file of the ROM ...i keep getting errors that "This package is for device greatlte etc" and the process stops , could you help with any ROMS suggested for snapdragon 955u

Sure. I'll try to find some roms then I'll pm you

jeetjeet said:
I am trying to flash other ROMS like Pixelexperience using the safestrap4.06v>Install>the zip file of the ROM ...i keep getting errors that "This package is for device greatlte etc" and the process stops , could you help with any ROMS suggested for snapdragon 955u
Click to expand...
Click to collapse
Forgot to mention installing other roms like pixel experience will remove your root.

I was able to root my S8+ with your method, thank you!
Now, I tried to use a module through Xposed but it doesn't work. I activated the module, rebooted and Xposed will detect it but it will not work even when it says that the module is active. Any suggestions?

Xpose probably broken pre installed. Try to reinstall xpose if you can

HEllo,
thank you for your work.
I am after all the stuff for SM-G955F
any idea?
thanks for the help

chandler132 said:
HEllo,
thank you for your work.
I am after all the stuff for SM-G955F
any idea?
thanks for the help
Click to expand...
Click to collapse
Will post for 955F but might not work and will need testers since i don't have the 955F

Flinnyd said:
Will post for 955F but might not work and will need testers since i don't have the 955F
Click to expand...
Click to collapse
thanks, I will test for you. Quick question, is it possible to bypass the FRP, if I flash the phone?

chandler132 said:
thanks, I will test for you. Quick question, is it possible to bypass the FRP, if I flash the phone?
Click to expand...
Click to collapse
From what I know, I believe it has to be bypassed to install a custom rom.

Flinnyd said:
From what I know, I believe it has to be bypassed to install a custom rom.
Click to expand...
Click to collapse
ok, so it means, that the installation will erase everything as well as the FRP?

Installing a custom rom will disable it

Does this work with the SM-G599U1? My BL is V8 and I had trouble installing this, and another root. It soft bricked my device and I had to flash stock BL I think? Anyways I'm a bit rusty and haven't done this since the Galaxy S3 was the biggest thing lol, so that may have contributed. Would love to hear some feedback on a link if this isn't the place to be rooting my device. Thanks!

AntyGuy77 said:
Does this work with the SM-G599U1? My BL is V8 and I had trouble installing this, and another root. It soft bricked my device and I had to flash stock BL I think? Anyways I'm a bit rusty and haven't done this since the Galaxy S3 was the biggest thing lol, so that may have contributed. Would love to hear some feedback on a link if this isn't the place to be rooting my device. Thanks!
Click to expand...
Click to collapse
I believe you can flash the 955U1 with this firmware but maybe I'm wrong. If you have bootloader v8 then flash the BL V8 file with odin with the AP file(second AP file download saying SAMFAILED) try that again and tell me if it works. If it doesn't then I'll release another method for the 955U1.
Thanks!

Flinnyd said:
I believe you can flash the 955U1 with this firmware but maybe I'm wrong. If you have bootloader v8 then flash the BL V8 file with odin with the AP file(second AP file download saying SAMFAILED) try that again and tell me if it works. If it doesn't then I'll release another method for the 955U1.
Thanks!
Click to expand...
Click to collapse
I tried again and I was successful. It was definitely confusing with all of the failed messages. but I got it. You can add that the 955U/1 works if you haven't tested yourself. Thanks again as a lot of the other methods seemed outdated and didn't work, or maybe I did it wrong lol.
Anyways, cheers!