#wooting two lekker not detected by wootility

1 messages · Page 1 of 1 (latest)

warm chasm
#

Title says it all. I already tried swapping usb ports restarting and hard resetting my keyboard.

cloud lake
#

Just replug the device. At this state the firmware already got flashed.

warm chasm
#

multiple times

twilit sparrow
#

Quick initial questions - Does the keyboard light up and function normally when plugged in?

warm chasm
#

yes, the lights work and basic keyboard functionality works. im typing with it now

twilit sparrow
#

Alright - Well that's good at least. Then I'll let Rocky do their thing. Master at figuring out why devices won't talk to Wootility 😄

warm chasm
#

hahaha thanks

#

well i swapped to a usb 2.0 port and still no luck

cloud lake
#

@warm chasm So what exactly is the problem? So far I assume the only problem is that the Wootility can't communicating with the device in the normal operation mode and it only can in restore mode.

warm chasm
#

that seems to be the issue

cloud lake
#

What Wootility version did you use?

warm chasm
#

4.4.13

cloud lake
#

Yeah, I noticed it's shown in the screenshot.

warm chasm
#

gg

cloud lake
#

Remember that you need to allow the device access permission.

warm chasm
#

havnt tried it, but ill give it a shot

cloud lake
#

Are you on Win?

warm chasm
#

yes

cloud lake
#

Please open the device manager and change the view to container. Expand the Wooting node and post a screenshot of that.

warm chasm
cloud lake
#

Ok, right click on the USB Composite Device entry and uninstall it. Everything must then be gone for that node. Then replug the device and try again.

warm chasm
#

there we go!

cloud lake
#

Can't tell what happened but it looked that somehow the device information for a specific part went bad preventing processes to access its interface.

warm chasm
#

hmmm, is this a "normal" or common issue?

cloud lake
#

No, saw it the first time now for newer boards. It was somehow common back in the days when the Wooting One came out.

#

Back then Win got easily confused with the drivers causing weird issues.

#

How long do you have the Wooting?

warm chasm
#

ive had my lekker since first wave, cant really remember when i got it

cloud lake
#

Hmm, have you performed an update before the problem started?

warm chasm
#

i think ive got number 97

#

yeah every update since i got it

cloud lake
#

Have you recently performed an update right before the problem occur?

#

Did the problem occur right after an update?

warm chasm
#

i havnt updated in a while, i just launched the software to check if there was one

#

oh wait, i did update wootility

#

just not the keeb

cloud lake
#

Has the software detected the device?

warm chasm
#

previously before this issue, yes

cloud lake
#

What happened then?

#

Why do you performed a restoring?

warm chasm
#

oh because when i updated wootility it would no longer detect my keyboard

cloud lake
#

Hmm, weird... Updating the Wootility don't mess with the drivers. So the Wootility should still detect the device. In the case the firmware is to old the Wootility may forced you to update but it still ask for permission to do that.

warm chasm
#

i dont know why it happened, but thank you so much for the help. i never would have figured that out myself

cloud lake
#

So if it was working before it should not mess with the device information causing the issue.