Related
Hi. I just download and install recovery software call: Dr.Fone for android.
After prepared my phone to works with this software it was restart.
Software is relay good as I could recover my sms but! All apps related to banks stops working and give me msg: You phone is rooted.
Apps : check my root - says: - phone is not rooted... so, any idea what happen?
did you root it?
did you unlock the bootloader?
how can I check if bootloader is unlocking?
OK, I open Service menu and under Configuration it says: Rooting status: Bootloader unlock allowed: No
So is not rooted, but why banking apps stop working and says: apps not working on rooted devices - before I install dr.Fone banking apps works with no problem.
goralpm said:
how can I check if bootloader is unlocking?
OK, I open Service menu and under Configuration it says: Rooting status: Bootloader unlock allowed: No
So is not rooted, but why banking apps stop working and says: apps not working on rooted devices - before I install dr.Fone banking apps works with no problem.
Click to expand...
Click to collapse
Then it is not unlocked because it says you cannot do it..
I think the app you istalled is the problem, uninstall it
Unless you have been through a process to root the phone will not maigically root itself.
Maybe you should repair the software with pccompanion just to be sure and not install dr.Fone app (Of which I have never heard of before..)
gregbradley said:
Then it is not unlocked because it says you cannot do it..
I think the app you istalled is the problem, uninstall it
Click to expand...
Click to collapse
I uninstall it, but is no change, still banking apps says phone is rooted.
Is any options to show what was change? Like log file or similar?
Unless you have been through a process to root the phone will not maigically root itself.
Click to expand...
Click to collapse
So, my hone is definitely not rooted?
Maybe you should repair the software with pccompanion just to be sure and not install dr.Fone app (Of which I have never heard of before..)
Click to expand...
Click to collapse
How can I repair with pccompanion?
I
goralpm said:
How can I repair with pccompanion?
I
Click to expand...
Click to collapse
Download pccompanion and run it.
choose software update and then click on repair my phone
goralpm said:
So, my hone is definitely not rooted?
I
Click to expand...
Click to collapse
Try it yourself:
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Im guessing you were taken for a ride with this app. Ill try to help you out a bit. That app (dr.whatever) left files on your phone that are probably the problem. Use your file explorer to navigate to your internal storage, find the folder named Android. Inside you will see two folders named data and obb. Inside you will find all the data for your applications (each located within thier own folder). Look through these for a folder with the name or developers name (sometimes this can be tricky because there are no spaces in the file name, as well its usually initials or abbreviations.) Locate the folder and delete it, then reboot. Since your not rooted, you cant wipe your caches and data as we do so just try this out.
Sent from my SGH-I317M using xda premium
mstickland said:
Im guessing you were taken for a ride with this app. Ill try to help you out a bit. That app (dr.whatever) left files on your phone that are probably the problem. Use your file explorer to navigate to your internal storage, find the folder named Android. Inside you will see two folders named data and obb. Inside you will find all the data for your applications (each located within thier own folder). Look through these for a folder with the name or developers name (sometimes this can be tricky because there are no spaces in the file name, as well its usually initials or abbreviations.) Locate the folder and delete it, then reboot. Since your not rooted, you cant wipe your caches and data as we do so just try this out.
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
there is no obb folder, just data.
OK I made same research i I find this:
http://www.youtube.com/watch?v=n7b1QXxWk-g
When I connect phone with dr.fone it was this same way....
That means my Phone is rooted?
Root Checker Pro:
Result:
Root Access is not properly configured or was not granted.
Detailed:
Super User Application Status:
Superuser application - version 3.1.3 -is installed
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: Is -l/system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Can anybody explain me what this mean and is my phone rooted or not?
why don't you just try and root again with either doomlords easy root or bin4rys root kit.
That way you will definitely be rooted
gregbradley said:
why don't you just try and root again with either doomlords easy root or bin4rys root kit.
That way you will definitely be rooted
Click to expand...
Click to collapse
OK, but is any chance to unroot?
goralpm said:
OK, but is any chance to unroot?
Click to expand...
Click to collapse
what do you want? To be rooted or not to be rooted?
gregbradley said:
what do you want? To be rooted or not to be rooted?
Click to expand...
Click to collapse
To be not rooted. Cos I cant use some apps, witch I use on regular basis.
If I take factory reset - it will be after unrooted?
I don't think that you are rooted at all, that Dr Fone app sounds fishy and bogus to me (as others have stated as well).
Best bet is imho to repair with PC Companion as greg has also mentioned. You could also try removing any superuser app that apparently is somewhere on you device, it might be that your banking app checks for this.
Edit:
That Dr Fone app is not even in my Play Store - I would probably opt for a factory reset, rather than repair. Sounds like malware to me. If you want to backup something from your device, stay with the regular, known and trusted apps!
Sent from my LT30p using xda app-developers app
goralpm said:
To be not rooted. Cos I cant use some apps, witch I use on regular basis.
If I take factory reset - it will be after unrooted?
Click to expand...
Click to collapse
Which apps can not be used on a rooted phone? I never came across anything I can't use on my rooted phone, as opposed to an unrooted one. Just the opposite is true. There are many apps and functions that do work on a rooted phone, which I would be missing a lot if I was not rooted.
Dr.Fone seems to have manipulated with your system. My suggestion is first using the Doomlord easy rooting kit. It works like a charm, and also allows unrooting later in case you do not need to be rooted. Then uninstall that Dr. Fone thing (and everything else you don't need).
Like some of the others I do have suspicions regarding Dr. Fone software. There are so many useful tools and apps from reputable sources you can use on a rooted phone, it is almost overwhelming. What made you grab such a dubious app?
Now it is already on the second page for a relatively simple issue which basically comes down to one point: Get rid of that Dr.Fone. Action required.
No offence intended.
Flash a stock ftf you definitely not be rooted anymore.
There are several apps that don't work on rooted phones, sky go being one of them.
It is generally done by apps that have copy right laws to enforce or subscription issues.
Sent from my C6903 using Tapatalk now Free
OK, I finally rooted my phone properly. Now I can use TitaniumBackup for full bacup - and restore phone to factory setting...
I used this method: http://forum.xda-developers.com/showthread.php?p=46373469#post46373469
goralpm said:
OK, I finally rooted my phone properly. Now I can use TitaniumBackup for full bacup - and restore phone to factory setting...
I used this method: http://forum.xda-developers.com/showthread.php?p=46373469#post46373469
Click to expand...
Click to collapse
I really don't understand you, in your last post you wanted NOT to be rooted...
Yea, confusing.
Hi, I recently rooted my Z3c using KingRoot. I ten installed custom Rom: SLiM ROM 4.9. Works great, but now I found out Kingroot is very untrustworthy. How do I remove/replace kingroot without loosing root?
I rooted as per these instructions:
whattechsays.com/root-xperia-z2-z3-lollipop
So I have SuperSU installed, but KingRoot does not appear in apps list - so no option to uninstall. I can see kingroot folder in internal memory. Is deleting this sufficient to remove kingroot and any potential back-door?
I am new to rooting, so please explain simply if you can.
Many thanks.
Better remove Kingroot, and unroot all at once. You have Slimrom installed so I'm assuming your bootloader is unlocked so simply flash SuperSu Zip via recovery to get back root.
Kingroot is unreliable and shady when it comes to rooting devices in fact its not even endorsed here in Xda
Revontheus said:
Better remove Kingroot, and unroot all at once. You have Slimrom installed so I'm assuming your bootloader is unlocked so simply flash SuperSu Zip via recovery to get back root.
Kingroot is unreliable and shady when it comes to rooting devices in fact its not even endorsed here in Xda
Click to expand...
Click to collapse
I already have SuperSU installed already. And when I run rootcheck it says SuperSU has root. I have ' uninstalled' Kingroot, however kingroot folder/files remain on internal memory and I assume it could still be active and hiding it's process?
Sent from my D5833 using Tapatalk
Came across this thread from Google, but since it doesn't look like you really got an answer, here goes.
When you flashed Slim ROM, you would have replaced the system partition where Kingroot was installed, meaning it is no longer there at all.
The files left on the internal memory would have been written by Kingroot before and can just be deleted.
Frenik said:
Came across this thread from Google, but since it doesn't look like you really got an answer, here goes.
When you flashed Slim ROM, you would have replaced the system partition where Kingroot was installed, meaning it is no longer there at all.
The files left on the internal memory would have been written by Kingroot before and can just be deleted.
Click to expand...
Click to collapse
Oh dear, another Kingroot user stuck, how many warnings about Kingroot need to be posted on the threads before people listen.
Personally, knowing about what Kingroot does and the information it sends to China, I would wipe my phone and start from scratch.
There is a good guide written by bilboa1, which is very easy to follow.
Frenik is right, if you flash a rom, then the system should get wiped also. Just make sure you wipe data as well as dalvik/cache then you might end up with a Slim rom with SuperSU.
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
I used the version 2.4 and worked like a charm
Although as above... even though i have stepped on the same rake as you... don't use KingsRoot... there probably is a fake copy of my phone somewhere in china thanks to that...
"use SuperSu Me" app
Sent from my D5833 using XDA-Developers mobile app
Hi fellas. I write ehre in order to not open a new thread. I recently bought one of this little beasts. I'm running 23.4.A.1.264 (stock in phone), Android 5.1.1. I've succesfully rooted it with king root 4.9.5. I've tried to change it to Supersu without success. I've tried supersu me, the script to remove kingroot to supersu from ver 1.8 to 2.4 and always lose root permissions. Could someone tell me what the f*** I am doing wrong?
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
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.
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!