android
  #1  
Old 03-24-2009, 07:07 PM
unixdude unixdude is offline
Junior Member
 
Join Date: Mar 2009
Posts: 3
Default white screen of death

Greetings,

Yes, this is my first post to this board. I'm new to this board, but not to forums in general.

I have a brand new Sansa e260, purchased in Feb from newegg.com. I have never seen anything but the white screen of death since I first powered this thing on. I also have a refurb'ed e250 which has worked perfectly, so I kinda know what to expect. I've spent the past couple of days searching all over the web, but have not found a solution to my problem. Normally I would return it to newegg, but I'm past the 30 day window for returns, so now I have to deal with SanDisk. I really would prefer to not deal with the helpless line, so I thought I would give this forum a try.

I have tried to downgrade the firmware by following the instructions in the "ultimate fix" thread without luck. I have been able to successfully boot into recovery mode and mount the 16mb partion which is only showing 1 file to my linux system. Here's the visible text from the version.txt file:

Code:
$ /bin/more /media/16MB-FORMAT/version.txt 
Version Info: Product Rev.: PP5022AF-05.51-S301-00.12-S301.00.12A-D
Base Code: 05.51-S301-00.12-S301.00.12A-D
ODM Ver.: S301-00.12-S301.00.12A-D
OEM Ver.: S301.00.12A-D
Build Type: -D
Build Date: 2006.03.29
Build Number: (Build 169.20)

$
I would like to try the procedures in the following thread, however I am unable to get e2tplus binary to execute and the compile fails.

http://www.anythingbutipod.com/forum...ad.php?t=33823

Code:
$ /usr/bin/sudo ./e200tool init
./e200tool: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
$ /sbin/lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0781:0720 SanDisk Corp. Sansa C200 series in recovery mode
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter
Bus 004 Device 002: ID 09ae:0001 Tripp Lite 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$
I also tried to compile e2tplus on my system, but apparently I do not have the correct cross-compiler packages installed.

Code:
$ /usr/bin/make
arm-elf-objcopy -Obinary arm_code.out arm_code.bin
make: arm-elf-objcopy: Command not found
make: *** [arm_code.bin] Error 127
$ /bin/uname -a
Linux new 2.6.27.19-170.2.35.fc10.x86_64 #1 SMP Mon Feb 23 13:00:23 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
$ /bin/ls -la /media/16MB-FORMAT/
total 24
drwxr-xr-x 2 root root 16384 1969-12-31 19:00 .
drwxr-xr-x 3 root     root  4096 2009-03-24 19:15 ..
-r-xr-xr-x 1 root root   512 1979-12-31 23:00 version.txt
$
so, considering everything I have already tried, what would be the next step?

I have tried too many things to list based on several threads on this site. Nothing seems to have worked. My best guess so far, is a corrupt version.txt file. Based on the thread posted above, I need to figure out how to get e2tplus working. So, what would help is what packages are required for the build? My system is running Fedora 10 64 bit on AMD proc. Please let me know if any further information is required.

Thanks to all who took the time to read my post.
Reply With Quote

Advertisement [Remove Advertisement]

  #2  
Old 03-24-2009, 08:25 PM
carpenter940 carpenter940 is offline
Member
 
Join Date: Aug 2007
Posts: 347
Default

I just ran this fix two days ago. Here are some thoughts on your situation.

Do you have libusb on you computer? I noticed that was having problems in the error message.

I didn't have to compile the e200tool. I know this because I don't know how to compile. I used Ubunto and just made sure to copy all files from both the file that were offered from the site you linked (e2tplus.zip and all the source files from e2tplus-dev.zip). and then just did the steps outlined.

The nand file (sansa-sda2) worked for both my e260 which would just boot itself over and over again and my e280 which only gave me "Load image failed" messages. This make me believe it will work on any e200 series.

One last thing, I have a e200 that has a white screen and I think it's just a LCD problem. I'm not sure this will help it. If it works let me know and I'll try it on mine too.
__________________
My Themes:
dancing cat Miss LED BECScope Mickey Heavy Metal
Reply With Quote

  #3  
Old 03-24-2009, 08:46 PM
unixdude unixdude is offline
Junior Member
 
Join Date: Mar 2009
Posts: 3
Default

Quote:
Originally Posted by carpenter940 View Post
I just ran this fix two days ago. Here are some thoughts on your situation.

Do you have libusb on you computer? I noticed that was having problems in the error message.

I didn't have to compile the e200tool. I know this because I don't know how to compile. I used Ubunto and just made sure to copy all files from both the file that were offered from the site you linked (e2tplus.zip and all the source files from e2tplus-dev.zip). and then just did the steps outlined.

