Database Develop

[Q] Custom Device Status

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.

[Q] Device Encryption not working.

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

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.

Problems after rooting, Help!

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!

Unrooted phone but still apps says my mobile is rooted.. HELP!

Hi guys,
I am using my 1+5T for almost 2.5+ yrs now and since beginning i rooted the mobile for trying new custom ROM's, installing substratum themes, ad blocking etc etc.
Now many banking/payment related apps, maadhar, etc are showing as my phone is rooted. Magisk HIDE is not helping anymore.
So, i uninstalled magisk root and still my OEM is unlocked. all the previous apps shows similar message as my mobile is rooted.
How should i completely unroot my mobile without leaving any trace so that these apps doesn't show rooted messages again ?
Any Idea ?
NOTE: Previously i completely unrooted my mobile & still many apps shows rooted so got to root my mobile and used magisk HIDE .....

Haki! said:
Hi guys,
I am using my 1+5T for almost 2.5+ yrs now and since beginning i rooted the mobile for trying new custom ROM's, installing substratum themes, ad blocking etc etc.
Now many banking/payment related apps, maadhar, etc are showing as my phone is rooted. Magisk HIDE is not helping anymore.
So, i uninstalled magisk root and still my OEM is unlocked. all the previous apps shows similar message as my mobile is rooted.
How should i completely unroot my mobile without leaving any trace so that these apps doesn't show rooted messages again ?
Any Idea ?
NOTE: Previously i completely unrooted my mobile & still many apps shows rooted so got to root my mobile and used magisk HIDE .....
Click to expand...
Click to collapse
As long as your bootloader is unlocked, they will report your device as rooted. If Magisk Hide alone doesn't work, try the "Repackage Magisk Manager" option in Magisk Manager settings. It works for me.
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
As long as your bootloader is unlocked, they will report your device as rooted. If Magisk Hide alone doesn't work, try the "Repackage Magisk Manager" option in Magisk Manager settings. It works for me.
Sent from my #FlagshipKiller6T using Tapatalk
Click to expand...
Click to collapse
I found the problem i uninstalled magisk manager then all apps started working with boot lock loader Unlock.
Now i locked everything and went back to normal.

Haki! said:
I found the problem i uninstalled magisk manager then all apps started working with boot lock loader Unlock.
Now i locked everything and went back to normal.
Click to expand...
Click to collapse
Hi, I too have your own problems with an app. I can no longer hide the root. How did you do? I Magisk I had flashed via Recovery

Fix_ita said:
Hi, I too have your own problems with an app. I can no longer hide the root. How did you do? I Magisk I had flashed via Recovery
Click to expand...
Click to collapse
I unrooted my mobile but still magisk manager was installed so apps showed message "my phone is rooted". After that i uninstalled magisk manager and all apps started working fine.
Now i am unrooted but my bootloader is unlock.

Well, I still have that same problem. But only from Samsung Pass with an actual message box, which says that my device is rooted so can't use the app for security reasons.
I rooted my Galaxy S20 FE 5G SM-G781B with Magisk and afterwards uninstalled it with the Complete Uninstall method, but after automatic boot, that procedure only gave me some weird errors and I couldn't boot the phone.
It got stuck to this error filled download mode screen. There I saw an option to lock the bootloader back. Well, did that but then my phone got itself into a boot loop!
I managed to get to the download mode (in between the loops) and then it became even more errored and with all red alert stuff there!
Thought I bricked the whole damn device which I only bought like two weeks earlier rip.
Well then after some google fun time I downloaded original stock firmware to odin it. Well, nothing worked and always failed!
Then afterwards it became to my attention to try to flash the firmware that I originally flashed just before installing Magisk.
Heck yeaaah that actually worked lol and all bank stuff works and even software update and I now have all the newest updates etc and Magisk and Root Checker shows no root and then I removed Magisk for good and rebooted the phone to check any surprises.
No surprises and everything works, EXCEPT Paypal app and Samsung Pass!
Paypal just says after trying to log in "Please check your information and try again", but Samsung Pass actually says that "Your device has been rooted. Samsung Pass cannot be used on rooted devices for security reasons."
So what the heck!
I hate myself for rooting the new phone for nothing and now my ocd suffers for having that stupid whatever error stuff there, especially since I actullay USE Samsung Pass and Paypal!
EVERYTHING else works just fine, but not those two!
Grrr!
So all you wise people, can I actually do something about this or not??
Cheers!

@Hopeasilmu I would expect that the Samsung apps will now be complaining since you probably tripped the Knox fuse when you unlocked the bootloader and rooted the device. Once that's tripped you can't get it back...
If you need more info on Knox there's plenty available both here on XDA (check the Samsung forums) and on the web in general.

Haki! said:
I unrooted my mobile but still magisk manager was installed so apps showed message "my phone is rooted". After that i uninstalled magisk manager and all apps started working fine.
Now i am unrooted but my bootloader is unlock.
Click to expand...
Click to collapse
You can still lock the boot loader. There is a way. I did that on my Samsung M31 however I cannot recall the steps.