wooting2 not working after restore | Wooting | Page 1

lament parrot Aug 3, 2023, 11:25 AM

#

After having some repeating problems with random keys not working for a while and then suddenly working again I had that issue again today with the spacebar and decided to restore again.

So I put the keyboard in restore Mode but accidentally used the old wootility first and after flashing it didn't reconnect.

I put it in restore again, flashed with the new wootility (4.5.5) and again, it flashed but does not reconnect or power on.

It does appear as wooting recovery device before flashing but afterwards only as this

Some help ASAP would be appreciated!

scenic quarryBOT Aug 3, 2023, 11:25 AM

#

Thanks for posting your support request!

Please note, the support center is only for community-based support with technical troubleshooting and general questions.

For official Wooting Customer Support, please use the Contact Us button on the Wooting Hub or email your request to social@wooting.io
note: use the email address associated with your order for fastest resolution

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, change/confirm your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it On Hold via the Wooting Hub!
https://hub.wooting.io/login

lament parrot Aug 3, 2023, 11:27 AM

#

Also tried to uninstall that device and rescan for new hardware but it comes up as the same

plain skiff Aug 3, 2023, 11:50 AM

#

Wooting Two - Not HE right?

lament parrot Aug 3, 2023, 12:19 PM

#

Correct

plain skiff Aug 3, 2023, 12:20 PM

#

Hmm... I know that trying to use old Wootility is bad. But I don't know if you can actually outright brick a board by doing so. @hard moon

lament parrot Aug 3, 2023, 12:26 PM

#

it certainly wasn't intentional or give any warnings

lofty prawn Aug 3, 2023, 12:34 PM

#

Have you tried the restoring process again?

lament parrot Aug 3, 2023, 12:35 PM

#

yes maybe three times, even once with ansi instead of iso

lofty prawn Aug 3, 2023, 12:40 PM

#

Hmm, it should not be a general issue. I was able to update my W1 and W2 just fine.

plain skiff Aug 3, 2023, 12:40 PM

#

To V4 and back to V3?

#

I don't have my Wootup W1 to sacrifice. It's been packed 😦

lament parrot Aug 3, 2023, 12:41 PM

#

What's weird to me is that it seems to be able to get back into restore Mode so it's not completely dead or bricked, it just does not want to do anything after flashing

lofty prawn Aug 3, 2023, 12:42 PM

#

lament parrot What's weird to me is that it seems to be able to get back into restore Mode so ...

The purpose of the restore mode is to recover from a bad state.

lofty prawn Aug 3, 2023, 12:42 PM

#

plain skiff To V4 and back to V3?

That should not cause this as far as I know. The device would lose it's serial number and so on.

lament parrot Aug 3, 2023, 12:43 PM

#

Which it most definitely is in

lofty prawn Aug 3, 2023, 12:43 PM

#

lament parrot Which it most definitely is in

What?

lament parrot Aug 3, 2023, 12:43 PM

#

A bad state

lofty prawn Aug 3, 2023, 12:43 PM

#

Please try it on another PC.

lament parrot Aug 3, 2023, 12:44 PM

#

I have connected to work PC but I can't install the wootility there

plain skiff Aug 3, 2023, 12:44 PM

#

lofty prawn That should not cause this as far as I know. The device would lose it's serial n...

You have infinitely more experience with this issue than me. I just remember reading that clear warning on the update that you should never try to plug a Flaretech board updated to V4 back into the V3. I don't know how bad it is in practice. And can't try it myself.

Hopefully you can figure it out 🙂

lofty prawn Aug 3, 2023, 12:45 PM

#

plain skiff You have infinitely more experience with this issue than me. I just remember rea...

Back then I have done it. 🙂
The device itself was working fine.

lofty prawn Aug 3, 2023, 12:46 PM

#

lament parrot I have connected to work PC but I can't install the wootility there

Is there the same issue in the device manager shown?

lament parrot Aug 3, 2023, 12:46 PM

#

Same error on work pc

lofty prawn Aug 3, 2023, 12:46 PM

#

If you are allowed to you can also use the web version of the Wootility on a Chromium based browser.

lament parrot Aug 3, 2023, 12:46 PM

#

Will that work without admin?

lofty prawn Aug 3, 2023, 12:47 PM

#

lament parrot Will that work without admin?

It should yes, same for the desktop version.

#

https://wootility.io/

Wootility Web

Instantly edit your Wooting keyboard profiles and colors from the browser.

lament parrot Aug 3, 2023, 12:48 PM

#

So put it in recovery and try flashing with web wootility?

lofty prawn Aug 3, 2023, 12:49 PM

#

lament parrot So put it in recovery and try flashing with web wootility?

Yes... But the restoring.

lament parrot Aug 3, 2023, 12:49 PM

#

Correct?

lofty prawn Aug 3, 2023, 12:50 PM

#

Yes, if you have the ISO version.

