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.
Related
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
war1957 said:
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
Click to expand...
Click to collapse
Yeah, it's odd. Doesn't work for me either. Even after multiple reboots. I'd love for someone to chime in for more details. I know this has been talked about somewhere, but the only answer I remember was selecting fake official status in Wanam and reboot a few times after that. After many reboots, it's still CUSTOM, but Knox and everything is 0x0. Thanks.
war1957 said:
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
Click to expand...
Click to collapse
That's really weird, because this worked fine for me. I didn't do anything differently though, are you sure you have Wanam enabled in the Xposed Framework? After you download a module you usually have to enable it. I would try unchecking and checking, rebooting in-between.
It's true. You have to enable that module within the Xposed App. Try a total shut down and not just a reboot as well.
Pull your battery. After that, the icon will go away. You also need to go look at your About Phone and see system status. Make sure it shows Official (It should). Good Luck and let us know....
When I removed the "Custom" icon from startup screen, it took more than one reboot cycle to go away.
The first reboot after applying the setting, there was still the "Custom" and unlocked lock. I thought nothing of it, since I didn't really care... But at some point after that, with no further action in Wanam, the "Custom" stopped showing on reboot.
I rooted again with the same method and custom miraculously vanished.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
LuckyColdJohnson said:
It's true. You have to enable that module within the Xposed App. Try a total shut down and not just a reboot as well.
Pull your battery. After that, the icon will go away. You also need to go look at your About Phone and see system status. Make sure it shows Official (It should). Good Luck and let us know....
Click to expand...
Click to collapse
Tahnks a bunch
After the *hard reset* it decided to work.
Happy customer now !! :laugh:
war1957 said:
Tahnks a bunch
After the *hard reset* it decided to work.
Happy customer now !! :laugh:
Click to expand...
Click to collapse
Glad to hear that, and thanks for hitting the thanks button. I'm glad we could help. Now, I'm going to give you your first thanks for replying back. Thanks again.
Hi. I have a MJ5 Note 3 rooted via Kingo, and it is completely stock other than that. The KNOX counters are still 0x0 and the Binary is still Samsung Official. However the system status shows Custom and I get the Custom padlock icon during boot. I have seen some references to Triangle Away being able to fix this on the Verizon variant. Has anyone tried Triangle Away on our N900A to remove the custom status? I'm a little hesitant to try it, because I don't want to chance it making one of the settings worse instead of better. I would like to hear if anyone has tried it on this phone and what the result was.
Thanks
Haven't used that. But Wanam exposed will remove the custom logo
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I think it'll work, but why not just use Wanam?
It'll let you do a bunch of other things you want to do too (I don't know what you want to do, but I still feel pretty confident in saying that. The list of tweaks it enables is impressive), so you're going to end up installing it anyway.
DrAzzy said:
I think it'll work, but why not just use Wanam?
It'll let you do a bunch of other things you want to do too (I don't know what you want to do, but I still feel pretty confident in saying that. The list of tweaks it enables is impressive), so you're going to end up installing it anyway.
Click to expand...
Click to collapse
To be honest, it is because I am familiar with Triangle Away and it's a simple app install. As for Wanam, I don't know anything about it or how to install it. It sounds like you first need to have the Xposed framework installed which I don't, and have never done either. I see a lot of people referencing Wanam and how useful it is, but I haven't run across a thread here in the AT&T Note 3 group that, explains where to get it and how to install it on the N900A.
Does it work with all firmware versions, is it easily reversible and the same goes for the Xposed framework?
It's an app on the play store. Just follow the instructions when u download it and it will install the framework. You need to be rooted first.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Xposed framework comes from here: http://forum.xda-developers.com/showthread.php?t=1574401 (I wasn't able to find it in the Play store)
It's one of those things where the app you download installs/uninstalls/manages the framework- it can be reversed by uninstalling through app, and then uninstalling the app.
It is compatible with almost any rooted android 4.0 or higher device.
Wanam comes from the app store, and supports touchwiz roms running android 4.2 or higher.
Those will both work with any version of the note 3 firmware.
I've never used triangle away; I don't understand the motivation for hiding the padlock. I got rid of it with Wanam, but that's certainly not what I got Wanam for.
I just downloaded Wanam and one of the options was to install the framework
Sent from my SAMSUNG-SM-N900A using xda app-developers app
DrAzzy said:
Xposed framework comes from here: http://forum.xda-developers.com/showthread.php?t=1574401 (I wasn't able to find it in the Play store)
It's one of those things where the app you download installs/uninstalls/manages the framework- it can be reversed by uninstalling through app, and then uninstalling the app.
It is compatible with almost any rooted android 4.0 or higher device.
Wanam comes from the app store, and supports touchwiz roms running android 4.2 or higher.
Those will both work with any version of the note 3 firmware.
I've never used triangle away; I don't understand the motivation for hiding the padlock. I got rid of it with Wanam, but that's certainly not what I got Wanam for.
Click to expand...
Click to collapse
Actually what I am trying to do is change the custom system status back to Normal. That is what Triangle Away is capible of doing on some devices that are not running a custom recovery, custom Rom or custom kernel. If all Wanam does is hide the Custom padlock at boot, but the Device status still shows as Custom in the settings, and system still shows Custom in Download mode, then I agree, its not a good use of the tool.
wherestheanykey said:
Actually what I am trying to do is change the custom system status back to Normal. That is what Triangle Away is capible of doing on some devices that are not running a custom recovery, custom Rom or custom kernel. If all Wanam does is hide the Custom padlock at boot, but the Device status still shows as Custom in the settings, and system still shows Custom in Download mode, then I agree, its not a good use of the tool.
Click to expand...
Click to collapse
Just checked, Wanam makes it look normal in device status and download mode, it doesn't just remove the padlock.
I still don't understand why we care if it shows custom in device status and download mode. Does this cause problems with some other software?
DrAzzy said:
Just checked, Wanam makes it look normal in device status and download mode, it doesn't just remove the padlock.
I still don't understand why we care if it shows custom in device status and download mode. Does this cause problems with some other software?
Click to expand...
Click to collapse
Thank you for checking. Did you have to download a separate module for doing this, and if so, which one?
My phone is used for work at a large corporation, and they are funny about unauthorized modifications or "hacking".
wherestheanykey said:
Thank you for checking. Did you have to download a separate module for doing this, and if so, which one?
My phone is used for work at a large corporation, and they are funny about unauthorized modifications or "hacking".
Click to expand...
Click to collapse
Only module you need is Wanam (and the xposed framework, of course)
Ah, I see - I'm not sure how well this will work for hiding your root access from your IT department, since anyone who is even vaguely familiar with android hacking need only look at your app list to determine that you're rooted - otherwise why would you have SuperSU, TiBu, and all the rest of those lovely root-required apps installed.
wherestheanykey said:
Hi. I have a MJ5 Note 3 rooted via Kingo, and it is completely stock other than that. The KNOX counters are still 0x0 and the Binary is still Samsung Official. However the system status shows Custom and I get the Custom padlock icon during boot. I have seen some references to Triangle Away being able to fix this on the Verizon variant. Has anyone tried Triangle Away on our N900A to remove the custom status? I'm a little hesitant to try it, because I don't want to chance it making one of the settings worse instead of better. I would like to hear if anyone has tried it on this phone and what the result was.
Thanks
Click to expand...
Click to collapse
Did you root while you had MJ5 and it didn't trip the counters? I'm suspicious of this Kingo app because I've never dealt with it before. My phone luckily has an older version so I was able to use the Root DeLaVega without issue, but my wife's Note 3 has MJ5 and I want to root it.
Also, Wanam is awesome. I used it to get rid of the Custom mark as well as many other things I love about my phone.
Elemino said:
Did you root while you had MJ5 and it didn't trip the counters? I'm suspicious of this Kingo app because I've never dealt with it before. My phone luckily has an older version so I was able to use the Root DeLaVega without issue, but my wife's Note 3 has MJ5 and I want to root it.
Also, Wanam is awesome. I used it to get rid of the Custom mark as well as many other things I love about my phone.
Click to expand...
Click to collapse
Yes I rooted while on MJ5 with Kingo and it didn't trip the KNOX counters or change the Binary status. All it did was change the system status to Custom and invoke the pad lock during boot. I installed Xposed Framework and Wanam this weekend and it repaired them both.
Thanks again to everyone who helped me with this process.
Elemino said:
Did you root while you had MJ5 and it didn't trip the counters? I'm suspicious of this Kingo app because I've never dealt with it before. My phone luckily has an older version so I was able to use the Root DeLaVega without issue, but my wife's Note 3 has MJ5 and I want to root it.
Also, Wanam is awesome. I used it to get rid of the Custom mark as well as many other things I love about my phone.
Click to expand...
Click to collapse
Kingo doesn't trip the counters.
There's also this method of rooting, which uses the trick used by RDLV - it's a bit of a big deal, though, since it's meant to be a way to recover from a bricked/mangled device:
http://forum.xda-developers.com/showthread.php?t=2559715
DrAzzy said:
Kingo doesn't trip the counters.
There's also this method of rooting, which uses the trick used by RDLV - it's a bit of a big deal, though, since it's meant to be a way to recover from a bricked/mangled device:
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
I watched a few YouTube videos while researching it, and I found several saying it tripped their KNOX flags, that's why I was worried. I successfully used it to root my wife's Note 3 last night without issue. So I had no problems. She too is on MJ5.
Sent from my Galaxy Note 3 using Tapatalk
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
Pretty sure you can't encrypt once you root. Or maybe it's once you put a custom recovery. I've never been able to use encryption after rooting my phones.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Drew333 said:
I rooted my device with towelroot, and installed the Xposed framework, and now I can't encrypt my device. When I attempt to, it shows the Android dude with a gear for a couple of seconds, then it dissapears, screen goes black, and after about a minute, the device restarts and boots normally. Has anyone else encountered this?
Click to expand...
Click to collapse
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Hey be careful if your looking to install Safe Strap. Word for word what hashcode said
"THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW."
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
STraver said:
I ran into this myself and couldn't figure it out. I had flashed, rooted, then tried to encrypt and had the same result you did. Finally I tried flashing, encrypting THEN rooting and it worked. Hope this helps.
Click to expand...
Click to collapse
I'm experiencing the same issue and changing the flash/encrypt/root sequence doesn't seem to change the results (encryption will not work, phone reboots). I'm attempting to root using CF's auto-root tools.
Wondering if there may be another root technique that wouldn't trip up the encryption process?
Disclaimers...
1. I know that encryption on a rooted device doesn't make much sense, but encryption is being forced down via the Exchange sync policies
2. I also know that the company might take a dim view of my attempt to root the device, but... they didn't explicitly tell me not to either
So i just finished the process of rooting my s2 tablet 810 5.1.1 and every time i reboot or turn the phone on and off i notice a message that says
"Kernel is not seandroid enforcing
set warranty bit: kernel"
Ive done some google searches and i would like to think its normal becuase i read in a thread that this is because of the knox trip.
however i also see threads dedicatied on how to resolve this "issue"
As some of you guys might already know if the version is 5.1.1, then you need a kernel to load during the process of root.
when i attempted to root the first time the kernel boot did not restart my tablet for me, so i manually restarted even though the option was set to auto-reset.
I now believe the process was incomplete because the tablet entered a boot loop after i ran the auto-root file. (Failed 1st attemp)
Second attempt i ran the kernel file and then the tablet rebooted successful, howver THIS is when the "Kernel is not seandroid enforcing set warranty bit: kernel"
is something wrong or is all good? gonna check if i have root after this post.
SIDE QUESTION
in the thread of the guy who posted about how to root he mentions how to put a custom recovery. Is that mandatory? or can i do this later when i want to install a custom ROM?
will post agian if anything important comes up after i check if ROOT
Okay so something interesting did come up. It seems i am rooted, however i keep getting a notification that an unauthorized action haas been taken and i must click on a restart to undo the changes that have been done.
its kind of annoying because it keeps popping up. I assumw this is the knox security.
there is an option for "sperate work and play" where i can install knox app in a safe and isolated space. what is this?
should i just ignore this poppup ? or is there a way to get rid of it?
someone to talk to would be nice right now .
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
I understand what a custom recovery does, ive had it on my two previous phones and have tried TWRP and CW.
however i only installed them because i wanted to flash a custom rom on those two phones. With my s2 tablet im looking to just stay with root for now, that is why i am asking if the custom recovery is a must? because i dont see any use for it if i am just going to keep my tablet rooted and not flash any roms yet
also any idea on how to get rid of that pop up in notification saying i must click the restart to undo the changes that have been made
danyvw said:
This is because your kernel was modified to be permissive in order to root your tablet.
Installing a custom recovery is a must and one of the main reasons of a rooted device, it will give you the possibility of making/restoring backups, installing apps and ROMs between other stuff.
The anoying pop-up can be disabled by freezing/uninstalling SecurityLogAgent
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Originally I said I froze and unistalled SecurityLogAgent, however I did not. So I did it now. I will report back if I go error free.
Thank you!
I am having this same issue. I have twrp recovery installed, I have disabled/unistalled everything with knox security symbol . I continue to get this error. I have wiped everything and started fresh and cannot get rid of this error. The second problem i am having, I cannot reinstall those apps with TB, I tried each of them and I even let it set overnight while I slept and it was still going when I woke up.....
1. How can I get rid of this error?
2. If I can't how can i get tb to reinstall knox or can I unroot without having these reinstalled?
this is everything I have froze, backed up, and unistalled
BBCAgent 2.0
com.samsung.android.bbc.fileprovider
com.samsung.knox.kss
com.sec.knox.containeragent2
com.sec.knox.packagegeverifier
com.sec.knox.sortcutsms
com.sec.knox.switcher
KLMS Agent 2.5.312
KNOX 2.3.0
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer2.4.0
Getting rid of all Knox apps is good when you are rooted but the anoying pop-up comes from SecurityLogAgent app and not from Knox apps, as soon as you freeze or uninstall it the message will stop.
Sent from my SM-T810 using Tapatalk
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.