raven fractal
Problem: When going through the Troubleshoot flow for a Wooting 60 HE, the process stays stuck on "Waiting for device to be connected". As a result, the device stays in Restore mode and is unusable.
Background: Over a span of 24 hours, the device started showing signs of undervoltage (random characters), and none of the Wooting-suggested solutions to troubleshoot worked, but during my attempts to fix it the keyboard stopped working altogether so I entered the Restore mode.
Specifics: Debug info from Wootility:
OS: Linux
Device: None connected```
Relevant `lsusb` output: `Bus 003 Device 005: ID 31e3:131f Wooting Wooting Restore`
**I have already tried:**
- Searched this channel for answers ✅
- Wrote social@wooting.io (it's the holidays) 🎄
- Disconnect all Razer peripherals and uninstall all Razer software (in my case I purged `openrazer` and `polychromatic`, and switched to a different mouse) ✅
- Try on a different computer (I tried on a windows laptop with both web-based and binary Wootility and the process stopped at the same stage) ✅
- Reboot the computer ✅
- Make sure `udev` permissions are correct (they were already set using the recommended vanilla settings per Wooting's website) ✅
**I have not tried:**
- Running Wootility as root (can't really be done easily on AppImages and is not safe anyway) ❌
**Supporting info:**
Tail of debug log:
```[2023-12-26 14:21:02.109] [debug] Searching for devices
[2023-12-26 14:21:02.110] [debug] Giving permissions for device {
deviceType: 'hid',
origin: 'file://',
device: {
name: 'Wooting Wooting Restore',
productId: 4895,
serialNumber: 'FIABAADXDEFF',
vendorId: 12771
}
}
[2023-12-26 14:21:02.111] [debug] Giving permissions for device {
deviceType: 'hid',
origin: 'file://',
device: {
name: 'Wooting Wooting Restore',
productId: 4895,
serialNumber: 'FIABAADXDEFF',
vendorId: 12771
}
}```
undone crag
granite moth