There is now a tool to let you roll back the firmware on your goggles so you can root, even if you flashed to a firmware that locks out root! ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-63Smmc0bNcg.html
Donate! Donate! These guys are busting their butts to give us what DJI couldn’t, the least we can do is show them how much we appreciate their hard work!
DJI easely could`ve done it a long long time ago. People would praise them for listening to the community and they would be the good guys. Would be a win-win for both parties. HUGE THANKS to the whole FPVWTF team for doing all this work and even bringing more features than we ever expected to have! You guys are true heroes! Thank you!
Never happy some people. Dji have given us freestylers the best most stable clearest system yet. No one else has. I don’t get the whole hate dji thing. If they didn’t give us awesome video there’s no additional features like this. V1’s for the win.
There is some wrong information floating around here in the comments: - DVR is working, please stop spreading misinformation - Root is working for V1 and V2 googles (and all air units). - Live Audio works for OG air-unit and V1 goggles
A few notes from the main author of msp-osd (me): * Yes, DVR works fine. I re-introduced this functionality in August when I re-wrote the MSP DisplayPort overlay to co-exist with the DJI goggles overlay. No functionality should be lost by using msp-osd (although there is a known bug, see below:) * Low Power Mode is always on before arming right now. Full power unlocks when you arm, as it always has. Most people fly this way anyway, if you don't know which way you fly, this is the way it already works for you. But for those who turn Low Power Mode Off intentionally using the Auto Temperature Control option, right now you need to re-select Auto Temperature Control Off each time you boot. I am working on fixing this sometime this week - this video caught me a bit by surprise and I'd hoped to have it done earlier so I could say "no known bugs" :) * It is very unlikely to be possible to record the OSD into the video directly from the goggles. The V1/V2 FPV Goggles don't have a lot of CPU power available, and software compositing high resolution video is quite CPU and memory bandwidth intensive. However, what we plan to do in the future is to write the OSD data to a file alongside the video (similar to the .srt files DJI uses today), and build a companion application which can "burn" the OSD data into the video on a computer later.
Sweet! I'm excited to try this. I use v1 goggles and an analog module for tinywhoops and the awesome dvr on analog module. Any concerns or changes on analog module usage? Latency? DVR?
couple of years i've been flying dji now, and still, when under any pressure, i struggle to see my voltage and timer, wish i could get mbs more in the center too. great stuff wtf team, this kinda project makes this hobby possible.
@@nigelolympia NP. i thought after update to 0606 mine did a reboot and not auto reconnect to DJI software, so i was able to connect to wtf. i have to delete my upper comment, just not helpful... :-)
Very nice. Works as advertised. The only thing I ran into was having to root twice, both the goggles and the vista. After the first time the configurator couldn't find a device to connect to. Apart from that, I just followed the video, didn't need to go to the github repo for anything. Very polished tools for a v1 root hack. Thank you everyone involved.
@@JoshuaBardwell What I meant was I has to root the goggles twice, and the vista twice, even though the first time said success and Windows said the device was connected the wtf code couldn't connect. After the second time it worked fine.
Fantastic, Joshua! Thanks a lot for the tutorial! 😃 If (IF) DJI was smart, they wouldn't fight this. They would incorporate it! But do you want to bet what's going to happen? Anyway, stay safe there with your family! 🖖😊
So stoked that this is a thing. Been waiting ever since I first heard about the root hack. Personally, I'm not super interested in the osd, but I really hope we see the 60 Mbps plug in at some point. Thanks to everyone involved for their hard work. 🙏🏻
Hey JB, have you ever considered running a fan under the table with duct work tube to the table top? If the fan noise really bothers you, that could be a clever fix.
Patience pays off, once again. I have been waiting on this to pull the trigger on rooting mine. I have v2s -AND- a DJI FPV drone, so I didn't risk it while experimental, and didn't want anything to update and lock me out.
I did it a few weeks ago. It’s seamless but I would advice if you can use a power supply rather than a battery and have a desk fan pointing at the gear while rooting. Also rooting can take a few minutes and during the process you might get a “cannot find device” message, just ignore it and don’t be tempted to start fiddling, the configurator will find the headset after a few seconds.
Thank you JB and the WTF team. Just a side question... if for some reason DJI releases a feature that interests the FPV world in a future release and we decide to apply an official release after rooting... do we just use the Bind and Power step to revert back... or once we are rooted... do we have to stay in the rooted world? Not that I expect DJI would release something worthy of potentially not having what WTF built... but was just wondering.
Just FYI there is still a bug in the OSD code where the vista will go into low power mode regardless of whether the auto temp control is set to off or on in the googles, this is only really a problem if you run your vista with auto temp control off and like it start recording manually, if you run it on you won’t notice any difference. The present solution is to go into the googles menu, select auto temp control and change it to on, then change it to off and the vista will then respect the setting until the next power cycle (yeah you have to do this every time). They are working on it, but it’s only just been discovered so won’t be fixed quickly.
@@REAL_N3W that’s correct, whatever your setting in the googles it’ll arm and unlock as normal once you arm. I personally like to run with auto temp control off because if I get stuck in a tree, I can still get video and turtle out of the tree after I’ve disarmed. If you run with it on when you disarm the vista goes into low power mode and 90% of the time the googles will loose sync from the vista and loose the video signal, which can depending how high you are in the tree or how far away the tree is, can make it difficult to turtle out.
msp-osd got updated to v0.6.5 today and the issue should be fixed. You should update both goggles and air side. Please let us know if the problem still occurs after updating.
For those thinking of doing this, but are dreading the task of having to convert all air units, let me assure you that the assumption is incorrect. You can, in fact, root, install WTFOS and install the MSP OSD package on the goggles and an unrooted air unit will still send its custom OSD. There is one downside in that the WTFOS blinks "Waiting for OSD..." in the bottom right corner. It isn't completely in the way, but would be nice if that didn't happen while Custom OSD was turned on!
Great video thanks Josh for bringing this to us asap. Was wondering if there was any update on being able to record the OSD elements in either google DVR / using the digiview app? That be the real game changer, so sad we cant do this as of now.
Their FAQ states that this would be very difficult because of how the video layers and focus mode work. What you could always do though is creating OSD text from blackbox data and adding that as an overlay in a video editing software. IIRC there are scripts that automate that process that even give you fancy gauges for speed and current. What developers could propably do without too much effort is writing subtitle files onto the internal storage of a Vista, just like the Air Unit does.
Okay so what actually changes when you turned off custom OSD in the goggles? There was like mah, and something ae that went away.... Why were those there in the first place? I guess that's all that confused me. Great vid JB! Also, I wonder if when the update comes to make the v2 goggles work with the O3AU, if they will lock out root or whatever 🤔
What that takes away is the few supporedt OSD elements that DJI supports over MSP, like battery voltage, GPS info and a few others. And it will be shown in DJI goggles font. Custom OSD isn't needed anymore since you have direct access to betaflgiht OSD.
Awesome! This is what fixed wing has always wanted since hd fpv! Live audio and full betaflight/Inav support❤️ Is live audio available for V2 goggles now? I heard they were working on it a while back
Live audio is currently only available for the V1 Goggles, because we re-enabled some dormant audio code DJI had left around. This code is not present on the V2 firmware. For V1s it's actually missing from the configurator currently, but it will return soon. For the V2 Goggles someone would need to write a new audio system from scratch. There were some early experiments but latency was bad. Like half a second bad. So it's a lot of work.
Unable to get this to work.. when attempting to connect to my googles i get "NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface." Anyone else gettng this error? any idea how to fix it?
Interesting but premature, I will wait till it's officially released and watch Madrc's stream on Friday with Joonas before risking my goggles, I can hold out for a couple more days plus by then I may see how many people brick their goggles if any.
Dang you are one lucky man, found a way to make a living doing something that's you like and looks fun. My first drone , was last seen flying northwest ... something failed . Expensive mistake , but lesson learned next venture was smaller but lacked function , by the 4th venture, full functions were realized. Since that time improvements have been made, but the project that has vexed me, has wings, and duct fans , and requires 13 of 16 channels , oh , it's a, YRF-4E. It was an experimental F4b Phantom, with cannards , it lived just up the road at WPAFB. I saw it first in 1967 or 8 , and made a decision to model it. Time with 6 kids , and money for such, well it became a retirement project. For a dozen years I have built and crashed ... went to WPAFB to capture details 2 cameras and lots of memory cards. They lost the plane, along with the staff we looked high and low. Wrote on FB about losing a prototype aircraft, gosh the airforce got mad ...lol . Yea well they didn't drag their wife around the base for hours looking for the plane. In a cranky letter , they explained it was out for paint. Several years went by and it was still out for paint. So I offered to come up and help after all I had some slightly used paint brushes out in the shed ... you know they still have no sense of humor. Now it's status is in storage . My tiny prototype flew across the yard and into the neighbors yard, ... since then every try has met with disaster, exploding fan units , failed servos, burnt wiring ...currently 3 new attempts lay about my work area, but I got old, hand and eyes ... ifvi build it , I don't trust myself to fly it. Well at least thevprototype flew, and is on rc groups ..., it was destroyed when I moved, oh well .
Thanks JB for taking us through this and thanks to the FPV-WTF Team. So far I'm sticking with Digital Font, that is until you tell us the one you prefer.
@@JoshuaBardwell A few people are working on bringing font installation and selection to the configurator. Hopefully some time soon after launch. That'll make it easier to find one you like. But there's another side to this coin, which is the fact that BF doesn't yet support an HD MSP DP grid (unlike iNav and Ardu). This means while we can make the characters smaller on the SD grid, the positioning remains exactly the same. So character spacing grows in a weird way, when the font gets smaller. At one point it starts looking ridiculous. We're talking to the BF devs about solutions.
I forgot to add - todays msp-osd v0.6.3 update brings an optional "fakehd" mode which does funny things to the grid and chops it up. Parts of the screen become dead zones and the rest have a higher resolution grid available. Check it out, details in msp-osd README.
Great video again Mr Bardwell! Have you ever tetsed the DLNA wireless broadcast of the DJI 2 goggles? Cos if the latency is low enough this could allow those of us that love crazy wide FOV to make their own box style goggles with NICE BIG FOV 😁
Hey joshua what should I do when I'm going to put in the cli set displayport_msp_serial = allowed range -1 - 40 when I use uart 1 on my aio should I put -1 then to make this work if I had uart 2 I would have to sat uart 1 but I'm using uart 1 so I'm not fully aware of this I hope for an answer Thank you so much for doing this you're the best greetings from Norway ❤️
Many thanks for answers love people like you who take time for people and help us who have just started with this hobby love you bardwell ❤️ because now I only get font font bin font font bin in dji goggels v2 dkal test and set display port on uart 0 as long as I I have msp on uart 1 Thank you
That is Awesome! Now DJI has to think about what feature they have to give us to exclude us again with the next update. DJI your turn... O3 Air unit with Canvas Mode support? Buy new stuff to get the feature?
Great vid - looking forward to doing this along. Been researching this (since one of my FPV buddies showed off his OSD) and also felt that now it looks really easy to do. The thing holding me off until now was DVR recording. But looks like now it works? greets, Mario
Yes, as noted by @bri3d (comment above), and from Ian's interview of WTF team, just camera video will be recorded in goggles DVR. Goggles hardware does not have power to re-encode video with OSD. One possible future feature is being able to do this re-encoding post-flight on a personal computer. (OSD MSP data would be saved like the DJI SRT is now)
Hey Joshua, I update my DJI V2 to version 0606 (is the correct fimware ) but I can't ROOT my goggles since it gives me an error in step 3. I did the virification that you did in DJI Assistant and everithing that you did but the problem still there. Any help ? Thanks for this great video.
The extra 10 mbps is reserve bandwidth. Using will offer slightly higher quality video, but if transition quality drops (distance, or obstruction) no extra bandwidth will be available for sending redundant packets, or telemetry data. So value of 60 vs 50 mbps will greatly depend on your personal flying situation. It's not all for free.
This was one of the big reasons I chose not to buy from them. Had they simply shown that they cared, I would likely be shelling out another $100-150 per quad just for their video system. Instead, they showed me that it's better to choose small/community driven projects, even if they lack can a few things. Still happy with analog and HDZero.
@@j005u It didn't work :D But if it will at some point then I'll hold up to my promise. This is the one thing I've been missing from DJI ecosystem, easily worth a donation if it starts to work.
I just completed my WTF OSD and I had to complete the Butter update. My goggles are from the DJI FPV kit. Now after completing all the updates and test flights everything worked as it should. Now today 2 days latter I went out to fly and found I had 2 sets of OSD in two different founts. I pulled the SD card out as your Video states that the OSD was on the SD card only. Still with no SD card I have OSD.
Looking forward to rooting my goggles. Will the OSD record on the goggles thou? Much needed for long range flying being able to see my GPS coordinates in the playback
@@JoshuaBardwell thank you. I'm gonna join your patreon. I have been meaning to for so long lol. Keep up the good work mate 👍 The firmware update on the v2 goggles in order to bind to the o3 I meant, does that affect the 1200mw mod? I'm building a supafly sync mode new quad and its fits the o3 beautifully
The firmware update is for the Vista, not the V2 goggles. it makes the Vista compatible with the Goggles 2 and not compatible with the V2 goggles. After that point, the old naco hacks don't work, but the ham_cfg hack that works on Avata and O3 now also works on Vista.
i'm so lost!!! i've been following the whole video! was on the right firmware for my v2, rooted, updated v2 to newst firm wear like you said to do and reinstalled wtfos. but how are you still on 606 after updating??? 8:52 mines saying the new updated version
A few notes from the root process from my experience on V01.00.0608 - close DJI assistant app! If you have it open, it will appear on COM portXX but will not start the root process. - takes about 2-3 minutes total, goggles will reboot several times. There are 5 steps in total, and if you've done it correctly the root text should look like this: 00:02 Attempting Step 1... 00:16 - Found Device: GL150, Version: 01.00.0608 00:16 Step 1 - Success! Rebooting... 00:32 Attempting Step 2... 00:49 Step 2 - Success! Rebooting... 01:05 Attempting Step 3... 01:15 Step 3 - Success! 01:15 Attempting Step 4... 01:20 Step 4 - Success! Rebooting... 01:20 Device went away... 01:20 Device came back... 01:39 Attempting Step 5... 01:41 Device went away... 01:42 Device came back... 01:44 Step 5 - Success! Rebooting... 01:57 All done - your device has been successfully rooted!
