Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS Install Issue (No Orbic Device found) #165

Closed
aaronkarp123 opened this issue Mar 15, 2025 · 2 comments
Closed

MacOS Install Issue (No Orbic Device found) #165

aaronkarp123 opened this issue Mar 15, 2025 · 2 comments

Comments

@aaronkarp123
Copy link

Hello, I am attempting to install rayhunter on a new orbic device on my Macbook Pro running MacOS 15.3.1. I initially had trouble that was resolved by following the steps in this issue. However, now when I attempt to run install-mac.sh I get the following output:

computername@MacBookPro release % ./install-mac.sh
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB

thread 'main' panicked at serial/src/main.rs:113:5:
No Orbic device found
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

My Orbic device is currently plugged in to my computer and powered on. Additionally, the USB tethering option is set to On. Any suggestions on what to try for this problem?

Thanks!

@aaronkarp123
Copy link
Author

The full backtrace is pasted below if that is helpful:

   0:        0x10a593246 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h161fe852ae799fbc
   1:        0x10a5a95a3 - core::fmt::write::h2f9812213241cbc5
   2:        0x10a590fa2 - std::io::Write::write_fmt::h38cbb392123ccd6d
   3:        0x10a593082 - std::sys::backtrace::BacktraceLock::print::h28c254b8e75870a2
   4:        0x10a5940e1 - std::panicking::default_hook::{{closure}}::h62f6dde5981534a4
   5:        0x10a593eb9 - std::panicking::default_hook::h166356404cd23068
   6:        0x10a5949c2 - std::panicking::rust_panic_with_hook::hc37270698fe8fd9c
   7:        0x10a594615 - std::panicking::begin_panic_handler::{{closure}}::h776221fbdc0e5cee
   8:        0x10a593729 - std::sys::backtrace::__rust_end_short_backtrace::hb64cdddf0b0c774b
   9:        0x10a59428c - _rust_begin_unwind
  10:        0x10a5b063f - core::panicking::panic_fmt::h4f14559255533f9b
  11:        0x10a56143e - serial::main::hdc08ea00910d731b
  12:        0x10a562056 - std::sys::backtrace::__rust_begin_short_backtrace::hfbddb0b0f9770a83
  13:        0x10a56204c - std::rt::lang_start::{{closure}}::ha73ad68e20a7710b
  14:        0x10a58eee8 - std::rt::lang_start_internal::hb2f1aec89f5a7470
  15:        0x10a56202c - _main
  16:     0x7ff810ab22cd - <unknown>

@aaronkarp123
Copy link
Author

This is resolved! For anyone encountering a similar issue, it was solved by turning the usb-tethering off and then back on in the Orbic UI. Guess that reset the option somehow, despite it showing a checkmark previously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant