Sansa E200 Bricked by Recovery Mode

[hallgreng]

The makefile did the trick, I just suck at gcc, i guess =]

Code: [Select]

$./e200tool init
e200tool v0.0.6-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (3460 bytes) ... done!

Im thinking that what I need to do now is $./e200tool write ic2.bin, but i dont want to do another stupid thing to break my device even more due to ignorance, so if you dont mind giving me a little instruction, I would be willing to follow it.

[Bagder]

Im thinking that what I need to do now is $./e200tool write ic2.bin

No, the proper procedure should be to verify which USB mode you can use. If not the firmware's, then recovery mode, then manufacturing mode and as a last restort the pre-boot mode.

Only in the pre-boot mode should the i2c attempt be made.

Seeing that e200tool detected your device as 0781:0720, we know that it isn't  pre-boot mode!

[bob]

Here's a stupid question, have you tried this, which I found on another site:

>The 1.03.01 firmware has a sleep mode... You have to hold down the power button
>for at least 30 seconds first. Then you can go into recovery mode.

>Before any of that though, you have to rename the bootloader and firmware to
>pribootLoader.rom and firmware.mi4

And for those who may know, can the device operate (that is, accept firmware) with blank flash devices?  Which of the modes you listed would it be in?

-bob

[Bagder]

And for those who may know, can the device operate (that is, accept firmware) with blank flash devices?  Which of the modes you listed would it be in?

I don't think anyone knows this for sure, but one guess is that the pre-boot mode is provided by the PP5024 itself and if so and the i2c rom would be damaged (as a "blank flash" probably implies), you'd still reach the pre-boot usb mode.

[hallgreng]

Well youre right, it seems that I was only in manufacturing mode. Yay? I was hoping for a little more trouble

Regardless, thanks for your help. My sansa is back from the dead thanks to you and your e200tool app.
Sorry it wasnt as busted as I thought, I would have liked to have contributed in my own small way.

[Bagder]

My sansa is back from the dead thanks to you and your e200tool app.

All the glory goes to MrH for this.

[A_BIRDY]

@ Hallgreng:

Awesome that your fixed yours!


@ Everybody but especially Badger + MrH:

REALLY Awesome that you've been working on this aspect of e200tool.
It seems I made the right choice going to a dedicated firmware hacking community as opposed to sending it back to the manufacturer.


@ Really Everybody

But now I'm kinda skrewed for a bit. My computer decided to not recognize its boot disk anymore... It'll be a while before I can get this problem fixed, but when I do! I'll get that i2c.rom, and I'll compile e200tool, and I'll connect my sansa in pre-boot mode! And then maybe it'll work and maybe not. Whatever.

Anyway, the point is thanks. Thanks for anyone who posted. Thanks to MrH and Badger for making e200tool and posting it on Rockbox forums, respectively. I'll post again when I finally fix the thing with a full tutorial in case this ever happens again. Seeya!

[A_BIRDY]

GUYS!!!
EXCITING NEWS!!!

I got on my dad's laptop with the intent to fix the damn silly thing!

It is recognized by the new version of e200tool!

All I need to know now is the address at which to write i2c.bin!

MrH/Badger, where are you!



Yet another exclamation point!

Thanks again! (Wow, lots of thanking lately...)

[Bagder]

Okay, brand new page with some basic e200tool instructions:

http://daniel.haxx.se/sansa/e200tool.html

[afshin3k3]

I have some problems with E200 tool, it cannot find my device.
(I use it on win XP and I dont know whether I have to try it on linux? )

Did anyone fix his device with Manufacturing Mode?

[Bagder]

I have some problems with E200 tool, it cannot find my device.

Please be a lot more specific when reporting problems and when you describe what you've done or else we can't help you.

1. In what mode is your Sansa when you try this?

2. What does e200tool report?

3. What USB vendor and device ID is your computer claiming the connected USB device is using when you're attempting this?

Did anyone fix his device with Manufacturing Mode?

Yes

[afshin3k3]

excuse me for unclearly in my previous post.

The problem is that I think i have put something wrong( or corrupted rom file) in my device during recovery mode and the recovery mode does not work anymore.
So i wanted to try the manufacturing mode but i think the e200 tool cannot find my device.
because the only thing it shows is:

e200tool init
e200tool v0.0.6-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 ... 2 1 not found
Searching for device 0b70:0003 ... 9 8 7 ... 2 1 not found

[Bagder]

What sansa model is this?

What USB vendor and device ID is your computer claiming the connected USB device is using?

Are you sure you are in manufacturing mode when you try this?

[afshin3k3]

It is e260 (not Rhaspody)

Where can I find out what USB vendor and device ID is my computer claiming the connected USB device is using?

I'm not sure I am in manufacturing mode, I just followed the instruction.

[Bagder]

Where can I find out what USB vendor and device ID is my computer claiming the connected USB device is using?

In linux you can use 'lsusb'