-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flashing firmware from Mac #467
Comments
Seems like I'm not alone: #459 (comment) Probably going to have to return the device as well 😞 |
Hi there, This is not a keyboard limitation as far as we know. Is there another PC you can try mounting the drive on? |
There is another Mac that I can try to use? But I'd expect the same behavior. |
I guess may as well try |
How did it go with the other computer? |
I don’t have usual access to it. It’ll be about a week or so.
…On Wed, May 8, 2024 at 08:46 Kinesis Keyboards ***@***.***> wrote:
How did it go with the other computer?
—
Reply to this email directly, view it on GitHub
<#467 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALSCCLG6PMM4Q7H6NBAMEETZBJCHFAVCNFSM6AAAAABHKA6PCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQHA4DCMJUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Great. If it doesn't work on the other computer we are happy to do an exchange (link below). Nut it seems unlikely (although certainly not impossible) that this is a keyboard hardware problem. |
Just following up on this @goDawgs18 did flashing it from the other computer rectify the issue? |
Hi,
I have:
However now I'm stuck because I cannot copy over the firmware into the directory because it is in read-only mode (or something).
When I look at the info for the directory it is marked as "You can only read". So as I mentioned I am unable to cannot copy the firmware over.
During my investigation I have even found a reddit post documenting my same issue: https://www.reddit.com/r/kinesisadvantage/comments/15osdmq/i_am_unable_to_flash_firmware_on_the_360_pro_due/
The text was updated successfully, but these errors were encountered: