¡Ya disponible! Investigación de Telegram 2025 — los principales insights del año 
TCF | News
Ir al canal en Telegram
This Channel Is For Information, Notification, Warning, News For Other Channels And Group » @TranssionCore (Announcement) » @TranssionCore1 (Group) » @TranssionCore2 (Logs) » @TranssionCore3 (News) » @TranssionCore4 (Proof)
Mostrar másSin datos
Suscriptores
Sin datos24 horas
-47 días
-1030 días
Carga de datos en curso...
Canales Similares
Sin datos
¿Algún problema? Por favor, actualice la página o contacte a nuestro gerente de soporte.
Nube de Etiquetas
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
abril '26
abril '26
+7
en 0 canales
marzo '26
+9
en 11 canales
Get PRO
febrero '26
+8
en 0 canales
Get PRO
enero '26
+30
en 2 canales
Get PRO
diciembre '25
+54
en 14 canales
Get PRO
noviembre '250
en 0 canales
Get PRO
octubre '250
en 0 canales
Get PRO
septiembre '250
en 0 canales
Get PRO
agosto '250
en 1 canales
Get PRO
julio '250
en 2 canales
Get PRO
junio '250
en 18 canales
Get PRO
mayo '250
en 2 canales
Get PRO
abril '25
+2
en 5 canales
Get PRO
marzo '25
+22
en 7 canales
Get PRO
febrero '25
+32
en 9 canales
Get PRO
enero '25
+3
en 3 canales
Get PRO
diciembre '24
+28
en 4 canales
Get PRO
noviembre '240
en 0 canales
Get PRO
octubre '24
+48
en 0 canales
Get PRO
septiembre '24
+230
en 2 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 28 abril | 0 | |||
| 27 abril | 0 | |||
| 26 abril | 0 | |||
| 25 abril | 0 | |||
| 24 abril | 0 | |||
| 23 abril | 0 | |||
| 22 abril | 0 | |||
| 21 abril | +1 | |||
| 20 abril | 0 | |||
| 19 abril | 0 | |||
| 18 abril | 0 | |||
| 17 abril | 0 | |||
| 16 abril | 0 | |||
| 15 abril | +2 | |||
| 14 abril | 0 | |||
| 13 abril | +1 | |||
| 12 abril | +2 | |||
| 11 abril | 0 | |||
| 10 abril | 0 | |||
| 09 abril | 0 | |||
| 08 abril | 0 | |||
| 07 abril | 0 | |||
| 06 abril | +1 | |||
| 05 abril | 0 | |||
| 04 abril | 0 | |||
| 03 abril | 0 | |||
| 02 abril | 0 | |||
| 01 abril | 0 |
Publicaciones del Canal
| 2 | [Announcement]
Problems "su"
We have identified a change in the behavior of the su command within the Termux environment, causing the error "No su program found". Below is the content of the latest /system/bin/su script responsible for this issue:
#!/data/data/com.termux/files/usr/bin/bash
unset LD_LIBRARY_PATH LD_PRELOAD
# See https://github.com/termux-play-store/termux-apps/issues/10 about an
# interesting detail of KernelSU - it doesn't actually place a su file in
# /system/bin, but hook execve(2) call in kernel to redirect it to kernel
# impl when executing /system/bin/su.
# So we don't want termux-exec to interfere here.
# Note also that setting TERMUX_EXEC_OPTOUT=1 here means that we cannot
# use the dash shell, as that shell does not actually setenv(3) on export.
export TERMUX_EXEC_OPTOUT=1
for p in /debug_ramdisk/su /sbin/su /system/sbin/su /system/bin/su /system/xbin/su /su/bin/su /magisk/.core/bin/su
do
if [ -x $p ]; then
# The su tool may require programs in PATH:
PATH=/debug_ramdisk:/sbin:/sbin/su:/su/bin:/su/xbin:/system/bin:/system/xbin \
exec $p "$@"
fi
done
echo "No su program found on this device. Termux"
echo "does not supply tools for rooting, see e.g."
echo "http://www.androidcentral.com/root for"
echo "information about rooting Android."
exit 1
1. Information
As of now, we have not investigated or received official information from the Termux developers regarding the specific technical reason why the su command is no longer usable by default. This recent update has turned the su binary into a mere search script (wrapper), as shown above, which frequently fails to detect root on many Android systems.
2. Same Issue on "tsu"
Many believe that installing the tsu package is an instant fix. However, in reality, the same issue occurs with tsu. These automated scripts still fail to detect root and trigger the error message:
> *"No superuser binary detected. Are you rooted?"*
>
3. Solution:
Manual Configuration
To resolve this, users are required to understand the complexity of the su binary path on their specific devices. There is no longer a "one-click" automated solution that works for everyone.
• Identify the Path:
You must manually find the physical location of your actual su binary (e.g., /data/adb/ksu/bin/su for KernelSU, or /system/xbin/su for Magisk).
• Manual Execution:
Call the full path directly, or create a manual alias within your .bashrc file.
• Self-Configuration:
If you do not understand where your system's root binary is located, root access within Termux will remain locked.
Conclusion:
Do not rely on automated scripts. Successful root access now depends entirely on your ability to manually map your system's binary paths.
TranssionCore Federation (TCF) | 0 |
