cancel
Showing results for 
Search instead for 
Did you mean: 

ROG Spatha's cursor not moving

ufoozgur
Level 7
Hi there, I had some issues with my Spatha previously. Seemed like the mouse was stucking but I fixed it by removing the battery and plugging it again. This time the mice works but only the buttons. Seems like the sensor stopped working and I can't be able to downgrade the firmware or resetting the firmware. Please give me a solution.
1,121 Views
14 REPLIES 14

I have almost the same problem and the mouse does not work I do not know what to do and I did not do anything just update, someone who can help me urgently, here is the link of my error and every time it is worse I have to end up leaving the default so that it is repaired sometimes and now the profile two try to change the DPS with the button and the application closes and the light of the DPS button does not turn on

https://rog.asus.com/forum/showthread.php?104756-ROG-Spatha-problems&highlight=Spatha

DazzXP
Level 7
I had issues with the polling rate going to 0 sensitivity going to 0 as such the mouse wouldn't move and the LED's turn sold white, as a work around i gone into the ROG armory and reset them back to default on my laptop since i can use the track pad or use my old Logitech G600 on my computer. However even doing that the cursor just wasn't accurate anymore. I did loads of searches and seemed to have missed this one every time in till today. I also found out at long last how to perform a factory reset of this mouse which works also.... intill you load up the armory then it screws everything up!

Factory reset of the mouse,
1# disconnect mouse
2# press and hold left mouse button, press and hold middle mouse button (scroll wheel) then press and hold right mouse button, with all 3 hold down wait 10 seconds
3# with buttons pressed down insert the USB cable and keep holding them down
4# after 10 seconds release buttons, there will be no lights on the mouse any longer but will resolve all the issues.

Now loading up the armory seems to perform an upgrade from the factory reset 1.09 firmware back to 1.69, once thats done it's screws the mouse up again and you end up back to the same situation with the mouse cursor being inaccurate.

So after factory reset uninstall the armory II and install armory 1 from here: http://dlcdnet.asus.com/pub/ASUS/mb/accessory/ROG_Spatha/ROG_Armoury_v10134.zip?_ga=2.139863795.1540...

Now they ask you to default the mouse but although it detected it as the spartha it will say connect ROG device, so perform the update to the latest version. After which it should be fine once the firmware is flashed the sensitivity is increased and the inaccurate issue is then also resolved.

Apparently from the thread posted above: https://rog.asus.com/forum/showthread.php?102305-Please-read-before-posting-any-new-Spatha-threads

the issue is caused by the profile being corrupted, hence why the factory reset clears it but then if using the same ROG armory software it copies the corrupted file back.

Now the issue appears to be related to when the dock is connected and the mouse are connected at the same time

So Only connect the Spatha or dock - not both. meaning if you want to use it as wired e.g charge battery you need to disconnect dock then plug mouse in, then if switching back disconnect mouse then plug dock in. This is far from ideal.

To bad this fix has came tooo late i had ordered the ASUS ROG Pugio and may have to excise the 1979 UK sales of goods act Law (6 year warranty) and get a refund since this is clearly a defect. I must say i am disappointed for a product that cost nearly £150.

DazzXP wrote:
I had issues with the polling rate going to 0 sensitivity going to 0 as such the mouse wouldn't move and the LED's turn sold white, as a work around i gone into the ROG armory and reset them back to default on my laptop since i can use the track pad or use my old Logitech G600 on my computer. However even doing that the cursor just wasn't accurate anymore. I did loads of searches and seemed to have missed this one every time in till today. I also found out at long last how to perform a factory reset of this mouse which works also.... intill you load up the armory then it screws everything up!

Factory reset of the mouse,
1# disconnect mouse
2# press and hold left mouse button, press and hold middle mouse button (scroll wheel) then press and hold right mouse button, with all 3 hold down wait 10 seconds
3# with buttons pressed down insert the USB cable and keep holding them down
4# after 10 seconds release buttons, there will be no lights on the mouse any longer but will resolve all the issues.

Now loading up the armory seems to perform an upgrade from the factory reset 1.09 firmware back to 1.69, once thats done it's screws the mouse up again and you end up back to the same situation with the mouse cursor being inaccurate.

So after factory reset uninstall the armory II and install armory 1 from here: http://dlcdnet.asus.com/pub/ASUS/mb/accessory/ROG_Spatha/ROG_Armoury_v10134.zip?_ga=2.139863795.1540...

