Root on S8?

Search This thread

nkomp18

Senior Member
Sep 20, 2012
67
2
What's the latest on Root on S8+?
I noticed some threads on the Snapdragon variant which has locked bootloader and is not yet possible to root.
But do we have a clear, verified method on the Exynos variant?
I just got mine today and I am not sure which source to trust. I want to find a guide that's been verified and won't cause any issues.
 

xeathpk

Senior Member
May 11, 2017
113
34
What's the latest on Root on S8+?
I noticed some threads on the Snapdragon variant which has locked bootloader and is not yet possible to root.
But do we have a clear, verified method on the Exynos variant?
I just got mine today and I am not sure which source to trust. I want to find a guide that's been verified and won't cause any issues.

If you have Exynos its the same process as rooting the S7. Flash the latest version of TWRP recovery, then inside TWRP format data and install no-verity-opt-encrypt-5.1.zip.

Lastly install Magisk v12.0 with TWRP and you're good to go. Alternatively you could install SuperSu v2.79 instead of Magisk but you'll have an almost impossible task of hiding your root from certain apps so I wouldn't recommend it myself.

EDIT: Reading back, it actually sounds like you may be new to rooting so I've gone and found a more in depth guide for you to help you along, enjoy mate :)

https://forum.xda-developers.com/galaxy-s8+/development/recovery-twrp-galaxy-s8-exynos-t3594756
 
Last edited:

nkomp18

Senior Member
Sep 20, 2012
67
2
Thanks for the guide!

You're a star. I am indeed a noob. I did root and install a custom rom on my previous phone but then again I also bricked it a couple of times and I really don't want to go through that again!

If you have Exynos its the same process as rooting the S7. Flash the latest version of TWRP recovery, then inside TWRP format data and install no-verity-opt-encrypt-5.1.zip.

Lastly install Magisk v12.0 with TWRP and you're good to go. Alternatively you could install SuperSu v2.79 instead of Magisk but you'll have an almost impossible task of hiding your root from certain apps so I wouldn't recommend it myself.

EDIT: Reading back, it actually sounds like you may be new to rooting so I've gone and found a more in depth guide for you to help you along, enjoy mate :)

https://forum.xda-developers.com/galaxy-s8+/development/recovery-twrp-galaxy-s8-exynos-t3594756
 

nkomp18

Senior Member
Sep 20, 2012
67
2
Hello everyone.
I rooted my new Galaxy S8+ and it was fine for about a day, but today it started crashing and keeps switching off.
I am really petrified, I am starting to regret doing this and also voiding the warranty.
Question: Can we somehow bring it back to exactly how it was before? By that, I mean, getting the automatic Samsung firmware updates (OTA updates)
 
Last edited:

MicroMod777

Recognized Contributor
Hello everyone.
I rooted my new Galaxy S8+ and it was fine for about a day, but today it started crashing and keeps switching off.
I am really petrified, I am starting to regret doing this and also voiding the warranty.
Question: Can we somehow bring it back to exactly how it was before? Perhaps factory reset?
How did you root it?

Sent from my SM-G955U using Tapatalk
 

nkomp18

Senior Member
Sep 20, 2012
67
2
Followed this guide.
It worked quite well for about a day. After the restart I started getting errors and the phone was almost unusable.
I did a factory reset now to be able to use the phone again, but I am starting to think that it would be safer to stick to Samsung's original firmware
 

xeathpk

Senior Member
May 11, 2017
113
34
Followed this guide.
It worked quite well for about a day. After the restart I started getting errors and the phone was almost unusable.
I did a factory reset now to be able to use the phone again, but I am starting to think that it would be safer to stick to Samsung's original firmware
You really dont have a lot of luck with rooting do you! Are you 100% sure you followed the guide down to the letter? If so its unlikely that your issues would be related to root unless you've made a mistake somewhere along the way. Its easily fixed if something has gone wrong.

These phones are almost impossible to hard brick unless you're messing with the partitions of the phone or something. Even if you've made a mistake you can easily make a backup, flash the stock ROM back and start the process again. Let me repeat again, are you sure that these problems are related to root and not another issue or app you've installed more recently?

