M6 SP different problem than usual

Glad this place exists. Sucked to sign up just for the possibility in downloading the dfu tool.

I figured i'd go ahead and post my problem first because dfu tool doesn't sound like it'd fix my problem.

So last night i was using my m6 for backing up my data with the m6 being the data transporter to my laptop. So i got all my data on there, when i was done transporting, i proceeded to delete the files i was transporting off of the m6. It wouldn't want to delete my last one unfortunately. This pissed me off, so i performed a firmware upgrade in the hopes that it'd format the player. Newer firmware doesn't do that anymore. So with the new firmware, i proceeded to go into super user in debian to pull an "rm -rf" which couldn't do anything since the folder i created on the m6 to put my data into said it was read only.

This left me going wtf? Not only was i super user, but i used the force option in the command for removing that folder. This pissed me off further. So since i knew that the player was fat32. I formatted the whole thing to fat32. Then i pulled a hard reset on the m6 so it would turn on again.

So it turns on again, but my new problem is wierd. The best way to describe it is that it's like two fat32 file systems are stacked on top of each other. When i plug the m6 into my comuter now. None of the MUSIC, FM, etc folders are there, it's just blank, and i can put data on there. So i put the new firmware files on it. Turned it off, and on again. The new firmware didn't take. Which tells me that the firmware that is operating fine is completely oblivious to the fact that i formatted the whole thing to fat32. In the m6 if i go to the browser i can still explore the normal file structure of you standard m6, while plugging it into a computer doesn't show it. And with that yes the m6 didn't see firmware files i tossed on there after i pulled the format

This problem is a little different than usual. What should i do?

- a hard reset (on/off + >>|) _should_ format the flash memory, effectively resetting your chip to the pristine state. If it doesn't, you're out of options (other than messing around with Linux)
- after that, install firmware. If the usual way doesn't work, use dfu tools (read about dfu tools before you use it)

I guess i'll have to use dfu tools then.