I wouldn't think so..
Perhaps you may want a second opinion, but it sounds to me like you just need to get your controller flashed correctly with Open SOlo.
The controller carries the wifi connection to Solo and I've found that any version mismatches break the wifi.
Here's the problem recovery link:
documentation/recovery.md at c1bfa88825ef50cd517fba2b9a0346875089e0a6 · OpenSolo/documentation · GitHub
A word of caution: if you haven't been inside a controller, they're somewhat difficult to work with. hard to separate the two halves, delicate
wires and connections so I wouldn't recommend it, but there may be no other way.
It looks to me like the process wipes out original factOry recovery partition, reboots, writes a new OpenSolo recovery partition, reboots, and does a factory reset-style install of OpenSolo using the partition created previously.
Does your controller boot successfully without Solo? Does it say "Waiting for Solo?"
Can you connect to Sololink on your PC or phone?
Can you ping 10.1.1.1 when connected via PC?
If connected to Sololink have you installed Solo-CLI?
What output do you get when you issue Solo info command? Is the controller at V2.4.2?
I'm trying to determine your current controller state... If the bird updated ok, but you never updated the controller, then it is still at 3DR version 2.4.2
If it is, then perhaps even though the bird isn't mucked up, it may be easier to reflash the IMX6 on Solo back to 3DR factory golden state and start the process over, rather than crack the controller. it now depends on where your controller is at.
I'm not an expert, so if yo do follow my advice, I am not responsible for the results. I have a different level of fear than most when it comes to breaking software...
Perhaps the OpenSolo authors may have different solutions, but if you didn't touch the controller, that is what I would guess you'd need to do.