So far my root, like many others so far, has been 100% stable. It shouldn't be giving you any issues by itself if done correctly.
 

nkomp18

Senior Member
Sep 20, 2012
67
2
This is reassuring. I followed the guide to the letter. I had magisk working and gave Titanium root and restored a few apps (around 10 apps).
Later I downloaded the package disabler app to stop the " Security log agent" giving me that annoying restart notification.
I am assuming you get that too, right?
The phone was okay for a while and the notification did go away.
However, during the day, my whatsapp crashed and then immediately after I started getting non stop pop ups saying:
'the process android.process.acore has stopped'
and
'the process android.process.media has stopped'
I noticed the formed would pop up every time the phone attempted to use Google account (which is constantly and always).
The media would pop up every time the phone attempted to read any type of media files, pictures, videos or music files.
I read a lot of guides online of how to make those go away, tried wiping cache (dalvik), all app caches, disconnecting all my accounts and whatever other suggestion I could find.
The phone was completely unusable.
I have no idea what caused it but I am now paranoid it will start again, at any moment, again for no reason
 

xeathpk

Senior Member
May 11, 2017
113
34
So your problems have stopped since then? Just cross your fingers and hope whatever troubleshooting you did solved your problems for good I suppose. It would be odd for root to be working for some time only to randomly start giving you trouble a day or two later. You sure you didn't disable anything you weren't supposed to with Package Disabler?
 

nkomp18

Senior Member
Sep 20, 2012
67
2
The problems stopped because I factory reset and I am not rooted now.
I am scared to re-root because the problem appeared out of nowhere. I hadn't done anything to trigger it, I wasn't using the phone at all during the day.
It could be anything triggering it. Has no one with a rooted phone had something like that happen to them?
 

xeathpk

Senior Member
May 11, 2017
113
34
Its more likely that Titanium Backup had something to do with your problem than the root. Could be a incompatible or corrupt backup that you restored with Titanium that wasn't playing nicely and causing crashes.

I haven't heard of anyone with any of the issues you describe by simply installing a custom recovery (TWRP) and Magisk (what gives the phone root access).

I'm almost certain that if you followed the guide and you rooted the device correctly than the Root would almost certainly be circumstantial, and not the culprit of your problems.
 

nkomp18

Senior Member
Sep 20, 2012
67
2
okay I think I'll try to reroot by flashing magisk and then testing it for a few days.
I will try to leave titanium out of it for a while. Then if the phone doesn't go crazy, I will make a nand backup and try titanium.
Let's hope it goes well.

I assume everyone else here has the security log agent notification problem, right? We all flashed the same rom.
How do people here deal with this annoying announcement?
 

xeathpk

Senior Member
May 11, 2017
113
34
okay I think I'll try to reroot by flashing magisk and then testing it for a few days.
I will try to leave titanium out of it for a while. Then if the phone doesn't go crazy, I will make a nand backup and try titanium.
Let's hope it goes well.

I assume everyone else here has the security log agent notification problem, right? We all flashed the same rom.
How do people here deal with this annoying announcement?
I just disabled it through the OS. One way is to wait till the next time you get the prompt. If you get the notification again pull the notification slightly to the left or right and then choose the gear icon to access the notification settings for the application.

If you'd like to disable it now you can find the app info and notification settings in Settings > Apps > Show System Apps and then scroll down to SecurityLogAgent. Inside you can disable the app or alter the notification settings.
 

Attachments

  • Screenshot_20170525-041222.jpg
    Screenshot_20170525-041222.jpg
    190.1 KB · Views: 594
  • 20170525_041645.jpg
    20170525_041645.jpg
    195.8 KB · Views: 614

nkomp18

Senior Member
Sep 20, 2012
67
2
Thanks for that.
Not sure how you managed it. For me the option to disable is grayed out and in the notification settings it is set to " Allowed" . The only option I have is to either make it a priority or not.
You seem to have a lot more control over your device. Very strange
 

xeathpk

Senior Member
May 11, 2017
113
34
Hmm that's very strange indeed. I wonder if it has anything to do with which FW you're using. Perhaps some prevent you from altering the SecurityEventLog? First thing I did when I got this phone was install an unbranded clean Australian XSA formware to get rid of my phone providers stock firmware.

