See my response further up in this thread. It has helped other people, maybe it can help you as well.
I don’t have Busybox (does anyone anymore, at least on purpose? I don’t think it’s used for rooting anything these days).
I spoke too soon with regarding the older APK, installing the older version of the app was only a temporary fix. I works every time, but eventually the app denies access again. I’ve added the app to the Magisk DenyList, but I doubt that will work. I think I’m just done with ST at this point. Samsung makes everything too hard, and if I’m going to work this hard then I might as well use Home Assistant instead.
1 Like
Rooted Razer Phone running Android 14 was working fine until today. Magisk Denylist entry working so far.
I’m in the same boat. Used to root, but haven’t had a rooted device in maybe 4-5 years. However it seems that busy box has persisted through a few device migrations. Removing busy box fixed the issue. It’s still dumb that Smart Things is even looking for a rooted device.
Thank you for posting this solution.
1 Like
I wonder why Samsung is copying Apple by selling expensive locked devices which they’d punish you for unlocking by forcefully denying that customer the services they also paid for!
I’ll always root my phone coz locking it should be my own concern as I own the device I bought. Never mind warranty as I also repair and fix my own things.
That’s why I’m now looking to get an ROG phone instead of locked bloated phones with stark warnings and disabled features. Surprisingly this bloatware was working a few days ago, on a rooted device but they must have been drinking too much Apple juice to lock such a thing. I do have my accounts all set up in that rooted phone and also do banking on it, what use is smart things when there’s other 3rd party apps that can do the same?!
I want to rival this locking madness with a new phone brand that gives the user choices to lock or unlock at will and to access any part of their device including the system folders and files and to root by simply setting this in settings and to remove bootloader hell in the process. To start, I’m busy reverse engineering all the BL and AP files, today I was working with init, about 3k lines of assembly code 
because power must get back to the people.
Stay rooted! Don’t buy this security bs
You have Toybox installed…
Delete it and try again.
1 Like
The same is true in your case: delete Toybox and try again. Why do you have it installed in the first place?
Why shouldn’t they have a “toolbox” to use on an Android based phone?
Maybe they want to use the commands.
Why should Smartthings be the gatekeeper to tell them what they should/shouldn’t have installed?
Riddle me this
Toybox.
The detection algorithm takes this into account and since there are ways to hide the fact that a phone is rooted, this might be necessary.
Anyway: if you don’t use Toybox or BusyBox, delete it.
I understand what you are saying, but… Samsung / SS shouldn’t be able to dictate what you have installed on your (your) phone.
They should explicitly state “This app ____ will cause this behavior if installed”.
It shouldn’t leave the customer guessing which app or setting is causing the issue.
Can you imagine all of a sudden not being able to view your security stuff because SS arbitrarily decides X app shouldn’t be installed on your phone (when you have a security issue at your home or business). It’s messed up!
You can’t change my mind on this!
I appreciate the effort you commented on.
This guy fuchs. Removing busy box fix it for me in about 3 seconds and I haven’t thought about that in 15 years
That was really helpful.
It took me some time to realize that the BusyBox app, which I had used on another phone, was restored from backup. The issue was resolved when I removed it.
Thank you!
Is there an alternative app if you use Smartthings just to access you’re soundbar?