lament parrot Aug 3, 2023, 12:53 PM

#

same issue, only that the browser asks permission to connect to the device, works the first time for wooting restore, second time (after flashing) it doesn't find any device

#

lofty prawn Aug 3, 2023, 12:54 PM

#

lament parrot same issue, only that the browser asks permission to connect to the device, work...

The restore mode is a different mode where you need to allow the permission again.

lament parrot Aug 3, 2023, 12:55 PM

#

which i did when it let me the first time, but as you can see it doesn't find it again after flashing and in device manager it shows up like above

lofty prawn Aug 3, 2023, 12:56 PM

#

Hmm, the shown error message on the device node in the device manager is new to me. Searching the web wasn't that helpful either.
It looks to me that this is maybe driver related. But then it should be fine on another system.

lofty prawn Aug 3, 2023, 12:58 PM

#

lament parrot which i did when it let me the first time, but as you can see it doesn't find it...

Can you provide a Registry dump of the following keys?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\

#

Then I can see how the system has detected all you USB devices which may gives me a clue.

lament parrot Aug 3, 2023, 1:04 PM

#

heres the wootility log for starters, registry will take a moment

📎 main.log

lofty prawn Aug 3, 2023, 1:08 PM

#

The other log file is more interesting.

lament parrot Aug 3, 2023, 1:09 PM

#

renderer?

#

or reg

#

📎 usb.txt 📎 hid.txt 📎 renderer.log

lofty prawn Aug 3, 2023, 1:16 PM

#

lament parrot renderer?

There are only two log files, so the renderer is more interesting than the main.

lament parrot Aug 3, 2023, 1:17 PM

#

i just didn't know if you meant renderer or registry with "logs" - but its all in the post above now

lofty prawn Aug 3, 2023, 1:18 PM

#

How did you created the Registry dump? I would expect an export but it seems you somehow copied the text.

lament parrot Aug 3, 2023, 1:18 PM

#

i exported as txt rather than reg so its easier to read in discord

lofty prawn Aug 3, 2023, 1:19 PM

#

I'm more used to the reg file. 🙂

lament parrot Aug 3, 2023, 1:19 PM

#

can do that too, hang on

#

📎 hid.reg 📎 usb.reg

lofty prawn Aug 3, 2023, 1:39 PM

#

So you tried the restoring on two different system right?

lament parrot Aug 3, 2023, 1:40 PM

#

yes

#

fatclient on my pc, webclient on work pc

#

in both cases it just seems to stop the process at the point after flashing when it should normally reconnect

lofty prawn Aug 3, 2023, 1:51 PM

#

After the firmware is transferred the device restarts and should start in the normal mode. When the host has enumerated the device the LEDs should went on.
It seems there is an issue for you which prevent the host to enumerate the device. So the device is registered as a faulty USB device with a vendor ID of zero. Please cross check this by opening the properties of the node in the device manager, go to the tab details and check the value for the device instance path.

#

In the Registry dumb I can see multiple bad device with different error messages. Not sure if these belong to the Wooting or not.

