Problems after rooting, Help! - Galaxy S5 Mini Q&A, Help & Troubleshooting

2 days ago i rooted my G800F with CF-auto-root through ODIN. (Used the latest CF-auto-root from here , with ODIN v3.10.6)
But after that my device is too laggy!
Much slower as it had 512 RAM. Root success was confirmed with Root Checker
SuperSU was also installed but sometimes i get a message that SU binary isn't installed.
I 've tried with "ROM toolbox" and "System App Remover" to unistall some system apps but i got the message "Failed to Unistall xxxxxxx app". But if i entered again "ROM toolbox" i found out that the xxxxxx app wasn't there. It has been unistalled!
Once Play Store didn't let me upgrade some apps, because it said that i must logged in to my account (which i was already logged in), and others problems like that!
What shall i do now?
Root again the device? Unroot the device and root again? Unistall Knox? (i've read somewhere that Knox is responsible for problems after rooting). Find another version for CF- auto-root? (the latest is for Build ID LMY47X.G800FXXU1BPB2 but mine is LMY47X.G800FXXU1BPC4 if it matters)
Please help!

Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...

lfom said:
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
Click to expand...
Click to collapse
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?

billphone said:
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
Click to expand...
Click to collapse
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.

lfom said:
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
Click to expand...
Click to collapse
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?

billphone said:
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
Click to expand...
Click to collapse
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.

lfom said:
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
Click to expand...
Click to collapse
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens

billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
SuperSU is the app, su is the superuser daemon. Good luck.

billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
So finally the problems are still here. The device is no longer laggy, but the root sometimes works sometimes doesn't.
I root again over the previous root, again the same. I unroot and again root, the same. I install a custom recovery and flash the SuperSU, the same results.
Initially working fine, giving rights to the applications but later sometime does not. With restart reverts briefly again.
What on earth has gone wrong? I have root many devices and all of them were working perfect!
I would like to avoid factory reset because i don't know how to restore my backup without problems.
Is there another solution?

Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?

lfom said:
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
Click to expand...
Click to collapse
Yes, i disable some apps with the word Knox in them. I don't know if is still a Knox app with a different name. Is there a list with Knox apps?
I didn't disable the Security Log neither its updates. Where can i find them?

So, finally i have a rooted device which randomly unroot itself!
And nothing can be done!

Related

Randomly Lost Root? - No Updates/OTAs applied

Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.

Trouble Rooting my Note 4

Hey everyone. I am not new at rooting phones but this appears to be the one phone that is giving me issues.
My note 4 is telus, was n910w
installed this rom:
http://forum.xda-developers.com/note-4-tmobile/development/rom-vision-x-n4-intl-t2943448
working beautifully thus far but I cant seem to root....
I have tripped KNOX 5 times so far trying to do it, each time it appears my phone is not rooted as titanium cannot verify SU, and aswell I have a root checker which tells me it is not rooted.
I have tried several versions of ODIN, and cf auto root n910t, AND V.
Do I maybe have to reinstall my rom? Or is there something I am missing because this is frustrating me....
Is there something I am doing wrong? Superuser IS on my phone, but its not doing anything but being there.... Please any kind of help would be appreciated as I am stumped.
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Framaroot
Sent from my Trident-A1 using XDA Free mobile app
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
This worked, I am a dummy lol
Thanks alot!
Glad I could help
Glad you got it worked out but note that you can only ever trip Knox once. Once it's tripped it's tripped, so don't worry about it.
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
I had lost root after flashing the PopRocks ROM. Couldn't figure it out and stumbled across this post. Now it works perfectly. Thanks! :good:

Losing root after 2 or 3 reboots

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.

Magisk - secure folder, software updates - all not working

I successfully installed magisk on my samsung s8 but now the secure folder, software updates and maybe other apps don't work as they recognise my phone being rooted. I thought the point behind magisk was to hide the phone from looking rooted?
how can i fix this issue?
thanks
You tripped KNOX by flashing custom binaries. You're boned.
is there a way to root the phone without tripping KNOX?
cpu2007 said:
is there a way to root the phone without tripping KNOX?
Click to expand...
Click to collapse
There might be, but I don't think there's any going back for you. As far as I know you can't revert a triggered KNOX...
I installed magisk because I thought knox won't be tripped but I was wrong.
Does anyone know how I can use secure folder, software updates and banking apps now that my app is rooted? they can all recognise my app is rooted and won't work
cpu2007 said:
I installed magisk because I thought knox won't be tripped but I was wrong.
Does anyone know how I can use secure folder, software updates and banking apps now that my app is rooted? they can all recognise my app is rooted and won't work
Click to expand...
Click to collapse
You can still hide Magisk from many apps with Magisk. You'll just have to activate Magisk Hide in the Manager settings. SafetyNet is added by default and any other app that detects root might be fooled if you add it to the Magisk Hide list.
I've said it before and I'm sure I'll say it again. The purpose of Magisk is NOT to hide root and pass SafetyNet (it's just a really nice feature); it's to make your system modifications systemless. You could use this to keep your devices ability to update through OTA, with a couple of extra steps. But, the main advantage for me (and it's the deal-breaker) is that I don't have to redo any of my system modifications after an update. These could be changing screen density, debloating system apps, systemising apps, changing prop values, etc. Before Magisk I could spend 30-45 minutes after an update just setting upp all the system tweaks the way I wanted it, only to realise a couples of days later I'd forgotten something. Now, with Magisk - flash the update, done!
Recommended reading if you're new to Magisk:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/magisk-details-dummies-to-developers-t3473486
And if you're having issues:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
I have activated Magisk Hide and selected the app (Lloyds banking app) then restarted the phone but the app can still recognize that the phone is modified.
I'll look at the other solution that are being proposed in one of the links you've sent and sew how it goes but if anyone has any advice on how to fix this, that will be great.
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Thanks
cpu2007 said:
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Click to expand...
Click to collapse
I don't do Samsung, but as I understand it: nope.
More info can probably be found in your device's forum here on XDA.
cpu2007 said:
I have activated Magisk Hide and selected the app (Lloyds banking app) then restarted the phone but the app can still recognize that the phone is modified.
I'll look at the other solution that are being proposed in one of the links you've sent and sew how it goes but if anyone has any advice on how to fix this, that will be great.
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Thanks
Click to expand...
Click to collapse
Realise this is a very late reply, but if still had no joy with Lloyd's banking app, it will store it's root detection so will still think your phone's rooted even after Magisk Hide. Need to wipe the app data or reinstall.

