Replies: 2 comments 1 reply
-
|
not sure but I think your internal storage might just be full, and that's why installation fails. I'd try to get a shell on the device (installer util orbic-start-telnet, then use nc to connect to port 24), then delete the /data/rayhunter folder and hope that clears up some disk space. chatgpt can probably help you with commands to figure out how much disk space you're using. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
See also #733 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So this is all on me, 100% (and maybe chatgtp). I am only writing this to describe my experience and also a little bit as I am confused how it could have happened since to my understanding nothing was pushed to the device due to a checksum mismatch.
I recently heard of this project and was excited to try it out. I was off work for a few days so I had time to play. I was going to just get an Orbic but then I remembered having a hotspot sitting in a drawer for a while and decided to check what it was and it was a Moxee K779HSDL and to my surprise it was supported.
Install was super easy and I had a working device, minus the green/red indication bar. I found an issue where someone found a fix and implemented it and it worked, but due to holidays was not currently being worked on. Well, I got some time on my hands and this looks easy enough I thought, so I figured would give it a go.
I should have just left well enough alone because it became evident quickly that I had no idea what I was doing. Probably compounded by fact that I am using a M1 Mac. So as one does in these situations, I consulted chatgtp who for the next, I would rather not say amount of time, just lead me around in circles between docker and some other stuff that I honestly don't even care to go back and check what it was.
After much coaxing I seemed to have a completed build. All seemed well until while trying to push it through I got a checksum error that I assumed prevented anything from being pushed through. I kept trying to get gtp to lead me the right way but no matter what I did, always a checksum error.
But as far as I know, the device up to this point was working. So I decided to try and just flash the original from the installer because in that issue I read there was also a note about storage space and was wondering if that was my issue. Again, I should have just left well enough alone, but I tried to push the original through using the release installer and got the same checksum error. So I did something stupid(er) and used the reset button on the device. And that's when it all broke.
Things I can tell that are different:
Assumption:
Since I can't connect to wifi, I can't even use the install tool to push a new firmware as the device wont be detected and even though it boots and I can cycle through menus its essentially bricked as all the settings have been lost and as far as I can tell, nothing I can do to fix.
Conclusion:
Again, 100% my fault. I own that. I am just reaching out in case this can be recovered. But really, because I don't understand what exactly did this. wouldn't the checksum mismatch error have prevented my customized firmware from being pushed through.
I don't think there is anything actionable here, so I did this as a discussion.
Beta Was this translation helpful? Give feedback.
All reactions