F5F Stay Refreshed Software Operating Systems Error reported on Phoenix & Remix OS: Minimal Bash Like Line not available.

Error reported on Phoenix & Remix OS: Minimal Bash Like Line not available.

Error reported on Phoenix & Remix OS: Minimal Bash Like Line not available.

S
sant10
Member
69
03-23-2022, 01:37 PM
#1
You're facing an issue with installing Phoenix OS on different hardware setups. The error you're encountering—"MINIMAL BASH LIKE LINE IS SUPPORTED"—suggests compatibility problems with the installer. It seems the system is expecting a certain level of functionality that isn't available in your environment. You've managed to get it working on a laptop with a less powerful processor and graphics, but not on your PC with a newer CPU and better hardware. The workaround you tried with Rufus worked, indicating that the installation media itself might be the issue. Consider checking the latest Phoenix OS installer for any updates or compatibility notes, and ensure you're using a version that supports your system configuration. If needed, try booting from a USB with a different installer or consult community forums for further assistance.
S
sant10
03-23-2022, 01:37 PM #1

You're facing an issue with installing Phoenix OS on different hardware setups. The error you're encountering—"MINIMAL BASH LIKE LINE IS SUPPORTED"—suggests compatibility problems with the installer. It seems the system is expecting a certain level of functionality that isn't available in your environment. You've managed to get it working on a laptop with a less powerful processor and graphics, but not on your PC with a newer CPU and better hardware. The workaround you tried with Rufus worked, indicating that the installation media itself might be the issue. Consider checking the latest Phoenix OS installer for any updates or compatibility notes, and ensure you're using a version that supports your system configuration. If needed, try booting from a USB with a different installer or consult community forums for further assistance.

F
FNAF_Fan565
Junior Member
9
03-29-2022, 02:18 AM
#2
Yes, it works fine.
F
FNAF_Fan565
03-29-2022, 02:18 AM #2

Yes, it works fine.

I
InnOBeZz
Junior Member
44
04-17-2022, 05:10 AM
#3
i tried a different approach by installing phoenix os from a usb and using rufus to boot it. after installation, i rebooted into windows 10 via grub, but when i switched back to phoenix os, it wasn’t available in the boot manager. the same happened with lineage os 14.1—only windows 10 appeared. i’m wondering if repairing the boot manager would help, perhaps by removing it with a media file and using commands like bootrec /FixMbr and bootrec /FixBoot to clear grub. then i could try installing phoenix os again from usb. i also want to know how to identify which drive is actually formatted for phoenix os since the system doesn’t display the available space clearly. thanks for helping with this issue.
I
InnOBeZz
04-17-2022, 05:10 AM #3

i tried a different approach by installing phoenix os from a usb and using rufus to boot it. after installation, i rebooted into windows 10 via grub, but when i switched back to phoenix os, it wasn’t available in the boot manager. the same happened with lineage os 14.1—only windows 10 appeared. i’m wondering if repairing the boot manager would help, perhaps by removing it with a media file and using commands like bootrec /FixMbr and bootrec /FixBoot to clear grub. then i could try installing phoenix os again from usb. i also want to know how to identify which drive is actually formatted for phoenix os since the system doesn’t display the available space clearly. thanks for helping with this issue.

Y
Ying_R4ven
Junior Member
29
04-18-2022, 01:13 AM
#4
I don't know how much typical Linux Android-x86 is going to give you, those drive names are the drive names Linux gives it in order it was detected in. There is also /dev/disk/by-?? that has different ways of selecting them that isn't based on auto detection. (like serial number and UUID) The mount command should tell you whats mounted where but Android may do funny things like loopback mounts. For the boot option, if it's UEFI (and it should be) just select it from the uefi boot menu in the bios. Grub doesn't need to be installed to the windows disk at all. (although it can boot windows just fine if it is) Also I'm not sure if Android can read NTFS or not.. that is overall it's big issue.. PhoenixOS may be a pretty nice.. minimal desktop potentially.. but it's hardware support won't be good. There is also some concerns about it's developers. The Haiku OS might fill the same role with better hardware support but have worse apps.
Y
Ying_R4ven
04-18-2022, 01:13 AM #4