attempt of a generic root explanation (in progress)

Hallo,
managing some different devices and run them mostly with custom ROMs, rooting was again and again a topic in this endeavour. During this course I've came accross so many resources but it isn't 100% clear for me. This is an attempt to get any uncertainties resolved.
Any input is welcome.
There are many explaining what rooting means, gaining administrative rights on the file system of your phone (in linux, root or superuser is the username of the master admin). With root access, you can install and uninstall anything you want on the phone. But resources what rooting actually does on modern Android are widely scattered around but I haven't found place yet where it all is well explained in one decent post. I've gone through some articles but still don't fully understand what it does and how can I hide later on as it certain apps won't run if they detect if a phone is rooted. These are my resources:
Best way to hide Root and SuperSU from apps that otherwise block access on Lineage?
Question about LOS root, SuperSU and Magisk
Does magisk manager go well with lineage os
LOS Root or Magisk?
As I mainly looked in to rooting LineageOS many resources are referring to this ROM after rooting you have to manage binaries
XDA-Developers Root Directory
iSu
phh's SuperUser
Magisk on xda Magisk Root
SuperSU
Magisk Root
LOS root addon on xda LOS root addon
unsorted collection:
https://techviral.net/top-best-root-apps/#4nbspTrickster_Mod
https://forum.xda-developers.com/showthread.php?t=803682
https://techviral.net/best-tricks-for-rooted-android/#13_Top_10_Best_Root_Apps_2016_for_Android
https://techviral.net/secure-rooted-android-from-security-threats/
https://www.androidauthority.com/root-android-277350/
https://en.wikipedia.org/wiki/Rooting_(Android)
I just wanted to know. If this is true for a root. I mean, does this sound like a properly rooted device under these circumstances?
Taken from a chat log...
"Device is now rooted but PLEASE TAKE NOTE:
1.Do not uninstall SuperSU
2.Do not Factory Reset
3.Do not turn off developer options
4.Do not disable OEM Unlock (if you have this setting)
5.Do not enable Reactivation Lock (if you have this setting)
6.Do not install System Updates"
03:01
why not factory reset? Does this sound like a permanent root?
Confused
2ISAB said:
why not factory reset? Does this sound like a permanent root?
Confused
Click to expand...
Click to collapse
depending on the method and ROM, root related modification could be overridden when flashing. This is one of the reasons why I kicked off this thread. I want to outline it in more details (as soon as I have some spare hours)
PackElend said:
depending on the method and ROM, root related modification could be overridden when flashing. This is one of the reasons why I kicked off this thread. I want to outline it in more details (as soon as I have some spare hours)
Click to expand...
Click to collapse
Well it's a N7 stock rom for my M9 using the controversial Oneclickroot advertised on XDA.
So I just want to know if they root permanently using team viewer remote root. ?
2ISAB said:
So I just want to know if they root permanently using team viewer remote root. ?
Click to expand...
Click to collapse
can't tell you need to ask in the specific thread
2ISAB said:
I just wanted to know. If this is true for a root. I mean, does this sound like a properly rooted device under these circumstances?
Taken from a chat log...
"Device is now rooted but PLEASE TAKE NOTE:
1.Do not uninstall SuperSU
Click to expand...
Click to collapse
Uninstall it should not be a problem, the su binary already in /system (system way) and in boot image (systemless way). But if you remove SuperSU from that app you will LOSE root!
2ISAB said:
2.Do not Factory Reset
Click to expand...
Click to collapse
It's because some devices play not good with Factory Reset with root. Like my ASUS ZF2, everytime I try to factory reset + root, the device lost boot.
2ISAB said:
3.Do not turn off developer options
Click to expand...
Click to collapse
Read note 4 and 5 below.
2ISAB said:
4.Do not disable OEM Unlock (if you have this setting)
Click to expand...
Click to collapse
OEM Unlock will allow your phone to root. If you are rooted and you disable this option, your phone will brick (as it will enable the device to check system signatures). I had this mistake and my SS phone said on reboot "Custom binary blocked by FRP lock"
The fix would be full stock ROM flash.
2ISAB said:
5.Do not enable Reactivation Lock (if you have this setting)
Click to expand...
Click to collapse
Read note 4.
2ISAB said:
6.Do not install System Updates"
Click to expand...
Click to collapse
This is not true. Some device can still install OTA, but you must unroot. Else your phone might get hard bricked.
2ISAB said:
why not factory reset? Does this sound like a permanent root?
Click to expand...
Click to collapse
Yes, it's a permanent root. You can unroot if you want.

Categories

Resources