Toybox questions..

[Ace1222]

Hey hopefully I'm posting in the correct sub section if not can a mod please move this. First off just want to say thanks for the information I've gotten lurking the past few months. I'm basically completely new learning basic coding etc. Sorry for the rant my question is ive been experiencing some cyber attacks which are very confusing and a long story...I'll try to keep it short...

Currently I'm on an old Samsung a21(buying the a54 when it comes out soon) my wife has a Samsung a53. Both phones have toybox installed but this wasn't flashed by me. I flashed her phone with the stock firmware last week to attempt to rid the hacking on it. Is it even possible to flash toybox remotely? I wouldn't think so as you would need to have several things lined up plus it connected to a pc. Nearly every device in my house has been corrupted down to smart watches, Bluetooth low energy devices, and especially computers. All of my pcs registrys are completely infected. My wife swears this is not her and has no idea how to do any of this. I have my suspicions with certain "coincidences" happening which are to numerous to name. Sorry for posting this here but I don't know where else to ask. If anyone could even point me in the right direction I'm willing to put In work. I've called professionals that basically advised me to trash everything. That's all fine and dandy but I need to understand this issue to prevent it from happening again. The scope of this issue is way over my head but I've made decent progress in the last three months. I'll check out the toybox guides here to see if that offers some clues
Thanks In advance for any advice.

 

[ze7zez]

Since you didn't write specific facts, I'll just answer about toybox.
Toybox has been on Samsung phones for a long time and is a system application without the ability to manually do an update.

Toybox - Wikipedia

en.m.wikipedia.org

 

[Ace1222]

Hey thanks for the reply. I didn't understand it was native to android. Would it be normal to have toybox version 0.8.4? I'll attach a picture maybe you can give me a little direction to go in. My phones able to be controlled remotely,modded apps, some weird things going down. Thanks again I'm pulling my hair out looking commands up.

 

[ze7zez]

(...) Would it be normal to have toybox version 0.8.4? I'll attach a picture maybe you can give me a little direction to go in. My phones able to be controlled remotely,modded apps, some weird things going down. (...)

Could you please ask the questions precisely?
There is nothing special in the attached picture.

 

[Renate]

You want to just do:

$ setenforce 0

But it probably won't let you do that because your shell is not root.

 

[jwoegerbauer]

Ace1222​

Toybox since Android 6 is default component of Android OS: it replaced former Toolbox. Toybox is located either in /system or in /vendor partition.

Latest Toybox version is 0.8.9 ( conatains SU cmdlet ), can get downloaded from here:

Index of /toybox/bin

 

[jwoegerbauer]

You want to just do:

$ setenforce 0

But it probably won't let you do that because your shell is not root.

This only temporarliy disables SELinux what isn't needed when updating Toybox binary.

 

[Renate]

This only temporarliy disables SELinux what isn't needed when updating Toybox binary.

I was only correcting the syntax on the OP's post #3.

 

[ze7zez]

This only temporarliy disables SELinux what isn't needed when updating Toybox binary.

How is the user supposed to update the binary file when there is no root?

 

[jwoegerbauer]

I never here said rooting Android is not needed to update Toybox binary.

To clarify things:

1. Obtaining Root only allows you the ability to modify the system. E.g. mounting partitions accessible as RW.

2. SELinux is a completely different entity. To change a devices SELinux State is written into the devices Kernel. The kernel is a part of the ROM. It determines whether or not the device is permitted to change it's SELinux State.

 

[ze7zez]

I never here said rooing Android is not needed to update Toybox binary.

To clarify things:

1. Obtaining Root only allows you the ability to modify the system.

2. SELinux is a completely different entity. To change a devices SELinux State is written into the devices Kernel. The kernel is a part of the ROM. It determines whether or not the device is permitted to change it's SELinux State.

OK.

This only temporarliy disables SELinux what isn't needed when updating Toybox binary.

How is user Ace1222 supposed to update the binary file when he does not have root, as you can see in the screenshot?
The user did not write that he has/wants root.

 

[jwoegerbauer]

If you would carefully read my posts -> the solution already implicitely was given by me: make use of temporary root!

 

[ze7zez]

If you would carefully read my posts -> the solution already implicitely was given by me: make use of temporary root!

Since you did/know how to do it on the Samsung Galaxy A21 and on the Samsung Galaxy A53 without burning the KNOX flag, just write. The user did not ask for it, but since you are advising, advise completely.

 

[jwoegerbauer]

 

[alecxs]

@jwoegerbauer

1. OP is not asking for updating toybox
2. there is no such "temporary root" for android on real devices (such as smartphones and tablets)
3. the toybox linked cannot replace the android version of toybox
4. toolbox is holding android specific applets (such as getevent) and cannot replaced by toybox

 

[jwoegerbauer]

2 & 3: You're absolutely wrong. I kindly ask you to end spreading nonsense, TIA.

4: Yes, Toybox doesn't contain getevent cmdlet as Toolbox does, but that's abolutely irrelevant here.

 

[alecxs]

get yourself a smartphone and learn the basics. I will pay $ 100 if you show any proof of your magic temporary root.

 

[Ace1222]

Sorry for causing any tension and debates here guys. I am interested in root access if that's what's needed. I'm totally ignorant and can sort of follow along what was posted. For clarification I don't have access to the rom folder even for read privileges. My intent is to figure out how/why my devices are being manipulated. E.g. why are there custom apps,partitions,user profiles, different access levels to folders that aren't in the root directory? Obviously my devices have been tampered with but I'm to ignorant to provide the information to help you help me.

 

[Ace1222]

You want to just do:

$ setenforce 0

But it probably won't let you do that because your shell is not root.

Yeah I tried that days ago and like you expected permission denied...

 

[alecxs]

on bootloader locked devices system cannot modified. samsung devices are secure, a simple factory reset will remove all potential malware. just don't use the same samsung/google accounts again afterwards and do not restore backup of apps you don't know.