Got two "two HE", Wootility bricked both via mandatory update with CRC error - restore fails too.

[empty zealot]

Hi,

I got two keyboards and attached the first one to my PC. It worked well so far.
Then I started up Wootility, which detected the keyboard just fine and stated that we need to upgrade the firmware before we can do anything at all. So I did click the fancy button and off it went.
All fine until it encountered an:

Error ID: Unknown
Error: CRC error. Got 6625933 but should be 2860372
CRC error. Got 6625933 but should be 2860372

(Yes, the error is stated twice in the UI).

I also tried to restore with the Desktop Version (App Image, 5.2.5), tried different USB Ports and Cables and finally I tried it with the second keyboard. Guess what? It wanted to upgrade too. Curiously I did and boom, I got myself the second brick.

See attached the log from Wootility Desktop of two unsuccessful restores.
I found the following GitHub issue, which seems to be at least closely related https://github.com/WootingKb/wootility-issues/issues/315

Anyone got the same or at least has a clue?

[young edge]

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update 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!

Do you need to...

• Cancel an order?
• Return/Refund an order?
• Get assistance with placing an order?
• Change the items in your order?
• Change your shipping address to a different country?
• Return a recent purchase?
• Get warranty support?

All of these types of requests need to be made via the Wooting Support Wizard!

[rose plover]

Is the keyboard plugged directly into the motherboard?

[empty zealot]

Yes, it is. Also tried different ports, 3.2, 3.1.

I only could not try on a different PC as I don't have any at hand right now.

[woeful orbit]

could you try 3 more restores and provide the main.log again

• i noitced in the main.log all the CRC codes are the same witch is strange

Regarding the ports i recommend to try port further away from tthe current locaiton in the event the 2 ports you tried share the same "USB-Controller"

.

for reference below is a part of the saved response i made for CRC errors (some steps can be skiped as already done)

---

To start, this error can be caused by the information being sent from the computer not being received correctly.
For example:

• System sends: Hello World
• Keyboard receives: He000aW12hD

Since this can relate to any point where data is transferred between the system and the keyboard, the issue can be caused by several factors (system, USB controller, USB port, USB-C cable, keyboard USB port, etc). Below are some troubleshooting steps that can help narrow this down and see if we can get the keyboard working again

---

Troubleshooting

Try another USB port on the system
We recommend trying a different USB port located further away from the current location, preferably colour-coded differently, to ensure that the keyboard is not connected to the same USB controller.

Try a different USB-C cable
In the situation that the USB-C cable is faulty, try another USB-C cable.

Inspecting the keyboard USB-C port
This is to check for anything out of the ordinary in the port that could be causing issues (hair, debris, bent pins, etc)

Because the port is very small, it may be difficult to see inside, so we recommend checking in a brightly lit room or shining a light into the port

**
Try another Computer**
If the steps above don't resolve the problem, try performing a restore on another device and see if this is limited to the current computer.

[empty zealot]

I tried with the front USB Port again and that worked now. Seems there is something wrong with ALL ports on the back when flashing.
However, I can plug it in the back now and it's working flawless. Unsure how I could provide you with anything else which could help to pin point the issue.

Same Cable, Same System

[prisma bone]

cpu and motherboard model numbers could help