DJI Air Unit Will Not Root

[Bookmdanno]

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!

[stylesuxx]

Windows 7 is EOL. Other people had issues with that too, would not recommend using win 7 for anything.

What you describe sounds like another process is claiming the device after reboot. Make sure no other programs that might be claiming the device are running (DJI assistant, other tabs running the configurator, Cura...). When I'm doubt try different USB cables and ports.

[Bookmdanno]

Thanks Chris.  So I'm using Win10, version 10.0.19043 Build 19043 on an ASUS G74S with Intel Core i7, and the latest versions of Chrome and Edge. I pasted some of the system info at bottom in case you might notice something that could be incompatible. I've tried two USB cables that both work fine for everything else.  I've tried all four of the USB ports.  With Chrome, when I click on 'ROOT DEVICE' the popup shows the device ok (CDC Serial (COM4) - Paired) but after selecting it and clicking 'Connect', nothing happens.  If I disconnect & reconnect the USB cable and try again - still nothing happens.  If I disconnect & reconnect the battery on the Air Unit, I get this 'Device came back ... Step 1 - Success! Rebooting then it just hangs forever. With MS Edge, it's about the same exept it reports 'Failed after 10 retries.' Any ideas?  Is there something I can look at to see further under the hood to find out what the root cause it? Thanks, Dan CHROME MS EDGE On Tuesday, November 8, 2022 at 01:38:01 AM MST, Chris ***@***.***> wrote: Windows 7 is EOL. Other people had issues with that too, would not recommend using win 7 for anything. What you describe sounds like another process is claiming the device after reboot. Make sure no other programs that might be claiming the device are running (DJI assistant, other tabs running the configurator, Cura...). When I'm doubt try different USB cables and ports. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stylesuxx]

As I mentioned before, I am pretty confident that some other program is claiming the connection before the configurator can. You made sure that this one tab is the only tab and that no other program like DJI Assistant, or any other program are picking up the connection (Cura for example loves to do that).

Unfortunately I can not see any of the additional infos you tried to post, but since the device shows up in the configurator, driver wise, everything should be fine. Could you post your trace ID (bottom left of the screen) - maybe I can see something suspicious there...

[Bookmdanno]

I closed everything so I don't know what would be claiming it.  Any easy method to see it if it is?Here's trace ID for attempt with Chrome.  After saying it found device WM150, it says version is UNKNOWN.  Then Step 1 Success!, rebooting, and hangs.v1.0.0 - Trace ID: d67c5d11-7901-43f4-8c4b-f07e41f61784 Attempt with Edge. v1.0.0 - Trace ID: fb6101ed-2bae-4bd6-a43d-16108e13251e If Air Unit is powered up, then WTFOS Configurator started, nothing happens when I select ROOT DEVICE and select the 'CDC ... Paired' in popup.  Configurator has to already be open, then power up Air Unit.  Then Configurator says, "Device came back'  Then before selecting the 'CDC...' in popup, it just goes right ahead with 'Attempting Step 1...' On Tuesday, November 8, 2022 at 09:12:29 AM MST, Chris ***@***.***> wrote: As I mentioned before, I am pretty confident that some other program is claiming the connection before the configurator can. You made sure that this one tab is the only tab and that no other program like DJI Assistant, or any other program are picking up the connection (Cura for example loves to do that). Unfortunately I can not see any of the additional infos you tried to post, but since the device shows up in the configurator, driver wise, everything should be fine. Could you post your trace ID (bottom left of the screen) - maybe I can see something suspicious there... — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Bookmdanno]

