{"id":134174,"date":"2023-07-19T08:00:00","date_gmt":"2023-07-19T08:00:00","guid":{"rendered":"https:\/\/fedoramagazine.org\/?p=38333"},"modified":"2023-07-19T08:00:00","modified_gmt":"2023-07-19T08:00:00","slug":"how-to-install-and-update-fedora-linux-on-android-using-termux","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2023\/07\/19\/how-to-install-and-update-fedora-linux-on-android-using-termux\/","title":{"rendered":"How to Install and Update Fedora Linux on Android using Termux"},"content":{"rendered":"

If you’re interested in running Linux on your Android device, you’re in luck! It’s possible to install Fedora Linux on Android using Termux. Termux is a terminal emulator for Android that allows you to run Linux commands and utilities on your phone or tablet. It does not replace Android. In this article, we’ll walk you through the process of installing Fedora Linux on Android using Termux and show you how to keep it up to date with the latest versions.<\/p>\n

<\/span> <\/p>\n

Step by step process <\/h2>\n

Step 1: Install Termux<\/strong><\/em><\/p>\n

To get started, you need to install Termux<\/a> from the Google Play Store. Once you have Termux installed, open it up and type the following command to update the package list:<\/p>\n

pkg update<\/pre>\n
Note: Termux requires Android >= 7 to run. Support for Android 5 and 6 was dropped at v0.83 on 2020-01-01, but you can find old builds on archive.org ( https:\/\/archive.org\/details\/termux-repositories-legacy\/<\/a> ) if needed.<\/p>\n
Step 2: Install Proot-Distro<\/strong><\/em><\/p>\n
Next, you’ll need to install Proot-Distro<\/a>. Proot-Distro is a tool that allows you to install and run Linux distributions in a chroot environment. To install Proot-Distro, run the following command:<\/p>\n
pkg install proot-distro<\/pre>\n
Step 3: Install Fedora<\/p>\n
With Proot-Distro installed, you can now use it to install Fedora. To install Fedora, run the following command:<\/p>\n
proot-distro install fedora<\/pre>\n
This will download and install the latest version of Fedora.<\/p>\n
Step 4: Configure dnf<\/strong><\/em><\/p>\n
Now that you have Fedora installed, you’ll need to configure dnf<\/em>, Fedora’s package manager. By default, dnf<\/em> may try to install SELinux packages, which won’t work properly in a chroot environment. To prevent this, exclude SELinux packages installation by editing the dnf<\/em> configuration file. Run the following command to open the dnf<\/em> configuration file for editing :<\/p>\n
cd ..\/usr\/var\/lib\/proot-distro\/installed-rootfs\/fedora\/etc\/dnf\nvi dnf.conf<\/pre>\n
You may substitute the nano <\/em> editor for vi<\/em>, if it is more to your liking. Once you’re in the file, find the line that says excludepkgs=<\/em> and add *selinux*<\/em> to the end of the line, like so:<\/p>\n
excludepkgs=*selinux*<\/pre>\n
It may be necessary to add the excludepkgs <\/em>line. Save these changes and exit the editor.<\/p>\n
Step 5: Install a Desktop Environment (Optional)<\/strong><\/em><\/p>\n
Fedora comes with a number of desktop environments to choose from. If you’d like to install a desktop environment, you can do so with the following commands:<\/p>\n
proot-distro login fedora\ndnf groupinstall \"Fedora Workstation\" --skip-broken<\/pre>\n
This will switch from termux into the chroot Fedora installation and install the GNOME desktop environment, along with a number of other packages. If you prefer a different desktop environment, you can replace Fedora Workstation<\/em> with the name of the group for your preferred environment.<\/p>\n
Step 6: Install VNC Server (Optional)<\/strong><\/em><\/p>\n
If you plan on using your Fedora installation with a graphical interface, you’ll need to install a VNC server. This will allow you to connect to the Fedora desktop from another computer or device. To install the TigerVNC server, run the following command:<\/p>\n
dnf install tigervnc-server.aarch64 -y<\/pre>\n
This will install the VNC server, along with any necessary dependencies.<\/p>\n
Step 7: Upgrading Fedora<\/strong><\/em><\/p>\n
Now that you have Fedora installed, you’ll want to keep it up to date with the latest versions. To upgrade Fedora, run the following commands:<\/p>\n
sudo dnf upgrade --refresh\nsudo dnf install dnf-plugin-system-upgrade\nsudo dnf system-upgrade download \u2013releasever=37\nexport DNF_SYSTEM_UPGRADE_NO_REBOOT=1\nsudo -E dnf system-upgrade reboot\nsudo -E dnf system-upgrade upgrade\nsudo dnf upgrade --refresh<\/pre>\n
First command sudo dnf upgrade –refresh <\/em> refreshes the package cache and updates any installed packages.<\/p>\n
The second command sudo dnf install dnf-plugin-system-upgrade<\/em> installs the dnf-plugin-system-upgrade<\/em> package, needed for the upgrade process.<\/p>\n
The third command sudo dnf system-upgrade download –releasever=37<\/em> downloads the necessary packages for the upgrade to version 37 of Fedora. Replace 37<\/em> with the desired release version.<\/p>\n
The fourth command export DNF_SYSTEM_UPGRADE_NO_REBOOT=1<\/em> sets an environment variable to prevent the system from rebooting after the upgrade.<\/p>\n
The fifth command sudo -E dnf system-upgrade reboot<\/em> reboots the system to start the upgrade process. Make sure to save any important work before running this command.<\/p>\n
The sixth command sudo -E dnf system-upgrade upgrade<\/em> performs the upgrade process.<\/p>\n
Finally, the seventh command sudo dnf upgrade –refresh<\/em> updates any remaining packages and ensures that your system is fully up to date.<\/p>\n
Errors Encountered<\/h2>\n
During the installation and upgrade process, you may encounter errors. Two common errors are described below, along with their solutions.<\/p>\n
Error 1:<\/strong><\/em> sudo: \/etc\/sudo.conf is owned by uid 1001, should be 0
Solution:<\/strong><\/em> This error occurs when the ownership of the sudo.conf<\/em> file is incorrect. To fix this, run the following command:<\/p>\n
chmod +s \/usr\/bin\/sudo<\/pre>\n
This sets the setuid bit on the sudo<\/em> command, which allows it to run with root privileges.<\/p>\n
Error 2:<\/strong><\/em> filesystem package didn’t get upgraded post OS upgrade
Solution:<\/strong><\/em> This error occurs when the filesystem<\/em> package is not upgraded during the upgrade process. To fix this, run the following commands:<\/p>\n
sudo rpm -e --nodeps filesystem\ndnf download filesystem<\/pre>\n
The first command removes the filesystem<\/em> package, and the second command downloads the latest version of the package. If you encounter any errors during the upgrade process, you can use rpmrebuild<\/em> to rebuild the package with any necessary modifications.<\/p>\n
Conclusion<\/h2>\n
In this article, we’ve shown you how to install Fedora Linux on Android using Termux and how to keep it up to date with the latest versions. While there may be some errors to overcome during the installation and upgrade process, following the steps outlined in this article should help you get Fedora up and running on your Android device in no time.<\/p>\n","protected":false},"excerpt":{"rendered":"
If you’re interested in running Linux on your Android device, you’re in luck! It’s possible to install Fedora Linux on Android using Termux. Termux is a terminal emulator for Android that allows you to run Linux commands and utilities on your phone or tablet. It does not replace Android. In this article, we’ll walk you […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[45,61,1488,43,46,47,1170],"class_list":["post-134174","post","type-post","status-publish","format-standard","hentry","category-fedora-os","tag-fedora","tag-fedora-project-community","tag-five-things-in-fedora-this-week","tag-for-system-administrators","tag-magazine","tag-news","tag-review"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/134174","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=134174"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/134174\/revisions"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=134174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=134174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=134174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}