I've been asked to check out a ladies phone from work. She has a Verizon variant of the Galaxy S6 Edge (SM-G925R6) from Chariton Valley.
She appears to have successfully rooted it as upon boot it has the SU popup asking to grant permission. However, the touchscreen does not work at all. I've managed to access the download (Odin maybe?) screen and can also get into the twrp recovery.
Does anyone know of any options that I can try and/or a custom ROM that would fix the situation?
I also noticed that it has a message something along the lines of kernel is not seandroid enforcing.
Any help would be greatly appreciated. Thanks.
Treadstone06 said:
I've been asked to check out a ladies phone from work. She has a Verizon variant of the Galaxy S6 Edge (SM-G925R6) from Chariton Valley.
She appears to have successfully rooted it as upon boot it has the SU popup asking to grant permission. However, the touchscreen does not work at all. I've managed to access the download (Odin maybe?) screen and can also get into the twrp recovery.
Does anyone know of any options that I can try and/or a custom ROM that would fix the situation?
I also noticed that it has a message something along the lines of kernel is not seandroid enforcing.
Any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Is it running 6.0.1 mm?
Sent from my SM-G925V using XDA-Developers mobile app
Related
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Once you rooted you customized the software. That custom padlock logo is a tattle tale telling on you! I believe your using an xposed module to "fake system status" in order to fool certain people. The xposed module is failing when you see this. It's possible an update, or setting was applied to the module making it fail. Or maybe it's losing it's superuser rights. I had the same thing happen to me. I used triangle away and haven't seen it again. It will surely come back on a factory reset I'm sure.
This happened to me as well and I know its not the xposed because I checked it. This has only happened 3 times and has not happen in like 4 days I checked my system and it says everything is official it did say custom the 3 times it happened I did do a factory reset and it still says official my question is has anyone found a way to unroot for warranty porpoises? Su will not unroot towelroot from what im seeing ...but if everything says official would you even need to worry about unrooting lol I mean if u just factory reset and sent it back I shows no sign of root its all official and no knox tripped ..just a thought ..
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Sent from my SM-N900A using XDA Free mobile app
Freezing "sysscope " on my sgs4 removed the custom unlock boot logo /icon like a charm, however it still bounces back and forth between official and custom on device status when looking.
mrcoffee1985 said:
I have rooted my note 3 via towelroot (thank you so much geohot!!!). I have installed exposed framework, supersu, busybox and safestrap. Here is the question: my note switches from device status custom to official. On some boots it will have the custom status icon on screen. Some boots it does not. This corresponds to the system info as well....sometime shows custom and sometimes official. Why is this? Its no big deal i'm just curious. Thanks.
Click to expand...
Click to collapse
Remove "busy box" file in XBIN system folder. Found this solution on a "Galaxy S4" forum. For a some reason a system keeps some leftovers after the full recovery done. Kinda wrong.
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
Pretty sure you can't encrypt once you root. Or maybe it's once you put a custom recovery. I've never been able to use encryption after rooting my phones.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Hey be careful if your looking to install Safe Strap. Word for word what hashcode said
"THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW."
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
STraver said:
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Click to expand...
Click to collapse
I'm experiencing the same issue and changing the flash/encrypt/root sequence doesn't seem to change the results (encryption will not work, phone reboots). I'm attempting to root using CF's auto-root tools.
Wondering if there may be another root technique that wouldn't trip up the encryption process?
Disclaimers...
1. I know that encryption on a rooted device doesn't make much sense, but encryption is being forced down via the Exchange sync policies
2. I also know that the company might take a dim view of my attempt to root the device, but... they didn't explicitly tell me not to either
So i just finished the process of rooting my s2 tablet 810 5.1.1 and every time i reboot or turn the phone on and off i notice a message that says
"Kernel is not seandroid enforcing
set warranty bit: kernel"
Ive done some google searches and i would like to think its normal becuase i read in a thread that this is because of the knox trip.
however i also see threads dedicatied on how to resolve this "issue"
As some of you guys might already know if the version is 5.1.1, then you need a kernel to load during the process of root.
when i attempted to root the first time the kernel boot did not restart my tablet for me, so i manually restarted even though the option was set to auto-reset.
I now believe the process was incomplete because the tablet entered a boot loop after i ran the auto-root file. (Failed 1st attemp)
Second attempt i ran the kernel file and then the tablet rebooted successful, howver THIS is when the "Kernel is not seandroid enforcing set warranty bit: kernel"
is something wrong or is all good? gonna check if i have root after this post.
SIDE QUESTION
in the thread of the guy who posted about how to root he mentions how to put a custom recovery. Is that mandatory? or can i do this later when i want to install a custom ROM?
will post agian if anything important comes up after i check if ROOT
Okay so something interesting did come up. It seems i am rooted, however i keep getting a notification that an unauthorized action haas been taken and i must click on a restart to undo the changes that have been done.
its kind of annoying because it keeps popping up. I assumw this is the knox security.
there is an option for "sperate work and play" where i can install knox app in a safe and isolated space. what is this?
should i just ignore this poppup ? or is there a way to get rid of it?
someone to talk to would be nice right now .
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I understand what a custom recovery does, ive had it on my two previous phones and have tried TWRP and CW.
however i only installed them because i wanted to flash a custom rom on those two phones. With my s2 tablet im looking to just stay with root for now, that is why i am asking if the custom recovery is a must? because i dont see any use for it if i am just going to keep my tablet rooted and not flash any roms yet
also any idea on how to get rid of that pop up in notification saying i must click the restart to undo the changes that have been made
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Originally I said I froze and unistalled SecurityLogAgent, however I did not. So I did it now. I will report back if I go error free.
Thank you!
I am having this same issue. I have twrp recovery installed, I have disabled/unistalled everything with knox security symbol . I continue to get this error. I have wiped everything and started fresh and cannot get rid of this error. The second problem i am having, I cannot reinstall those apps with TB, I tried each of them and I even let it set overnight while I slept and it was still going when I woke up.....
1. How can I get rid of this error?
2. If I can't how can i get tb to reinstall knox or can I unroot without having these reinstalled?
this is everything I have froze, backed up, and unistalled
BBCAgent 2.0
com.samsung.android.bbc.fileprovider
com.samsung.knox.kss
com.sec.knox.containeragent2
com.sec.knox.packagegeverifier
com.sec.knox.sortcutsms
com.sec.knox.switcher
KLMS Agent 2.5.312
KNOX 2.3.0
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer2.4.0
Getting rid of all Knox apps is good when you are rooted but the anoying pop-up comes from SecurityLogAgent app and not from Knox apps, as soon as you freeze or uninstall it the message will stop.
Sent from my SM-T810 using Tapatalk
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
I cannot Install Xposed in a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
Make sure you're using a deodexed rom and not a Nougat and one more thing use Samsung xposed version support by wanam for example
ghoster76 said:
Make sure you're using a deodexed rom and not a Nougat and one more thing use Samsung xposed version support by wanam for example
Click to expand...
Click to collapse
Thank you for the info. I have no idea what that is. But I'll research it and figure it out.
samsung use this https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 by wanam
It worked!! I was about to go insane with this xposed framework installation. I can finally play youtube videos on the background without ads. The community on this site is amazing.
Thank you so much for your help.
If you ever come to Spain, I'll give you a tour to celebrate!?