fpv-wtf / wtfos-configurator

Configurator for wtfos, with built in margerine
GNU Affero General Public License v3.0
42 stars 16 forks source link

gogglesV2 GP150 Rooting #293

Closed notgohobo closed 1 year ago

notgohobo commented 1 year ago

fresh goggles 01.02.00.60

used butter to downgrade assistant says no firmware change try to root via site. error message Aborted! Device did not reboot in time, please power cycle and try again.

tried booting up in HD mode has 606 FW. connect to dji assistant says downgrade to 01.00.0607, do so retry rooting, same error

try butter again try rooting, same error Aborted! Device did not reboot in time

any advice would be helpful. Kind Regards, Notgohobo.

DJI Assistant flash 10  1 00 0606 rooting aborted

stylesuxx commented 1 year ago

You need to be in DIY mode.

notgohobo commented 1 year ago

thank you for your reply

Is this DIY Mode?

1678044579319 1678044579389 1678044579397

stylesuxx commented 1 year ago

Yes, this looks fine.

notgohobo commented 1 year ago

ok Tried rooting again

00:01 Attempting Step 1...

00:33 - Found Device: GP150, Version: 01.00.0607

00:33 Step 1 - Success! Rebooting...

01:35 Aborted! Device did not reboot in time, please power cycle and try again.

regards, Notgohobo.

stylesuxx commented 1 year ago

Can you hear the goggle actually rebooting? Can you please post output of chrome://device-log/ after the rooting process (please clear before connecting the goggles)

notgohobo commented 1 year ago

Ok log2

Yes can hear the goggles reboot. Device Log2.zip

stylesuxx commented 1 year ago

The error relating to SetupDiGetDeviceProperty is very suspicious - which version of windows are you on?

notgohobo commented 1 year ago

8.1

stylesuxx commented 1 year ago

Yeah, you should not be using this anymore. Win 8 is EOL since beginning of this year. I would recommend you try on a different - more up to date - machine.

You could also try what people did here (manually unplug): https://github.com/fpv-wtf/wtfos-configurator/issues/212

notgohobo commented 1 year ago

Alright I will try an updated machine. Thank you

famousamos793 commented 1 year ago

Hello, I am getting this exact same issue running Windows 10 Home...

stylesuxx commented 1 year ago

@notgohobo - any update on this? Otherwise I will close this issue.

@famousamos793 - please open your own issue and provide all needed information. Basically the same things I asked from @notgohobo.

famousamos793 commented 1 year ago

Hello and good afternoon! Thank you for following up! My issue was fixed after simply restarting windows, and trying everything all over again.

I think a windows restart might be required for some machines after the driver install.

stylesuxx commented 1 year ago

Closed due to inactivity