Rayhunter is a new open source tool we’ve created that runs off an affordable mobile hotspot that we hope empowers everyone, regardless of technical skill, to help search out cell-site simulators (CSS) around the world.
Just got mine and getting this error. Would appreciate any support you nerds can give me because I don’t have a Github account:
Using adb at ./platform-tools/adb Force a switch into the debug mode to enable ADB /Applications/release/install-common.sh: line 20: ./serial-macos-latest/serial: Bad CPU typein executable
Edit: Installed via Linux, here’s what the UI looks like
There’s now a green line going across the top of the display and apparently if it detects any problems the line will turn red. Still no idea how I get that info back to the EFF though.
It’s the other way around, an Apple Silicon Mac would be able to run an intel binary through Rosetta (I think there’s almost no exceptions at this point). It’s intel macs that can’t run Arm specific binaries.
It didn’t mention anything about the CPU in the install instructions…
Try locating the binary that crashes with the “Bad CPU type” exception and run the file command on it. It will show you which architecture the binary was built for.
Oh, right, you did say “just got mine”… Never mind me. It does seem like it could be a mismatch between what the adb was compiled for and what it’s being asked to install on.
Just got mine and getting this error. Would appreciate any support you nerds can give me because I don’t have a Github account:
Using adb at ./platform-tools/adb Force a switch into the debug mode to enable ADB /Applications/release/install-common.sh: line 20: ./serial-macos-latest/serial: Bad CPU type in executableEdit: Installed via Linux, here’s what the UI looks like
There’s now a green line going across the top of the display and apparently if it detects any problems the line will turn red. Still no idea how I get that info back to the EFF though.
Do you use an Apple Silicon Mac by any chance?
I don’t
Can I message you on Matrix to help you diagnose this?
It’s the other way around, an Apple Silicon Mac would be able to run an intel binary through Rosetta (I think there’s almost no exceptions at this point). It’s intel macs that can’t run Arm specific binaries.
You’re right, I forgot about that
From what’s written here, it appears you have an Intel Mac and the thing has only ARM Mac executable, or the other way around.
It didn’t mention anything about the CPU in the install instructions…
I guess I’ll give it a try on my Linux machine.
Edit: Linux install was successful
Try locating the binary that crashes with the “Bad CPU type” exception and run the
filecommand on it. It will show you which architecture the binary was built for.That’s good to hear
I think it needs special hardware to run on:
That’s what I’m trying to run it on.
Oh, right, you did say “just got mine”… Never mind me. It does seem like it could be a mismatch between what the adb was compiled for and what it’s being asked to install on.