cancel
Showing results for 
Search instead for 
Did you mean: 

Rog Azoth Keyboard m701 2.4ghz wireless not working

Kuknissen
Level 8

My Rog azoth keyboard suddenly stopped working in wireless mode after i charged it. Everything was working fine before that. But now it dissapears form Armory Crate when i switch to 2.4ghz. Ive tried updating it, and switching over to wireless with and without the cable attached. Ive tried multiple USB ports.

1,746 Views
1 ACCEPTED SOLUTION

Accepted Solutions

Kuknissen
Level 8

Updating to the new drivers 4.1.0.13 that suddenly popped up fixed the issue 🙂

View solution in original post

9 REPLIES 9

Nate152
Moderator

Hello Kuknissen

Try resetting your ROG Azoth by pressing and holding the Fn + Esc keys for 10-15 seconds.

You'll have updates in Armoury Crate after the reset, try the updates and see if your keyboard is working in 2.4GHz wireless mode.

 

 

 

This did not make a difference. Still same problem unfortunately.

Nate152
Moderator

Sorry to hear that didn't help.

It sounds like there could be an issue with the battery, in which case, I'll have you contact ASUS Technical Support for further assistance.

ASUS Technical Support phone number (Norway)  +47 2350 2550 (Mon-Fri 09:00 - 17:00)

Let me know how you make out.

 

 

 

 

 

I dont think so, cause it lights up and the oled screen works. But no input gets to the PC. 

Nate152
Moderator

Ok, if it lights up with the cable disconnected, the battery should be fine.  

Try uninstalling all HID Keyboard Device and ROG Azoth from device manager then reboot.

After this, do the updates in Armoury Crate and see if 2.4GHz wireless mode is working.

device.png

 

There was no updates in Armoury crate, but uninstalling those devices did not work either.

Kuknissen
Level 8

I tried it on my ROG Ally now aswell. The 2.4ghz doesnt work there either, but it works fine wired or with BT. And it was working fine on 2.4ghz until i needed to charge it the first time. After that it has been malfunctioning in 2.4ghz.

Kuknissen
Level 8

Updating to the new drivers 4.1.0.13 that suddenly popped up fixed the issue 🙂

Nate152
Moderator