I'm sorry I couldn't be of more help in that regard. You might be able to disable it through package Disabler again but I'm not sure how that would go down. Personally I'm weary about using a Disabler on certain things because they can sometimes break some functionality of other apps or features or cause other such problems if you're not careful. Its entirely up to you though.

If I were you I'd just make sure to create a full backup with TWRP immediately after root and before altering anything so you'll have a fully working system image to return to in case anything goes wrong.
 

nkomp18

Senior Member
Sep 20, 2012
67
2
Just to let you know that now things are stable after the factory reset and I have rooted again with magisk without problems.
Also I restored my apps with Titanium, again without problems.
I am pretty certain the issue was caused by the free "package disabler' app which apparently deleted all the accounts and of the phone and attempts to recreate them. This corrupted files on the phone making the phone completely unusable.
The funny thing is, you can disable the annoying services directly from Titanium so that stupid app is not even needed.
So I am writing this here in hope it will help someone.
 
  • Like
Reactions: SammyBoyWonder

xeathpk

Senior Member
May 11, 2017
113
34
Just to let you know that now things are stable after the factory reset and I have rooted again with magisk without problems.
Also I restored my apps with Titanium, again without problems.
I am pretty certain the issue was caused by the free "package disabler' app which apparently deleted all the accounts and of the phone and attempts to recreate them. This corrupted files on the phone making the phone completely unusable.
The funny thing is, you can disable the annoying services directly from Titanium so that stupid app is not even needed.
So I am writing this here in hope it will help someone.


Glad to hear that you finally got to the bottom of it. Enjoy bud. :)
 
  • Like
Reactions: SammyBoyWonder

duronimo

New member
May 24, 2017
3
0
s8+ root ever? (sprint)

I use my phone as a router. Without root my s8+ is sitting in a drawer. I simply know too.much to walk around without root access to the Unix box in my pocket ... What's the hold up? Should I return it to beast bye? I'd rather mail it to whomever can crack it....then pay them to mail it back....heh.....

