Hooray! Sansa e260v2 doesn't charge out of MSC mode, refuses to install drivers...

I have an e260v2 that I bought used around 1 1/2 months ago. It’s worked fine for that long. But a couple of days ago I reformatted my PC’s hard drive, and things started going south.

BEFORE ANYONE SAYS IT: Yes, the firmware is up to 3.01.16A

The Sansa didn’t immediately install its drivers when I first connected it after reinstalling Windows. The little Sansa icon never showed up on the taskbar. When I connect it to ANY USB port (hub or otherwise) it doesn’t charge, and nothing shows up on My Computer. No drive or anything. It says Connected on the Sansa itself, though. So I went into the settings and forced it into MSC. It charges, and stuff shows up on My Computer.

Of course, if it had worked, I wouldn’t be here.

Still no drivers installed, but at least it shows up. BUUUUUUUUUUUT…

This is what shows up in My Computer:

drives

Drive F only shows up when the Sansa is plugged in. The drive is inaccessible. It isn’t recognized by Windows; it tells me to put a disk in drive F.

And this is what’s inside the SANSA E260 folder

Files

No syncing; no files in any of the folders; no interface with the computer, basically. Sansa itself works fine, though. Anyone have any idea of what to do?

Message Edited by tgsos on 08-07-2009 06:34 PM

  1. Your F: Removable Disc drive is the external card slot. This will show in Explorer when you are connected in MSC mode whether there’s a card inserted or not. The fact that you don’t is why you’re getting the ‘inaccessible’ msg.
  2. Looks like you have some pretty serious corruption there. I’d format it to clear it all out and start over.
  3. The only ‘drivers’ it needs are those included as part of Windows Media Player 10 or 11. You may need to re-install this to activate them. But they are only needed if you intend to use MTP mode; like if you want to ‘sync’ your music via WMP. Otherwise it should work just fine in MSC mode; just drag & drop your music files from your My Music folder on your computer to the Music folder on your player.

I tried everything you said. WOW. What is this thing’s problem? I formatted it, and then this:

Like everything doubled up. No folder with a hash or an invalid square character is even accessible. How do I wipe everything? Is there some kind of factory reset function or something? Some way to roll back everything?

Also, now I don’t even have music. ;_; 

How are you formatting it?

Your e260v2 model will have a on-board Format option in the Settings menu. It will format itself.

Looks like your filesystem is corrupted.  Connected in MSC mode, try one of the following methods:

Right click on My Computer and select Manage.   Click on the icon Disk Management.  Right click on the Sansa in the list in the upper right, or below, and select properties , then select the tools tab.  Here we have the Check for errors button.

Or, from a command prompt, once you see the drive letter assigned to the Sansa.  Let’s assume it’s “E” for this example.  In the Run box, enter cmd.  This will open a command prompt box.  Then use chkdsk to check the drive.

The command is chkdsk e: /f  where " e" is the drive letter, and "/f" is a toggle that tells the utility to fix the errors found.

Bob  :smileyvery-happy:

THIS UPDATE WRITTEN AS I GO ALONG 

Used the in-Sansa format (since you asked me how I formatted it), and used it again before posting. Random corrupted files were gone after the second format. Put a song in through MSC, which played fine. Switched it to MTP, turned it off, and turned it back on. Froze halfway through Refresh Database screen. Turned it off, pressed left button with Hold on to force MSC, connected it to PC, and the corrupted files are back. Same weird directories, same random files. Formatted it a couple more times (in Sansa, since after a connection the thing stays on) for the hell of it but MTP still refused to work (charged the Sansa though). Put a different song in through MSC, played fine, changed to MTP and turned it off. Still not detected. After connection I trned it off, and it froze on the boot screen (SanDisk sansa). Turned it to MSC after a while, since actually getting it past the boot screen took a while. O HAY GUYS! Corruption’s back. My Sansa seems to have been posessed by the Governor of Louisiana…

what is this i dont even

Seriously though, what’s wrong with my Sansa? Why is it corrupting everything all of a sudden? Is there anything I can do that doesn’t involve cracking it open?