Unknown USB Device (Device Descriptor Request Failed)```

#

Would be nice if you can unplug the Wooting and uninstall all the disconnected devices in the device manger.
If you want you can use this script I wrote.

📎 Delete_Everything_Disconnected.bat

lament parrot Aug 3, 2023, 1:55 PM

#

device instance path includes "woot_003" among other stuff

#

if you need the complete one i can take a screenshot

lofty prawn Aug 3, 2023, 1:56 PM

#

The goal is to get rid all the bad device and to connect the Wooting again to see what the error message is for it.

lament parrot Aug 3, 2023, 1:56 PM

#

its a bit of a faff because on my normal pc i can currently only use screenkeyboard...

#

let me try that script then, do i run that as a bat file?

#

oh nevermind its already a bat...

lofty prawn Aug 3, 2023, 1:57 PM

#

By the way, is the device directly connected the host by a port of the I/O panel of the mainboard?

lament parrot Aug 3, 2023, 1:58 PM

#

its been connected to a KVM switch as well a usb hub as well as to the mainboard directly

#

under normal circumstances it would be connected to a kvm switch

lofty prawn Aug 3, 2023, 1:58 PM

#

No 🙂 That can't true, it can't be connected to all tree the same time.

lament parrot Aug 3, 2023, 1:59 PM

#

no not at the same time, but i've tried all those variants

lofty prawn Aug 3, 2023, 1:59 PM

#

Please connect it directly to the host on a USB port of the I/O panel of the mainboard on the back.

lament parrot Aug 3, 2023, 1:59 PM

#

it currently is

lofty prawn Aug 3, 2023, 1:59 PM

#

Also, please reboot the PC. Not just a shutdown and start. Just in case to free up any potential OS issue.

lament parrot Aug 3, 2023, 2:00 PM

#

sure but as its happening on multiple PCs i don't see the fault at the PCs end but i'll reboot to check that off the list

lofty prawn Aug 3, 2023, 2:00 PM

#

So after uninstalling all unconnected device nodes there should be only one device left in the Registry which has a vendor ID of zero.

#

So can you please provide another Reg dumb of the USB key. After the Wooting was connected again.

lofty prawn Aug 3, 2023, 2:01 PM

#

lament parrot sure but as its happening on multiple PCs i don't see the fault at the PCs end b...

I know... That's why I added just in case. 🙂

lament parrot Aug 3, 2023, 2:02 PM

#

give me a moment, starting up again now

#

i ran the script, do you want both usb and hid reg files again?

#

also there is a whole lot of VID_03EB etc entries still

#

but only two USB that are only 0000

lofty prawn Aug 3, 2023, 2:09 PM

#

The VID 0x03EB with the PID 0x2403 should be the restore mode of the W2. Because a firmware update likely can't change that.
The new normal mode should be on VID 0x31E3 and PID 0x120x (where x is between 0 and 2 depending on the analog mode).

lofty prawn Aug 3, 2023, 2:10 PM

#

lament parrot give me a moment, starting up again now

As mentioned only the USB key.

lament parrot Aug 3, 2023, 2:11 PM

#

so currently the keyboard is connected but not in restore mode after "purging" with your script, do you want me to put that in restore mode or disconnect or leave it connected "normally" before exporting?

lofty prawn Aug 3, 2023, 2:12 PM

#

Please let it in the normal mode.

#

We know that the restore mode is working, otherwise you wouldn't be able to perform a restoring.

lament parrot Aug 3, 2023, 2:12 PM

#

📎 usb.reg

lofty prawn Aug 3, 2023, 2:14 PM

#

~~What happened when the issue started? I guess you tried an update, or?~~
Never mind, it's in the first post.

lament parrot Aug 3, 2023, 2:15 PM

#

🙂

#

also i've already got a support ticket open for that particular "key stops working" problem but they haven't gotten back to me after the first couple of basic attempts... but that was more of an inconvenience rather than catastrophic failure

lofty prawn Aug 3, 2023, 2:16 PM

#

So maybe the issue is due to the restoring on the old Wootility.

#

Need to test that again...

lament parrot Aug 3, 2023, 2:20 PM

#

how do you mean?

lofty prawn Aug 3, 2023, 2:22 PM

#

I need to do some tests.

#

So I updated W2 to the newer firmware on Wootility Lekker and restored it back to the old one (Non-Lekker) and then updated it to the new again. It was detected by the system without issues but the profile data got corrupted.
After a restoring on the newer Lekker the profile data seems fine. I don't have switches installed so the keyboard freaks out by phantom inputs but the host has no issues detecting the device.

#

So please perform a restoring on the old Wootility. Please do it twice to also reset any data.

#

Check if the keyboard is detected again.

lament parrot Aug 3, 2023, 2:49 PM

#

i don't have it installed anymore, do you know if the installer is anywhere on discord? its not on the wooting.io website as far as i can tell

lofty prawn Aug 3, 2023, 2:51 PM

#

https://s3.eu-west-2.amazonaws.com/wooting-update/wootility-win-latest/wootility+Setup+3.6.16.exe

lament parrot Aug 3, 2023, 2:51 PM

#

thank you

#

https://tenor.com/view/good-news-gif-20210278

#

so... in theory good news in sofar as it is working again, but the spacebar key is still broken

#

now currently the keyboard is still running the old firmware, would you recommend updating to the new one again?

lofty prawn Aug 3, 2023, 3:26 PM

#

lament parrot now currently the keyboard is still running the old firmware, would you recommen...

You should reset the data first. There is the potential that it don't work again after updating.

#

But I think it's worth trying.

lofty prawn Aug 3, 2023, 3:27 PM

#

lament parrot so... in theory good news in sofar as it is working again, but the spacebar key ...

So what exactly is the issue with it?

lament parrot Aug 3, 2023, 6:37 PM

#

lofty prawn So what exactly is the issue with it?

seems like it fixed itself once more - until some other key stops working i guess - basically what happened was that initially the "H" key stopped working, then at some point it started to work again but instead the "K" key stopped working, then it was the "," key and this last one was the space bar (all over a period of several weeks) - and i just can't put my finger on it, obviously its not a hardware issue with the key itself, i've even replaced the switch on one of them with a spare one i had from the kickstarter (had two sets of switches)

#

so i'm guessing its just something very weird going on with the board but i don't know

#

i think for the moment i'll operate under "don't fuck with it" guidelines and just leave it at the old but at least working firmware 😄

and thanks for your help again Rocky, you saved my bacon

lofty prawn Aug 3, 2023, 6:45 PM

#

The older Flaretech keyboard work by reflectring infrared light. So if the sensor or emitter is covered by dusk or dirt it can cause issues. Like a hair can even cause phantom inputs.

#wooting2 not working after restore