& Thanks "Duronimo"
former ops #oldwarez (undernet)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    https://www.oneclickroot.com/samsung/samsung-galaxy-s8/

    Haven't tested it yet... Wife just unboxed hers today.


    Sent from my iPhone using Tapatalk

    Those sites are phony as f***.
    5
    Without unlocked bootloader, root and ready to install custom AOSP Rom with xposed, I do not need a new phone.
    At that point there are absolutely no reasons to downgrade my Nexus 6.
    I really like the features that offer Galaxy s8 plus but software is over 60% of any device.

    ---------- Post added at 11:49 AM ---------- Previous post was at 11:44 AM ----------

    As a Verizon user I've learned to not even ask about root or look forward to it. And you know what. I'm ok with that.

    It just incredible, you are missing so much with your phone !! :eek:
    4
    Why do I do this every time I get a new phone that hasn't got any root out yet ??

    As the flashoholic customization-junkie I am, I simply cannot wait for proper root or resist trying all these king, supersume, oneclick, this that and the other, and all these crappy apps and tools that claim to give you root, and every time I end up ****ing the phone up somehow, so that much of the security-functionality like knox stop working, and won't be fixed no matter what I do. Side Switch recovery restore, Odin firmware flash, reset erase... nothing gets the error fixed, and now I can't run S Health or Secure Folder, and most certainly other things I haven't found out yet. I actually get a message that my device is rooted when I try to run S-Health, and a message that the device has been tampered with when trying to make a secure folder.

    And so it has been with every Samsung device since my N7100 Note II back in the day. And every time I come to a point where I regret even trying any of that crap, as I have now. But every time I come to this, I also realize that every time this happens, it doesn't take long before some twrp and supersu are coming, and then custom ROMS, and I just as soon forget about all the crap I did the first days and don't give it another thought until I yet again find myself with a brand new but "broken" device after ****ing it up, yet again.

    And every time, there's threads like this, with people worried about if root is coming or even possible because locked bootloaders and self-restoring recovery and all that **** Samsung is throwing our way with each new flagship model to try to keep us out.

    And as always, all that **** doesn't really matter. A locked bootloader can simply be exchanged with an unlocked one through a kernel / bootloader odin, and I'm sure someone, more than one, is sitting and fiddling with some kernel that will enable custom recovery and supersu / root, right at this very moment.

    I believe the S-health issue is that efuse hardware **** that got tripped, but it's strange because it said "device has been tampered with" or something first, but suddenly it started saying "device has been rooted" in S-Health, but it still says "tampering" in secure folder. I have no idea if it's supersu, superuser, magisk or some king **** that has fooled my S-Health into thinking my s8+ is rooted. I have tried sideloading and pushing and installing just about every superuser app, and some busyboxes.

    Yeah, I know, it's really ****ed up, but what can I say, have you ever seen a junkie before ?? It ain't pretty, and I'm a true flashoholic junkie. I actually managed to root a Sony Xperia Go with a locked bootloader once, just by ****ing with every app and service possible.

    Though, I tend to agree with some comments over here about root not being that important anymore, at least not at Samsung devices. I have a Nexus 6p, which I get all my AOSP needs satisfied with. as such, and I like many of the Samsung special features, like S-Health, which I've used since my N7100-days.

    BTW, to bypass that "device is rooted" issue I just installed an old version of S-Health, which then was installed as a user-app and not a system-app, and that fixed it.

    Root will come, I am certain it will !!!

    Wow...
    3
    WHY?

    Why do I do this every time I get a new phone that hasn't got any root out yet ??

    As the flashoholic customization-junkie I am, I simply cannot wait for proper root or resist trying all these king, supersume, oneclick, this that and the other, and all these crappy apps and tools that claim to give you root, and every time I end up ****ing the phone up somehow, so that much of the security-functionality like knox stop working, and won't be fixed no matter what I do. Side Switch recovery restore, Odin firmware flash, reset erase... nothing gets the error fixed, and now I can't run S Health or Secure Folder, and most certainly other things I haven't found out yet. I actually get a message that my device is rooted when I try to run S-Health, and a message that the device has been tampered with when trying to make a secure folder.

    And so it has been with every Samsung device since my N7100 Note II back in the day. And every time I come to a point where I regret even trying any of that crap, as I have now. But every time I come to this, I also realize that every time this happens, it doesn't take long before some twrp and supersu are coming, and then custom ROMS, and I just as soon forget about all the crap I did the first days and don't give it another thought until I yet again find myself with a brand new but "broken" device after ****ing it up, yet again.

    And every time, there's threads like this, with people worried about if root is coming or even possible because locked bootloaders and self-restoring recovery and all that **** Samsung is throwing our way with each new flagship model to try to keep us out.

    And as always, all that **** doesn't really matter. A locked bootloader can simply be exchanged with an unlocked one through a kernel / bootloader odin, and I'm sure someone, more than one, is sitting and fiddling with some kernel that will enable custom recovery and supersu / root, right at this very moment.

    I believe the S-health issue is that efuse hardware **** that got tripped, but it's strange because it said "device has been tampered with" or something first, but suddenly it started saying "device has been rooted" in S-Health, but it still says "tampering" in secure folder. I have no idea if it's supersu, superuser, magisk or some king **** that has fooled my S-Health into thinking my s8+ is rooted. I have tried sideloading and pushing and installing just about every superuser app, and some busyboxes.

    Yeah, I know, it's really ****ed up, but what can I say, have you ever seen a junkie before ?? It ain't pretty, and I'm a true flashoholic junkie. I actually managed to root a Sony Xperia Go with a locked bootloader once, just by ****ing with every app and service possible.

    Though, I tend to agree with some comments over here about root not being that important anymore, at least not at Samsung devices. I have a Nexus 6p, which I get all my AOSP needs satisfied with. as such, and I like many of the Samsung special features, like S-Health, which I've used since my N7100-days.

    BTW, to bypass that "device is rooted" issue I just installed an old version of S-Health, which then was installed as a user-app and not a system-app, and that fixed it.

    Root will come, I am certain it will !!!
    3
    I'm sure root will happen.....when.....who knows. The S7 and s7e had eng.kernels for MM and Nougat all within a few months If even that.

    Sent from my SM-G950T using XDA-Developers Legacy app

    Yeah and the eng kernels are crap