Sansa E250 Blue Ring no Display

[Aprules2]

I found an E250 at a yard sale a few months ago and I have been using it and it worked fine. Today I decided I'd do a firmware upgrade. So I went to Sansa's site downloaded the Firmware updater and installed 1.02.24. My Sansa rebooted after and kept locking up. When it did finally load, I tried to turn the wheel and things would just randomly open. After trying to format the unit and reinstall the firmware and running in circles using Sansa's crappy tutorials I ended up bricking my phone. Blue ring no display. So I found a few sites that said to use the e200tool. After a lot of effort I got it to run, the process finishes and the E250 loads into recovery mode. Then the drive opened up on my desktop, with firmware.txt as the only file. So I went to Sansa's website and downloaded the version 1.02.24 and unzipped it. The files were PP5022.MI4 and BL_SD_boardSupportSD.ROM, which I copied to the Sansa drive. I told the computer to eject the drive, the Sansa said drive ejected, I unplugged the usb cable and it didn't auto restart like it usually does. So I held down the menu button for 20 Seconds and then pushed it to turn it back on. But I still have just a blue ring and no display. Is it possible the firmware from Sansa is corrupted? It had the original 1.0.0 on it when I got it, am I not compatible?
Post Merge: October 19, 2011, 09:30:02 PMI'm doing some more reading and think I figured out what I did wrong. On Sansa's site it says to format your drive when you're having issues with the upgrade. When I couldn't get the device into the proper usb mode for my pc to read it, I read you can boot it in Recovery Mode and then format the drive and load the new firmware. What I just found out is I formatted the recovery partition. What the hell do I do?
Post Merge: October 19, 2011, 11:22:21 PMUpdate... I tried changing what Version.txt says to the proper info I found on another forum, then adding the rom and loader, while in recovery mode. It still doesnt work my screen says

*********************
Welcome to Recovery Mode
*********************

USB cable connected
Enter USB2.0 MSD mode

then I copy my files and remove the cable and it adds the lines

Safe to Disconnect USB
Exit USB2.0 MSD mode

it never reads the files or reboots after the install.

[Chronon]

It sounds like you're stuck in Manufacturing mode.  Check this page:
http://www.rockbox.org/wiki/SansaE200Unbrick

Feel free to ask questions before proceeding.

[gevaerts]

Check if the flash board is still properly seated. See http://forums.rockbox.org/index.php/topic,22154.msg152893.html#msg152893 for details.

[Aprules2]

It sounds like you're stuck in Manufacturing mode.  Check this page:
http://www.rockbox.org/wiki/SansaE200Unbrick

Feel free to ask questions before proceeding.

Ive actually done everything in this post. I used e200tool to get the Sansa to reboot into Recovery mode. Then Windows finally recognizes my Sansa and opens the recovery Partition. I copied the 2 firmware files to the recovery partition, and made the Sansa.fmt file. But it has no effect on the player. Is almost as if the files from the Recovery Partition arent being written to the main player.

[Chronon]

How about the daughter board?

[mc2739]

I copied the 2 firmware files to the recovery partition, and made the Sansa.fmt file.

In my experience, copying both files to the recovery partition in the same session does not work.  Try try copying the BL_SD_boardSupportSD.ROM file first and then reboot into recovery mode.  If that works, then copy the PP5022.MI4 file.

[Aprules2]

I tried to copy Just the one file and it still didn't work, also my version.txt file is still all scrambled.

I haven't opened it yet I don't have any philips head screwdrivers small enough to open it. I'll try and run to the store tomorrow.

[mc2739]

There is a thread at anythingbutipod to deal with a corrupt version.txt file that uses a modified e200tool.  The link is: http://www.anythingbutipod.com/forum/showthread.php?t=33823

I have used this tool in testing, but not to repair a particular issue.