I don't know how much typical Linux Android-x86 is going to give you, those drive names are the drive names Linux gives it in order it was detected in. There is also /dev/disk/by-?? that has different ways of selecting them that isn't based on auto detection. (like serial number and UUID) The mount command should tell you whats mounted where but Android may do funny things like loopback mounts. For the boot option, if it's UEFI (and it should be) just select it from the uefi boot menu in the bios. Grub doesn't need to be installed to the windows disk at all. (although it can boot windows just fine if it is) Also I'm not sure if Android can read NTFS or not.. that is overall it's big issue.. PhoenixOS may be a pretty nice.. minimal desktop potentially.. but it's hardware support won't be good. There is also some concerns about it's developers. The Haiku OS might fill the same role with better hardware support but have worse apps.

G
Graser17
Member
68
04-18-2022, 07:05 AM
#5
In the end I realized it was a poor volume. I attempted the fixmbr and fixboot commands via cmd using a Windows installation media, but encountered an error when running "bootrec /FixBoot" and it reported corruption. Then I used diskpart to list disks, selected the correct one, cleaned and created a primary partition with NTFS format quickly. Everything was deleted, but my data was backed up. After reinstalling Windows, I discovered another issue: I was using Phoenix OS or Remix OS via UEFI boot despite being on legacy hardware. Instead of choosing it, I picked "USB STORAGE DEVICE" from Legacy Boot, installed the device, and it worked! It functioned perfectly.

However, I didn’t want the GRUB boot manager to appear. So I removed Phoenix OS and used a Windows installation media to follow these steps:

1. Verify your volume is intact and confirm the operating system type (32-bit or 64-bit).
2. If the volume appears damaged, use a Windows installation media to repair Windows via:
- Repair Windows → Troubleshoot → Command Prompt
- Type: diskpart >> list disk >> select disk x [your internal drive]
- Clean >> create partition primary >> format fs=NTFS
- Exit and reboot, then reinstall Windows.
3. When installing via ISO, ensure your USB boots into the right BIOS:
- Legacy systems: boot via USB as "USB STORAGE DEVICE"
- UEFI systems: boot via UEFI and specify the correct name (e.g., Kingston USB)
4. After fixing, use the Phoenix OS installer (not ISO) to set up Windows 10 as the default boot option and remove GRUB.

This process resolved boot issues for Phoenix OS, Remix OS, Bliss OS, Android x86, and Lineage OS. Thanks for all your advice!
G
Graser17
04-18-2022, 07:05 AM #5

In the end I realized it was a poor volume. I attempted the fixmbr and fixboot commands via cmd using a Windows installation media, but encountered an error when running "bootrec /FixBoot" and it reported corruption. Then I used diskpart to list disks, selected the correct one, cleaned and created a primary partition with NTFS format quickly. Everything was deleted, but my data was backed up. After reinstalling Windows, I discovered another issue: I was using Phoenix OS or Remix OS via UEFI boot despite being on legacy hardware. Instead of choosing it, I picked "USB STORAGE DEVICE" from Legacy Boot, installed the device, and it worked! It functioned perfectly.

However, I didn’t want the GRUB boot manager to appear. So I removed Phoenix OS and used a Windows installation media to follow these steps:

1. Verify your volume is intact and confirm the operating system type (32-bit or 64-bit).
2. If the volume appears damaged, use a Windows installation media to repair Windows via:
- Repair Windows → Troubleshoot → Command Prompt
- Type: diskpart >> list disk >> select disk x [your internal drive]
- Clean >> create partition primary >> format fs=NTFS
- Exit and reboot, then reinstall Windows.
3. When installing via ISO, ensure your USB boots into the right BIOS:
- Legacy systems: boot via USB as "USB STORAGE DEVICE"
- UEFI systems: boot via UEFI and specify the correct name (e.g., Kingston USB)
4. After fixing, use the Phoenix OS installer (not ISO) to set up Windows 10 as the default boot option and remove GRUB.

This process resolved boot issues for Phoenix OS, Remix OS, Bliss OS, Android x86, and Lineage OS. Thanks for all your advice!

A
AthenasLight
Posting Freak
781
04-18-2022, 10:08 AM
#6
Remember to reference us when you respond, otherwise you won't receive a notification.
A
AthenasLight
04-18-2022, 10:08 AM #6

Remember to reference us when you respond, otherwise you won't receive a notification.

J
JessDrewx
Junior Member
5
04-24-2022, 02:45 AM
#7
This link leads to a video about a dog named Max.
J
JessDrewx
04-24-2022, 02:45 AM #7

This link leads to a video about a dog named Max.

I
iDeadlyRekt
Member
183
04-24-2022, 11:22 PM
#8
Functioning correctly
I
iDeadlyRekt
04-24-2022, 11:22 PM #8

Functioning correctly