It looks like others have had a live session and maybe shared their desktop so the problems could be debugged remotely.  Is there any chance we could do that? On Tuesday, November 8, 2022 at 09:44:54 AM MST, Dan ***@***.***> wrote: I closed everything so I don't know what would be claiming it.  Any easy method to see it if it is?Here's trace ID for attempt with Chrome.  After saying it found device WM150, it says version is UNKNOWN.  Then Step 1 Success!, rebooting, and hangs.v1.0.0 - Trace ID: d67c5d11-7901-43f4-8c4b-f07e41f61784 Attempt with Edge. v1.0.0 - Trace ID: fb6101ed-2bae-4bd6-a43d-16108e13251e If Air Unit is powered up, then WTFOS Configurator started, nothing happens when I select ROOT DEVICE and select the 'CDC ... Paired' in popup.  Configurator has to already be open, then power up Air Unit.  Then Configurator says, "Device came back'  Then before selecting the 'CDC...' in popup, it just goes right ahead with 'Attempting Step 1...' On Tuesday, November 8, 2022 at 09:12:29 AM MST, Chris ***@***.***> wrote: As I mentioned before, I am pretty confident that some other program is claiming the connection before the configurator can. You made sure that this one tab is the only tab and that no other program like DJI Assistant, or any other program are picking up the connection (Cura for example loves to do that). Unfortunately I can not see any of the additional infos you tried to post, but since the device shows up in the configurator, driver wise, everything should be fine. Could you post your trace ID (bottom left of the screen) - maybe I can see something suspicious there... — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stylesuxx]

If the version shows unknown, then there is some other issue. Please use DJI Assistant and check which version is installed and down/upgrade to 0606.

Remote will only work once you are rooted, otherwise I would have offered that ;-)

[Bookmdanno]

DJI Assistant shows correct 0606 version (So does WTFOS Configurator on old Win7 pc but not using that now).  Maybe I'll try refreshing the Air Unit FW.  Just desperately grasping at straws now. lol On Tuesday, November 8, 2022 at 10:06:28 AM MST, Chris ***@***.***> wrote: If the version shows unknown, then there is some other issue. Please use DJI Assistant and check which version is installed and down/upgrade to 0606. Remote will only work once you are rooted, otherwise I would have offered that ;-) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stylesuxx]

Yes, please try refreshing.

[Bookmdanno]

I'm guessing it's a driver issue with Win10 because DJI Assistant 2 does not see the Air Unit on this pc.  But on the Win7 pc it does and it shows ver 0606.  But I went ahead and refreshed 0606 on the Win7 pc which worked fine.  Then put it back on the Win10 pc and DJI Assistant 2 still doesn't see it.  I tried rooting it again and same problem - failed after 10 retries.  But it acts weird because the Configurator does NOT do anything after selecting the "CDC ... Paired" popup and clicking connect.  The Configuator only tries rooting if Ait Unit power is cycled and then it goes ahead and tries it even though I haven't yet selected "CDC ..." and 'Connect' in popup - it just does it anyway and leaves the popup open. Do you know of any USB driver issues or way to check for correct Win10 drivers?  Device Mgr says they're working properly but I'm wondering if there're newer  On Tuesday, November 8, 2022 at 10:12:22 AM MST, Chris ***@***.***> wrote: Yes, please try refreshing. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stylesuxx]

If the assistant does not see the device then yes, might be a driver issue (or still an issue with another app claiming the device). Use zadig and play around with the different driver options. Also post output from chrome://device-log clear the log, plugin device, refresh, post screenshot.

[Bookmdanno]

