bad interpreter

Quick answer

Fix bad interpreter, /bin/bash not found, CRLF line endings, wrong shebangs, and copied shell scripts that fail on Android Termux.

This guide keeps bad interpreter simple: identify the clue, run one command, then fix the smallest broken part.

For bad interpreter, focus on Termux troubleshooting and use the output to decide the next small fix instead of reinstalling everything.

What to check

• Treat bad interpreter as one small failing layer: path, package, Python, Git, browser, or Android permission.
• For bad interpreter, keywords that usually matter are: bad, interpreter.
• If the first command for bad interpreter gives a different error, follow the new clue instead of forcing this guide.

Copyable command

For bad interpreter, replace placeholders only when they appear in the command.

head -n 1 script.sh
sed -i "s|^#!/bin/bash|#!/usr/bin/env bash|" script.sh
pkg install dos2unix -y
dos2unix script.sh
chmod +x script.sh
./script.sh

Read the output

1. head -n 1 script.sh — checks the part of the Termux troubleshooting workflow that usually causes this issue for bad interpreter.
2. sed -i "s|^#!/bin/bash|#!/usr/bin/env bash|" script.sh — checks the part of the Termux troubleshooting workflow that usually causes this issue for bad interpreter.
3. pkg install dos2unix -y — installs the package that the command or script depends on for bad interpreter.
4. dos2unix script.sh — checks the part of the Termux troubleshooting workflow that usually causes this issue for bad interpreter.
5. chmod +x script.sh — adds execute permission when Android or Git did not preserve it for bad interpreter.
6. ./script.sh — checks the part of the Termux troubleshooting workflow that usually causes this issue for bad interpreter.

Fix in a safe order

1. If the bad interpreter error changes, read the new clue instead of repeating the old fix.
2. Keep screenshots or copied terminal text for bad interpreter; they make paid help faster if you need it.
3. Save the bad interpreter output before editing files.

Common mistakes

• Running the bad interpreter command from the home folder when the project is somewhere else.
• Following a desktop Linux answer that ignores Android storage paths while fixing bad interpreter.
• Closing Termux before copying the output that explains bad interpreter.

Related Assistance pages