Sansa e260: Player is Bricked

[yoursavior]

After installing RockBox the LCD screen stopped working. I am not able to access Recovery mode, but I am currently in Manufacture mode. The scroll light remains on while the rest of the player refuses to work.

[safetydan]

Have you read this? http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick

[yoursavior]

Yes, but I don't have Linux, so I'm unable to find the proper e200tool.

[zajacattack]

You can get the Windows version at http://www.rockbox.org/twiki/bin/view/Main/UsefulSansae200Tools. If you need directions on how to get it working with the drivers, I can post them.

[yoursavior]

That would be extremely helpful if you could, as I have no clue as to what I'm supposed to be messing with when I get it hooked up.

[zajacattack]

OK, first you must download the e200tool for Windows from where I showed you, and you must download the bootloader and firmware (you can do a google search to get these). Then:
1. Connect your Sansa in manufacturing mode.
2. When prompted by Windows to install drivers, install from a specific location and point Windows to the first .inf file (0781-0720.inf)
3. Go to the command prompt, change to the directory with the e200tool binary, and run the command "e200tool init" (without the quotes).
4. If it successfully attaches to the Sansa, you should be prompted for another driver from Windows. If not, you need to try again.
5. This time point Windows to the other .inf file (0666-E200.inf)
6. Once that is installed, copy your BL file (probably named "BL_SD_BoardSupportSD.rom") to the directory with e200tool.exe
7. Now, while holding Rec on your Sansa, execute "e200tool recover BL_SD_BoardSupportSD.rom" (without the quotes) from the command prompt. KEEP REC HELD UNTIL YOU ENTER RECOVERY MODE!
8. Now, right-click My Computer, go to Hardware tab, then to Device Manager, and uninstall the original driver (under Libusb-win32 Devices). Then, right-click Universal Serial Bus controllers and select "Scan for hardware changes". Windows will then re-install the old driver, and the recovery disk should now show up in My Computer.
9. Copy the bootloader (BL_SD_BoardSupportSD.rom) and the firmware (pp5022.mi4) to it.
10. Now, safely remove your Sansa. It should say something about a new bootloader and firmware. BOOM! Your Sansa is back is regular condition
NOTE: If this doesn't work, you are probably in pre-bootloader mode and need to replace the i2c rom, which I can post directions for if you need.

[yoursavior]

Do I need the original Sansa bootloader and firmware or the RockBox bootloader and firmware? Or do I need a dual bootloader?

Also, what command prompt? The one from e200tool disappears right after I open it.

[zajacattack]

Yes, the Sansa's original bootloader and firmware, not rockbox. And, you can go to Start->Accessories->Command Prompt then you just do "cd C:\[whatever the path to your e200tool folder]" (without the quotes)

[yoursavior]

Ok, I got to step 5 and the "New Found Hardware Wizard"  froze before I could input the next driver. How do I re-open that window?

[zajacattack]

Simply right-click My Computer, go to Hardware tab, open Device Manager, and find the "Unknown Device". Right-click it and select "Update driver" or something similar. You will then get the same wizard.

[yoursavior]

I don't see a Hardware tab. These are the menus that come up when I right-click My Computer...

EDIT: I found My Devices but there is no Unknown Device option.

[zajacattack]

In that case, expand all of the menus (click the + signs) and find the device whose symbol has a yellow sign and exclamation point (!) by it. That should be the Sansa.

[yoursavior]

I just got to step 7 and something odd happened. The Sansa never went into recovery mode, but a window asking to instal a driver did come up. Then, when I went to uninstal the driver under libusb, libusb was no longer in the device manager.

[zajacattack]

OK, try disconnecting your Sansa, reconnecting it, and then running "e200tool recover BL_SD_BoardSupportSD.rom"

[yoursavior]

"Searching for device 0781:0720 ... found!
Initializing USB stub <4780 bytes> ...
Length write error <-5, Input/Output error>"

Did I do something wrong?