Here are my wifi connection issues and notes:
Brax3 devices keep giving the “check password and try again” error.
We have tried setting the AP to 2.4GHz g only, 2.4 GHz n/g/b mixed, 5GHz n/a mixed, WPA and WPA2, all fail with only the Brax3 phones while other devices authenticate correctly and work properly.
I disabled WPA and was able to connect to an open network on the same AP. So, it’s something to do with the authentication operation in the software.
Also, I am able to authenticate via WPA2 on the hotspot feature of my Brax2.
I also have a Linksys e1200 running DDwrt, WPA(2) connections to it fail with the Brax3 in the same manner.
A new beta build has just been pushed as OTA, with heavy changes to the Wifi stack. All feeback welcome.
To install it by OTA, the beta updater is required, which can be installed from here: beta/UpdaterBetaIode6v2.apk · master · ota / ota · GitLab
That beta updater can be uninstalled at any time, to come back to the stable channel (in App info, uninstall updates).
It is also possible to download and sideload it (https://gitlab.iode.tech/ota/betas/-/raw/master/iode-6.6-20250803-brax3-ota.zip) via adb from a computer in recovery mode. To boot in recovery mode, press volume up while powering on or rebooting the device, start Recovery, then Apply update, and Apply from ADB. Sideload with the command: ‘adb sideload iode-6.6-20250803-brax3-ota.zip’.
First post here, but I have the same issue, running the just-released Beta. I can’t connect to my tp-Link Archer A20 v1.0, 1.1.4 Build 20231011 rel.36819(5553) which is rejecting with an error message about the WPA2 password (which I’ve verified multiple times is correct) on both 5 and 2.4 GHz networks. This router uses the Broadcom BCM4365E. Luckily I can connect to my other router, a Netgear XR1000.
Confirmed, I forgot the connection and re-added. I should also add that my firewall (which provides DHCP) doesn’t even see the MAC address for the phone when trying to connect to the tp-link router (in bridged mode).
OK, sadly I am seeing the same attempting to connect to WPA (only) as my APs all work fine with WPA2. Effectively no improvement for those devices.
I have tried the full “Bluetooth and Wifi” reset as well, no improvement. I think we will need some more feedback from @vincent if there are other things we may be able to adjust.
So, I cant contribute to WPA, since UI removed WPA due to vulnerabilities. So I can only test WPA2-3 and WPA2-3 Enterprise. Those all work now for me. But I’m running some extreme compared to most.
@vincent@rik
I don’t know if this can help, but after trying to connect to my AP WPA2 Personal using the BraX3 GUI, the command cmd wifi list-networks shows a duplicated key:
Code
Network Id SSID Security type
1 AP wpa2-psk
1 AP wpa3-sae^
And log (verbose) : PreferenceGroup: Found duplicated key: "StandardWifiEntry:{"SCAN_RESULT_KEY":"{\"SSID\":\"AP\",\"SECURITY_TYPES\":[2,4]}","IS_TARGETING_NEW_NETWORKS":true}". This can cause unintended behaviour, please use unique keys for every preference."
Not sure which you are running now, but on my beta device, just like you mentioned, I can never seem to locate an update in the Updater. So I always go to gitlab with my device browser, download the beta, and always have to use the option in the Updater “Local update” under the 3 dots.
I have already tried this method several times in the past, but it doesn’t work on my device either.
No matter the update method, the OTA installs, but after rebooting, the screen turns off and on three times. After logging in, I notice that the version of IodéOS hasn’t changed.
I’m trying to understand what I might be doing differently from other testers that could explain the problem.
Is your bootloader locked? (mine is unlocked)
did you use SP Flash Tools to update? (I only used fastboot)
Ohhhh, you know, I recall someone else on the beta team mentioning this a while back. The only way they could update was a full reset, which wiped the data.
So, my history on the device went like this:
When we first received our beta devices, I used adb on the first one or two betas.
Then there was a beta, which also contained some updated MicroTek firmware. I used the SPFlash tool on that one (as plamen suggested), BUT I did not do the full format of the device. I recall that is when some of the IMEI issues popped up (which I did not experience).
After that I started applying betas via the updater tool.
But then one came out (the first one that iode made public on the gitlab site), and I saw it, and installed it manually.
Since then my Updater has also not reported any new updates.
I dont know if that was a fluke, or something broke. @rik did suggest that maybe I try to reinstall the updater, but I just have not done that at this point.
I have not experienced any of the issues others have, with IMEIs or odd update issues. I kinda wondered if that firmware update process tanked a bunch of folks.
┌─[guest@parrot]─[~/Desktop/iode-6.6-20250803-brax3-ota]
└──╼ $adb sideload iode-6.6-20250803-brax3-ota.zip
adb: failed to stat file iode-6.6-20250803-brax3-ota.zip: No such file or directory
┌─[✗]─[guest@parrot]─[~/Desktop/iode-6.6-20250803-brax3-ota]
└──╼ $