Do you want to root your Snapdragon Galaxy S8 Plus? Here’s a quick and efficient tutorial to help you root Galaxy S8 Plus Snapdragon using SamFAIL on all carriers. The method works for SM-G955U and SM-G955U1 models sold in the US.
Samsung has been consistently releasing its flagship devices in two different variants – Exynos and Snapdragon since the S7 era. The trend continued with last year’s Galaxy S8/Note 8 series and the current S9/Note 9 lineup. We have already seen root for the Exynos S8, and it is based on the standard rooting method involving TWRP and SuperSU/Magisk. But things tend to get a bit complicated when it comes to Snapdragon-equipped Samsung devices and rooting, largely due to the locked bootloader on the US models.
Root has been available for the Snapdragon models on earlier firmware builds via the SamFAIL exploit, what we also used to root Galaxy Note 8 N950U. But later revisions to the firmware and more importantly, the Bootloader version rendered the exploit useless. However, thanks to XDA’s Recognized Contributor jrkruse, we now have a working method to root Galaxy S8 Plus Snapdragon with the added benefit that it does not trip the dreaded KNOX counter.
Features of the modified SamFAIL firmware include:
- Preloaded with SafeStrap recovery
- Pre-rooted with the latest SuperSU
- Xposed Framework installed
- Dolby Atmos toggle
- and more…
Depending upon your phone’s bootloader version, there are two different sets of files to help you root Galaxy S8 Plus Snapdragon. Follow the pointers below to find out your bootloader version. This process will work regardless of whether you are running Android 8.0 Oreo or Android 7.1.1 Nougat. What’s important is that your Bootloader version/revision matches with one of the below.
- U4XXXX (Bootloader rev4)
- U5XXXX (Bootloader rev5)
Does this method work on the Galaxy S8 too? – Simple, no! That’s because the S8 firmware with V3 bootloader or above has been patched against the SamFAIL method. So now that you know what’s gonna happen, head over to the instructions to root Galaxy S8 Plus Snapdragon.
Important Notes
- The instructions are solely meant for the Snapdragon version of Galaxy S8+ (G950U/U1), sold in the US. Do not attempt to use this method on an Exynos model.
- This method will only allow root access on the device. Flashing of custom recovery/ROMs is still a no-go, on account of the locked bootloader.
- Your device will only charge up to 80% battery level. Although several users have reported that it only showed 80% visually, while the device actually functioned like it was charged to 100%.
- You might sometimes observe a tint on the screen. In such a situation, simply turn off and then turn on the screen to fix it.
Prerequisites
- Please backup all your phone data prior to commencing. This process will wipe all data on your device. We recommend you follow our guide on how to backup Android phones
- Charge your S8 Plus to at least 70% battery level. This will prevent any sudden shutdown during the process.
- Download and install Samsung USB drivers on your PC.
Make sure to go through all the notes and fulfill all the requirements before you follow the instructions below to root Galaxy S8 Plus Snapdragon.
Downloads
- Latest Odin Flash tool: PrinceComsyModifiedODIN.zip
- SamFAIL Pre-rooted Firmware: G955USQS4BRB1_ODIN_SAMFAIL_V4&V5.zip
How to Root Galaxy S8 Plus Snapdragon using SamFAIL
- Download the latest Odin and pre-rooted firmware files and extract them to an easily accessible location on the PC.
- Power off your Galaxy S8 Plus completely.
- Then press and hold the Volume Down + Bixby + Power button until you see the warning screen.
- Read the warning message carefully and then tap the Volume Up button once to enter Download Mode
- Connect the phone to the PC using the USB cable.
- Run ‘Odin PrinceComsy.exe’ by double-clicking on it.
- The COM port on the Odin window should light up Blue. If it doesn’t, then make sure that you have installed proper USB drivers and also that Kies is not running in the background.
- Click the ‘BL’ button and select the ‘BL_V4_PART_1.tar‘ OR ‘BL_V5_PART_1.tar‘ (depending on whether you are on Bootloader version 4 or 5)from the folder you extracted earlier.
- Click the ‘Start’ button to start the flashing process.
» IMPORTANT: As soon as the process finishes and the phone shuts down, hold the Volume Down + Bixby button to re-enter Download Mode. - Click the ‘AP’ button and this time, select the ‘AP_SYSTEM_IMG_PART_2.tar’.
- Click on ‘Start’ to initiate the flashing process.
» The process will end up with the ‘FAIL’ message (This is perfectly normal, so nothing to worry about) and the phone will reboot automatically. When it does, make sure to hold the Volume Down + Bixby button again to enter Download Mode. - Next, make sure to click the ‘Reset’ button in Odin window.
- Click the ‘AP’ button and select the ‘BL_V4_PART_3.tar‘ OR ‘BL_V5_PART_3.tar‘ (depending on whether you are on Bootloader version 4 or 5).
- Finally, click on ‘Start’ to flash the file and thus root Galaxy S8 Plus Snapdragon using SamFAIL.
Once done, the phone will reboot automatically into a fresh rooted and de-bloated system. If you have got any questions regarding the method, feel free to check out the original XDA thread.
Note: If the phone gets stuck on boot animation for more than 10 minutes, reboot to recovery mode (Volume UP + Bixby + Power) and perform a wipe data/factory reset, followed by a wipe cache partition, and then reboot the device.
That’s it. You should now have root access on your Galaxy S8+ Snapdragon with SuperSU and are ready to unleash the full potential of your device. If you want to verify if your device has been successfully rooted, download and run the Root Checker app from the Play Store.
Hope you found our guide on How to Root Galaxy S8 Plus Snapdragon helpful. If you come across any roadblocks during the process, drop a comment below, and we will be more than happy to help you out.
Source: XDA
Thank you so very much. This is the most comprehensive root tutorial on the web hands down. After about 30 minutes of panic attacks and nail biting during the root process, it worked like a charm.
Hi Brian! You’re welcome and thank you for such kind words. I am glad the tutorial was helpful.
hi, this method has been a life saver. I was wondering however if there’s a way to switch to magisk instead? I love Xposed, but im looking to try out magisk if possible
Hi Bryan! I am afraid it’s not possible to get Magisk running, since it needs a modified boot image to work, and for that, you would need an unlocked bootloader (Which is certainly not possible). Thus, you will only have to stick to SuperSU. But you can (May be, I am not fully sure) try installing Xposed as a standalone.
Hi Dhananjay. When I go to settings -> Lock screen and security -> Face recognition, after trying to register my face it outputs an error message: “Face recognition not working, if it keeps happening, restart your phone”. What should I do?
Hi again, Alex. I have researched the XDA thread for this issue, however since no one reported it, I am sure it’s not a bug. Have you tried repeating the procedure from scratch?
Hello, it worked very fine, the only thing is that the face unlock function does not work, is there any fix for that issue?
Hi Alex. It should work fine since the developer did not state any issue present related to that. What error does it show when you try to set up Face Unlock?
If I use the pre-rooted image, will I be able to flash factory binary to the phone, so that I can change carrier information? Ever since I bought the phone and had T-mobile unlock my phone through their database, things went horribly wrong after putting in AT&T Sim. It basically changed the phone info, making it think it belonged to AT&T, but my main Sim is Mint Mobile (T-Mobile MVMO).
Hi Miles. In that case, simply re-flash the stock firmware for T-Mobile and then re-root your phone using this process.
Are there any roms that are compatible with this root?
I am sorry, but no.
I’m happy to say that I’ve successfully rooted my phone. Are there any roms that are compatible with this or will it revert my root?
Hi Kuro! Glad to know that! I am not sure you will be able to install anything else apart from this. This is basically a pre-rooted system partition.
Hy Dhananjay,
how to check my bootloader version?
Hi Indra. That could be depicted from the software version installed on your phone. Please open the dialer and enter *#1234# and let me know the exact details you see on the screen.
version android after flash?
Hi Lester. It will be BRB1 build based on Nougat.
Stuck at splash at boot. I tried the instructions provided, going to recovery mode, reset to stock, clear cache partition, rebooted, same issue. Tried 3 times! Any advice perhaps? Thank you in advanced!
Hi AustinL. Have you tried re-doing the process from step 1?
One more thing, did you have a V4 or V5 bootloader?
I believe V5 bootloader, but I used proper files. What I ended up doing, I think if I can remember correctly, is starting over, and upon first boot it said file system corrupt and asked me (in android window) to reset device, so I said YES, and it allowed me to setup as if it were a brand new phone and proceeded through setup. There were some errors connecting google at first if I remember correctly so I tried skipping passed it and linked it later without issues.
I do wonder now – with this method being success for me, how to utilize the ROM1-4 slots? I tried researching and some say cannot use on this model: Verizon G955U due to bootloader.
Here are my main questions for those slots:
1 – Can you use any other version of android, rooted or non-rooted? As if I wanted to boot to ROM1 which is essentially copy of STOCK, and have root access, where as booting to ROM2 would be a build without root access for utilization of Samsung Secure Folder, Chase Pay/Samsung Pay, etc?
2 – Can you refer me to a link which is a guide for how to properly utilize files during the installation phase of setting up ROM1-4? I tried and found that most files are image.7z and require BL_1 files to be used with ODIN, so that is OK if I also need computer during first time setup of each ROM slot, but really lost on how to actually proceed through the setup of each slot because I tried to do once and it said “NO OS INSTALLED” when booting after TWRP/SafeStrap reported successful flash of image to ROM1. To be fair, I was using completely different built ROM for ROM1 slot, Stock was rooted nougat where ROM1 was going to be non-rooted oreo.
3 – With this solution installed, what is the correct process to restore from backup? I had backed up STOCK, couldn’t figure out how to duplicate STOCK to ROM so made my changes to STOCK, and this morning maybe one change too many before reboot and cannot get beyond lock screen, no response. I just went straight to try to restore, said error mounting at the end…
Again, thank you in advanced for your time!
Hi again! Glad it booted fine. Before I try and answer your questions, can you please tell me what you mean by “How to utilize the ROM1-4 slots?”. Did you mean using the DualBootPatcher to boot multiple ROMs?
Hi I have a G955W and used this method to root. Phone seems to show model G955U in settings after root. Is there a specific method that I need to follow to unroot back to original firmware and G955W? I don’t seem to be able to simply flash original firmware with Odin and stock G955W firmware BL,AP,CO and CSC. Any help on this would be super appreciated. Thanks.
Hi Michael. What error does it show when you try to flash G955W firmware using Odin?
Hi,
Thank you for the response. Sorry, I should have given you more information when describing the issue.
When I try using the PrinceComsy version here is what I am getting in the log before a window pops up saying Odin Downloader has stopped working.:
Odin engine v(ID:3.1203)..
File analysis
SetupConnection..
initialization..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
{Then the Window Pops up “Odin stopped working”}
I am using the stock firmware for my device and carrier. (downloaded from updato.com) I verified that it was the correct baseband version (G955WVLS5BSA1) as was originally on the phone. I have tried using ODIN ver 3.13.1 as well and I get the “FAIL! SHA256 is invalid” error.
Both versions are giving me the blue highlighted 0:[COM4] indicating that Odin can see my mobile device so I think I have good drivers on my windows machine.
I am selecting all the files from the firmware (BL , AP , CP , CSC) all checked off and all finish checking MD5 successfully in Odin when added.
I have ensured that “Auto Reboot” and “F. Reset Time” are the only things checked off in the options tab as well.
Not sure what could be wrong… any help would be greatly appreciated.
Hi Michael. Don’t be sorry about it. Your reply has given me all the necessary details. I want you to download this patched version of Odin 3.13.1 that skips the SHA256 checks. Please retry flashing the stock firmware via this and let me know if it succeeds.
Hi Dhananjay,
Awesome! Thank you so much for your help. It worked perfectly!
Thx
Hi Michael!
Did you really succeeded in rooting your SM-G955W ? I have same phone, same baseband version than you ( G955WVLS5BSA1) and I’ve tried many methods to root my S8+ and so far, nothing works.
I might give it a try.
Thx
Hi Audrey,
Yes I have rooted my phone following the method here. I can verify that it does work for the SM-G955W with this baseband version.
Hi again, Michael. I am glad it worked. I have updated the Odin article with the link to the patched version as well.
Hi, I was wondering if there is a way to use SuperSU in SBIN mode when using this root method? I would like to use SUHide and all the information I have found indicates that SuperSU needs to be running in SBIN mode to use SUHide. Thanks for the great posts and information. Very well done.
Hi Mike. First off, thank you for your appreciation.
Since the method uses the latest SuperSU release, then I am quite sure that SuperSU will run in SBIN mode.
“FAIL! SHA256 is invalid”
g955u bl v5
i used the last version of odin
please help me
I have the same device and had the same issue. Use the PrinceComsy Version. Working like a Charm
i faced same problem but solved
use Odin “PrinceComsy”
Hi Bilal. Thanks for pointing that out. I have updated the instructions accordingly.
I thought when I went with the GS8+ I would not have any need to root. After a year, I have decided to give it a try, mainly to use TBU. A couple of questions:
1. My current baseband version is G955U1UEU5CRK3. There is a software update pending with a baseband version G955U1UES5CRL2. Safe to assume either version is okay for rooting (using bootloader v5) and therefore I can take the update prior to rooting?
2. Once rooted, do I need to “block” any future OTA updates to hold root?
3. Is there currently a proven process for returning to the unrooted condition?
Your tutorial is really well written and clear. I appreciate your effort.
Hi Don! It’s wise of you to appreciate it! Just out of curiosity, what is TBU that you’ve referred to here?
As for your questions:
1)Yes, your phone is rootable and there’s no benefit of taking OTAs, the method pushes your system back to an older firmware.
2) This will block future OTAs
3) You can always flash back the stock firmware using Odin.
Over everything, I would like to know the reason for rooting first. So, if there’s an alternative to do the same without root, then that is what I would recommend.
Thanks for the information. By TBU, I meant Titanium backup. Probably not a real good reason to root. Auto backup of apps/data to Samsung cloud seems to work well. I assume Samsung has yet to block your method with the latest clr2 update.
Thanks
You’re welcome, Don! Yeah, even I think likewise. It’s best to keep the software up-to-date unless you have a strong reason for rooting.
The method can’t be blocked, it just downgrades your system to an older firmware that was rootable. Yes, if the bootloader version upgrades to V6, then this method would be unusable.
I wish Google soon pushes app/data backup service to its phones as well (Like my Pixel 2 XL/3 XL). I wouldn’t blame your reason to root, some people do it for TBU. But if there’s an alternative like Samsung Cloud, then I wouldn’t feel the need to root.
Well I got in a rush and soft bricked my 8+. Insurance sent me a brand new 8+. Didn’t think they would so I jumped the gun and bought one myself. Now I have two phones so I can afford to try this again. I “think” I caused the problem when I was downloading the AP file. Question:
Para 11 says “the phone will boot automatically. When it does,..enter download mode”.What is the timing on this? Do I take action to enter download as soon as it starts to reboot or do I wait for it to startup? What if it doesn’t reboot. Is this where I would go to recovering and clear cache, etc.”
This time I have a stock firmware on my sd card so I am hoping if all else fails, I can enter recovery and reboot from the card.
Thanks for all you help.
ATTENTION ALL: if you happen to ignore and try to use magisk with this exploit anyways, and find yourself facing a soft brick Reflash the BL_V4_PART_1 using the 3.13 Odin *PRINCE COMSY VERSION*
that is all
Thanks, Mike! I am sure this info shall prove very helpful to others here.
EDIT: I have modified your comment slightly to reflect our Comments Policy.
i tried bl v5 and this message result “FAIL! SHA256 is invalid”
although my bl is v5 and my carrier is sprint
what should i do please help me bro
Hi. Which version of Odin tool did you use?
Odin 3.13.1
it dosen’t work in my phone g955u bl v5
and when i try to install official bl from the official rom it dosen’t accept any files from oden
All threads completed. (succeed 0 / failed 1)
Odin engine v(ID:3.1301)..
File analysis..
Total Binary size: 199 M
SetupConnection..
All threads completed. (succeed 0 / failed 1)
Removed!!
Added!!
Odin engine v(ID:3.1301)..
File analysis..
Total Binary size: 199 M
SetupConnection..
Initialzation..
FAIL! SHA256 is invalid
All threads completed. (succeed 0 / failed 1)
if you read the tutorial it says it is supposed to say fail, and it will eventually restart. That is where i am having my issue it says fail but it is not restarting on its own. I wait for over 10 minutes and no restart them i did “Note: If the phone gets stuck on boot animation for more than 10 minutes, reboot to recovery mode (Volume UP + Bixby + Power) and perform a wipe data/factory reset, followed by a wipe cache partition, and then reboot the device.” and tried again and same thing …
Hi, Shadokeeper. By any chance, is the ‘Auto Reboot’ option unchecked in the ‘Options’ tab of Odin tool? Please check and let me know.
my phone is “g955usqu5crk1” lasted update
will this way work for me?
can you record video doing this way 😀
Hi Saleh, yes, it will work for your phone. However, note that the this is a pre-rooted Nougat ROM and not Oreo. So, you will have to compromise with the previous Android version if you really need root.
g955usqs2brb1 qualcomm snapdragon 835 will work? for tmobile
Hi. This is for S8+ with BL version 5 or 4. Since yours is version 2, I suggest you go with PartCyborgROM that uses the same method. Please make sure to carefully read the whole thread and understand the process before you begin.
Hi, is there a way to make it work on G955W ( Canadian carriers ) ?
Yes, it should work. The CSC stays the same, only the system and bootloader partitions are modified.
Hi !
Noob question but better than a dumb one. For my device it is currently running 8.0.0
Baseband is G955USQU5CRIB
Should this method work for me ?
I tried it and on the download page it didn’t reboot and it did give me the messages below while it was plugged in
Look forward to hearing from you !
Added!!
Odin engine v(ID:3.1210)..
File analysis..
SetupConnection..
All threads completed. (succeed 0 / failed 1)
Hi Red. Yes, this method will work for your model.
Did you use the correct files? I mean did you use BL_V4_PART_1.tar or BL_V5_PART_1.tar
Also, which Odin version did you use?
device currently running 8.0.0 really work?
no need to downgrade?
Also, since my phone is already running BL revision 2, won’t the SamFAIL PartCyborgRom method work for it? That method will work for the Snapdragon G955u running Android 8.0 and running BL revisions 1 & 2. I just don’t know if my security patch level from March 1st, 2018 possibly patched that exploit method? As far as I know, that root method was implemented December of 2017, but I don’t know if it was patched with the March 2018 security update or in a later security update. Or do you think I should try to update my phone and hopefully get BL revision 4 or 5 and then try this method here you have given?
Hi again Tom, there’s something that I would point out here.
Your S8+ is running Android Oreo and unfortunately, there’s no way to root it. The only root methods available, be it PartCyborgROM or this one, these are only for Nougat firmware.
Since your phone is on V2, I suggest you opt for PartCyborgROM that supports V2 BL, but then it will take your phone back to Nougat.
But I thought this article said that this root method works for both Nougat and Oreo?
Scratch that. I just now realized you meant that it will take you from Oreo, back to Nougat, in order for root to work. I thought it meant root worked for Oreo also at first 😂 It’s been a long two days.. I apologize.
Thanks for the help and guidance, I appreciate it! I’m entirely new to Samsung so this has been a bit of an adjustment. I’ve been on a rooted lollipop OnePlus X for nearly two and a half years now, so I haven’t been up on more recent developments like companies (or I should say, carriers) cracking down on bootloaders, just like I didn’t know that Samsung didn’t even use Fastboot lol.
Anyways, thanks for the help and have a good one!
My baseband version is: G955USQU2CRC5
So I assume that I am on version 2, correct?
So, is there a way to upgrade to version 4 or 5?
I just bought this phone and it came with Android 8.0.0 already installed and the last security patch was March 1, 2018.
But I do have software update/s available (I don’t know if there are multiple waiting behind one another or if it’s just one update). If I update, is it possible I’ll get one of the current revisions (4 or 5)?
Hi Tom, yes you are right, the BL version of your phone is V2. Yes, once you start updating, you will reach V4 and then V5 BL eventually.
When I opened the Odin application a message about having the proper binary used. Then after clicking past the message, while on the first step with flashing the BL I came across a sha256 message so I then downloaded a patched version of Odin , same version, however I am stuck at the setupconnection message and it has not progressed at all.
Hi Brandon, please try using this one.
Hi, if I don’t tick the re-partition then it says re-partition failed. However, If I do, it says it can’t open the specified file (Line: 1892).
Model: G950U1UESCRF5
I am also having troubles downgrading from 8.0 to 7.0 version for Android if you have any tips Thanks
Hi Eric, at what step does this happen?
As for downgrading, you cannot downgrade from 8.0 to 7.0 due to bootloader restrictions.
It worked for me. I’m on an sm955u and I was able to downgrade from 8.0 to 7.0
Hi Michelle, it will only work if both the 8.0 and 7.0 firmware have the same bootloader revision. I believe it was the same, in your situation.
Is there a way to do this on snapdragon oreo with bootloader version 3? I tired using both v4 and v5 bl part 1 and obviously they failed.
Thanks
Hi Alan, I am sorry but it only works for BL v4 and v5. v3 is not supported.
Thought so. Is there a way to upgrade the bootloader to 4 or 5?
i did an upgrade on my phone and it is on version G950U1UES5CRF5, so the bootloader is now version 5, and when i tired the root odin fails on part 1 saying the re-partion operation failed. Am i missing something else?
Thanks
Please make sure that re-partition is not ticked under the ‘Options’ in Odin program.
It is not checked, and i am still getting that same error
That’s odd. What do you see in the PIT menu that’s beside the ‘Options’ in Odin window? Also, did you choose any .pit file in Odin?