#wooting two lekker not detected by wootility
1 messages · Page 1 of 1 (latest)
Just replug the device. At this state the firmware already got flashed.
already did that and no dice
multiple times
Quick initial questions - Does the keyboard light up and function normally when plugged in?
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 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.
that seems to be the issue
What Wootility version did you use?
4.4.13
Yeah, I noticed it's shown in the screenshot.
gg
Did the web version work?
https://wootility.io/
Remember that you need to allow the device access permission.
Are you on Win?
yes
Please open the device manager and change the view to container. Expand the Wooting node and post a screenshot of that.
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.
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.
hmmm, is this a "normal" or common issue?
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?
ive had my lekker since first wave, cant really remember when i got it
Hmm, have you performed an update before the problem started?
Have you recently performed an update right before the problem occur?
Did the problem occur right after an update?
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
Has the software detected the device?
previously before this issue, yes
oh because when i updated wootility it would no longer detect my keyboard
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.
i dont know why it happened, but thank you so much for the help. i never would have figured that out myself
So if it was working before it should not mess with the device information causing the issue.