As I have already documented on Discord this Air Unit Light after rooted regularly does not allow correctly installed packages to run at boot for this dinit issue. But then imparting this command in CLI the two selected services instead run smoothly as you can see in the image, without giving that command i cannot activate them, so I lose them at every reboot:

/opt/etc/init.d/rc.unslung restart

@j005u has already performed remote session to check what it might be but has not figured out where the problem lies, and from what I read on Discord @stylesuxx had helped someone solve this problem always on an Air Unit Lite, I don't know if he succeeded or not. We have already reflashed slot_1 to the stock version after checking the md5 of ota.zip with these commands, it gave no errors:

unrd slot_1.status_successful 0 unrd slot_1.status_active 0 unrd slot_2.status_active 1 rm -rf /blackbox/wtfos reboot

But even after this operation, after wtfos repair/fix the problem was not solved. Now in my ignorance if doing an initd restart after booting solves the problem one solution might be to create a check on whether the selected services actually start during boot (check of related PID or other), in case they are found to be disabled you run an rc.unslung restart, I think that would be the simplest solution. It is possible that the execution of that services at boot occurs at a time where they find a condition so they cannot be executed? I don't know. If you do not understand where efffectively the problem lies I think it is enough to find an empirical way to skip the problem. Tried with 606 and 608 firmware, same problem. Re-executed reflashing with Assistant as well, but I remain in a dead end. Without these services available at reboot the root in this unit is therefore useless. I've execute root and everything else with the configurator on three other identical units and I haven't had any problems, selected services are performed at boot regularly. I'm in your hands........ :-(

WTFOS is not installed. the ATTEMPT FIX button does nothing and the INSTALL button does nothing either. What should I do? I've been trying to install WTFOS for the second day. Root is done more than once successfully.

I'm able to root the devices fine and receive the success message at the end. Going to any other tab on the wftos page and clicking connect shows "no compatible devices found". If I go back to the root'ing page the device shows available in com ports.
Same issue on v1 goggles, and caddx vista.

When I try to root my googles my browser always crash with STATUS_ACCESS_VIOLATION. I also checked develop.fpv.wtf/root and I face the same problem.

My setup

• Windows 10 pro
• All programs closed
• Avast antivirus protection turned off UPDATE: I uninstalled it from the system and still get STATUS_ACCESS_VIOLATION
• proper version on Googles (606 on both modes verified in the googles and in DJI Assistant)
• proper USB-C data cable (original from DJI)
• batteries charged, I wasn't touching any cable during first try (nothing was disconnected during the process)

I've tested in on Chrome, Edge, different USB ports in my laptop and same issue occurs:

Some dev tools log:

Created new watcher...
Startup check
connect true true true
Disposing old watcher...
Created new watcher...
00:01 Attempting Step 1...
00:02 Device went away...
Unlock step failed: DOMException: Failed to execute 'open' on 'SerialPort': Failed to open serial port.
00:08 Device came back...
00:11 Attempting Step 1...

After that browser crashes.

The additional problem that occurred after I tried rooting is that my googles are no visible in DJI Assistant anymore. I tried reinstalling it to the latest one v2.1.14 and same problem - no googles in DJI Assistant. UPDATE: in DJI Assistant sometimes I do see googles but just for less than 1 second. That is not problem of broken cable or port in laptop or in the googles.

My feeling is that my googles are available in the system for less that 1 second and they are gone. From time to time they re-appear and are gone again. It was not happening before trying to ROOT. Connection was rock solid before I tried to root.

I suspect that this is similar to the closed case #192 ... but thought that I should report it.

Have 2 Vista units rooted with wtfos installed & the msp-os & FCC patches ... one is on a 6s build & another on a 4s. Using the V2 goggles & all, both Vistas and goggles are on 0606.

All is working solid on the 4s but not on the 6s ... the 6s repeatedly get it's wtfos stuck in the health checks & needs to be fixed there, after that I need to re-root, install wtfos again + the patches.

Think I've narrowed it down to that the 6s battery often creates a spark (arcing) when I connect the xt60 to the quad ... imagine that can create a current spike which makes the Vista change slot to 2 (similar to quickly connect & disconnect the battery)? The 4s quad batteries never generates arcing & it's maybe the reason for it to work reliably?

The other day I had the 6s quad powered on the bench & the OSD was working as it should in the goggles ... disconnected the battery, & an hour later I again connected the battery & got a pop sound due to arcing between the quad xt 60 & the battery xt60 ... & now the OSD wasn't working anymore. After connecting the Vista to the WTFOS configurator site the wtfos installation needed to be fixed.

Read that you were working on a long term solution for this ... any news when this can be addressed?

hi rooted air unit but try to install wtfos it keeps rebooting and wont install wtfos rooted and installed wtfos on other of my airunits no problems and vistas rootng was successfull

After successful root, installing of WTFOS and MSP-OSD it isnt recognized anymore. It works great on my desk directly after installing. but at the next day nothing works anymore. The configurator says i need to install WTFOS again on my vista, but the installation tooks only 2s and nothing changes. I tried different browsers, cables and reboot my vista many many times. im not able to use WTFOS on my vista anymore

The root process successfully finds the Air Unit and the FW version is correct (01.00.0606). But it aborts in Step 1 because "Device did not reboot in time". Should this process work on Windows 7 with latest version of Chrome? Sometimes retrying causes Windows to go looking for a USB driver but it says it can't find it. DJI Assistant has no trouble talking to the Air Unit and WTFOS Configurator recognizes it so doesn't that mean the necessary drivers are already installed? I tried all four of the USB ports on this ASUS G74S machine. One doesn't respond at all and the other 3 all end up with the same result - Air Unit not rebooting in time. I tried it again on a Windows 10 pc with both Chrome and Edge. Same problem with Chrome. With Edge, it gets to Step 2 and aborts after 10 retries. This is a brand new Air Unit and it bound with my googles and worked fine before trying to root it. Battery voltage was good and it had plenty of cooling air from a strong fan. Thanks for any help you can provide!

hello, i have a problem with fpv.wtf the glasses v2 worked great! but with the air unit the root worked but when i try to connect it always throws me off the internet site what can i do? lg.

The UI could offer extended configuration options for packages that have them.

We know already @bri3d needs a way to select the font for msp-osd and @funnel needs a way to switch between PAL/NTSC.

On the other hand we can also expect there to eventually be an interface on the Goggles themselves for this, so I think this needs quite a bit of thought put into it how to actually handle it.

• [x] Test Googles V2
• [x] Test on Vista
• [x] Test on OG Air-Unit
• [ ] Test Goggles V1

Todo:

• [x] Step 4 - Success! Rebooting... check multiple times
• [ ] Use ping commands before invoking actual command
• [x] Test timeout between device coming online and invoking the actual command

Hi. For a week I can't overlay the recorded osd on my video. Updated to the latest version, selected fonts, tried absolutely everything, this error is issued every time. Please help me solve it.

I can't connect my Caddx Vista with the configurator. On the developer version it shows up on the menu but then I get the "adb kill server" error. I tried to upgrade the driver with Zadig like someone else on this GitHub did but unfortunately it still doesn't work.

Also and I don't know if that's related to the problem. When I connect my Vista the first time it isn't recognized as a USB driver, it's in the devices and printer menu. I always have to connect a second time so that it recognizes it as a USB driver.

can't root my dji v2 goggles. It starts and then, 01:32 Aborted! Device did not reboot in time, please power cycle and try again. and when I recycle it does the same thing. what are I doing wrong?

Is this something that already exist somewhere? Would be nice to have it just to quickly glance over to see if anything have been updated... instead of needing to connect goggles or Vistas/Air units to the configurator to find out.

Or is this too much administrative work?

Time to start pulling this together! I think it works well enough that it's worth getting it merged and dealing with it from there.

Tried to keep the TS as separate as possible as suggested. All the main functionality is under osd-overlay in TS in it's own little bubble. The UX components are plain JS.

All of the processing is done in a web worker to keep it all separate on that front.

Remaining WIP tasks, I think:

• Pepper in translations where they should be!
• Rework UX generally. I'm not particularly happy with the layout, etc. You should be able to grab all of your files in a big bundle and just drag them onto the page and let it figure it out for you, e.g.
• Expose errors in UX rather than getting folk to dig into developer console.

The MP4 parsing, etc. needs broken out into it's own library because it's absolutely useful for other things. Bit of a longer term goal for me.