I reinstalled an "HIDUSB" driver - not really knowing what I'm doing - didn't help. Here's Chrome log after selecting 'Root Device" and selecting popup items.  So obviously a serial port opening error.  But I don't know why. SerialError[13:14:08] Failed to open serial port: FILE_ERROR_ACCESS_DENIED  Here's the Chrome log after following your instructions: SerialEvent[13:10:42] Serial device added: path=COM4 instance_id=USB\VID_2CA3&PID_001F&MI_04\7&3A7FE9B5&0&0004 vid=2CA3 pid=001F USBEvent[13:10:42] USB device function updated: guid=22a8238d-54b9-4fb9-9ee7-519c91d09644, interface_number=4, path="\\?\usb#vid_2ca3&pid_001f&mi_04#7&3a7fe9b5&0&0004#{86e0d1e0-8089-11d0-9ce4-08003e301f73}", driver="usbser" USBEvent[13:10:42] USB device function updated: guid=22a8238d-54b9-4fb9-9ee7-519c91d09644, interface_number=0, path="\\?\usb#vid_2ca3&pid_001f&mi_00#7&3a7fe9b5&0&0000#{cac88484-7515-4c03-82e6-71a87abac361}", driver="usbrndis6" USBEvent[13:10:42] USB device function updated: guid=22a8238d-54b9-4fb9-9ee7-519c91d09644, interface_number=0, path="\\?\usb#vid_2ca3&pid_001f&mi_00#7&3a7fe9b5&0&0000#{ad498944-762f-11d0-8dcb-00c04fc3358c}\{42f6eba1-3e22-47d9-a3e5-003d4ce6447f}", driver="usbrndis6" USBEvent[13:10:42] USB device function updated: guid=22a8238d-54b9-4fb9-9ee7-519c91d09644, interface_number=3, path="\\?\usb#vid_2ca3&pid_001f&mi_03#7&3a7fe9b5&0&0003#{20343a29-6da1-4db8-8a3c-16e774057bf5}", driver="libusb0" USBUser[13:10:42] USB device added: path=\\?\usb#vid_2ca3&pid_001f#123456789abcdef#{a5dcbf10-6530-11d2-901f-00c04fb951ed} vendor=11427 "DJI", product=31 "DJI FPV Air Unit", serial="123456789ABCDEF", driver="usbccgp", guid=22a8238d-54b9-4fb9-9ee7-519c91d09644 SerialEvent[13:10:38] Serial device removed: path=COM4 USBUser[13:10:37] USB device removed: path=\\?\usb#vid_2ca3&pid_001f#123456789abcdef#{a5dcbf10-6530-11d2-901f-00c04fb951ed} guid=7ad7432a-0bfa-449a-b12e-892d4183bc16 On Tuesday, November 8, 2022 at 11:46:43 AM MST, Chris ***@***.***> wrote: If the assistant does not see the device then yes, might be a driver issue (or still an issue with another app claiming the device). Use zadig and play around with the different driver options. Also post output from chrome://device-log clear the log, plugin device, refresh, post screenshot. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. On Tuesday, November 8, 2022 at 11:46:43 AM MST, Chris ***@***.***> wrote: If the assistant does not see the device then yes, might be a driver issue (or still an issue with another app claiming the device). Use zadig and play around with the different driver options. Also post output from chrome://device-log clear the log, plugin device, refresh, post screenshot. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stylesuxx]

SerialError[13:14:08] Failed to open serial port: FILE_ERROR_ACCESS_DENIED

Yeah, you don't have the correct permission, that's most likely also the reason why you can't access it in DJI Assistant. Can you try running chrome as Administrator? I can find almost no information about this error on windows. One guy seemed to have luck with zadig though...

[Bookmdanno]

'Run as administrator' - now why didn't I think of that?  Well, maybe that would've solved it but after tearing the remainder of my hair out, and fooling around with Task Mgr and shutting down all kinds of Processes that in my expert opinion (lol), I deemed as unecessary, and then uninstalling, deleting, and reinstalling the USB drivers, it finally gave up harassing me and decided to let me have my way.  It rooted it and I was able to install WTFOS!Now the problem is that the pc won't recognize the Goggles to be able to root and program them. Opened new ticket:  #227.Thanks On Tuesday, November 8, 2022 at 03:14:22 PM MST, Chris ***@***.***> wrote: SerialError[13:14:08] Failed to open serial port: FILE_ERROR_ACCESS_DENIED Yeah, you don't have the correct permission, that's most likely also the reason why you can't access it in DJI Assistant. Can you try running chrome as Administrator? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stylesuxx]

OK, so you did some random stuff and it worked. Great. We still don't know what the issue was. CLosing this down.