termux-desktop
termux-desktop copied to clipboard
adi1090x
Bricked My Entire System
It literally bricked my entire system I can't install apps anymore open anything and when I restart it it doesn't open the launcher like the Google pixel launcher then when I restart it again it bootloops until I delete my bricked system and reinstall it again (Android 7.1.2 ARMEBI 7v 32Bit 1.5gb ram)
If your cell phone is. Root, using termux with root is dangerous, it wasn't his fault
To anyone coming across this, don't use sudo/su. Termux is a user app, all data is in the user space, you're not accessing Android's system files. I was wondering why su commands were failing then I realized my mistake.
It literally bricked my entire system I can't install apps anymore open anything and when I restart it it doesn't open the launcher like the Google pixel launcher then when I restart it again it bootloops until I delete my bricked system and reinstall it again (Android 7.1.2 ARMEBI 7v 32Bit 1.5gb ram)
On Termux website it's clearly written to use Termux GUI on Device with Android Version A9 or Above... Broo it's your fault...You should read and research well before doing anything.
Android 7.1.2 ARMEBI 7v 32Bit 1.5gb ram
This is no longer a supported Android version for Termux, and this issue is unrelated to the installation of termux-desktop which does not include any su / tsu commands nor does it install any root packages.
Please note that actions that you commit as a root user are your responsibility as they imply knowledge over the affected system.
If you are still able to access your phone's recovery, you're still able to reinstall Android. This depends from phone to phone and unfortunately I am not familiar with particular steps to root and flash a Pixel phone. Maybe if you look up your phone model on XDA forums you may find a solution to do so and getting back to your device. Furthermore I highly recommend frequent backups if you're rooting your phone (and experimenting with superuser actions), from personal experience.
Having this said, suggesting to close this issue since it's irrelevant to this repo (there are no root packages or actions handled)