The nand file (sansa-sda2) worked for both my e260 which would just boot itself over and over again and my e280 which only gave me "Load image failed" messages. This make me believe it will work on any e200 series.

One last thing, I have a e200 that has a white screen and I think it's just a LCD problem. I'm not sure this will help it. If it works let me know and I'll try it on mine too.
Thanks for the input. You gave me a idea to check for libusb. It's installed, but appears to be only a 64 bit version. I'm going to assume the compiler is looking for the 32 bit version. I'll check the flags in the makefile and see if that will fix. If not, then I guess I'll just d/l a 32 bit version boot cd and try to fix it that way.

Code:
$ /usr/bin/sudo /usr/bin/find /usr -name "libusb*" -ls
9790083    4 -rwxr-xr-x   1 root     root         1358 Oct 21 02:23 /usr/bin/libusb-config
10158353    4 drwxr-xr-x   3 root     root         4096 Dec 15 00:57 /usr/share/doc/libusb-devel-0.1.12
9793226   36 -rwxr-xr-x   1 root     root        35552 Oct 21 02:23 /usr/lib64/libusb-0.1.so.4.4.4
9791170    0 lrwxrwxrwx   1 root     root           19 Dec 14 09:23 /usr/lib64/libusb-0.1.so.4 -> libusb-0.1.so.4.4.4
9814501    4 -rw-r--r--   1 root     root          182 Oct 21 02:23 /usr/lib64/pkgconfig/libusb.pc
9790520    0 lrwxrwxrwx   1 root     root           21 Dec 14 09:23 /usr/lib64/libusbpp-0.1.so.4 -> libusbpp-0.1.so.4.4.4
9793158    0 lrwxrwxrwx   1 root     root           19 Dec 15 00:57 /usr/lib64/libusb.so -> libusb-0.1.so.4.4.4
9790240   24 -rwxr-xr-x   1 root     root        21112 Oct 21 02:23 /usr/lib64/libusbpp-0.1.so.4.4.4
9795625    0 lrwxrwxrwx   1 root     root           21 Dec 15 00:57 /usr/lib64/libusbpp.so -> libusbpp-0.1.so.4.4.4
$
Reply With Quote

  #4  
Old 03-24-2009, 09:24 PM
unixdude unixdude is offline
Junior Member
 
Join Date: Mar 2009
Posts: 3
Default

Just for the heck of it, I decided to attempt a manual update of the firmware to version 1.02.18. I downloaded a copy of 1.02.18a.mi4, then booted the e260 into recovery mode, copied the 1.02.18A.mi4 file to the 16mb partition and rebooted it. Then I rebooted into recovery mode and confirmed the firmware ID string was updated in version.txt. Version.txt was updated and the screen is still all white.

Code:
$ /bin/cat /media/16MB-FORMAT/version.txt 
Version Info: Product Rev.: PP5022AF-05.51-S301-02.18-S301.02.18A-D
Base Code: 05.51-S301-02.18-S301.02.18A-D
ODM Ver.: S301-02.18-S301.02.18A-D
OEM Ver.: S301.02.18A-D
Build Type: -D
Build Date: 2006.11.03
Build Number: (Build 32.10)
$
Reply With Quote

  #5  
Old 05-14-2009, 01:36 PM
macgeek417 macgeek417 is offline
Junior Member
 
Join Date: May 2009
Posts: 1
Default

Just plug it in in recovery mode, and make a new folder on your desktop named "sansa.fmt" (without the quotes)

copy that folder to the the recoovery disk, and unplug. This will reformat the Sansa and reinstall the origionl FW. you can then re-do whatever else you had on it!
Reply With Quote

  #6  
Old 11-05-2009, 12:04 AM
Bustama85 Bustama85 is offline
Junior Member
 
Join Date: Nov 2009
Posts: 1
Default

Hi. I'm new to both forums and this technical work you both worked on in these threads( i think they're called?). I was curious to know if you guys ever fixed this issue with the white screen of death? If you did, how did you do it? Please keep in mind that I'm not at all tech saavy.
Reply With Quote

  #7  
Old 11-05-2009, 12:57 AM
skip252 skip252 is offline
Administrator
 
Join Date: Dec 2007
Location: Chicago
Posts: 5,204
Default

I have unbricked a few V1 e2xx Sansas using these instructions. There's no way to tell if unixdude was able to fix his problem. His last activity was in April 2009.
Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT -5. The time now is 03:00 AM.