installing homebrew pkg failed with macOS 15.7.4（Intel）and no error informations

[mikeliu1031]

Output of brew config

/

Output of brew doctor

/

Description of issue

hi, I try to install homebrew pkg in my macbook pro, but it failed in the last. And there is no any error informations.
PLZ, help me to fix it, thx.

[nahyun27]

Hi! Based on your brew config and brew doctor outputs both showing only /,
it looks like Homebrew was not successfully installed yet.
So those commands aren't actually running from a valid Homebrew installation.

Also, the installer shown in your screenshot appears to be a third-party .pkg installer, not the official Homebrew installation method.
This could be the root cause of the silent failure.

Please try the official installation method instead (clean + official Install):

1. Remove any broken install

sudo rm -rf /usr/local/Homebrew
sudo rm -rf /usr/local/bin/brew
sudo rm -rf /usr/local/Caskroom
sudo rm -rf /usr/local/Cellar

---

2. Fix permissions (Intel Macs)

sudo chown -R $(whoami):admin /usr/local

---

3. Install using the official method

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

---

4. Verify

brew doctor
brew config

You should now see proper Homebrew paths instead of just / :)

[p-linnane]

A few corrections here since this is marked as the accepted answer:

The .pkg installer in the screenshot is Homebrew's official .pkg installer. It's linked directly from brew.sh and the installation docs, and is signed by my personal developer account. It's not third-party.

@mikeliu1031 rather than removing directories, let's figure out what actually went wrong first. Check the macOS installer log at /var/log/install.log. That should show the specific error the .pkg installer hit. You can also open Console.app and search for "install" around the time you ran it.

[nahyun27]

Thanks for the clarification.
I didn’t realize the .pkg installer is officially provided and linked from brew.sh.
Checking /var/log/install.log to identify the exact failure seems to be the right next step rather than assuming an installation method issue.
Appreciate the correction :)