Sansa will not turn on / only blue ring appears
Sansa Will Not Turn On
Sometimes, when updating the firmware using Sansa Updater, the bootloader isn't written properly and causes the blue scrollwheel on the Sansa to be the only thing that turns on, and the display doesn't turn on at all. When this happens, a low level device mode, Manufacturing Mode, must be used to attempt to recover it. Details for recovering it are described in the Guide: Recovering a bricked Sansa (USE AT YOUR OWN RISK) thread. Please note, while it is risky, the only other thing to do besides those steps is to return it to Sandisk, which will take about two weeks. Sandisk (usually) will still accept Sansas even after those steps have been performed.
Also, here's a howto I wrote for those who don't have any luck with the Windows version:
Download a copy of Ubuntu Linux: http://mirrors.kernel.org/ubuntu-rel...sktop-i386.iso
A black window should appear. In that window, type:
Next, put your Sansa into Manufacturing Mode:
"Bus 001 Device 005: ID 0781:0720 SanDisk Corp." (Mainly, just the ID is important, 0781:0720. The bus and device may change.)
If you do, you're in Manufacturing Mode, and you may continue.
Enter the following while holding REC:
When it gets to 'Execution started!' you should see the Sandisk logo appear on your Sansa's screen. If you are still holding REC, it should then go to Recovery Mode. (if you weren't holding REC, repeat this entire process again) After it enters Recovery Mode, Ubuntu should Auto Mount the drive, under something similar to /media/disk.
If it didn't get mounted under /media/disk, find what it was mounted under, and substitute that location for /media/disk in the next section. If it wasn't mounted at all (it should have been) do "dmesg" and look for a line near the bottom similar to "SCSI device sdc: 32769 512-byte hdwr sectors (17 MB)". You are mainly looking for what's after the word 'device' - in this case, sdc. Then do 'mkdir -p /media/disk && mount /dev/sdc /media/disk' being sure to substitute sdc for whatever dmesg said, if needed.
Once it is mounted, do:
Disconnect your Sansa, turn off hold, and see if it works. If it doesn't, repeat these steps again if needed.
Also, these steps were done on a fresh, unmodified copy of Kubuntu 7.04 from a USB drive. On Kubuntu, to get to the terminal, go to the 'K' symbol -> System -> Konsole.
I've also found the following:
If e200tool hangs when initializing the USB stub, disconnect and reconnect the Sansa, and try again.
Reading and writing to the I2C isn't completely stable. I found that when programming it, the scrollwheel flashes rather fast. While I can't say for sure if it's normal, it doesn't seem to affect the Sansa when programming it. If there's a protocol error, I noticed the scrollwheel will flash on and off about every second. MrH says this means there's a serious error, but in the three times I got that, my Sansa was not permanently affected.
While not suggested (never 'try' this) I found that programming the I2C with invalid text will not harm the Sansa. It will however, force it into Pre-boot mode.
If you get a protocol error, disconnect your Sansa and try again.
There are two I2C files on Daniel's (Bagder) site. One is a dump from an e260, the other was from an e280. When dumping the I2C from my e250, I found that the md5sum matches the e280 I2C. I have tested both I2C files on Daniel's site, and both work with the e250 (and probably the others)
While I have been able to do a lot of 'testing' with e200tool without bricking my Sansa, I suggest you do not test what e200tool can do unless you fully understand what you are doing, with the exception of when following a guide, such as this (though we aren't testing what it can do in this guide)
I have not attempted to format the Recovery Mode partition, so I can not say what the effects of that are.
I have found that in line 1245 of the bootloader, it mentions the e250. I have tested changing it to e260 etc., and see no difference.
In the bootloader, it mentions:
UID is on a new line, and while I don't see it mentioned anywhere else, I'd recommend not placing a file in Recovery Mode that ends with UID.
|All times are GMT -5. The time now is 12:39 AM.|