NOTE: As of this post, I saw someone else posted. This post took forever to make, and I didn’t see it until now. Gonna go ahead and see what he says. 

Message Edited by tgsos on 08-07-2009 10:44 PM

Oh wow. It keeps getting better.

Thank you neutron_bob for helping out. Unfortunately, my Sansa is apparently insane now.

I ran the error-checking twice, once with each method. Nothing happened. The corrupted files and folders are still there.

chkdsk told me it found no errors in the disk.

I screamed something at it in Japanese.

I don’t know any Japanese.

My Sansa now freezes around 98% through Refreshing Database screen in addition to freezing on the boot screen.

Anything else? I’m getting desperate, and I don’t want my only MP3 player to die. I don’t understand what happened. Has this happened to anyone else?

Perhaps, the OS is building those crazy files.  Let’s try a few steps:

While connected in MSC mode, delete every file that is preceded with a square character.  You should have a correct group of files and folders remaining.

Then download this firmware, 03.01.16a.  Unzip the binary file and place it on your desktop.  Then drag and drop the e200pa.bin file into the root directory of the Sansa.  Don’t drop it into any of teh folders, just place it in the open Windows Explorer window for the Sansa (the root directory).

Then, let’s unplug the Sansa after the transfer: click on the safely remove hardware icon in the system tray first.

The Sansa will display “firmware upgrade in progress”.

It should rebuild the file structure correctly.

Let me know what happens.

Bob  :smileyvery-happy:

@tgsos wrote:

THIS UPDATE WRITTEN AS I GO ALONG 

 

Put a song in through MSC, which played fine. Switched it to MTP, turned it off, and turned it back on. Froze halfway through Refresh Database screen. Turned it off, pressed left button with Hold on to force MSC, connected it to PC, and the corrupted files are back. Same weird directories, same random files. Formatted it a couple more times (in Sansa, since after a connection the thing stays on) for the hell of it but MTP still refused to work (charged the Sansa though). Put a different song in through MSC, played fine, changed to MTP and turned it off. Still not detected. After connection I trned it off, and it froze on the boot screen (SanDisk sansa). Turned it to MSC after a while, since actually getting it past the boot screen took a while. O HAY GUYS! Corruption’s back. My Sansa seems to have been posessed by the Governor of Louisiana…

So your problem seems to lie within the MTP mode. MSC appears to work just fine. It’s only after you switch to MTP, then back again to MSC that this occurs, right?

Well, the most simplistic solution would be to leave the player in MSC mode [Patient: “Doctor, it hurts when I do this!” Doctor: “Then don’t do that! That will be $100. Pay the receptionist on your way out.”]. But I know you want to find out the cause, whether you use MTP mode or not. I would. It would bug the b’jeebers outta me.

Since MTP mode uses drivers included in Windows Media Player, what version WMP do you have? It might be worth an upgrade (or re-installation) to WMP 11. You should be able to back off to version 10 if you don’t like it, but check to see if either version solves or triggers your corruption problem.

You can also un-install it in MTP mode in Device Manager and re-install it (be sure to safely dis-connect and re-boot your computer after un-installing). That should force Windows to re-initialize the MTP drivers.

Let us know how you fare.

:smileyvery-happy: :smileyvery-happy: :smileyvery-happy: :smileyvery-happy: 

Thank you fine gentlemen for helping out. I finally figured out what was wrong. When Bob made this comment, something hit me:

@neutron_bob wrote:

Perhaps, the OS is building those crazy files.

He probably meant the Sansa’s OS. It wasn’t.

It was mine.

I did something horribly wrong during installation, and my computer corrupted the file system every time I connected the Sansa. I don’t know why it did that, but a fresh install fixed it. Tapeworm was correct: it all had to do with connecting with MTP. And I had to reinstall everything. Without feedback from you guys, I might not have figured out the problem. Thank you for all your help, advice, and patience; all my problems are solved now. MTP works, charging works, and it doesn’t corrupt anymore.