-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vista Rooted but site crashes when I try to connect to install WTFOS #230
Comments
Could you please try the develop build: https://develop.fpv.wtf |
Hi, thanks for replying and your. I was able to install WTFOS and the packages using the develop build, but I do not have OSD in the googles. No WTFOS and no Custom DJI OSD. Do I have to update my goggles with the develop build of the WTFOS as well in order for everything to connect? I made sure that everything is enabled in Betaflight. UPDATE I now also went ahead and uninstalled WTFOS from the Vista using the develop build. The plan was to then remove the Root using the CLI, unfortunately I cannot establish a connection and receive the following message - 'Could not connect to device, make sure that adb server is not running on your machine (adb kill-server) and that you are not connected in another tab/window. When I try to re-root the Vista now, I receive the following message 'The signing server could not be reached. It might be down or your ISP might be blocking it.' UPDATE 2 I managed to recover my vista using the recovery bind button method, connecting to the DJI Assistant and re-installing firmware V01.00.0606. I went back and to the WTFOS configurator, and was able to access the CLI. I ran the command to remove the root hack, and even though it said that it was successful, upon returning to the configurator, it seemed like the Vista was still rooted, which is very confusing. I ran the root again just for good measure (in the development configurator) and installed WTFOS. Everything went well but I don't get OSD or DJ custom OSD in my goggles. I removed WTFOS again and did a recover once more using the DJI Assistant. My DJI Custom OSD is back. I have no idea why this Vista is being so difficult. Apologies in advance for the essay, but I just wanted to describe the process that I have been through and where I currently stand. |
Please try using Butter to downgrade to a clean state: https://github.com/fpv-wtf/butter |
Thanks, I'll give that a try, hopefully it resolves the issue. |
Any update on this? |
Apologies but I haven't had the time to tend to it this week. I'm hoping to get to it next week, I'll leave an update when I do. |
I just had some time finally to sit down and go over the whole Butter process. So my Vista on this particular quad is currently on version 01.00.0606 (and it's working fine, it roots fine, it just refuses to install and run WTFOS properly). The recovery file says that it's for version 01.00.0608, which would mean that I would be required to upgrade all of my drones to that version of the firmware, which is something that I don't want to do right now. Is there a way for Butter to do a recovery to version 01.00.0606? |
I don't really think that there should be an issue between those two versions, I mean, no need to upgrade everything. |
Awesome, everything is updated and working as it should. Butter is pretty awesome! Thanks for all of your help and everything that you do for the FPV community 😎👍 |
Hello,
I rooted a Vista, but when I try to re-connect to install WTFOS, or to get into the CLI, or any type of connection besides a root, the fpc.wtf website crashes (I click connect, choose the Vista in the com port pop-up menu, connect again, and then crash). I tried re-rooting another three times, and it does so successfully every time, but I can't successfully connect to the Vista to do anything else after that.
I rooted another Vista successfully this very evening, but I'm having trouble with the second one. I tried two different browsers on two different PCs just to make sure. I did some searching to see if anyone else came across this issue, but I didn't find any answers. Any help would be greatly appreciated, thank you kindly.
The text was updated successfully, but these errors were encountered: