Sansa E200 Bricked by Recovery Mode

[qtip]

1) Have you tried programming the i2c rom WITHOUT running ./e200tool recover BL_SD_boardSupportSD.rom first?

2) Do you have a different USB port and/or computer that you could try using?

1) Yes, no change.

2) Yes, also no change  

I have got exactly the same problem the usb is no longer detected, the blue ring comes on but there is no device showing up in the usb list I have tried three different PCs 2 different OS but it will not show up.. any ideas ??

[Abdullah85]

hi
first of all I wanna let you know that I am using linux fedora 8 and also I have Win xp in my laptop
I was able to get recovery mode 2 days ago ,,, because I was whenever start my sansa I get go to recovery mode ! message
and then I went to sansalinux.com then I downloaded their files to put it in my sansa in recovery mode  
but the I got that the files that I am trying to put in is bigger size than the recovery mode
so I unmount the driver and I unplug the device so gave message reading ,,, writting
and then I held down power off button and I got it turned off
 
NOW ,,
whenever I start my sansa I get blue ring and No lights on my screen
 
I read in many forums that there is manufacturing mode and pre-boot mode
Now I dont know what mode I got
in fedora 8 when I use the script of e200tool I get this

[root@localhost s]# sudo ./e200tool recover BL_SD_boardSupportSD.rom
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x1065fc38
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

but I think I should get this

e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_BOARDSUPPORTSD.ROM' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x10660198
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

I tried to use unbutu live cd and use command lsusb I get this :

ubuntu@ubuntu:~/Desktop/sansa/e200tool$ lsusb
Bus 005 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 001 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 004 Device 011: ID 0b70:0003 PortalPlayer, Inc.
Bus 004 Device 001: ID 0000:0000

ubuntu@ubuntu:~/Desktop/sansa/e200tool$ ./e200tool i2cprogram i2c-e280.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c-e280.bin'
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found!
ubuntu@ubuntu:~/Desktop/sansa/e200tool$ ./e200tool init
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
Failed to claim the interface (-1, Operation not permitted)

and I dont get this
(ID 0781:0720 SanDisk Corp)

so I think the device is not recognized by fedora and unbutu live cd.
so what can I do
 
and thanks in advance

[gevaerts]

You need root rights for e200tool, so use sudo (also for lsusb)

[Abdullah85]

same problem I get this

[root@localhost e200tool]# ./e200tool recover BL_SD_boardSupportSD.rom
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
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!

and it should be like this

e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_BOARDSUPPORTSD.ROM' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x10660198
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

I also tried in my fedora this one

[root@localhost e200tool]# /sbin/lsusb
Bus 001 Device 001: ID 0000:0000  
Bus 005 Device 016: ID 0b70:0003 PortalPlayer, Inc.
Bus 005 Device 004: ID 0781:a3a4 SanDisk Corp.
Bus 005 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  

and I think it should be ID 0781:0720

[zajacattack]

Yes, see you are in pre-boot mode. Here's what you do:
1. Connect your players to the computer (without holding and buttons, and in Linux of course)
2. Go to http://daniel.haxx.se/sansa/e200tool.html and download e200tool
3. Download the latest firmware and bootloader files for your Sansa and put them in the same folder as e200tool
4. As well, download the i2c rom file for your player from http://daniel.haxx.se/sansa/e200tool.html
5. Connect your Sansa if you haven't already and run "./e200tool init" followed by "./e200tool i2cprogram I2CROM.bin", where "I2CROM.bin" is whatever you named the i2c rom file when you downloaded it
6. When and only when it finishes, disconnect your Sansa, and reconnect it in manufacturing mode
7. Run "./e200tool recover BL_SD_boardSupportSD.rom" while holding RECORD on your player
8. Once the player has booted to recovery mode, copy the bootloader and firmware files over to it
9. Disconnect your Sansa, it should be fixed

[Abdullah85]

WOoOoOoOoW

I got it baaaaaaack thanks  

I really want to kiss you right now  


thanks again and again

[cheesecake]

I'm having extreme difficulty

When using lsusb in a kubuntu live cd, all i get is Bus 001 Device 001: ID 0000:0000 
When running e200 tool from the download on daniel.haxx i can't get it to recognize it no matter what i do.
Do i just need to get a new mp3 player?

Edit: I'm getting the Bus 001 even without my Sansa connected.  also, i am running everything as root.
Windows recognizes that there is a disk, but i can't find it under device manager.

[Epholl]

Hello.

I am (was) a happy owner of a rockboxed e250 Sansa v1. Everything went okay, Rockbox functional, all good.

But yesterday, I noticed some files and folders in the file structure disappeared and some songs gone missing too. I tried to find them using the database, but it did not work. Then I booted to original firmware and waited for the database to refresh. Back in Rockbox, the files were found in the database, but the file structure was still missing the folders + files.

My brother has a similar Sansa with a bit newer version of Rockbox, so we pasted his Rockbox on my Sansa - problem solved, everything okay again.

Today, I took my Sansa to school and turned it on there (wanted to listen to some music of course). What did I see? Display black, wheel lit. Turning on - off... Did not help. Seemed like the manufacture mode, when I checked the net... The problem is here: When I connect my bricked Sansa to the USB, my comp detects nothing, Sansa keeps black screen and lit wheel.

Tried all (at least I hope all) the instructions on this site: http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick

I am not sure, but I guess it is the end if the device cant communicate with the USB... Tested on 2 PCs.. No response.

Thanks for any help.

[Mystious]

Here are the Steps of what I did, got stuck (like y'all), and how I fixed my Sansa e260:


1. Follow the Steps at http://fixmysansa.blogspot.com/
2. If you get stuck at STEP 3 (which I did like most of you)  when it says to
Paste

sudo su
./e200tool recover BL_SD_BOARDSUPPORTSD.ROM

Go to File System/Media and see if theres any folder. If there is a folder, then proceed. If not, follow the following steps:
4. Download the I2c-e260.bin file for your player from http://daniel.haxx.se/sansa/e200tool.html
5. In TERMINAL, type in "./e200tool init" THEN "./e200tool i2cprogram i2c-e260.bin"
6. When Finishes, disconnect your Sansa and reconnect
7. REDO all the steps at  http://fixmysansa.blogspot.com.   When you get to the step that tells you to paste "./e200tool recover BL_SD_boardSupportSD.rom" while holding RECORD on your player, your TERMINAL should NOW looks like this:

e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_BOARDSUPPORTSD.ROM' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x10660198
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

**This mean that there is now a new folder  in File System/Media (mine was File System/Media/Disk-1)
8. Proceed and continue with  http://fixmysansa.blogspot.com/
9. Once you have 3 files BL_SD_BOARDSUPPORTSD.ROM, PP5022.MI4, Sansa.fmt in the folder. Disconnect your Sansa.
10. Turn off HOLD/LOCK and restart, if screen freezes, hold Power Button till it shuts and restart again. And hope your sansa is back to normal as mine did. GOOD LUCK!

[Epholl]

Thank you manytimes. We got into the 16MB part, although reformatting did not help.
http://anythingbutipod.com/forum/showthread.php?t=33373 This did help me a lot, because the problem was in the daughterboard. I do not know how, but it was disconnected from the mainboard, thus, I now understand, why the player saw only a 1/2 of the memory, or why the 16MB part reformatting did not help... Thank you one more time.

[gevaerts]

Thank you manytimes. We got into the 16MB part, although reformatting did not help.
http://anythingbutipod.com/forum/showthread.php?t=33373 This did help me a lot, because the problem was in the daughterboard. I do not know how, but it was disconnected from the mainboard, thus, I now understand, why the player saw only a 1/2 of the memory, or why the 16MB part reformatting did not help... Thank you one more time.

You formatted the 16MB recovery drive? In that case, good luck in getting your player back to a working state...

[virtuoso015]

Not really !!!

Even if you have formatted your recovery drive, and the player is not getting updated (or formatted using sansa.fmt), it can still be recovered. I will be posting soon about what one needs to do !!! Please bear with me for a little while more

[Bagder]

The unbrick wiki page explains how to get back, use the manufacture mode and e200tool.

[virtuoso015]

Yes, that is true , but in some cases, like mine(http://forums.rockbox.org/index.php?topic=18197.0) , no method worked. So, i have extended e200tool to include  nandread and nandwrite commands which read and write sectors directly from the disk. This way i was able to burn the whole 20MB hidden partition dump onto the NAND disk and get the player working again

[Bagder]

Yes, that is true , but in some cases, like mine

I would call that in one case. I've worked with Rockbox on the e200v1 probably longer than most others and as far as I know you are the first and only one who has needed that procedure!

This said, I'm of course interested in getting your e200tool changes as a diff so that others can enjoy them!