Sansa E200 Bricked by Recovery Mode

[JdGordon]

you need to run " e200tool.exe recover BL_....."

[Brambo]

fLo, firstly the tool DOESN'T WORK ON WINDOWS (at least not with me)

1. download knoppix live cd and burn that on cd
2. insert the cd and restart your computer, now your pc will boot the live cd and start linux.
3. now start reading my post with the instructions on how I fixed my sansa from that point (I think it's on page 7 or

Where do you get stuck?

[chrisjs169]

Ok, try this:

Open the command prompt
Type the following

Code: [Select]

cd C:\e200tool
(wait for it to change directories)
e200tool recover bl_sd_boardsupportsd.rom
(follow e200tool directions)

EDIT:  Didn't notice posts above, so this is sort of a repeat

[Rcholla32]

Wat is Manufaction mode plz write back because i messeed it up by recovey mode

[Rcholla32]

My sansa is not working because i was formating it right and my computer shut off and it sad free up 6 mb for music db. and i use the sansa e200 tool and now the scrool wheel is now working thats it

[Lue]

HI @ all.

theres just another stone in my way to a fixed sansa:

Code: [Select]

sudo ./e200tool recover BL_SD_boardSupportSD.rom
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 8 found!
Write at 0x1065fc38
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

But after this nothing happened and afterRebooting my sansa -> same result, blue wheel lite.

So I have to restore the i2c boot rom, or not?
I have a sansa e280 must be european version, but there is no i2c file dumped for my sansa. can I use another one?

Thank you,
Lue

[Bagder]

So I have to restore the i2c boot rom, or not?

It might very well be so.

I have a sansa e280 must be european version, but there is no i2c file dumped for my sansa. can I use another one?

We don't know.

[Lue]

Thank you,

is there a big difference between the i2c file from the e260 to the e280?
If not may i could use the i2c file from the e260 eu version,or will this brick my sansa even more!?

Thank you,
Lue

[Brambo]

Lue,

I recovered my sansa e270 US with the e280 US i2c file because mine isn't on the e200tool page... so I'm not 100% sure, but for me it worked, using a i2c file that differs from my sansa type...

IF, IF you wanna try to recover with other i2c rom file, I advise you to try the EU 260 version because you also have a EU version... but use at your own risk... good luck!

[Lue]

OK ...so far so good..

I got into recovery mode direct after I use the command:  sudo ./e200tool revover xxx.rom

The Recovery mode looks like this:

Code: [Select]

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

USB cable connected 
Enter USB2.0 MSD Mode
LUN0 locked
LUN0 unlocked
LUN0 locked
LUN0 unlocked
LUN0 locked
LUN0 unlocked

when I copy the mi4 file into the device and i plug the sansa of there stands:

Safe to disconnect..

will recover....

But then there remains the blue wheel lite and a black screen....


Help!?

When I press the on button 20sec and try to get into recovery mode - no chance...

Help me please..

Lue

**Update**

When i do it like jdgordon on page 7 (..."So as soon as it starts copying the rom across disable the hold switch, then as soon as you get the sansa logo on the screen disconnect the usb cable.")

I can connect the sansa on my windows pc and I have the 16mb recovery mode partition.
When I copy the mi4 file in it and disconnect the sansa, the sansa says "write image error"

What can I do??

Help!


Update-nr2

May there is an option to install rockbox to  install the original firmware!?
I don't know what to do....

[PepeZuniga]

Hi everybody! I've just done the most stupid thing. I have a Sansa e260 and I tried to format the device. I turned off the player, put the hold and then turned on. I get the Recovery mode, and don't know why I copied the i2c.bin file into the 16MB folder that appears when you are in that mode. After this my sansa got crushed. It doesn't turn on anymore and my PC does not detect it. Can anyone help me??!!! Plz!!!

[saratoga]

Hi everybody! I've just done the most stupid thing. I have a Sansa e260 and I tried to format the device. I turned off the player, put the hold and then turned on. I get the Recovery mode, and don't know why I copied the i2c.bin file into the 16MB folder that appears when you are in that mode. After this my sansa got crushed. It doesn't turn on anymore and my PC does not detect it. Can anyone help me??!!! Plz!!!

Probably a dozen people have already done that in this thread.  Read back a few posts and do what they did to fix it.

[PepeZuniga]

Probably a dozen people have already done that in this thread.  Read back a few posts and do what they did to fix it.

Yeap, it seems to. But now I have a new problem. Now my PC sees something in the usb port but I can not make the e200tool work properly. It can't detect the device. It appears:

e200tool v0.0.6-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 ... 9 8 7 6 5 4 3 2 1 0 not found!

I've seen in previous comments that other people got the same thing, but couldn't understand what they did to fix it. If someone can help me, it will be great!

[Bagder]

Now my PC sees something in the usb port but I can not make the e200tool work properly. It can't detect the device.

So what vendor/device IDs do your computer think the "something" in the USB port has?

In what mode is your sansa when you try this?

[PepeZuniga]

Now my PC sees something in the usb port but I can not make the e200tool work properly. It can't detect the device.

So what vendor/device IDs do your computer think the "something" in the USB port has?

In what mode is your sansa when you try this?

Ok, the device ID is 0b70:0003 or at least it says so in the device maneger. How can I know in which mode is my sansa if the screen is completly blacked out. It doesn't react to anything. Thank you.