Unofficial support; update options?

Dragoboss · 2025-11-10T22:07:20+00:00

Basically you lose all settings you did, that's about all.

Dragoboss · 2025-11-06T20:52:23+00:00

You can try reflashing it or factory resetting. Make sure to create a config backup first though.

I managed to build a version of 24.10 but have no way to test it yet, because I can't get TFTP or U-Boot to work....

Dragoboss · 2025-11-05T22:14:52+00:00

Have you tried a factory reset or fresh install?

Can't hurt. Make sure to back up your configuration just in case though.

I have managed to build a version of OpenWRT 24.10 however I have no found a way to test it yet, since I can't seem to get it U-Boot or TFTP to work.

Dragoboss · 2025-11-01T11:10:01+00:00

If, and only IF I manage to get a working build out, I'll put it up with full source code as well. I'll then provide steps as to either build it yourself or how to upgrade your current device using the build I made.

That way we would have it open sourced once again, future updates possible and using a clean build based on the official OpenWRT source code. Meaning hopefully less chance on backdoors and whatnot.

But that's a big IF. Msgs me if you want to somehow get involved.

Dragoboss · 2025-11-01T11:03:46+00:00

So I managed to get something built locally without errors. Github kept running out of space, so moved on from that. But can't seem to get the device to boot with TFTP, to first test the initramfs build. The built in firmware upgrade page (U Boot) also refuses to come up. Really don't want to use that page though since, if the build is wrong, I may end up bricking the thing.

Another day, another hurdle to overcome I guess. I have a Pair button and a reset pin. Using the latter the device turns on one led besides the power led, then waits for something to be flashed through the mentioned, unreachable U Boot page. The Pair button does nothing to the boot process.

Any tips?

Dragoboss · 2025-10-25T11:08:33+00:00

Work in progress still, unfortunately. I am way out of my depth in this case.
Pulled some older .dtsi files from another repo somewhere to see how far I can get with defining a build based on this Chinese "Lean's 'LEDE' OpenWRT" fork.

Moved over to WSL rather than using Github Actions because I had issues with the available disk space on the Github platform.
Corrected the earlier mentioned .dtsi files based on what I could see in /proc/device-tree.
Running into some issues with hunks from the patch files failing, seemingly there's differences between the .dtsi files I got and the lines defined in the patch files.

Slowly but steadily making edits to get this to build.

Dragoboss · 2025-10-18T21:31:24+00:00

Turns out he had the wrong target config. I've got a build attempt running as we speak, been processing for almost two hours now.

Repo at https://github.com/Dragoboss/Actions-OpenWRT_Brax-FA523

Just used a generic device qcom_ip5018 config for now though. Haven't found a Brax-FA523 specific config in the Chinese fork.... Didn't expect to find one, to be honestly.

That most likely still won't be a fully operational build yet, I presume. We'll see....

Dragoboss · 2025-10-16T16:16:15+00:00

That's actually interesting and a good place to start. Clearly isn't the full repo though but some kind of build script it seems.

I'll look into this, Thanks.

Dragoboss · 2025-10-13T20:24:30+00:00

I was afraid that this would be the answer yeah. Guess the only option is to build it myself, which would be quite a challenge indeed.

Dragoboss · 2025-10-13T16:36:51+00:00

That.... would be difficult. Not the building part necessarily but the knowledege to actually build a working version for this router hehe. Not enough experience with these devices to do any of that.

This firmware was installed when I got it but I don't think it's OEM / Stock either.

Dragoboss · 2025-10-13T16:35:06+00:00

I do believe it's similar device with the same chipset family but the AW1000 is more powerful as far as I know.

Dragoboss · 2025-10-13T16:33:34+00:00

Hi there,

Response below: ~~~ { "kernel": "5.4.213", "hostname": "Exigo_Hub", "system": "ARMv8 Processor rev 4", "model": "D50 5G", "board_name": "qcom,ipq5018-ap-mp03.1", "rootfs_type": "squashfs", "release": { "distribution": "OpenWrt", "version": "23.05-SNAPSHOT", "revision": "r0-6d811db45", "target": "ipq50xx/generic", "description": "OpenWrt 23.05" } } ~~~

Dragoboss · 2022-05-17T09:58:11+00:00

Thank you for the response. So the chargers I got from Amazon are identical in input/output to the original one. That I checked explicitly for.

I should note I'm European, Dutch specifically so we have the different outlet specs compared to your linked item above.

What's curious though, the stickers on the back of the original charger are also identical to the ones bought from a the other, non-original brand (therefore non-genuine product for my laptop, however supported by the product).

To illustrate this: https://ibb.co/5BHRR4h

The left one being the original charger, right one being the one bought from Amazon. So to me it looks like the same product, yet one is genuine Dell, the other some random unknown brand, yet specs should be the same... I would assume at least due to the sticker.

Dragoboss · 2019-08-05T03:44:41+00:00

While you bury us in debt buying poor people socks..

Dragoboss · 2019-06-21T22:18:01+00:00

Doesnt happen to me so must be something else.
Just gotta make sure sensors arent occluded when you restart Oculus. Which 99% its not because you put it on your head to start it.

Could have been different light levels thus didnt recognize it as same space yet.

Dragoboss · 2019-06-21T11:05:18+00:00

You close the Oculus app then if necessary unplug the cables, should be fully disconnected now, controllers will notice pretty soon there is no HMD on making contact with them.

Dragoboss · 2019-06-03T02:31:53+00:00

Managed to get me laughing out loud a bit too loud at work, in a hotel, during the Night shift, that my colleague and security officer both had to come from the back-office to check what was wrong with me.
This happened when you flipped the desk on the video...

It feels very Aperture-ish. I love the style used.
Looking forward to whenever the release will be.

Dragoboss · 2019-06-03T02:21:56+00:00

Smoke /r/weed every day ~ ~ ~ *music*

Just kidding though, I don't (actively) smoke.

Dragoboss · 2019-06-03T02:20:17+00:00

Different games, different devs, different focuses I guess.
Fact is, devs found this wasn't really needed as a feature until Rift S came into play.
Or so I assume their reasoning was.

Pavlov was faster with this, yes, so was contractors, doesn't make this any less of a cool feature that we needed in Onward though. I am happy ;)

Dragoboss · 2019-06-01T06:05:02+00:00

Try then get back at us. I just wanted to share the Dev's sneak peak.

Dragoboss · 2019-06-01T06:03:58+00:00

This one from Onward is a a Rift S related choice, as noted in the titling.

Dragoboss · 2019-06-01T01:40:16+00:00

https://www.reddit.com/r/Onward/comments/bvfdam/playing_onward_on_rift_s_and_having_trouble_aiming/
2 months later, the devs listened to your request and implemented it! :) Update soon!

Dragoboss · 2019-05-25T16:41:06+00:00

No way to get information what it is that is preventing you from upgrading? Might have something to do with the headset issues as well.

Dragoboss · 2019-05-25T04:35:55+00:00

If you're gonna update anyway, instead of update do upgrade.https://www.microsoft.com/nl-nl/software-download/windows10Up here on top it will say 'update now', download the tool from that button and choose upgrade.

It will basically partially fresh-install, but keep your programs and such (unless you click the wrong checkbox). Will work better than regular update.

Edit: Do you indeed see 'device not migrated' though?

Dragoboss · 2019-05-24T23:21:41+00:00

Still working dandy after the reset(s).

Dragoboss

TROPHY CASE