Endi mavjud! Telegram Tadqiqoti 2025 — yilning asosiy insaytlari 
TCF | News
Kanalga Telegram’da o‘tish
This Channel Is For Information, Notification, Warning, News For Other Channels And Group » @TranssionCore (Announcement) » @TranssionCore1 (Group) » @TranssionCore2 (Logs) » @TranssionCore3 (News) » @TranssionCore4 (Proof)
Ko'proq ko'rsatishMa'lumot yo'q
Obunachilar
Ma'lumot yo'q24 soatlar
-47 kunlar
-1030 kunlar
Ma'lumot yuklanmoqda...
O'xshash kanallar
Ma'lumot yo'q
Muammo bormi? Iltimos, sahifani yangilang yoki bizning qo'llab-quvvatlash boshqaruvchimizga murojaat qiling>.
Taglar buluti
Kirish va chiqish esdaliklari
---
---
---
---
---
---
Obunachilarni jalb qilish
Aprel '26
Aprel '26
+7
0 kanalda
Mart '26
+9
11 kanalda
Get PRO
Fevral '26
+8
0 kanalda
Get PRO
Yanvar '26
+30
2 kanalda
Get PRO
Dekabr '25
+54
14 kanalda
Get PRO
Noyabr '250
0 kanalda
Get PRO
Oktabr '250
0 kanalda
Get PRO
Sentabr '250
0 kanalda
Get PRO
Avgust '250
1 kanalda
Get PRO
Iyul '250
2 kanalda
Get PRO
Iyun '250
18 kanalda
Get PRO
May '250
2 kanalda
Get PRO
Aprel '25
+2
5 kanalda
Get PRO
Mart '25
+22
7 kanalda
Get PRO
Fevral '25
+32
9 kanalda
Get PRO
Yanvar '25
+3
3 kanalda
Get PRO
Dekabr '24
+28
4 kanalda
Get PRO
Noyabr '240
0 kanalda
Get PRO
Oktabr '24
+48
0 kanalda
Get PRO
Sentabr '24
+230
2 kanalda
| Sana | Obunachilarni jalb qilish | Esdaliklar | Kanallar | |
| 28 Aprel | 0 | |||
| 27 Aprel | 0 | |||
| 26 Aprel | 0 | |||
| 25 Aprel | 0 | |||
| 24 Aprel | 0 | |||
| 23 Aprel | 0 | |||
| 22 Aprel | 0 | |||
| 21 Aprel | +1 | |||
| 20 Aprel | 0 | |||
| 19 Aprel | 0 | |||
| 18 Aprel | 0 | |||
| 17 Aprel | 0 | |||
| 16 Aprel | 0 | |||
| 15 Aprel | +2 | |||
| 14 Aprel | 0 | |||
| 13 Aprel | +1 | |||
| 12 Aprel | +2 | |||
| 11 Aprel | 0 | |||
| 10 Aprel | 0 | |||
| 09 Aprel | 0 | |||
| 08 Aprel | 0 | |||
| 07 Aprel | 0 | |||
| 06 Aprel | +1 | |||
| 05 Aprel | 0 | |||
| 04 Aprel | 0 | |||
| 03 Aprel | 0 | |||
| 02 Aprel | 0 | |||
| 01 Aprel | 0 |
Kanal postlari
| 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 |
