Sansa e260: Player is Bricked

[zajacattack]

No, currently, the cause of that problem is unknown. The best solution as of now is to disconnect your Sansa, reconnect and try again. Mindless repetition appears to make this go away eventually.

[yoursavior]

"Initializing USB stub <4780 bytes> ... done!
Writing 'BL_SD_BoardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found"

Does the Hardware Wizard need to copy "libusb0.sys" to the e260? I put in the right address for the file but then it says it had an error copying the file over and the file is not on my computer afterwards.

[zajacattack]

Yeah, you're gonna need that. Try downloading the libusb-win32 DEVICE DRIVER. It should have those two files the wizard needs.

[yoursavior]

"Initializing USB stub <4780 bytes> ...
Length write error <-116, Connection timed out>"

:/

[zajacattack]

Same thing; keep trying.
I wish there was something to do, but repetition is all we have at this point

[yoursavior]

It's alternating between timed out connections and not being able to find the drive.

[zajacattack]

Perhaps wait and try tomorrow, or, if you want to try again, just reboot the comp and do it again.

[yoursavior]

It worked! But, more problems.

It's on the "Refresh Database" screen and was just about to finish loading when vertical red lines appeared and the Sansa froze. What should I do to fix this?

[zajacattack]

You probably have corrupted files. First off, hold down power for 15 sec. If that fails, just take out the batter and pop it back in. Next, you must get it connected to the computer. Have Windows run checkdisk on it. If that doesn't fix it, format it.

[yoursavior]

I turned it off and its back to being a brick. :/

*sigh*

[zajacattack]

OK, repeat what you did before, except this time, also put an empty file named "sansa.fmt" (without the quotes) in the recovery disk. This should cause the Sansa to self-format.

[yoursavior]

Since it's no longer loading up the Hardware Wizard, which device do I install the first driver in?

[zajacattack]

If you go to the Device Manager, under Universal Serial Port controllers, you will see a device with a yellow exclamation point. Right-click it, select "Update driver" and then install the first one. The second one should already be installed and you will re-install the Windows one once you get to recovery mode.

[yoursavior]

EDIT 2: I uninstalled the USB Device under Lsbusb and it messed up the whole thing and I had to start over.

[yoursavior]

"Searching for device 6666:e200 ... found!
Execution started!"

What does this mean? Should I keep holding down the rec. button?