Skip to content

Comments

Add warning to moxee page#873

Merged
cooperq merged 2 commits intomainfrom
moxee-warning
Feb 11, 2026
Merged

Add warning to moxee page#873
cooperq merged 2 commits intomainfrom
moxee-warning

Conversation

@untitaker
Copy link
Collaborator

see #865

@vurtsnake
Copy link

As part of the warning, I propose that this should be included on the moxee page as part of the process for upgrade installs until/if it's added as automated to the installer that you wrote in #733 -

The space on moxee is so tight that the first installation of the release firmware with fat LTO succeeds, but the upgrade doesn't. That is because the data partition cannot hold both rayhunter-daemon and rayhunter-daemon.tmp.

The following steps are necessary to un-break the device, if you don't just want to factory reset it:

telnet into it or use installer util orbic-shell
rm /data/rayhunter/rayhunter-daemon* -f
killall rayhunter-daemon to actually free the disk space, as the currently running binary is still referenced by the running process
I feel that performing those steps automatically in all installers (removing target file before transfer, and shutting down rayhunter before install) would probably make them more robust in general.

@untitaker
Copy link
Collaborator Author

@vurtsnake there is definitely strong indication that were dealing with a storage issue here, but these steps are entirely useless if the wifi is down.

@vurtsnake
Copy link

@untitaker You are correct - however, in both my case and @Draz-it 's case on the bricked moxee bug, both of ours were working, until we started the upgrade process. The wifi had not shut down until the failed upgrade process occurred. Looking from a documentation standpoint, the moxee page, presuming you mean https://efforg.github.io/rayhunter/moxee.html

Should at the moment either have the instructions listed above for folks still wishing to attempt upgrading as the barest precaution, but better a strong suggestion to simply not attempt upgrading at this time at all to prevent bricking.

tl;dr - docs should be trying to prevent even more moxee owners from bricking their devices right now if possible. I hope that's the direction you're going for.

cooperq
cooperq previously approved these changes Feb 10, 2026
@untitaker
Copy link
Collaborator Author

@vurtsnake i added a note that upgrades should not be attempted either until we figure this out.

@untitaker untitaker requested a review from cooperq February 10, 2026 20:46
@cooperq cooperq merged commit 9128eef into main Feb 11, 2026
20 checks passed
@cooperq cooperq deleted the moxee-warning branch February 11, 2026 01:06
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

Successfully merging this pull request may close these issues.

3 participants