There is more than one a way to recover.
When the quadstick is shipped out, there is an X360CE example config
loaded into the flash that will set the emulation mode to 2, allowing
flash access, so if your Quadstick still has that file, the first option
below would be the way to go. If fact, if you have a bunch of PC config
files affected by the "stutter", you might actually want to just leave the prefs.csv file the way it is, with emulation mode 6, and switch to a config file that allows flash access
when you want to make changes and leave flash access off the rest of the time. If you are not sure which file number would be the X360CE file, just load one after the other until you see the flash drive appear in the file manager.
In general I encourage users to never edit the prefs.csv file manually.
All the different settings on the various QMP tabs are what go into the prefs.csv file. prefs.csv is not like the csv files from the various configuration spreadsheets.
These are the options for gaining flash access in order of convenience:
- If you have a config CSV file that sets the emulation mode to 0, 2 (X360CE), or 4, in the flash drive, then you can select that file and gain access to the flash, as long as that config is selected.
- You can force the Quadstick to skip loading the default.csv and prefs.csv files by plugging in a 3.5mm switch into the IN jack on the back and close the switch while the Quadstick boots up. It will start up running a simple fall-back configuration with a game controller in the first four modes, and mouse mode in mode five, similar to the Default Configuration, and you will have flash access. Sometimes plugging the lip sensor into the IN jack can be detected as a closed switch and force the quadstick to skip loading the config files.
- You can force the Quadstick to erase the flash drive completely and re-download all your configuration CSV files. A completely blank Quadstick will run that fall-back configuration with a mouse mode in mode five.
You're not the first person to do this