Now they ask you to default the mouse but although it detected it as the spartha it will say connect ROG device, so perform the update to the latest version. After which it should be fine once the firmware is flashed the sensitivity is increased and the inaccurate issue is then also resolved.

Apparently from the thread posted above: https://rog.asus.com/forum/showthread.php?102305-Please-read-before-posting-any-new-Spatha-threads

the issue is caused by the profile being corrupted, hence why the factory reset clears it but then if using the same ROG armory software it copies the corrupted file back.

Now the issue appears to be related to when the dock is connected and the mouse are connected at the same time

So Only connect the Spatha or dock - not both. meaning if you want to use it as wired e.g charge battery you need to disconnect dock then plug mouse in, then if switching back disconnect mouse then plug dock in. This is far from ideal.

To bad this fix has came tooo late i had ordered the ASUS ROG Pugio and may have to excise the 1979 UK sales of goods act Law (6 year warranty) and get a refund since this is clearly a defect. I must say i am disappointed for a product that cost nearly £150.


I can confirm. the 5 day, the new armory 3.0.14 stop working. all the present where gone. i make the mouse rest. and sensor stop working. I did what you say. reset the mouse, uninstall the armony and get the 1.0.134 took a few reset untill the mouse appears wired and wireless. update the app. now is 1.2.26 FIRMWARE 1.69, dock 1.32

I will test these for a few days and see if these fix the issue on the new one.

For any reason mine does not stick the preset and i have to make all over again. as some issues with lights and on the end reset the mouse. forcing to downgrade the app so i can use the mouse again. Still checking why these is happening. I will continue using these 1.02.26 and report back here.
Learn, Play Enjoy! We help and collaborate, NOT complain!

DazzXP wrote:
I had issues with the polling rate going to 0 sensitivity going to 0 as such the mouse wouldn't move and the LED's turn sold white, as a work around i gone into the ROG armory and reset them back to default on my laptop since i can use the track pad or use my old Logitech G600 on my computer. However even doing that the cursor just wasn't accurate anymore. I did loads of searches and seemed to have missed this one every time in till today. I also found out at long last how to perform a factory reset of this mouse which works also.... intill you load up the armory then it screws everything up!

Factory reset of the mouse,
1# disconnect mouse
2# press and hold left mouse button, press and hold middle mouse button (scroll wheel) then press and hold right mouse button, with all 3 hold down wait 10 seconds
3# with buttons pressed down insert the USB cable and keep holding them down
4# after 10 seconds release buttons, there will be no lights on the mouse any longer but will resolve all the issues.

Now loading up the armory seems to perform an upgrade from the factory reset 1.09 firmware back to 1.69, once thats done it's screws the mouse up again and you end up back to the same situation with the mouse cursor being inaccurate.

So after factory reset uninstall the armory II and install armory 1 from here: http://dlcdnet.asus.com/pub/ASUS/mb/accessory/ROG_Spatha/ROG_Armoury_v10134.zip?_ga=2.139863795.1540...

Now they ask you to default the mouse but although it detected it as the spartha it will say connect ROG device, so perform the update to the latest version. After which it should be fine once the firmware is flashed the sensitivity is increased and the inaccurate issue is then also resolved.

Apparently from the thread posted above: https://rog.asus.com/forum/showthread.php?102305-Please-read-before-posting-any-new-Spatha-threads

the issue is caused by the profile being corrupted, hence why the factory reset clears it but then if using the same ROG armory software it copies the corrupted file back.

Now the issue appears to be related to when the dock is connected and the mouse are connected at the same time

So Only connect the Spatha or dock - not both. meaning if you want to use it as wired e.g charge battery you need to disconnect dock then plug mouse in, then if switching back disconnect mouse then plug dock in. This is far from ideal.

To bad this fix has came tooo late i had ordered the ASUS ROG Pugio and may have to excise the 1979 UK sales of goods act Law (6 year warranty) and get a refund since this is clearly a defect. I must say i am disappointed for a product that cost nearly £150.


Well thanks, i finally managed to reset this crap and fix the sleep issue now, the tracking issues comes and goes so im not sure anymore, at first i read about the revert to armour 1 and it fixed it for a couple hours so i cant know for sure whats the real issue (well other than being a 150€ crap mouse afterall), maybe its also a firmware issue if anything ill revert the mouse to day 1 and never update it ever again

To think people need to search in the end of the world for a factory reset, never worked before until i found your guide