Hi Guys, I know a lot of people here on xda cannot go on their daily lives without root on their phone, but there are these pain in the bottom applications that refuse to run when root is detected. my only means of hiding root back then was using an xposed module, may I know if someone else have an idea on how to hide root from apps? thanks in advance!~
SuperSU Pro has the option that works for some apps. Not sure if it is in the standard version.
Best solution is to boycott HBO.
root cloak still works with 5.1.1. you can find it here in the forums. get the latest alpha version and it should work.
Hey all my version is the G920AUCU3BOJ7...I've tried PingPong root and it says my device can't be rooted yet. Is there anything that can help me root my device. My recent tab is stuck and it causes my phone to constantly switch between apps. I went through all the proper channels AT&T and Samsung and they won't help me. I also factory reset my device uninstalled all apps ever put on it and nothing works. I read you can disable the recent tab, but to do that I need root acess to the device. Any help would me much apprechiated.
Thanks,
Ryan
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
Hi All,
I'm trying to set up my work MDM, which uses centrify. I get an error that the device does not meet requirements, and I'm sure it's related to root. Anyone have any experience with centrify and how to properly hide it root from it? I clicked on centrify in the magisk hide, but it still detects root. I think Centrify uses some component of Samsung Knox as well. Any help would be appreciated. Thanks!
Tips for hiding root:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
If it uses Knox you're out of luck. Nothing Magisk can do there...
Hello somebody,
i am along time on xda, since samsung s2 and i am along time a best friend of root for the device.
The best opinions for me, supersu and twrp. I have root, and every time i can save a stable backup of my system with twrp. I running a very stable s8 with system-root via chainsfire supersu (chainsfire make a good work a long time). My s8 running android 7.0 and i didn't missing anything. I am big fan from samsung, so i buy a Samsung s10 (SM-G973F).
I have order the new phone from the beginning and it looks like a good phone (i am only missing the notification led from the older samsungs, but it is okay),
I Daley read the news about root and last week i also root my new phone with magisk (i would love to running twrp also, but for the s10 i know it is not stable at this time).
Now, my problems. I know with the new method of magisk, there are some problems like wlan and Bluetooth Connection. I never had this problems, because i make a full backup with samsung smart-switch and restore this with running firmware with magisk. I never run the patched firmware without root options, so i think, when i start the phone with the wrong combo, i can also have the problems.
I read, there is the libsecure_storage companion module for magisk, i have install it, but i dont understand the instruction..."after installing this modul, you may wish to edit /system/etc/......." When i really change anything on system, didn't broke me the safetynet?
Next problem, i am running on s8 airaudio with system-audio. On s10 there are only the options with microphone, so install the "air-audio" module frome magisk, but when i try to connect to my audio system, it shows me only an error, anybody have some solution?
Last of my problem, i am loving xposed and i know on magisk there are only edxposed, anybody have a good instruction how i can install edxposed on the s10?
Theres a lot of problems but i think it is not impossible to fix this. Sorry for my bad English, i am from germany.