Database Develop

[Q] KINGO Root for AT&T Note 3 - Part 2

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.

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!

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.

Samsung Pay and Magisk

Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.

Same. Then this droidx program protecting pay app
Sent from my SM-N910V using XDA-Developers Legacy app

Try the universal safteynet net module

Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.

grymkmb said:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
Click to expand...
Click to collapse
I'm on an LG

I've got the same issue with galaxy tab 3
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.

Same problem here; Magisk works but Samsung pay won't work

Even tried freezing magisk. Though still no go must be detecting something.

hkbladelawhk said:
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Click to expand...
Click to collapse
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.
If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)
sevenday4 said:
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Click to expand...
Click to collapse
Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.

There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Booo!

someone please made an apps that can hide or fake the Knox status.

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
This is possible by disabling safetynet check at boot level before compiling the kernel

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.

gghose said:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
Click to expand...
Click to collapse
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.

Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.

Magisk hide 14
Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in [email protected]. Thank you so much. Bye.

Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.

Spot on fella, just got it working on OP5 with lineage ROM.

dcbii said:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Click to expand...
Click to collapse
Root explorer won't let me remove it from xbin. How exactly did you do it?
Sent from my iPad using Tapatalk

[warning] Do not disable Samsung Payment Services

So I was disabling (not uninstalled) a few apps I didn't use on my rooted S9 with Alexis ROM v1.7 (which was working extremely well).
I do not have Samsung account, and do not use S-Pay (or any payment apps). So I disabled Samsung payment Services" and phone immediately locked, and said "Phone Locked" on lock screen and "payment app was removed without authorization." I could not type in password, no options on lock screen. Tried to dirty re-install of Alexis Rom 1.7, no luck. Had to clean install rom. :/

That's why you should disable instead of removing apps.

what do you do? can you reflash stock rom with odin? or it became a brick?

AlexInvar said:
That's why you should disable instead of removing apps.
Click to expand...
Click to collapse
golden7 said they disabled it, not uninstalled it.

moocou said:
golden7 said they disabled it, not uninstalled it.
Click to expand...
Click to collapse
Should be possible to re-enable via ADB then right?

AlexInvar said:
Should be possible to re-enable via ADB then right?
Click to expand...
Click to collapse
No idea!
They said they fixed it by clean installing the rom.

Had the same problem. Fixed it by moving all Apps again to their place. Need to find out which of the Apps I'm not allowed to remove.
Samsung is really a pain in the ass!

AlexInvar said:
Should be possible to re-enable via ADB then right?
Click to expand...
Click to collapse
Yeah, and boy do I wish I'd thought of that. I disabled Payment Services on a Galaxy A70 via Titanium Backup -- poof, instant total lockout. Instead of thinking smart (at least trying adb) I reinstalled the firmware, re-twrp'd, re-rooted, and then the whole setup and apps installs again.