[Apple Silicon] Keyboard unusable after failed remap

[pashkes]

Version

0.7.2

Operating System

MacOS 13.5
but it doesn't work for everyone

Description

I instaled the app on my mac m1 and try to set up key, after save I get an error that the shortcut can't save and now my keyboard don't connect to any device, light is not on, reset (fn, tab, r) can't be helped
I also try to connect via a console on Win but device didn't detect

When I try to update firmware I always see text waiting and nothing happen 😭

[donn]

Air or Halo? Also, can you send a photograph of the metal plaque on the back of the keyboard

Also, try the Windows firmware updater (if applicable) - Mac one never worked for me.

This is serious- if the software is somehow corrupting the bootloader then something is going horribly wrong

[pashkes]

Air or Halo? Also, can you send a photograph of the metal plaque on the back of the keyboard

Also, try the Windows firmware updater (if applicable) - Mac one never worked for me.

This is serious- if the software is somehow corrupting the bootloader then something is going horribly wrong

Air. I tryed to update on Windows

[donn]

That does match mine... welp.

The last thing I can ask you to try is https://github.com/carlossless/sinowealth-kb-tool. If you can download the Windows version and it can recognize your keyboard, I can send you a firmware dump from my own keyboard so you can try to flash and fix it.

For now, I'll add an advisory for M1 Macs to the Readme. Sorry about this

[pashkes]

That does match mine... welp.

The last thing I can ask you to try is https://github.com/carlossless/sinowealth-kb-tool. If you can download the Windows version and it can recognize your keyboard, I can send you a firmware dump from my own keyboard so you can try to flash and fix it.

For now, I'll add an advisory for M1 Macs to the Readme. Sorry about this

I'm trying to start the tool on Windows under admin with connected the keyboard but nothing happen. Any dialogs don't bubble. Maybe I do something wrong or should try macOs version?

[donn]

@pashkes It's a CLI tool: I'll give you some instructions in a moment

[donn]

1. Download and decompress sinowealth-kb-tool-x86_64-pc-windows-msvc-v0.0.2.tar.gz. There should be exactly one file, called sinowealth-kb-tool.exe.
2. Shift + right click the Windows button in your task bar, and press "Windows Powershell (Administrator)"
3. Navigate to the folder containing sinowealth-kb-tool.exe using cd.
4. Execute this command: .\sinowealth-kb-tool.exe -r --part nuphy-air75 out.ihex

Report back with a screenshot of your full window.

[pashkes]

1. Download and decompress sinowealth-kb-tool-x86_64-pc-windows-msvc-v0.0.2.tar.gz. There should be exactly one file, called sinowealth-kb-tool.exe.
2. Shift + right click the Windows button in your task bar, and press "Windows Powershell (Administrator)"
3. Navigate to the folder containing sinowealth-kb-tool.exe using cd.
4. Execute this command: .\sinowealth-kb-tool.exe -r --part nuphy-air75 out.ihex

Report back with a screenshot of your full window.

Looks like the tool doesn't support air 75

[donn]

Try nuphy-air60, I got the Air75 support merged but it's not in a release version yet and it's just a copy of Air60's data anyway

Also, while you're there, I'd like you to run .\sinowealth-kb-tool.exe -r --part nuphy-air60 bootloader.ihex as well.

[pashkes]

Try nuphy-air60, I got the Air75 support merged but it's not in a release version yet and it's just a copy of Air60's data anyway

Also, while you're there, I'd like you to run .\sinowealth-kb-tool.exe -r --part nuphy-air60 bootloader.ihex as well.

 No KB found. Trying bootloader directly...
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src\isp.rs:60:93
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[donn]

Assuming this isn't a permissions issue, that means the firmware flasher cannot find either the keyboard or the bootloader. Can you check device manager to see what pops up when the keyboard is plugged in? Also, can you try a different USB-C cable?

[pashkes]

when connect to another port I saw the error, it's means that unknown device

Windows stopped this device because it reported problems. (Code 43)

Request for USB device descriptor failed.